DOCS / ARCHITECTURE

Guarded lifecycle contracts

Inspect the transport-neutral contracts for context, playbooks, proposals, approval, verification, audit, and lifecycle results.

PHASE 1 · PRE-1.0PYTHON 3.11+EDIT ON GITHUB ↗

Domain state

  • IncidentContext groups bounded ContextItem evidence for one incident.
  • PlaybookDocument declares versioned, typed actions with risk levels and bounded parameter definitions.
  • PolicyDocument maps playbook actions to approval requirements; unknown actions and missing rules fail closed.
  • ActionProposal links a playbook action to a diagnosis and evidence by SHA-256 digest, bounds parameters, expires, and carries execution_allowed=false.
  • ApprovalDecision records approved, rejected, or pending status plus approver, reason, and revision pins.
  • VerificationRequest, VerificationCheck, and VerificationRecord capture explicit passed, failed, unknown, or timed-out outcomes.
  • AuditEvent records inspectable transition detail; LifecycleResult returns the complete non-executing run.

Current orchestration

run_guarded_lifecycle coordinates ports — and never executes

Evidence collection, persistence, and report writing compose separately through their own ports and adapters, so applications choose exactly which capabilities to wire in.

Recovery invariants