RCVV Embargo Scenario: Reporter + Coordinator + Vendor1 + Vendor2
Overview
The RCVV embargo scenario follows an embargo through a revision cycle, a late second vendor and an accidental collapse. A Reporter submits a report to a Coordinator, who opens the case and invites a first Vendor. Creating the case activates the default embargo. So the proposal of the Reporter and the later proposal of the first Vendor each revise an embargo that is already in force.
The Coordinator invites a second Vendor only after both revisions are active. When the second Vendor accepts the invitation, it signs the embargo then in force. When the Reporter reports public disclosure, the embargo ends on its own. No participant terminates it.
Participants:
- Reporter — discovers the vulnerability, submits the report, proposes new embargo terms and later publishes.
- Coordinator — receives the report, then validates, engages and owns the case. It activates each revision.
- Vendor1 — joins by invitation, consents to the first revision, proposes the second and develops a fix.
- Vendor2 — joins late, signs the embargo in force and develops a fix.
- Case Actor — the actor that holds the CASE_MANAGER role for this case. It commits every embargo decision to the ledger and relays each proposal to the other participants.
Protocol narrative
1. Report submission
The Reporter submits the report, the Coordinator validates it and engages the case, and Vendor1 joins by invitation.
The default embargo is active from case creation, so the case is at Embargo Management (EM) state ACTIVE.
Antecedent: Reporter has knowledge of the vulnerability.
2. Embargo proposal
The Reporter proposes new embargo terms.
The proposal goes only to the CASE_MANAGER.
The CASE_MANAGER moves the case to EM REVISE, records the proposal and relays it to the Coordinator and Vendor1.
Vendor1 accepts, which records its consent and changes no EM state.
The Coordinator, as Case Owner, answers with its decision for the case.
It activates the revision, and the case returns to EM ACTIVE.
Each participant waits for the relayed invitation on its own replica. No participant waits for a message from another participant.
With the revised embargo in force, the Reporter asks about it in a case note, and Vendor1 answers. In this scenario the Reporter proposes terms before it asks anything, and Vendor1's next decision comes after its answer.
Antecedent: the case is engaged and EM is ACTIVE.
3. Embargo revision
Vendor1 proposes further terms. The CASE_MANAGER relays the proposal to the Reporter and the Coordinator. The Reporter accepts, and the Coordinator, as owner, activates the revision.
Antecedent: the first revision is active.
4. Vendor2 late invite
The Coordinator invites Vendor2 only after the second revision is active. Accepting the invitation records Vendor2's consent to the embargo in force, so Vendor2 is a signatory before it does anything else.
Antecedent: the second revision is active.
5. Fix lifecycle
Both vendors report the fix ready. The embargo does not change.
Antecedent: Vendor2 is a signatory to the active embargo.
6. Accidental collapse
The Reporter reports public disclosure. The report moves the case to the public-aware state, and the CASE_MANAGER ends the embargo in response.
EM moves to EXITED on the canonical case.
EM then moves to EXITED on each replica when the ledger entry reaches it.
Nothing requests the termination.
The protocol itself collapses the embargo as a consequence of the disclosure.
Antecedent: the fixes are ready.
7. Case closure
Every participant closes the case. Vendor1, the Reporter, and Vendor2 leave first. The Coordinator, the Case Owner, leaves last. A departure sent after the owner's is not recorded, so every other participant's departure is recorded first.
Antecedent: the vulnerability has been published.
8. Ledger dump
The scenario writes each participant's case ledger for the invariant harness, on success and on failure.
The story as the code tells it
This is the plot of the scenario as the demo code composes it, generated from that code. It is here so a reader can check the narrative above against what the demo actually runs; where the two disagree, the narrative is the one written independently, so read it as the claim and this as the evidence.
- Reporter decides: Report it to a Coordinator
- The Reporter submits its report; the Coordinator engages the case.
- Coordinator decides: Invite the Vendor
- The Coordinator invites the Vendor, and the Invite is delivered.
- Vendor decides: Accept the invite
- The Vendor accepts the Invite, takes its replica and triages the report.
- The Reporter's and the Vendor's replicas catch up with the case.
- Reporter decides: Propose new embargo terms
- Case creation activated the default embargo, before anyone proposed.
- The Reporter revises the default embargo; the Coordinator activates it.
- The Reporter asks whether the revised embargo leaves time for a fix.
- Vendor decides: Propose an embargo revision
- Vendor1 revises the embargo; the Reporter consents; the owner activates.
- Vendor2 is invited once the revision is active, and signs it.
- Both vendors report fix ready; the embargo is untouched.
- The fix being ready leaves the embargo in force.
- The Reporter publishes, and that alone ends the embargo.
- Every participant closes the case; the Case Owner leaves last.
- Closing the case leaves the already-ended embargo ended.