What does an orchestration layer owe the guarantees below it?

Orchestration frameworks tend to treat memory, authorization, and telemetry as optional plugins. If routine execution can bypass them, the guarantees they provide are advisory. The fabric should make enforcement structural rather than opt-in.

Mandatory enforcement hooks and explicit state transitions may preserve component guarantees across a routine; this requires failure and replay testing.

• Routine definitions with explicit pre- and post-conditions
• Enforcement hooks so grants and memory writes cannot be skipped
• Model fallbacks that prefer refusal over fabricated success
• Deterministic replay of a routine from its recorded trace

Planned evaluation: hook-bypass rate and replay fidelity across routines. No measured results are reported here.

• Replay fidelity is untested against non-deterministic external tools

Orchestration stack running the routines used by the other projects, with enforcement hooks wired to Agent Guard and MemKit.

• Replay-based regression testing for routines
• Cross-run comparison of decision paths

• Composition semantics for enforced routines
• Failure containment across multi-agent routines