ARCHITECTURE FRAMEWORK INDEX
>_ FRAMEWORKS, DEFINITIONS & ARCHITECTURAL RELATIONSHIPS
The Framework Index is the reference system behind Rack2Cloud architecture research. Each framework defines a repeatable architecture pattern, operational boundary, governance model, failure condition, or decision structure used throughout the site.
Frameworks are organized by pillar and linked through documented architectural relationships rather than topic similarity.
90 named frameworks — 89 independently documented, 1 patched into #85 (see review queue). 71 identifiers remain reserved for future publication.
>_ CORE SYSTEMS
Architecture Pillars
Five domain pillars. The canonical authority model for rack2cloud architecture doctrine.
Explore →Engineering Toolkit
Full tool inventory — diagnostic calculators and analyzers across all pillars.
Explore →Audit Services
Architecture assessments and readiness reviews for migration, cost, recovery, and zero-trust.
Explore →Infrastructure Playbooks
Field-tested failure runbooks for enterprise infrastructure recovery scenarios.
Explore →Canonical Specifications
Authoritative reference specifications for rack2cloud architecture patterns.
Explore →Framework Index
Architecture frameworks mapped by operational domain, control boundary, and documented relationship.
Explore →>_ FRAMEWORK COVERAGE
>_ MOST CONNECTED FRAMEWORKS
| Framework | Pillar | Connections |
|---|---|---|
| Migration Survivability Test | Virtualization | 6 |
| Recovery Authority Fragmentation | Data Protection | 6 |
| Recovery Design Boundary | Data Protection | 6 |
| Recoverability Gap | Data Protection | 6 |
| Capacity Illusion Index | AI Infrastructure | 5 |
| Effective GPU Yield | AI Infrastructure | 5 |
| Phantom Scarcity | AI Infrastructure | 5 |
>_ PILLAR NAVIGATION
>_ FRAMEWORK DIRECTORY
AI Infrastructure
The set of always-on infrastructure layers (serving, routing, caching, observability) that inference workloads permanently occupy once they reach…
The gradual, unbudgeted expansion of the steady-state inference footprint as models, contexts, and integrations accumulate.
The accumulated performance and cost penalty incurred when AI placement decisions defer latency until it must be bought back through architecture…
The failure mode in which an operation reports success by system metrics while the underlying objective was not actually met.
The absence of any owner with enforceable authority over AI runtime behavior as AI control planes emerge as shadow IT.
The fraction of purchased GPU capacity that produces useful work after scheduling, fragmentation, and idle losses.
A measure of how much apparent GPU capacity is illusory — provisioned and visible but not practically allocatable.
The condition in which GPU jobs queue despite idle hardware because fragmentation and scheduling make capacity unallocatable.
The simultaneous presence of job queues and idle GPUs in the same cluster.
The capacity permanently lost to allocation fragmentation across GPUs and nodes.
The economic efficiency lost when GPU infrastructure runs below its achievable workload density.
The load level at which interactive inference latency degrades far enough to break the user interaction model.
The nonlinear relationship between inference load and latency/throughput as a serving stack approaches saturation.
The compounding growth of queued token work under load — small arrival increases amplify into large queue and latency growth.
The appearance of healthy aggregate throughput while per-request latency and interactivity have already collapsed.
The shift of effective infrastructure authority into the network layer as the network becomes the AI control plane.
The delta between provisioned compute capacity and the compute that actually executes useful work.
The practical upper bound on workload density imposed by contention, scheduling, and failure-domain constraints before nominal capacity is reached.
The pattern of investing in AI capability faster than in the governance required to operate it, inverting the required order of investment.
The workload and architecture line beyond which accelerated compute is structurally required rather than optional.
The boundary defining where AI execution must be local to data and fabric for the architecture to function.
The line at which data pipeline and storage availability constrains AI training and inference execution.
The infrastructure maturity threshold required before autonomous operations can be safely delegated to machines.
The boundary defining which systems hold authority to execute workloads within AI runtime and cluster orchestration.
The line between operational states the observability layer can actually see and those structurally invisible to it.
The point at which AI observability stops being passive telemetry and becomes an enforcement and governance layer.
The chain of components that must all survive for distributed inference service to continue through failures.
The architectural line separating AI systems designed to survive component and dependency failure from those that merely assume availability.
The amount of orchestration, governance, retrieval, policy evaluation, and control-plane work required to produce a unit of AI execution. Compute…
The formal boundary within which an agentic system may delegate execution authority — constrained by explicit scope, identity, ownership, and…
The gap that opens when operational dependency on a service advances faster than the assurance mechanisms — SLA, behavioral commitments, policy…
The AI Evidence Artifact Layer is the architectural layer responsible for producing portable, attributable, verifiable execution evidence that…
Cloud Strategy
The elasticity lost when workloads move from cloud burst capacity to fixed owned capacity — a delta repatriation economics must explicitly price.
The cloud services (identity, DNS, data services, tooling) that remain in use after repatriation and keep the organization partially cloud-dependent.
The risk that capacity purchased for repatriated peak demand sits idle, stranding capital when demand shifts or forecasts miss.
The tendency to keep workloads where they already run because sunk cost and operational familiarity bias the economics against movement.
The period over which repatriation's operational investments (staff, tooling, facilities) must amortize before the move nets positive.
A model defining where sovereignty control must actually be enforced — control plane, data plane, jurisdiction — before sovereignty architecture…
The total set of interfaces (consoles, CLIs, APIs, browsers) through which infrastructure can be changed and which therefore must be governed.
The portion of governance capability that does not transfer when moving between operating models, such as public cloud to private cloud.
The period after an operating-model change during which operations stabilize into a repeatable norm — and during which operational risk is elevated.
The period during which a cloud exit remains executable at acceptable cost — a window that closes as dependency accumulates.
The point at which sovereign or jurisdictional policy must translate into enforceable control-plane configuration — where most sovereign AI designs…
The accumulation of operational authority by a single vendor or platform control plane until alternatives become impractical.
The line between cloud dependencies an organization has explicitly mapped and those it discovers only at failure or exit time.
The boundary defining who and what holds authority to move workloads and data between environments.
The point at which architecture choices multiply egress volume and cost beyond linear expectations.
The point at which incremental cloud cost optimization is exhausted and only workload refactoring produces further savings — at step-function cost.
The point at which accumulated economic factors (egress, licensing, commitments) constrain architectural movement like gravity.
The requirement that every sovereignty claim — jurisdictional, key-custody, operational, supply-chain — be backed by a verifiable chain of…
The point at which control-plane authority must be explicitly owned; where ownership of enforcement authority is undefined, multiple systems can…
The point at which authority defined through ownership models, policies, and governance structures must translate into executable operational…
The point at which authority transitions from being operationally effective to being organizationally legitimate. Below the boundary: authority can…
The point at which systems must continue operating despite the loss, compromise, unavailability, or removal of the authorities that normally govern…
The point at which a decision affects multiple cloud environments and no single authority can execute, govern, or recover that decision without…
The point at which an economic evaluation mechanism has already filtered the set of architectural options an architect will be shown, before any…
Virtualization
The condition in which a multi-hypervisor or VMware-coexistence estate splits operational authority across multiple management planes, leaving no…
The line separating storage architectures that survive component, node, and site failure with defined behavior from those whose survival is assumed.
The performance range within which a system remains viable during degraded and failure conditions, not just steady state.
The forward window within which platform lifecycle decisions (upgrades, support, licensing) remain governed; beyond it, lifecycle debt accumulates…
The delta between the governance, authority, policy enforcement, and operational context implicitly provided by a source platform and the explicit…
The point at which a platform accumulates enough operational authority, behavioral assumptions, and integration gravity that its true dependency…
The property of a migrated environment that determines whether it can absorb its first real production incident using only the operating model,…
Modern Infrastructure & IaC
A classification of where IaC drift originates (console changes, emergency fixes, automation side effects) so drift is designed for detection rather…
The distance between documented multi-cloud failover designs and failovers that could plausibly execute under real failure conditions.
The line between operational knowledge captured in systems (recoverable) and knowledge held only in people or ephemeral runtime (lost) —…
The point at which declared infrastructure intent and enforced infrastructure behavior diverge because ownership of reconciliation was never…
A six-level progression model describing the maturity states through which infrastructure automation evolves: Level 0 Manual Infrastructure → Level…
The principle that every automation system eventually costs more to maintain than it saves unless governance scales with complexity. The curve…
The principle that infrastructure state accumulates faster than architecture evolves. State, once created, exerts gravitational pull on every…
The Infrastructure Evidence Gap is the structural absence of a chain-of-custody record linking an infrastructure change's approved intent to its…
The structural absence of a defined path back from an authorized configuration exception to a governed, IaC-tracked state. Four variables govern…
Data Protection
The bounded set of failure conditions an architecture is explicitly designed to survive; outside the envelope, behavior is undefined rather than…
The distance between having data replicated cross-region and being able to actually recover service from it.
The interval during which replication faithfully propagates corruption or ransomware to all copies before detection.
The failure to account for the dependencies (identity, DNS, configuration, services) a replicated workload needs to actually run in the recovery…
The complete set of state — beyond data — that must exist for a recovered workload to function; the true recovery target.
The line between DR tests that validate actual recovery and tests that validate only the test procedure.
The structural condition in which recovery fails because the recovery system's own dependencies sit inside the failure blast radius.
The progression by which undocumented recovery dependencies compound in complexity until the recovery plan can no longer be executed in sequence…
Recovery authority becomes fragmented when the people, systems, credentials, approvals, and operational knowledge required to execute recovery do not…
The line between systems whose recovery characteristics have been intentionally designed and systems whose recovery behavior is only discovered…
The Recovery Execution Boundary is the point at which a designed recovery topology encounters the operational capabilities and authority model of the…
The recoverability gap is the distance between a recovery plan validated under clean-failure scenarios and a recovery architecture that survives…
The point at which recovery isolation continues to function after identity, management-plane, and control-plane compromise. Architectures cross the…
The period between successful data recovery and verified operational recovery. The larger the gap, the greater the difference between protection…
A recovery process is deterministic when the same failure condition produces the same recovery outcome within a bounded variance envelope.…
The point at which identity — not network topology, VLANs, or perimeter control — becomes the boundary that actually determines whether a change,…
>_ RELATIONSHIP EXPLORER
-
#3 Inference Residency Creep
— Moderate strength
Both frameworks are named in the same anchor post — Persistent Inference Residency Stack is the steady-state footprint; Inference Residency Creep is its unbudgeted growth.
-
#2 Persistent Inference Residency Stack
— Moderate strength
Both frameworks are named in the same anchor post — Persistent Inference Residency Stack is the steady-state footprint; Inference Residency Creep is its unbudgeted growth.
-
#77 Cloud Dependency Residue
— Moderate strength
Both are named in the same Repatriation Economics anchor post as distinct cost variables in the same calculation.
-
#78 Stranded Capacity Risk
— Moderate strength
Both are named in the same Repatriation Economics anchor post as distinct cost variables in the same calculation.
-
#79 Economic Persistence Bias
— Moderate strength
Both are named in the same Repatriation Economics anchor post as distinct cost variables in the same calculation.
-
#80 Operational Amortization Window
— Moderate strength
Both are named in the same Repatriation Economics anchor post as distinct cost variables in the same calculation.
-
#76 Repatriation Elasticity Gap
— Moderate strength
Both are named in the same Repatriation Economics anchor post as distinct cost variables in the same calculation.
-
#78 Stranded Capacity Risk
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#79 Economic Persistence Bias
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#80 Operational Amortization Window
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#76 Repatriation Elasticity Gap
— Moderate strength
Both are named in the same Repatriation Economics anchor post as distinct cost variables in the same calculation.
-
#77 Cloud Dependency Residue
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#79 Economic Persistence Bias
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#80 Operational Amortization Window
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#76 Repatriation Elasticity Gap
— Moderate strength
Both are named in the same Repatriation Economics anchor post as distinct cost variables in the same calculation.
-
#77 Cloud Dependency Residue
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#78 Stranded Capacity Risk
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#80 Operational Amortization Window
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#76 Repatriation Elasticity Gap
— Moderate strength
Both are named in the same Repatriation Economics anchor post as distinct cost variables in the same calculation.
-
#77 Cloud Dependency Residue
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#78 Stranded Capacity Risk
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#79 Economic Persistence Bias
— Moderate strength
Co-resident in the same Repatriation Economics anchor post.
-
#82 False Completion
— Moderate strength
Both named in the same AI Placement Latency/Cost post — Latency Debt is the accrued cost; False Completion is the metric failure that hides it.
-
#81 Latency Debt
— Moderate strength
Both named in the same AI Placement Latency/Cost post — Latency Debt is the accrued cost; False Completion is the metric failure that hides it.
-
#87 Operational Normalization Window
— Moderate strength
Both named in the same Private Cloud Operating Model post — Governance Portability Gap is what doesn't transfer; Operational Normalization Window is the stabilization period after the move.
-
#86 Governance Portability Gap
— Moderate strength
Both named in the same Private Cloud Operating Model post — Governance Portability Gap is what doesn't transfer; Operational Normalization Window is the stabilization period after the move.
-
#90 Capacity Illusion Index
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Effective GPU Yield and Capacity Illusion Index are paired output metrics.
-
#91 Phantom Scarcity
— Moderate strength
Co-resident in the GPU Utilization Analyzer — low yield and Phantom Scarcity describe the same underlying allocation failure.
-
#92 Queue–Idle Paradox
— Moderate strength
Co-resident in the GPU Utilization Analyzer — yield loss and the Queue-Idle Paradox are the same symptom measured two ways.
-
#93 Fragmentation Tax
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Fragmentation Tax is the primary cause of reduced Effective GPU Yield.
-
#94 Economic Density Loss
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Economic Density Loss is the dollar expression of reduced yield.
-
#89 Effective GPU Yield
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Effective GPU Yield and Capacity Illusion Index are paired output metrics.
-
#91 Phantom Scarcity
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Capacity Illusion Index quantifies Phantom Scarcity.
-
#92 Queue–Idle Paradox
— Moderate strength
Co-resident in the GPU Utilization Analyzer as paired capacity-illusion metrics.
-
#93 Fragmentation Tax
— Moderate strength
Co-resident in the GPU Utilization Analyzer — fragmentation is the mechanism behind the capacity illusion.
-
#94 Economic Density Loss
— Moderate strength
Co-resident in the GPU Utilization Analyzer as paired capacity/economic metrics.
-
#89 Effective GPU Yield
— Moderate strength
Co-resident in the GPU Utilization Analyzer — low yield and Phantom Scarcity describe the same underlying allocation failure.
-
#90 Capacity Illusion Index
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Capacity Illusion Index quantifies Phantom Scarcity.
-
#92 Queue–Idle Paradox
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Phantom Scarcity and the Queue-Idle Paradox describe the same allocation failure from different angles.
-
#93 Fragmentation Tax
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Fragmentation Tax is the direct cause of Phantom Scarcity.
-
#94 Economic Density Loss
— Moderate strength
Co-resident in the GPU Utilization Analyzer as paired scarcity/loss metrics.
-
#89 Effective GPU Yield
— Moderate strength
Co-resident in the GPU Utilization Analyzer — yield loss and the Queue-Idle Paradox are the same symptom measured two ways.
-
#90 Capacity Illusion Index
— Moderate strength
Co-resident in the GPU Utilization Analyzer as paired capacity-illusion metrics.
-
#91 Phantom Scarcity
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Phantom Scarcity and the Queue-Idle Paradox describe the same allocation failure from different angles.
-
#93 Fragmentation Tax
— Moderate strength
Co-resident in the GPU Utilization Analyzer — fragmentation produces the Queue-Idle Paradox.
-
#94 Economic Density Loss
— Moderate strength
Co-resident in the GPU Utilization Analyzer as paired paradox/loss metrics.
-
#89 Effective GPU Yield
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Fragmentation Tax is the primary cause of reduced Effective GPU Yield.
-
#90 Capacity Illusion Index
— Moderate strength
Co-resident in the GPU Utilization Analyzer — fragmentation is the mechanism behind the capacity illusion.
-
#91 Phantom Scarcity
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Fragmentation Tax is the direct cause of Phantom Scarcity.
-
#92 Queue–Idle Paradox
— Moderate strength
Co-resident in the GPU Utilization Analyzer — fragmentation produces the Queue-Idle Paradox.
-
#94 Economic Density Loss
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Fragmentation Tax is the mechanism; Economic Density Loss is its cost.
-
#89 Effective GPU Yield
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Economic Density Loss is the dollar expression of reduced yield.
-
#90 Capacity Illusion Index
— Moderate strength
Co-resident in the GPU Utilization Analyzer as paired capacity/economic metrics.
-
#91 Phantom Scarcity
— Moderate strength
Co-resident in the GPU Utilization Analyzer as paired scarcity/loss metrics.
-
#92 Queue–Idle Paradox
— Moderate strength
Co-resident in the GPU Utilization Analyzer as paired paradox/loss metrics.
-
#93 Fragmentation Tax
— Moderate strength
Co-resident in the GPU Utilization Analyzer — Fragmentation Tax is the mechanism; Economic Density Loss is its cost.
-
#96 Inference Saturation Curve
— Moderate strength
Co-resident in the AI Inference Saturation Analyzer — the Interaction Collapse Point sits on the Inference Saturation Curve.
-
#97 Token Queue Amplification
— Moderate strength
Co-resident in the Saturation Analyzer — Token Queue Amplification is the mechanism driving toward Interaction Collapse.
-
#98 Throughput Illusion
— Moderate strength
Co-resident in the Saturation Analyzer — Throughput Illusion masks the approach to Interaction Collapse.
-
#95 Interaction Collapse Point
— Moderate strength
Co-resident in the AI Inference Saturation Analyzer — the Interaction Collapse Point sits on the Inference Saturation Curve.
-
#97 Token Queue Amplification
— Moderate strength
Co-resident in the Saturation Analyzer — queue amplification is the mechanism shaping the saturation curve.
-
#98 Throughput Illusion
— Moderate strength
Co-resident in the Saturation Analyzer as paired curve/illusion metrics.
-
#95 Interaction Collapse Point
— Moderate strength
Co-resident in the Saturation Analyzer — Token Queue Amplification is the mechanism driving toward Interaction Collapse.
-
#96 Inference Saturation Curve
— Moderate strength
Co-resident in the Saturation Analyzer — queue amplification is the mechanism shaping the saturation curve.
-
#98 Throughput Illusion
— Moderate strength
Co-resident in the Saturation Analyzer — queue amplification is masked by the throughput illusion until it isn't.
-
#95 Interaction Collapse Point
— Moderate strength
Co-resident in the Saturation Analyzer — Throughput Illusion masks the approach to Interaction Collapse.
-
#96 Inference Saturation Curve
— Moderate strength
Co-resident in the Saturation Analyzer as paired curve/illusion metrics.
-
#97 Token Queue Amplification
— Moderate strength
Co-resident in the Saturation Analyzer — queue amplification is masked by the throughput illusion until it isn't.
-
#100 Corruption Propagation Window
— Moderate strength
Co-resident in the Cross-Region Replication post — the Replication-Recovery Gap is the structural condition; Corruption Propagation Window is its time-bound failure mode.
-
#101 Dependency Recovery Blindness
— Moderate strength
Co-resident in the Cross-Region Replication post — Dependency Recovery Blindness is a specific instance of the Replication-Recovery Gap.
-
#102 Recovery State
— Moderate strength
Co-resident in the Cross-Region Replication post — Recovery State is the target the Replication-Recovery Gap fails to close.
-
#99 The Replication–Recovery Gap
— Moderate strength
Co-resident in the Cross-Region Replication post — the Replication-Recovery Gap is the structural condition; Corruption Propagation Window is its time-bound failure mode.
-
#101 Dependency Recovery Blindness
— Moderate strength
Co-resident in the Cross-Region Replication post as paired failure-window/blindness conditions.
-
#102 Recovery State
— Moderate strength
Co-resident in the Cross-Region Replication post — corruption propagation is a threat to reaching Recovery State.
-
#99 The Replication–Recovery Gap
— Moderate strength
Co-resident in the Cross-Region Replication post — Dependency Recovery Blindness is a specific instance of the Replication-Recovery Gap.
-
#100 Corruption Propagation Window
— Moderate strength
Co-resident in the Cross-Region Replication post as paired failure-window/blindness conditions.
-
#102 Recovery State
— Moderate strength
Co-resident in the Cross-Region Replication post — Dependency Recovery Blindness is precisely what keeps Recovery State out of reach.
-
#99 The Replication–Recovery Gap
— Moderate strength
Co-resident in the Cross-Region Replication post — Recovery State is the target the Replication-Recovery Gap fails to close.
-
#100 Corruption Propagation Window
— Moderate strength
Co-resident in the Cross-Region Replication post — corruption propagation is a threat to reaching Recovery State.
-
#101 Dependency Recovery Blindness
— Moderate strength
Co-resident in the Cross-Region Replication post — Dependency Recovery Blindness is precisely what keeps Recovery State out of reach.
-
#106 The Density Ceiling
— Moderate strength
Co-resident in the Modern Virtualization Compute Architecture LP page — the Provisioned-to-Executed Gap is bounded above by the Density Ceiling.
-
#105 Provisioned-to-Executed Gap
— Moderate strength
Co-resident in the Modern Virtualization Compute Architecture LP page — the Provisioned-to-Executed Gap is bounded above by the Density Ceiling.
-
#133 Policy Intent Drift
— Moderate strength
Coordination Density is the upstream cause; Policy Intent Drift is a named downstream consequence of rising coordination overhead.
-
#134 Sovereignty Evidence Chain
— Moderate strength
Coordination Density is the upstream cause; Sovereignty Evidence Chain is a named downstream consequence of rising coordination overhead.
-
#135 Control Plane Ownership Boundary
— Moderate strength
Coordination Density is the upstream cause; Control Plane Ownership Boundary is a named downstream consequence of rising coordination overhead.
-
#133 Policy Intent Drift
— Moderate strength
Coordination Density is the upstream cause; Policy Intent Drift is a named downstream consequence of rising coordination overhead.
-
#134 Sovereignty Evidence Chain
— Moderate strength
Coordination Density is the upstream cause; Sovereignty Evidence Chain is a named downstream consequence of rising coordination overhead.
-
#135 Control Plane Ownership Boundary
— Moderate strength
Coordination Density is the upstream cause; Control Plane Ownership Boundary is a named downstream consequence of rising coordination overhead.
-
#132 Coordination Density
— Strong strength
Policy Intent Drift traces its reconciliation-ownership failure directly back to rising coordination/orchestration overhead.
-
#134 Sovereignty Evidence Chain
— Moderate strength
Downstream siblings of #132 — both trace rising coordination overhead to a boundary failure, one in infrastructure execution, one in sovereignty evidence.
-
#135 Control Plane Ownership Boundary
— Moderate strength
Same-parent siblings: #135 addresses ownership authority at the strategic/organizational layer; #133 applies the identical boundary question to infrastructure execution and reconciliation.
-
#132 Coordination Density
— Strong strength
Policy Intent Drift traces its reconciliation-ownership failure directly back to rising coordination/orchestration overhead.
-
#134 Sovereignty Evidence Chain
— Moderate strength
Downstream siblings of #132 — both trace rising coordination overhead to a boundary failure, one in infrastructure execution, one in sovereignty evidence.
-
#135 Control Plane Ownership Boundary
— Moderate strength
Same-parent siblings: #135 addresses ownership authority at the strategic/organizational layer; #133 applies the identical boundary question to infrastructure execution and reconciliation.
-
#129 Operational Memory Boundary
— Strong strength
Sovereignty Evidence Chain is the direct successor to Operational Memory Boundary — sovereignty is a provenance question ('how do you know') applied to control-plane authority.
-
#132 Coordination Density
— Moderate strength
Coordination Density is an amplifier, not a prerequisite: rising coordination density raises the stakes of an unevidenced sovereignty link, but the Evidence Chain holds even at low coordination density.
-
#129 Operational Memory Boundary
— Strong strength
Sovereignty Evidence Chain is the direct successor to Operational Memory Boundary — sovereignty is a provenance question ('how do you know') applied to control-plane authority.
-
#132 Coordination Density
— Moderate strength
Coordination Density is an amplifier, not a prerequisite: rising coordination density raises the stakes of an unevidenced sovereignty link, but the Evidence Chain holds even at low coordination density.
-
#132 Coordination Density
— Strong strength
Control Plane Ownership Boundary traces its authority-ambiguity failure back to rising coordination/orchestration overhead, the same root #133 and #134 share.
-
#132 Coordination Density
— Strong strength
Control Plane Ownership Boundary traces its authority-ambiguity failure back to rising coordination/orchestration overhead, the same root #133 and #134 share.
-
#122 Recovery Dependency Collapse
— Strong strength
Recovery Dependency Spiral is the operational mechanism (dependency cascade during plan execution) beneath the structural collapse condition Recovery Dependency Collapse describes.
-
#112 Lifecycle Governance Horizon
— Moderate strength
Operating Model Transfer Gap pairs with Lifecycle Governance Horizon — governance debt accumulates before migration, then fails to transfer during it.
-
#115 Control Plane Capture
— Moderate strength
Pairs with Control Plane Capture — authority accumulation is the pattern that makes the operating-model gap invisible until incident time.
-
#115 Control Plane Capture
— Moderate strength
Pairs with Control Plane Capture — authority accumulation is the pattern that makes the operating-model gap invisible until incident time.
-
#138 Infrastructure Automation Ladder
— Strong strength
Automation Debt Curve is the economic consequence of the maturity position Infrastructure Automation Ladder measures — Ladder is where you are, Debt Curve is what staying there costs.
-
#115 Control Plane Capture
— Moderate strength
Cross-pillar reuse: agentic tool-chain authority failures follow the same structural pattern as Shadow Control Plane in infrastructure.
-
#85 Runtime Authority Vacuum
— Moderate strength
Execution without ownership (#85) is the precondition Agentic Authority Boundary names more precisely for agentic delegation.
-
#129 Operational Memory Boundary
— Moderate strength
Forward dependency: evidence-grade execution records connect to Operational Memory Boundary — Authority Chain Opacity is the agentic expression of the same memory gap.
-
#132 Coordination Density
— Moderate strength
Higher coordination density amplifies the blast radius of agentic authority boundary failures.
-
#115 Control Plane Capture
— Moderate strength
Cross-pillar reuse: agentic tool-chain authority failures follow the same structural pattern as Shadow Control Plane in infrastructure.
-
#129 Operational Memory Boundary
— Moderate strength
Forward dependency: evidence-grade execution records connect to Operational Memory Boundary — Authority Chain Opacity is the agentic expression of the same memory gap.
-
#121 Observability Authority Boundary
— Moderate strength
Behavioral dependency failures require AI Observability Governance instrumentation to actually detect them.
-
#129 Operational Memory Boundary
— Moderate strength
Forward dependency: 'what changed when a workflow breaks' is an Operational Memory Boundary question applied to vendor behavior.
-
#141 Agentic Authority Boundary
— Moderate strength
Authority gap in agentic deployments connects directly to the assurance gap the vendor lacks a contractual mechanism to close.
-
#129 Operational Memory Boundary
— Moderate strength
Forward dependency: 'what changed when a workflow breaks' is an Operational Memory Boundary question applied to vendor behavior.
-
#112 Lifecycle Governance Horizon
— Strong strength
Doctrine chain: Lifecycle Governance Horizon (governance debt accumulates) precedes Dependency Visibility Boundary in the VMware exit sequence.
-
#137 Operating Model Transfer Gap
— Strong strength
Doctrine chain: Operating Model Transfer Gap (governance doesn't migrate) precedes Dependency Visibility Boundary (can't see what you depend on).
-
#122 Recovery Dependency Collapse
— Moderate strength
Forward dependency: unmapped recovery dependencies surface as Recovery Dependency Collapse once visibility is lost.
-
#122 Recovery Dependency Collapse
— Moderate strength
Forward dependency: unmapped recovery dependencies surface as Recovery Dependency Collapse once visibility is lost.
-
#112 Lifecycle Governance Horizon
— Strong strength
Series opener: Lifecycle Governance Horizon starts the VMware Exit Architecture doctrine chain that Migration Survivability Test closes.
-
#137 Operating Model Transfer Gap
— Strong strength
Series middle: Operating Model Transfer Gap identifies what fails to transfer; Migration Survivability Test measures whether the gap survives a real incident.
-
#143 Dependency Visibility Boundary
— Strong strength
Series middle: Dependency Visibility Boundary identifies what can't be seen; Migration Survivability Test is where the blind spot gets tested for real.
-
#122 Recovery Dependency Collapse
— Moderate strength
Forward dependency: the recovery primitive failure exposed by the first incident on the new platform is Recovery Dependency Collapse in migration form.
-
#129 Operational Memory Boundary
— Moderate strength
Institutional knowledge that never transferred during migration surfaces as Operational Memory Boundary failure under incident pressure.
-
#144 Recovery Authority Fragmentation
— Moderate strength
Authority gaps surface when an incident spans old and new platform simultaneously — the personnel-authority half of the same series closer.
-
#122 Recovery Dependency Collapse
— Moderate strength
Forward dependency: the recovery primitive failure exposed by the first incident on the new platform is Recovery Dependency Collapse in migration form.
-
#129 Operational Memory Boundary
— Moderate strength
Institutional knowledge that never transferred during migration surfaces as Operational Memory Boundary failure under incident pressure.
-
#144 Recovery Authority Fragmentation
— Moderate strength
Authority gaps surface when an incident spans old and new platform simultaneously — the personnel-authority half of the same series closer.
-
#122 Recovery Dependency Collapse
— Moderate strength
Pairs with Recovery Dependency Collapse on blast-radius design — both are D1-adjacent design questions.
-
#144 Recovery Authority Fragmentation
— Moderate strength
Pairs with Recovery Authority Fragmentation on authority-ownership design — both are D1-adjacent design questions.
-
#146 Recovery Design Boundary
— Strong strength
Direct successor: D2 Recovery Platform Architecture assumes the Recovery Design Boundary #146 validates has already been crossed.
-
#144 Recovery Authority Fragmentation
— Moderate strength
Distinguishes from Recovery Authority Fragmentation: #144 is a human/organizational authority failure; #147's failure state is a platform/control-plane failure. The two compound in practice.
-
#146 Recovery Design Boundary
— Strong strength
Forward dependency: D4 Ransomware Survival Architecture assumes D1 backup validation from Recovery Design Boundary is already complete.
-
#147 Recovery Execution Boundary
— Strong strength
Forward dependency: D4 assumes D2 platform-authority validation from Recovery Execution Boundary is already complete.
-
#144 Recovery Authority Fragmentation
— Moderate strength
Distinguishes from Recovery Authority Fragmentation: #144 evaluates personnel-centric authority against general DR scenarios; #148 evaluates infrastructure authority under ransomware-class compromise specifically. The two compound in practice.
-
#134 Sovereignty Evidence Chain
— Strong strength
Doctrinal chain second link: Sovereignty Evidence Chain establishes jurisdictional proof; AI Evidence Artifact Layer is the AI-execution-proof instance of the same evidence principle.
-
#121 Observability Authority Boundary
— Moderate strength
Distinguishes from Observability Authority Boundary: #121 is observability becoming an enforcement layer; #149 is whether observability produces artifacts that satisfy external proof at all. An org can cross #121 and still fail #149.
-
#129 Operational Memory Boundary
— Moderate strength
Doctrinal chain first link: Operational Memory Boundary states the memory requirement that AI Evidence Artifact Layer must satisfy at execution time.
-
#134 Sovereignty Evidence Chain
— Strong strength
Doctrinal chain second link: Sovereignty Evidence Chain establishes jurisdictional proof; AI Evidence Artifact Layer is the AI-execution-proof instance of the same evidence principle.
-
#129 Operational Memory Boundary
— Moderate strength
Doctrinal chain first link: Operational Memory Boundary states the memory requirement that AI Evidence Artifact Layer must satisfy at execution time.
-
#147 Recovery Execution Boundary
— Strong strength
Direct successor: D3 Cyber Vault Architecture assumes the execution layer Recovery Execution Boundary validates is already trustworthy.
-
#148 Recoverability Gap
— Moderate strength
Distinguishes from Recoverability Gap: #148 evaluates full adversarial survival across five ransomware threat types (D4); #150 evaluates whether the isolation mechanism itself survives credential/management-plane compromise. The two compound.
-
#133 Policy Intent Drift
— Strong strength
Upstream dependency: policy state must be governed (Policy Intent Drift) before it can be snapshotted into an evidence artifact.
-
#135 Control Plane Ownership Boundary
— Strong strength
Upstream dependency: authorization identity requires a defined ownership model (Control Plane Ownership Boundary) before evidence can attribute it.
-
#149 AI Evidence Artifact Layer
— Moderate strength
Doctrinal parallel: #149 addresses execution proof in AI runtime systems; #151 addresses the identical architectural principle in IaC pipeline systems.
-
#135 Control Plane Ownership Boundary
— Strong strength
Upstream dependency: authorization identity requires a defined ownership model (Control Plane Ownership Boundary) before evidence can attribute it.
-
#149 AI Evidence Artifact Layer
— Moderate strength
Doctrinal parallel: #149 addresses execution proof in AI runtime systems; #151 addresses the identical architectural principle in IaC pipeline systems.
-
#135 Control Plane Ownership Boundary
— Strong strength
Direct successor: #135 identifies where authority resides; Operational Authority Boundary evaluates whether that authority actually reaches the execution plane.
-
#146 Recovery Design Boundary
— Strong strength
Direct successor: #146 defines the designed/assumed line; Restore Design Gap names and measures the gap when only data recovery (layer 1) is designed and layers 2–5 are assumed.
-
#122 Recovery Dependency Collapse
— Moderate strength
Pairs with Recovery Dependency Collapse (blast radius — what fails together) as a D1-adjacent Data Protection design concern.
-
#144 Recovery Authority Fragmentation
— Moderate strength
Pairs with Recovery Authority Fragmentation (who owns recovery authority) as a D1-adjacent design concern.
-
#152 Operational Authority Boundary
— Strong strength
Direct successor: #152 evaluates whether authority reaches the execution plane; Governance Legitimacy Boundary evaluates whether that authority is organizationally legitimate.
-
#134 Sovereignty Evidence Chain
— Moderate strength
Cross-pillar reference (not redefinition) — same treatment CS4 gave #132: Sovereignty Evidence Chain is cited by Governance Legitimacy Boundary without being restated.
-
#107 Governance Investment Inversion
— Strong strength
AIGA builds directly on Governance Investment Inversion (D1 domain) as one of its four anchor frameworks.
-
#118 Autonomous Operations Readiness
— Strong strength
AIGA builds directly on Autonomous Operations Readiness (D4 domain) as one of its four anchor frameworks.
-
#121 Observability Authority Boundary
— Strong strength
AIGA builds directly on Observability Authority Boundary (D6 domain) as one of its four anchor frameworks.
-
#85 Runtime Authority Vacuum
— Strong strength
AIGA builds directly on Runtime Authority Vacuum (D5 domain) as one of its four anchor frameworks.
-
#154 Governance Legitimacy Boundary
— Strong strength
Direct successor: #154 evaluates whether authority is organizationally legitimate under normal conditions; Authority Survivability Boundary evaluates whether the architecture survives when that authority disappears entirely.
-
#157 Cross-Cloud Ownership Boundary
— Moderate strength
Supporting framework: Cross-Cloud Ownership Boundary addresses multi-cloud authority-span scenarios as one input into survivability, not as the CS7 stage anchor itself.
-
#156 Authority Survivability Boundary
— Moderate strength
Feeds CS7 Strategic Resilience as Cluster 04 (Cross-Cloud Survivability) — sole placement, not a redefinition of the stage anchor.
-
#146 Recovery Design Boundary
— Strong strength
Third in the D1–D3 progression: #146 asks whether a recovery path is designed at all; Deterministic Recovery Model asks whether that path produces a repeatable outcome.
-
#147 Recovery Execution Boundary
— Strong strength
Third in the D1–D3 progression: #147 asks whether the platform can execute the path under failure; Deterministic Recovery Model asks whether execution is repeatable.
-
#144 Recovery Authority Fragmentation
— Moderate strength
Pairs with Recovery Authority Fragmentation on the Authority variable — personnel/credential lens on the same determinism question.
-
#148 Recoverability Gap
— Moderate strength
Pairs with Recoverability Gap — adversarial compromise is a variance amplifier across all four determinism variables simultaneously.
-
#153 Restore Design Gap
— Moderate strength
Differentiates from Restore Design Gap: #153 describes the undesigned space between technical and operational recovery; #158's Validation variable prescribes the invariant that closes that space.
-
#4 Drift Origin Model
— Strong strength
Lineage origin: Drift Origin Model established that drift has traceable origins — the first link in the four-framework configuration-governance chain #159 closes.
-
#133 Policy Intent Drift
— Strong strength
Lineage middle: Policy Intent Drift showed declared and enforced policy diverge even in automated systems — the second link #159 collides with at incident time.
-
#151 Infrastructure Evidence Gap
— Strong strength
Lineage middle: Infrastructure Evidence Gap established a pipeline can execute successfully while losing the authorization chain — the third link #159 collides with at incident time.
-
#148 Recoverability Gap
— Moderate strength
Closing framework of the Evidence Gap series: Recoverability Gap (Part 1) established the evidence-gap pattern in recovery that Identity Boundary Inversion generalizes.
-
#154 Governance Legitimacy Boundary
— Moderate strength
Referenced without redefinition by Governance Legitimacy Boundary (CS6) — same treatment CS6 gave #134.
-
#154 Governance Legitimacy Boundary
— Moderate strength
Referenced without redefinition by Governance Legitimacy Boundary (CS6) — same treatment CS6 gave #134.
-
#131 Economic Gravity Boundary
— Moderate strength
Explicitly differentiated: #131 asks whether economics constrains architectural outcomes already on the table; #161 asks whether an economic mechanism already decided which outcomes would be on the table at all.