Case Lifecycle
This section explains how a Vultron coordination case starts and how its history is recorded and shared. It also explains how control of the case can move between organizations.
- A Case Under Vultron — What a Coordinated Vulnerability Disclosure case looks like from a participant's seat under Vultron: who owns it, what each participant sees and controls, and what an embargo invitation asks of them.
- The Case Model — The domain objects that make up a case and how they relate.
- The CASE_MANAGER and the Case Ledger — Who writes a case's history, which entries it records, and how every participant receives them.
- Case Initialization — Why the CASE_MANAGER, not the report receiver, creates the case, and the ledger entries case creation commits.
- Ownership Transfer — How the CASE_OWNER role moves between participants via the CASE_MANAGER.
- Case Authority, Trust, and Routing — Who may change a case, why every case message goes through the CASE_MANAGER, how a new participant learns which actor to trust, and where a closed case stops accepting writes.
- Case Ledger Synchronization — How replicas order ledger entries and catch up on the ones they missed.