The commercial product is not a room, a server, or a model in isolation. It is a sovereign operating environment: a qualified leasehold, private infrastructure, tenant-controlled software, and organization-specific intelligence delivered as one governed system. Sovereignty is the accepted operating result of custody, topology, access, ownership, and enforceable handoffs across that stack.
The Base Building Developer / Property Operator establishes the property boundary: usable voltage, power quality, fiber pathways, physical access, environmental readiness, and a documented building handoff. The Carrier / Network Provider and Infrastructure Provider establish the technical substrate through contracted connectivity, network identity, demarcation, compute, storage, backup, monitoring, and hardware support. Those roles MUST NOT access, store, or administer tenant compute workloads or data streams, and they MUST NOT receive authority over the tenant's data, policy, or organizational intelligence.
The Tenant Organization is the authority inside the boundary. It owns the workload decisions, identity model, data governance, risk acceptance, human-review policy, and the resulting organizational intelligence. The Tenant MUST retain ultimate risk authority; accountability SHALL NOT be delegated to operators. An Edge Software Integrator MAY provide local orchestration, observability, updates, policy enforcement, and operational handoffs, but MUST NOT assert ownership over tenant intelligence, vector memory, or raw telemetry. A Workflow Engineering Partner MAY discover and migrate workflows, build governed protocols and routers, establish evaluations, and commission organization-specific adaptations, but SHALL NOT claim ownership of new foundational model weights generated via tenant adaptations.
Those adaptations can include adapters, fine-tunes, retrieval assets, routing policies, evaluation sets, and related configuration. They remain tenant-owned assets subject to final contract terms and third-party licenses; a deployment does not necessarily create new foundational model weights. This ownership boundary lets capability compound without transferring the organization's intelligence to the landlord, carrier, or integration partners.
Commercial accountability is assembled through a contract stack rather than a single blanket promise: lease exhibits define the physical environment, carrier orders define connectivity, equipment schedules define infrastructure, statements of work define integration and workflow migration, acceptance records establish the governed baseline, and operating SLAs define measurable targets, escalation, remedies, and change control for each service boundary.
Commercial delivery architecture
Sovereignty is the accepted operating state produced by coordinated property, carrier, tenant, software, and workflow obligations.
Base Building Developer / Property Operator
Qualified space, electrical capacity, fiber pathway, physical security, environmental readiness
Accept with: Lease exhibit · site survey · building handoff
Carrier / Network Provider + Infrastructure Provider
Connectivity, network identity, demarcation, compute, storage, backup, monitoring
Accept with: Carrier order · commissioning record · asset register
Tenant Organization + Edge Software Integrator
Identity, policy, local orchestration, observability, updates, operational handoffs
Accept with: Access matrix · policy baseline · acceptance runbook
Workflow Engineering Partner
Workflow migration, governed protocols, routers, evaluations, and organization-specific adaptations
Accept with: Workflow map · evaluation results · release record
Tenant Organization
Workloads execute inside the declared boundary; evidence and organizational intelligence remain under tenant custody
Accept with: Operational evidence · change log · ownership schedule
Delivery lifecycle
This is a responsibility model, not a published service guarantee. Measurable targets, remedies, and exclusions belong in the applicable lease exhibits, carrier orders, statements of work, and operating SLAs. Boundary language uses RFC 2119 normative terms (MUST, MUST NOT, SHALL, SHALL NOT).
The narrative above is non-normative. The clauses below state the same architecture as testable requirements, and a conformance claim is evaluated against them rather than against the prose.
A conforming deployment MUST separate the property owner, the tenant, and the software integrator into distinct parties whose holdings do not overlap, in accordance with the Tripartite Ownership Model.
The property owner in a conforming deployment MUST NOT hold ownership of, access to, or a contingent interest in tenant compute hardware, inference data, retrieval assets, or model outputs.
The software integrator in a conforming deployment MUST NOT hold ownership of tenant data, policies, evaluations, routing logic, retrieval assets, or commissioned model adaptations.
A conforming deployment MUST provide the tenant with a documented exit under which inference capability, retrieval assets, and accumulated institutional memory remain operable after termination of any agreement with the software integrator or the property owner.
A conforming deployment MUST disclose to the tenant every third-party license, model license, and usage restriction that constrains the tenant's use of outputs produced within the enclave.
A conforming deployment MUST NOT use tenant material to train, fine-tune, evaluate, or improve any model or system made available to another party.
A Class C shell MUST disclose the ownership structure under which a future enclave would be delivered, so that a prospective tenant can evaluate the separation required by ANO-9.1 before committing.