010-chassis-adoption-and-workspace

The cell: a Cargo workspace, pinned rahi crates, a declared manifest, and one line of main

Lifecycle approvedImplementation completeVerification unknownQualification unknown

The workspace and the seam to the chassis. rahi crates are pinned to one exact version in the workspace manifest and are never vendored or patched. The application is a `Cell`: it returns a manifest, a migration list, a router, and an operator router, and `main` hands it to rahi's runner, which owns argument parsing, boot, the verbs, and the exit codes. The manifest is the capability ceiling, and it starts closed: no egress host is declared until a spec needs one.

Read the full pinned specification ↗

Relationships

depends on

002-memory-thesis

depended on by

011-memory-model

Claimed units

establishes

{
  "kind": "file",
  "path": "Cargo.toml"
}

establishes

{
  "kind": "file",
  "path": "rust-toolchain.toml"
}

establishes

{
  "kind": "file",
  "path": "deny.toml"
}

establishes

{
  "kind": "file",
  "path": "apps/aicortex/Cargo.toml"
}

establishes

{
  "kind": "file",
  "path": "apps/aicortex/src/main.rs"
}

establishes

{
  "kind": "file",
  "path": "apps/aicortex/src/cell.rs"
}

establishes

{
  "kind": "file",
  "path": "apps/aicortex/manifest.toml"
}

establishes

{
  "kind": "file",
  "path": "apps/aicortex/tests/cell.rs"
}

extends

{
  "nature": "additive",
  "spec": "001-agentic-harness",
  "unit": {
    "kind": "file",
    "path": "spec-spine.toml"
  }
}

Source headings

010: The cell
1. Purpose
2. Territory
3. Behavior
4. Functional requirements
5. Acceptance criteria
6. Out of scope
7. Resolved decisions
Status (2026-09-17, complete: the chassis release landed)
Verification

Frozen anchors

No frozen anchors declared.