# Own the Stack

Every layer adopted without an exit path becomes structural. Years later the question 'can we move?' has no good answer, and the cost of finding out is a rewrite.

## About this page
- Canonical: https://quarkcs.io/automation-blueprints/sovereign-enterprise-stack
- Type: AutomationBlueprint
- Published: 2026-09-06
- Updated: 2026-09-06

## Problem
Every layer adopted without an exit path becomes structural. Years later the question 'can we move?' has no good answer, and the cost of finding out is a rewrite.

## Agent Loop
- Trigger: A new capability is proposed — a model, a platform, a managed service.
- Context: Current stack, data residency obligations, licence terms, integration contracts and the organisation's own capability.
- Agent: Map the proposed component against the existing architecture and report what it would make structural.
- Policy: Any component that cannot be replaced without a rewrite requires explicit sign-off.
- Human checkpoint: Architecture review approves anything that reduces portability.
- Action: Record the decision, its exit path, and the conditions that would trigger a move.

## Tools
- read_architecture
- read_data_residency
- compare_alternatives

## Flow
1. Capability proposed
2. Map against current stack
3. Check residency and licence terms
4. Compare open alternatives
5. Approve or reject portability impact (human approval)
6. Record decision and exit path

## Systems
- Framework M
- Object storage
- Identity provider
- Kubernetes

## Framework M DocTypes
- Decision
- Component
- DataResidencyRule