Standalone
Captures governed operational work and receipts, but does not claim Sentinel statutory sealing.
Responder captures governed operational work. It can operate standalone, or escalate into Sentinel for sealed handoff, retry, auditability, purge control, and enterprise evidence handling.
Standalone captures remain operational evidence. They do not impersonate sealed Sentinel governance.
availableoptionalSentinel onlyResponder is the frontline intake capability. Sentinel remains the sealed statutory handoff and proof-room capability.
Captures governed operational work and receipts, but does not claim Sentinel statutory sealing.
Escalates the same intake into Sentinel for proof-room handling, guard state, and sealed handoff receipts.
Surfaces active drafts, torsion posture, profile hash, buffered state, and retry actions without opening logs.
Record incident type, location, declared time, summary, affected parties, and reference-only evidence pointers.
Show advisory reportability signals from Foundry-compatible profiles without creating a private statutory rule engine.
Export JSON or Markdown packs in standalone mode, or prepare a governed Sentinel handoff when Sentinel is installed.
Submit through the buffered Sentinel handoff path for sealed governance, retry, auditability, and purge control.
Capture incident facts, immediate context, and evidence references without entering a full escalation console.
See handover readiness, reportability pressure, buffered dispatch state, and retry posture in the workspace.
Receive structured handover packs that preserve operational context and make Sentinel escalation cleaner when required.
Offer Responder as a standalone capability or pair it with Sentinel without changing the intake package identity.