Frozen copy of the Vultron Protocol Specification draft-1, as released in v2026.11.0: commit 1ae1bda2cf7e4f6b2f66b954f9f28256c595a4d8, built 2026-11-13 (UTC). These pages never change. Their links that leave the specification go to the live site, which changes.

Skip to content
Explanation

Annex A Worked Example: Single-Vendor CVD

The whole specification on one page

The specification is also published as a single page that holds every section and annex in order, for printing or for searching the whole text at once.

This page holds informative Annex A of the Vultron Protocol Specification: a two-party Coordinated Vulnerability Disclosure (CVD) case traced from first contact to closure. Its two-letter message codes, such as RS for Report Submission, are protocol shorthands, listed with their wire activities in §4.13 Formal Message Set.

Annex A — Worked Example: Single-Vendor CVD [I]

This annex traces one two-party case from first contact to closure. Each step names the message sent and the state transition it reports, so the sequence can be read against the state machine sections (§6 Report Management (RM) State Machine through §9 Participant Embargo Consent (PEC) State Machine).

Four embargo outcomes are shown — accepted, rejected, countered, and accepted then revised — because embargo negotiation is where two-party cases most often diverge.

A Finder Becomes a Reporter

As we mention in RM Interactions, Finders have a few hidden state transitions before the Coordinated Vulnerability Disclosure (CVD) process really begins. The figure below shows an example. The Finder must discover, validate, and prioritize their finding before they start the CVD process.

---
title: Finder Pre-Report Steps
---
sequenceDiagram
    actor Finder
    Finder ->> Finder: Discover
    Finder ->> Finder: Validate
    Finder ->> Finder: Prioritize

Finders become Reporters when they report a vulnerability to someone else. The next figure shows a Finder that sends a report (RS) together with an embargo proposal (EP) to a Vendor. The Vendor receives the report and updates their state to match.

Then the Vendor replies with three messages. It acknowledges receipt of the report (RK) and of the embargo proposal (EK). It also confirms that the Vendor is aware of the report (CV).

The EK response confirms that the Vendor received the embargo proposal (EP). It does not accept the proposal. We discuss acceptance in the next subsection.

---
title: Finder Submits Report and Embargo Proposal
---
sequenceDiagram
    actor Finder
    actor Vendor
    Finder ->> Finder: Discover, Validate, Prioritize
    Finder ->> Vendor: RS, EP
    note right of Vendor: Report Received
    note right of Vendor: Embargo Proposed
    note right of Vendor: Vendor Aware
    Vendor -->> Finder: RK, EK, CV

Vendor Evaluates Embargo

In this section, we show a variety of responses a Vendor might have to an embargo proposal.

Vendor Accepts Embargo

First is a basic accept sequence. The Vendor accepts the proposed embargo and tells the Reporter with an EA message. The Reporter acknowledges this with an EK in response.

---
title: Vendor Accepts Embargo Proposal
---
sequenceDiagram
    actor Reporter
    actor Vendor

    Reporter ->> Vendor: EP
    note right of Vendor: Embargo Proposed
    Vendor -->> Reporter: RK
    Vendor ->> Reporter: EA
    activate Reporter
    activate Vendor
    note right of Vendor: Embargo Active
    Reporter -->> Vendor: EK
    deactivate Reporter
    deactivate Vendor

Vendor Rejects Embargo

Next we show a rejected proposal. As above, this is a simple sequence. The Vendor rejects the proposal with an ER message, and the Reporter acknowledges this with an EK message.

---
title: Vendor Rejects Embargo Proposal
---
sequenceDiagram
    actor Reporter
    actor Vendor

    Reporter ->> Vendor: EP
    note right of Vendor: Embargo Proposed
    Vendor -->> Reporter: EK
    Vendor ->> Reporter: ER
    note right of Vendor: Embargo Rejected
    Reporter -->> Vendor: EK

Vendor Counterproposal

Here we show a Vendor embargo counterproposal. The Vendor responds to the prior EP message of the Reporter with an EP message of their own. The Reporter first acknowledges the counterproposal with an RK message. Then the Reporter evaluates it and accepts it with an EA message. Finally, the Vendor acknowledges the acceptance with an EK message.

But no embargo is active until the Reporter accepts it. This method of counterproposal might delay the start of an embargo.

---
title: Vendor Counterproposal
---
sequenceDiagram
    actor Reporter
    actor Vendor

    Reporter ->> Vendor: EP
    note right of Vendor: Embargo Proposed
    Vendor -->> Reporter: RK
    Vendor ->> Reporter: EP
    Reporter -->> Vendor: RK
    Reporter ->> Vendor: EA
    activate Vendor
    activate Reporter
    note right of Vendor: Embargo Active
    Vendor -->> Reporter: EK
    deactivate Vendor
    deactivate Reporter

Vendor Accepts then Proposes Revision

Yes, And...

"Yes-And" is a heuristic from improvisational theatre. In it, Participants are encouraged to agree with what their counterpart suggests and add to it, instead of rejecting it outright. It is a good model for cooperation among parties who share an interest in a positive outcome.

Finally, the following diagram shows what we think is a better approach than a simple counterproposal. In this "Accept-then-Counter" sequence, the Vendor first accepts the embargo that the Reporter proposed. Then the Vendor immediately sends a revision proposal of their own. The difference is that the Vendor accepts the proposal first, so they are in an active embargo state before they try to renegotiate.

This sequence is intended to agree with our earlier discussion of default embargo strategies. You can think of this as the "Yes-And" rule for embargo negotiations.

---
title: Vendor Accepts then Proposes Revision
---
sequenceDiagram
    actor Reporter
    actor Vendor

    Reporter ->> Vendor: EP
    note right of Vendor: Embargo Proposed
    Vendor -->> Reporter: RK
    Vendor ->> Reporter: EA
    activate Vendor
    activate Reporter
    note right of Vendor: Embargo Active
    Reporter -->> Vendor: EK
    Vendor ->> Reporter: EV
    note right of Vendor: Embargo Revise
    Reporter -->> Vendor: RK
    Reporter ->> Vendor: EC
    note right of Vendor: Embargo Active
    Vendor -->> Reporter: EK 
    deactivate Vendor
    deactivate Reporter

Vendor Sets Priority

Here we show two responses from a Vendor in the course of prioritizing a report.

Vendor Accepts Report

This figure shows a Vendor that accepts the report for further work with an RA message. The further work is probably to develop a patch.

---
title: Vendor Accepts Report
---
sequenceDiagram
    actor Reporter
    actor Vendor

    Vendor ->> Vendor: Receive, Validate, Prioritize
    Vendor ->> Reporter: RA
    note right of Vendor: Report/Case Accepted
    Reporter -->> Vendor: RK

Vendor Defers Report

In contrast, this figure shows the Vendor as it defers the report with an RD message. In both cases, the Reporter acknowledges the Vendor's messages with an RK message.

---
title: Vendor Defers Report
---
sequenceDiagram
    actor Reporter
    actor Vendor

    Vendor ->> Vendor: Receive, Validate, Prioritize
    Vendor ->> Reporter: RD
    note right of Vendor: Report/Case Deferred
    Reporter -->> Vendor: RK