Mission Guardian
Status
Section titled “Status”Main product direction for agentic execution guardrails. Progressively replaces open promises tied to Gouvernance Lite for mission-critical guardrails.
| Field | Value |
|---|---|
| Server routes | mission-guardian |
| Use cases | core/use-cases/mission-guardian |
| Maturity | beta |
Mission Guardian covers gate decisions tied to missions, leader, QA and orchestration transitions. It makes blockers explicit, traceable and actionable before an agent or a leader continues a mission.
Surfaces
Section titled “Surfaces”| Surface | Detail |
|---|---|
| Server routes | mission-guardian (Fastify route groups) |
| Core use cases | core/use-cases/mission-guardian |
| Runtime prompts | Served by Cortex Runtime Hub when available |
| Integrations | squad-leader via transition guards, squad-orchestration via the mission pipeline |
| UI view | MissionGuardianView (phases tracking, evidence, QA verdict) |
Recommended public framing
Section titled “Recommended public framing”- “Mission Guardian enforces mission guardrails and makes refusals visible.”
- Do not promise a complete autonomous governance embedded in arka-deck — Mission Guardian covers mission gates, not the entire governance domain.
Boundaries
Section titled “Boundaries”- Automatic CR integration is still in progress.
- Consumed evidence and its schemas are defined by use cases; consuming addons must not create parallel routes.
Going further
Section titled “Going further”- Squad Orchestration: ./squad-orchestration
- Gouvernance Lite: ./gouvernance-lite