The Cabin Crew Protocol is the Reference Implementation for the AI Agent Manifesto.
This document details how the protocol strictly adheres to the 5 Immutable Laws + the Capability Isolation principle.
"Reasoning must be separate from action. Intent must be decoupled from Execution."
Implementation:
- Flight Plan Mode: Engines generate a plan (
PlanToken) inflight-planmode. No state changes occur. - Take-Off Mode: Execution happens only in
take-offmode, which mandates a validPlanToken. - Preflight Check: The Orchestrator validates the plan before authorizing execution.
"Every output must carry its creation story... cryptographic link between the agent's identity, the input context, the model used, and the final output."
Implementation:
- PlanToken: Contains
workspace_hash,model(e.g.gpt-4),engine_id, andprotocol_version. - Binding: This token is cryptographically bound to the artifacts it produced.
"No agent can be its own authority. Safety guardrails must exist outside the agent's cognitive loop."
Implementation:
- Gateways:
LLMGatewayandMCPGatewaywrap all external calls, enforcing policy (rate limits, DLP) outside the engine logic. - Orchestrator Veto: The Orchestrator can deny a
PreflightOutputregardless of the Engine's confidence.
"Logs must be proofs, not just text."
Implementation:
- Signatures:
AuditEventincludes a cryptographicsignaturefield. - Hash Chain:
AuditEventsupportschain_hashfor ledger-style non-repudiation.
"Static keys are a failure of architecture."
Implementation:
- Identity Tokens: The protocol supports
identity_token(OIDC/JWT) inEngineInputfor short-lived, verifiable workload identity.
"Agents must not simultaneously process untrusted input, access sensitive systems, and perform state-changing operations... external supervision is mandatory."
Implementation:
- Human-in-the-Loop: Explicit support via:
PreflightOutput.decision: 'REQUIRE_APPROVAL'WorkflowState: 'WAITING_APPROVAL'ApprovalRequest/ApprovalResponsestructures.