Definition
The state vault is the local-only store that holds the token map between original operational identifiers and capsule tokens. It enables AI outputs to be restored back into the originating workflow with original identifiers — inside the enterprise — without the external LLM ever seeing the originals.
What it stores
- Token map: capsule tokens ↔ original operational identifiers
- Workflow context: which capsule belongs to which incident, ticket, or runbook
- Policy reference: which marker policy applied to this capsule
- Privacy budget reference: how much of the workflow's DP budget this capsule consumed
Where it lives
Always local. The token map never traverses the external boundary. In Path A (external approved LLM), the LLM sees only capsule tokens; the state vault rehydrates after the response returns. In Path B (on-prem local lightweight model), everything is local end to end.
Why it matters
Without restoration, AI outputs are stuck as token salad. The operations team needs the result as a usable artifact in the originating workflow — a ticket update with real device IDs, a runbook step referencing the actual site, an RCA pointing to the actual incident reference. The state vault is what makes that possible while keeping the originals out of the model.
Outputs the state vault produces
- Restored RCA inserted into the ticket system
- Restored runbook step inserted into the runbook
- Restored summary inserted into the EHR or hospital portal
- Restored mission summary inserted into the command system (Path B only)
- Restored compliance review draft inserted into the review workflow
Auditability
Every restoration is logged. The audit trail records the capsule, the policy applied, the path used, the token map operations, and the destination of the restored output. Compliance teams can trace any restored field back to its capsule and policy.
Reference statement
The capsule is what the AI sees. The state vault is what the business sees. The boundary between them is the operational guarantee.