statecraft.
Catalog/rustev

010-integrations

Optional ecosystem integrations and serving boundary

Lifecycle approvedImplementation completeVerification unknownQualification unknown

A shared boundary contract for three independently optional integration crates: `rustev-aicortex` adapts attributed context and observation proposals, `rustev-rahi` adapts evidence delivery and optional operational hosting, and `rustev-serve` exposes bounded registered-plan execution over an application-operated service boundary. Every integration preserves explicit identity, provenance, failure and unresolved effects; none grants authority, owns domain judgment, or makes Rustev depend on an ecosystem service. Concrete external API bindings and readiness claims require later evidence before implementation.

Read the full pinned specification ↗

Relationships

Claimed units

  • establishes
    {
  "kind": "directory",
  "path": "integrations/rustev-aicortex/"
}
  • establishes
    {
  "kind": "directory",
  "path": "integrations/rustev-rahi/"
}
  • establishes
    {
  "kind": "directory",
  "path": "integrations/rustev-serve/"
}
  • extends
    {
  "nature": "additive",
  "spec": "001-boundaries-and-authority",
  "unit": {
    "kind": "file",
    "path": "Cargo.toml"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "001-boundaries-and-authority",
  "unit": {
    "kind": "file",
    "path": "Cargo.lock"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "001-boundaries-and-authority",
  "unit": {
    "kind": "file",
    "path": "Makefile"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "001-boundaries-and-authority",
  "unit": {
    "kind": "directory",
    "path": "tools/rustev-boundaries/"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "031-public-api-and-release-family",
  "unit": {
    "kind": "directory",
    "path": "tools/rustev-release/"
  }
}

Source headings

  1. 010: Optional ecosystem integrations and serving boundary
  2. 1. Purpose
  3. 2. Territory and lifecycle
  4. 3. Behavior
  5. 3.1 Common boundary
  6. 3.2 Dependencies and partial adoption
  7. 3.3 Identity, provenance and failure
  8. 3.4 Binding records before implementation
  9. 3.5 Aicortex adapter
  10. 3.6 Rahi adapter
  11. 3.7 Serving adapter
  12. 4. Out of scope
  13. 5. Observable negative cases
  14. Acceptance
  15. Verification
  16. Implementation record
  17. Questions settled by R-34
  18. Binding records (section 3.4, R-44)
  19. `rustev-aicortex`
  20. `rustev-rahi`
  21. `rustev-serve`

Frozen anchors

No frozen anchors declared.