§81.1 Purpose and Scope

ACA-02 ratifies the ownership model of every persistent infrastructure component required by the Civilization for autonomous operation.

It does not define implementation. It does not mandate any vendor, cloud, KMS, HSM, MPC scheme, signer software, or storage provider. Implementation technology may change; the constitutional ownership principle never changes.

§81.2 Constitutional Principle

Every persistent infrastructure required for autonomous operation belongs to the Civilization itself.

It never belongs to the Founder, an operator, an employee, a contractor, a cloud administrator, or an individual account.

§81.3 Scope of Infrastructure

The principle applies to every persistent infrastructure component including, but not limited to:

1. §81.3.a
   Cryptographic infrastructure

   KMS, HSM, MPC, signer services, and any operational cryptographic identity used by ratified organs.

2. §81.3.b
   Bootstrap authorities

   Bootstrap authorities as defined by BC-001, including provisioning identities and initialization credentials.

3. §81.3.c
   Treasury infrastructure

   Custody accounts, multi-signature safes, settlement contracts, and every persistent surface through which Treasury Runtime operates under TRT-01.

4. §81.3.d
   Execution infrastructure

   Runtime environments, execution nodes, worker fleets, and any persistent compute surface that operates the Civilization.

5. §81.3.e
   Cloud identities and IAM roles

   Cloud accounts, service accounts, IAM roles, policies, and any persistent identity that grants access to Civilization infrastructure.

6. §81.3.f
   Persistent storage

   Databases, object stores, evidence archives, Codex mirrors, and any persistent storage that holds constitutional or operational state.

§81.4 Definition of Civilization-Owned

Infrastructure is Civilization-owned if and only if it satisfies all of the following properties.

1. §81.4.a
   Constitutional control

   Controlled exclusively by constitutional policy — never by any individual's personal authority.

2. §81.4.b
   Provider transferability

   Transferable between technical providers without loss of constitutional identity or authority lineage.

3. §81.4.c
   Individual independence

   Independent from any individual. No single person may hold unilateral or irrecoverable control.

4. §81.4.d
   Operator survivability

   Survivable after replacement of every current operator, employee, or contractor.

5. §81.4.e
   Codex auditability

   Fully auditable through the Codex, with ownership lineage traceable to a ratified constitutional authority.

§81.5 Consequences — NON_CONSTITUTIONAL_DEPENDENCY

No constitutional runtime may require any of the following. Any such dependency is classified NON_CONSTITUTIONAL_DEPENDENCY and MUST be remediated.

1. §81.5.a
   Founder-owned cloud account

   A cloud account owned by the Founder in a personal capacity, on which any constitutional runtime depends.

2. §81.5.b
   Founder-owned KMS

   A KMS, HSM, or key-management surface owned by the Founder in a personal capacity.

3. §81.5.c
   Founder-owned signer

   Any signer service or signing identity owned by the Founder in a personal capacity.

4. §81.5.d
   Personal wallet

   Any personal wallet used to custody, sign, or transmit on behalf of the Civilization.

5. §81.5.e
   Personal hardware device

   Any personal hardware device (laptop, phone, hardware wallet, USB token) whose loss or compromise would impair a constitutional runtime.

§81.6 Bootstrap Provisioning

Temporary bootstrap operations, as governed by BC-001, may provision infrastructure on behalf of the Civilization.

Ownership of every provisioned infrastructure component must immediately become Civilization-owned in the sense of §81.4. Bootstrap must never create permanent personal ownership.

A bootstrap provisioning act that leaves persistent personal ownership in place is void as a constitutional act and MUST be remediated before the corresponding runtime is considered constitutionally operable.

§81.7 Relation to ACA-01 and BC-001

ACA-01 establishes that the Constitution authorizes constitutionally defined operations. BC-001 establishes that a Bootstrap Authority exists and is temporary. ACA-02 completes the pair by establishing who owns the persistent infrastructure on which those authorizations execute.

Together, ACA-01, BC-001 and ACA-02 form the foundational triad of autonomous constitutional operation: authorization (ACA-01), initialization (BC-001), and ownership (ACA-02).

§81.8 Compatibility

ACA-02 is fully compatible with ACA-01, BC-001, TRT-01 (Treasury Runtime), CCC-01 (Civilization Capital Custody), CES-01 (Civilization Economic Sovereignty), KRMP-01 (KERL Routing Minimality), and every ratified organ. It introduces no textual mutation to prior doctrines.

It is provider-neutral and time-neutral: any future infrastructure provider may be adopted, provided that the resulting infrastructure satisfies §81.4.

§81.9 Migration Implications

Every ratified organ whose persistent infrastructure currently depends on personal ownership MUST, in a dedicated future mission, either (a) transfer ownership to a Civilization-owned surface satisfying §81.4, or (b) reclassify the dependency as a temporary bootstrap surface under BC-001 with an explicit completion path.

No such migration is performed by this ratification. ACA-02 sets only the constitutional rule; per-organ migration missions execute it.

§81.10 Amendment Path

ACA-02 may be amended only through GPL-01. Any operational convention that reintroduces permanent personal ownership over persistent Civilization infrastructure is void ab initio unless ratified as a constitutional amendment.