044-reference-deployment
The reference deployment: three nodes on Kubernetes, object storage behind it, evaluation green
Lifecycle approvedImplementation pendingVerification unknownQualification unknown
The wave 4 exit condition and the product's own proof. A three-node StatefulSet on Kubernetes with object storage for backups and archived ledger segments, one origin behind an ingress, metrics scraped, backups on a schedule, and an end-to-end harness that drives the whole product through a real client path: sign in, connect, capture, import, curate, recall, promote, export, and erase. When this is green the specification has been demonstrated rather than argued.
Read the full pinned specification ↗Relationships
depends on
Claimed units
- establishes
{ "kind": "file", "path": "deploy/k8s/kustomization.yaml" } - establishes
{ "kind": "file", "path": "deploy/k8s/statefulset.yaml" } - establishes
{ "kind": "file", "path": "deploy/k8s/service.yaml" } - establishes
{ "kind": "file", "path": "deploy/k8s/ingress.yaml" } - establishes
{ "kind": "file", "path": "deploy/k8s/backup-cronjob.yaml" } - establishes
{ "kind": "file", "path": "deploy/k8s/servicemonitor.yaml" } - establishes
{ "kind": "file", "path": "deploy/k8s/secret.example.yaml" } - establishes
{ "kind": "file", "path": "deploy/README.md" } - establishes
{ "kind": "file", "path": "scripts/k8s-validate.sh" } - establishes
{ "kind": "file", "path": "crates/aicortex-harness/Cargo.toml" } - establishes
{ "kind": "file", "path": "crates/aicortex-harness/src/lib.rs" } - establishes
{ "kind": "file", "path": "crates/aicortex-harness/tests/e2e.rs" }
Source headings
- 044: The reference deployment
- 1. Purpose
- 2. Territory
- 3. Behavior
- 4. Functional requirements
- 5. Acceptance criteria
- 6. Out of scope
- 7. Resolved decisions
- Verification
Frozen anchors
No frozen anchors declared.