Expand description
Durable (file-backed) session registry — the policy process’s canonical session store, mirroring the credential-revocation authority’s discipline.
A JSONL append log holds one record per registration and one per revocation. Registration validates, appends, and fsyncs BEFORE the session becomes visible; revocation appends its marker BEFORE the in-memory status flips and the verified-subject cache generation is flushed (publication-before-eviction, v16 §3.3). Session identifiers are never reassigned: records are never dropped on load (an expired-but-present record still blocks re-registration), unlike the credential store whose entries expire with their tokens.
Structs§
- File
Backed Session Registry - Durable session registry: an in-memory index in front of a JSONL append file. This is the canonical registry form owned by the policy process.