RVCV-extension Scenario: Reporter + Vendor1 + Coordinator + Vendor2
Overview
The RVCV-extension scenario shows a Vendor-initiated case that grows through a Coordinator to include a second Vendor via the actor-suggestion flow. The Reporter reports to Vendor1, who owns and coordinates the case. Vendor1 invites a Coordinator; the Coordinator then suggests Vendor2 to the case. Vendor1, as Case Owner, approves the suggestion, and the Case Actor formally invites Vendor2.
Both vendors reach the fix-ready state before joint disclosure.
Participants:
- Reporter — discovers the vulnerability and submits the report; in the case it holds the Reporter role; the protocol has no separate Finder role (ADR-0078).
- Vendor1 — receives the report; validates, engages, and owns the case.
- Coordinator — invited by Vendor1; suggests Vendor2.
- Vendor2 — joins via the actor-suggestion path; develops and ships a fix.
- Case Actor — the actor that holds the CASE_MANAGER role for this case; it writes every canonical ledger entry and fans it out to the participants.
In the demo it runs on the dedicated
case-actorcontainer, but its authority comes from the role, not from where it runs.
Protocol narrative
1. Reporter submits a vulnerability report to Vendor1
The Reporter reports to Vendor1's endpoint. No ledger entry is created yet.
Antecedent: Reporter has knowledge of the vulnerability.
2. Vendor1 validates and engages the case
Vendor1 reviews the report and accepts it. validate_report and engage_case
entries appear in the ledger.
Antecedent: Report received from Reporter.
3. Participant status records are created
The Case Actor records the engagement's status as an add_participant_status_to_participant entry; each record seated at case creation was ledgered as a create_case_participant entry.
Antecedent: engage_case is in the ledger.
4. The Reporter asks and Vendor1 answers
The Reporter asks a question in a case note, and Vendor1 answers it.
Each note is sent as one Add(Note) carrying the note inline, and recorded as an add_note_to_case entry, which attaches it to the case.
Vendor1 decides whom to invite only after these notes.
Antecedent: engage_case is in the ledger.
5. Vendor1 invites the Coordinator
Vendor1 sends the Coordinator an invite_actor_to_case entry.
Antecedent: engage_case is in the ledger.
6. Coordinator accepts the invitation
The Coordinator joins the case. An accept_invite_actor_to_case entry is
recorded.
Antecedent: invite_actor_to_case is in the ledger (step 5).
7. Coordinator suggests Vendor2
The Coordinator recognizes that Vendor2 is affected and submits an
offer_case_participant entry proposing Vendor2 for membership (ADR-0026).
Antecedent: Coordinator's accept_invite_actor_to_case entry is in the ledger.
8. Vendor1 approves the recommendation
Vendor1, as Case Owner, reviews and approves the suggestion. An
accept_actor_recommendation entry is recorded.
Antecedent: offer_case_participant is in the ledger.
9. Case Actor invites Vendor2
The Case Actor, acting on Vendor1's approval, sends Vendor2 an
invite_actor_to_case entry.
Antecedent: accept_actor_recommendation is in the ledger.
10. Vendor2 accepts the invitation
Vendor2 reviews and accepts. An accept_invite_actor_to_case entry is recorded.
Antecedent: The Case Actor's invite_actor_to_case entry is in the ledger.
11. The Coordinator and Vendor2 add notes
The Coordinator and Vendor2, now participants, reply in the same thread.
Each note is recorded as one more add_note_to_case entry.
Antecedent: Vendor2's accept_invite_actor_to_case entry is in the ledger.
12. Both vendors reach fix-ready
Vendor1 and Vendor2 each advance to VFd (fix-ready) status.
Antecedent: engage_case is in the ledger.
13. Participants publish; embargo terminates
All participants publish. The embargo exits ACTIVE.
Antecedent: At least one vendor has reached fix-ready.
14. All participants close the case
close_case entries appear for each participant.
Vendor2, the Coordinator, and the Reporter leave first; Vendor1, 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: validate_report and engage_case are in the ledger.
Unobservable edges
| Unobservable step | Why not in ledger |
|---|---|
| Reporter submits report to Vendor1 | Report submission precedes the case. |
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 the Vendor
- The Reporter submits its report; the Vendor engages the case.
- The Reporter asks whether a workaround exists; the Vendor answers.
- Vendor decides: Invite a Coordinator
- The Coordinator and Vendor2 are ready to be invited to the case.
- Vendor1 invites the Coordinator to coordinate the case.
- The Coordinator has joined and the embargo is still active.
- Everything the opening recorded has reached the Reporter's and the Coordinator's replicas of the case.
- Case Owner decides: Keep it: accept the Coordinator's suggestion
- The Coordinator suggests Vendor2 via ADR-0026; Vendor1 approves.
- Ledger Fanout reaches the Reporter, the Coordinator and Vendor2.
- The Coordinator and Vendor2 answer the thread the opening posted.
- Both vendors report fix ready; both stop at VFd (CSB-15-002).
- Vendor1, the Case Owner, publishes first; the Reporter reports last.
- Vendor2, the Coordinator and the Reporter leave; Vendor1 leaves last.