release: freeze Nexus One AI 1.0.0-rc1

specs/001-enterprise-experience/plan.md

@@ -111,7 +111,32 @@ specs/001-enterprise-experience/
 ├── data-model.md
 ├── quickstart.md
 ├── contracts/
-│   └── customer-experience-contract.md
+│   ├── customer-experience-contract.md
+│   ├── architecture-decisions.md
+│   ├── compatibility-evaluation.md
+│   ├── installer-artifact-contract.md
+│   ├── online-universal-acquisition.md
+│   ├── offline-license-policy.md
+│   ├── offline-validation-lab.md
+│   ├── payload-inventory-sizing.md
+│   ├── release-lifecycle-provenance.md
+│   ├── model-pack-lifecycle.md
+│   ├── release-signing-trust.md
+│   ├── installer-threat-model.md
+│   ├── update-rollback-policy.md
+│   ├── workstation-hardware-model-baseline.md
+│   ├── workstation-runtime-compatibility-baseline.md
+│   ├── schemas/
+│   │   ├── artifact-manifest.schema.json
+│   │   └── signature-envelope.schema.json
+│   └── test-vectors/
+│       ├── README.md
+│       ├── compatibility-cases.json
+│       └── workstation-iso-manifest.valid.json
+├── analysis/
+│   ├── installer-release-consistency.md
+│   ├── gate-evidence-allocation.md
+│   └── gate-1-decision-dossier.md
 └── checklists/
     └── requirements.md
 ```
@@ -169,3 +194,18 @@ and keep deployed copies synchronized through explicit verification.
 ## Complexity Tracking
 
 No constitutional violations require justification.
+
+## Installer Release Architecture Workstream
+
+The four-artifact release matrix is a cross-cutting packaging workstream within this feature, not a
+new product feature. Its normative lifecycle, payload, trust, recovery, sizing, and evidence rules are
+defined in `contracts/installer-artifact-contract.md`.
+
+Sequence is Online Universal Server maintenance, then Offline Workstation as the first new offline
+implementation, followed only after shared-contract evidence by Offline Server S/M and Offline Server
+L/Max. Large models are separate signed packs; installed products share one signed offline-update
+bundle format. Planning does not authorize builds or runtime changes.
+
+Before Offline Workstation implementation, resolve the architecture-readiness blockers in
+`analysis/installer-release-consistency.md`. Re-run consistency analysis after those decisions and
+again after real Workstation artifact evidence, before either offline Server ISO starts.