Tracking issue for the special/base cartridges (scope c) — the cross-cutting kinds the maker composes from.
Current state (verified 2026-06-05)
boj-server-cartridges/cartridges/cross-cutting/: 12 .idr across agentic, build, debug, fleet, health, nesy, orchestration.
cartridges/templates/: 1 .idr (the maker seed).
feedback-mcp (in boj-server) is the one fully-real reference cartridge.
Why these are special
Unlike domain cartridges (mostly ABI/memory-safety proofs), the base/cross-cutting kinds carry behavioural / protocol obligations:
- orchestration — routing soundness (a request reaches exactly one correct downstream); no-orphan / no-dup.
- agentic — capability-bound execution (a step can only use granted capabilities).
- nesy — symbolic-soundness (the neural→symbolic bridge preserves declared invariants).
- fleet / build / debug / health — lifecycle + isolation invariants.
What remains
- Define the bespoke proof-obligation set per cross-cutting kind (above is the starting point).
- Specify the "base framework proof bundle" the maker (scope f) inherits by construction — the "proven pre-mint framework" the factory carries so individual cartridges never re-derive it.
- Use
feedback-mcp to pin the gold-reference proof set every minted cartridge ships with.
Done when
- Each cross-cutting kind has a defined obligation set + at least a compiling skeleton
.idr.
- The inheritable base proof bundle is specified and referenced by the maker (scope f).
Proving track — tightly coupled to the maker (scope f).
Filed via Claude Code · https://claude.ai/code/session_019tMcRS1Dm1nWjjYP4WvbJa
Tracking issue for the special/base cartridges (scope c) — the cross-cutting kinds the maker composes from.
Current state (verified 2026-06-05)
boj-server-cartridges/cartridges/cross-cutting/: 12.idracrossagentic,build,debug,fleet,health,nesy,orchestration.cartridges/templates/: 1.idr(the maker seed).feedback-mcp(inboj-server) is the one fully-real reference cartridge.Why these are special
Unlike domain cartridges (mostly ABI/memory-safety proofs), the base/cross-cutting kinds carry behavioural / protocol obligations:
What remains
feedback-mcpto pin the gold-reference proof set every minted cartridge ships with.Done when
.idr.Proving track — tightly coupled to the maker (scope f).
Filed via Claude Code · https://claude.ai/code/session_019tMcRS1Dm1nWjjYP4WvbJa