statecraft.
Catalog/rahi

033-dev-substrate-and-harness

The dev substrate and the harness: compose for N=1, boot the real binary, wait on /readyz, a cookie jar

Lifecycle approvedImplementation completeVerification unknownQualification unknown

Two things a contributor needs: a compose file that runs the N=1 topology (the image with a bind-mounted volume, watched rebuilds) and a harness crate that boots a built cell binary under a throwaway data directory with fresh keys and OS-allocated ports, starts a rauthy on loopback when one is available, waits on /readyz and never on /healthz, and hands back an HTTP client with a cookie jar so authenticated flows are testable. One instance per test file, never per test. Carries enrahitu://033.

Read the full pinned specification ↗

Relationships

Claimed units

  • establishes
    {
  "kind": "file",
  "path": "docker/compose.yml"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/rahi-harness/Cargo.toml"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/rahi-harness/src/lib.rs"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/rahi-harness/src/boot.rs"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/rahi-harness/src/client.rs"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/rahi-harness/src/cookies.rs"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/rahi-harness/src/rauthy.rs"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/rahi-harness/tests/boot.rs"
}
  • extends
    {
  "nature": "additive",
  "spec": "031-single-container-packaging",
  "unit": {
    "kind": "file",
    "path": "crates/rahi-ops/src/rauthy_env.rs"
  }
}

Source headings

  1. 033: The dev substrate and the harness
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 4. Functional requirements
  6. 5. Acceptance criteria
  7. 6. Out of scope
  8. 7. Resolved decisions
  9. 8. Status
  10. Verification

Frozen anchors

No frozen anchors declared.