User Stories
This page is not normative
This page is not considered a core part of the Vultron Protocol as proposed in the main documentation. Although within the page we might provide guidance in terms of SHOULD, MUST, etc., the content here is not normative.
The Vultron Protocol is designed to support a variety of use cases. The following user stories are intended to capture the requirements of these use cases. While the protocol is designed to support these use cases, it is not required that all use cases be supported by the protocol.
Where appropriate, a reference implementation will be provided for each applicable user story. The User Story Traceability Matrix maps each story to the formal requirements in the specifications that satisfy it.
Original User Stories from 2022 CERT/CC Whitepaper
Stories numbered from 2022_001 through 2022_102 originated in
the Coordinated Vulnerability Disclosure User Stories
whitepaper.
These user stories reflect internal discussions with the CERT/Coordination Center (CC) based on our own experiences in developing and using the VINCE platform as well as our ongoing CVD practices. The user stories are expected to be utilized by the CVD team to better understand, create, and implement a CVD Protocol. In addition, the CERT/CC believes that these user cases will be useful for any enterprise designing or implementing its own CVD policies, processes, and procedures.
The remaining stories have been added since that whitepaper was published.
Coverage
The table below gives each story's coverage: how many requirements in the specifications name that story as one of the needs they exist to serve. The count links the story's entry in the User Story Traceability Matrix, which lists those requirements grouped by specification file.
A story whose coverage cell reads No mapped requirements is one that no requirement names yet. That is a recorded gap rather than an error. Some of these stories describe needs the protocol has not taken up. The stories about bug bounties are waiting on a decision about whether bounty programs are in scope at all.
Coverage is a count read from the specifications, not a judgment of how well the protocol serves a story. The specifications hold the mapping, so both this table and the matrix are generated from them and a check in the build fails when either one drifts.
The story pages from the 2022 catalog once carried a support level, a judgment made as of v0.4.0 of whether the protocol provided, allowed or did not support each story. Coverage replaces it, and no page carries it now.
Who Speaks in a Story
Each story is told by a persona: the "As a …" that opens it. The personas form four families. Participant is anyone who takes part in a case, and its members are the CVD roles, such as Vendor or Coordinator. Implementer is anyone who builds or runs software that speaks the protocol: a Peer Implementer, a Node Operator or a Tool Author. Researcher is anyone who studies or checks the protocol model and its records: a Protocol Author or an Auditor. Contributor is anyone who works on this reference implementation: a Maintainer, a Coding Agent or a Demo Operator.
A story's speaker is the highest level that includes every party the story concerns and no party it does not. "As a Participant" means every CVD role, and "As a Vendor" means only the Vendor. A story names a member only when it does not hold for the whole family. The Story Personas section of the glossary defines each persona.
Adding a Story
Reuse an existing story when one already states the need; add a story only when none does.
- ID. A new story's ID is
story_<year>_NNN: the year it is added, then the next unused number in that year. Thestory_2022_*stories are frozen. An ID is never reused, and a story page is never deleted: a story that is split or withdrawn keeps its page, marked superseded by the IDs that replace it. - Page. The page is
story_<year>_NNN.mdin this directory. Its frontmatter declares onlystakeholder_type: [project-contributor]. The story text sits on one line between the<!-- story-start -->and<!-- story-end -->markers. A Notes section explains the need. A Metadata section lists Speaker (the family, and the member when the story names one), Roles (the CVD roles concerned, only when the speaker is a Participant), Related issues (the issues the story came from or relates to), Drafted for (the issue it was written for) and Added (the date). A test checks every page for this shape. - Table and matrix. Do not edit the table below or the User Story Traceability Matrix.
Both are generated from the specifications: run
uv run docs-site --writeafter adding a page, and the new story appears with No mapped requirements until a requirement names it in itsstories:field.
User Stories Table
Legend
- Coverage counts the requirements in
specs/that cite the story in theirstories:field. It links the story's section of the traceability matrix. - No mapped requirements means no requirement cites the story yet.
| ID | Title | Coverage |
|---|---|---|
| 2022_001 | As a Finder I want to discover how to report a vulnerability so that I can notify the affected vendors and start CVD | 4 |
| 2022_002 | As a Participant I want to receive vulnerability reports that I have submitted through a platform so that I can participate and track coordination efforts | 19 |
| 2022_003 | As a Participant I want to Discover others' policies | 15 |
| 2022_004 | As a Participant I want to parse/evaluate others' policies | 10 |
| 2022_005 | As a Participant I want to optimize all of the policies involved | 8 |
| 2022_006 | As a Participant I want to decide if I will/can engage | 49 |
| 2022_007 | As a Participant I want to throw a flag if policy trouble detected | 5 |
| 2022_008 | As a Participant I want to warn Participants and need to invoke other channels/humans. | 3 |
| 2022_009 | As a Participant I want to want to post/publish/advertise my policy | 18 |
| 2022_010 | As a Participant I want to Publish/share/advertise embargo dates, have hard and absolute limits, have a default/starting point, be able to extend, and propose and accept, stop when all accepts • have a default/starting point • be able to extend • propose and accept • stop when all accepts | 32 |
| 2022_011 | As a Participant, I want to provide information about my bug bounty program to entice reporters to use it | 1 |
| 2022_012 | As a Participant, I want to report a (new) vulnerability | 53 |
| 2022_013 | As a Participant I want to Add a Participant? (de-duplicate) | 48 |
| 2022_014 | As a Participant, I want to negotiate embargo/disclosure schedules, modify/renegotiate them, and know when others have published | No mapped requirements |
| 2022_015 | As a Participant, I want to notify others of my intent (date) to publish | 6 |
| 2022_016 | As a Participant, I want limited/ACK of vulnerability/and have full/proper advisory | 18 |
| 2022_017 | As a Participant, I want to share my draft publication with others | 2 |
| 2022_018 | As a Participant, I become aware of the existence of of public exploit (e.g. PoC) and want to tell others | 17 |
| 2022_019 | As a Participant, I become aware of exploitation in the wild and want to tell others | 17 |
| 2022_020 | As a Participant, I want to publish a vulnerability (external to protocol) | 4 |
| 2022_021 | As a Participant, I want to advertise the locale (language, location, geo-scope, area of authority), aspects of my policy | 3 |
| 2022_022 | As a Participant, I want to advertise the scope (e.g., products, version ranges, sites/domains) of my CVD capability | 3 |
| 2022_023 | As a Participant, I want to constrain whom I communicate with because I want to enforce an embargo and communicate only with those who have a need to know. | 112 |
| 2022_024 | As a Finder/Reporter, I want to constrain whom I communicate with because I want to maintain my anonymity. | 4 |
| 2022_025 | As a Vendor/Deployer, I want to constrain whom I communicate with until a patch or mitigation has been published and released. | 13 |
| 2022_026 | As a Coordinator, I want to constrain whom I communicate with to work within an embargo and communicate only with those who have a need to know. | 19 |
| 2022_027 | As a Participant, I want to Address Participants constraints, e.g., entity lists | 35 |
| 2022_028 | As a vendor or coordinator, I want others to find my information and reporting intake (duplicate of X) | 5 |
| 2022_029 | As a Vendor, Deployer, and Other, I want to assign my own ID to a case | 6 |
| 2022_030 | As a Participant , I want to discover and use/map to a global/shared case ID (Might just be a GUID assigned at first notification, CVE is a partial example, vxref) | 28 |
| 2022_031 | As a Finder, Reporter, Vendor, Coordinator, Other, I want to get from another Participant a list of cases I am involved in with them | 4 |
| 2022_032 | As a Reporter, Vendor, Coordinator, Other, I want to ask Participant A if Participant D is in a case. Operator may decide/policy, may be based on whether C and D are in the same case. "A" may or may not answer, that is their policy. Participant may decide/policy, may be based on whether C and D are in the same case. | 8 |
| 2022_033 | As a Finder, Reporter, Vendor, Coordinator, Other, I want to request/state that I do not want others to know I am in a case. Participant still gets to decide their policy. Covers researcher asking for anonymity. Vendor can ask not to be listed and operator can disagree/still list. | 3 |
| 2022_034 | As a Participant I want to use my global/federated user ID to interact with other Participants | 14 |
| 2022_035 | As a Participant I want to have confidence in the identity and group membership of others (and be willing and able to use others' groups) | 62 |
| 2022_036 | As a non-vendor Participant I want to determine how integrated authentication/authorization is in the CVD protocol | 15 |
| 2022_037 | As a vendor I want to publish vulnerability advisories | 2 |
| 2022_038 | As a vendor or coordinator, I want to receive vulnerability reports | 20 |
| 2022_039 | As a Participant I want to ask questions/generally communicate with another case Participant | 39 |
| 2022_040 | As a Participant I want to ask questions/generally communicate with another case Participant unicast/point-to-point | 9 |
| 2022_041 | As a Participant I want to ask questions/generally communicate with all the Participants in a case (broadcast) | 10 |
| 2022_042 | As a Participant I want to ask questions/generally communicate with a subset of case Participants | 3 |
| 2022_043 | As a Participant, I want to communicate in a common case channel | 3 |
| 2022_044 | As a Participant I want to communicate with selected case Participants | 4 |
| 2022_045 | As a Participant, I want to produce a shared verified public record of case activity | No mapped requirements |
| 2022_046 | As a Participant, I want the case to have a leader (global case owner, CVD leader) | 53 |
| 2022_047 | As a Participant, I want to propose a case leader, possibly myself | 6 |
| 2022_048 | As a Participant, I want to vote/accept a proposed case leader | 14 |
| 2022_049 | As a Participant I want to announce the case leader to all Participants | 3 |
| 2022_050 | As a Participant I want to transfer case leadership to a different Participant | 63 |
| 2022_051 | As a Participant, I want to depose (or vote down?) a case leader, possibly myself (step down), possibly requiring a suggestion of a replacement | 6 |
| 2022_052 | As a Participant I want to add (declare and notify others) new Participants to a case | 64 |
| 2022_053 | As a Participant, I want to propose new Participants to a case | 42 |
| 2022_054 | As a Participant I want to vote/accept new Participants to a case | 32 |
| 2022_055 | As a Participant, I want to state that I paid or received a bounty | No mapped requirements |
| 2022_056 | As a Participant, I want to ask if another Participant paid a reporter | No mapped requirements |
| 2022_057 | As a Participant, I want to ask a reporter if they were paid | No mapped requirements |
| 2022_058 | As a Participant I want to share a draft advisory with others | 2 |
| 2022_059 | As a Participant I want to share a draft advisory with others and request feedback (including status) | 3 |
| 2022_060 | As a Participant I want to request advisory (draft) from a Participant | 2 |
| 2022_061 | As a Participant, I want to request someone else’s (vendor) status so I can note changes in others status | 12 |
| 2022_062 | As a Participant, I want to state my status so others are aware of it. | 36 |
| 2022_063 | As a Participant, I want to include a non-vendor role Participant in a case | 28 |
| 2022_064 | As a Participant, I want to include the Government (some/any part, could include regulator) so that they may participate in the case. | 1 |
| 2022_065 | As a Participant, I want to include the Industry/trade group so that they may participate in the case. | 1 |
| 2022_066 | As a Participant, I want to stop participating in the case. | 58 |
| 2022_067 | As a Participant, I want to stop participating in the case and inform others that I am no longer participating. | 23 |
| 2022_068 | As a Participant, I want to stop participating in the case and no longer will receive or reply to forwarded queries. | 7 |
| 2022_069 | As a Participant, I want to tell others that I published so that they can know about the vulnerability and the mitigation or remediation. | 15 |
| 2022_070 | As a Participant, I want to convey how information I provide can be used so that others can apply the mitigation or remediation correctly. | 2 |
| 2022_071 | As a Participant, I want to convey how information I provide can be used while obeying the TLP restrictions so that others can apply the mitigation or remediation correctly. | 2 |
| 2022_072 | As a Participant, I want to convey what restricted information or degree of restriction I will accept so that I won't be accused of mishandling restricted information. | 2 |
| 2022_073 | As a Participant, I want to convey what TLP restricted information or degree of restriction I will accept so that I won't be accused of mishandling TLP restricted information. | 1 |
| 2022_074 | As a Participant, I want to keep track of events and timelines so that I have a complete report and don't miss a deadline. | 78 |
| 2022_075 | As a Participant, I want to see response times/states of other Participants so that I can be prepared for the next state in the CVD process. | 14 |
| 2022_076 | As a VDP operator, I want the CVD protocol to also support VDP | 2 |
| 2022_077 | As a Participant, I want to be able to ask further questions about a report, to ensure I fully understand the vulnerability and mitigation or remediation options. | 15 |
| 2022_078 | As a coordinator, I want to drive better (shorter?) embargo timelines, to ensure they are feasible. | 6 |
| 2022_079 | As a coordinator, I want to collect and optimize embargo timelines of all Participants (probably duplicate of 103) to ensure the timelines are feasible. | 16 |
| 2022_080 | As a Participant, I want to publicly disclose sooner than others but minimize their (the others) exposure/risk | 31 |
| 2022_081 | As a Participant I want to communicate important public state change message/information with all Participants. | 36 |
| 2022_082 | As a non-vendor Participant I want to be informed of CVD in order to perform activities like risk assessment, mitigation, verify mitigation, not be surprised, prepare messaging, etc. | 5 |
| 2022_083 | As a Participant, I want to contribute to the creation, modification and publication of an advisory. | 3 |
| 2022_084 | As a vendor I want to reward the reporter by paying a bounty. | No mapped requirements |
| 2022_085 | As a reporter I want to be rewarded with a bounty. | No mapped requirements |
| 2022_086 | As a Participant I will prioritize my response to requests for information or action so that I contribute to a risk-minimizing CVD process and outcome | 17 |
| 2022_087 | As a Participant I want to share and receive information I can use to prioritize my work regarding the vulnerability report. | 5 |
| 2022_088 | As a Participant, I want to avoid missteps by maintaining knowledge of the state of case and what options are available. | No mapped requirements |
| 2022_089 | As a Participant I want a mechanism which with assure me of the authentication and verify integrity of messages. | 47 |
| 2022_090 | As a Participant we need a mechanism which will ensure the appropriate level of authentication of all Participants | 20 |
| 2022_091 | As a Participant we need a mechanism which will ensure the confidential transport and storage of information. | 7 |
| 2022_092 | As a Participant, I want to know who else is participating in a case to ensure I don't void an embargo. | 15 |
| 2022_093 | As a Participant, in an effort to ensure the Participant list is complete I want to know who else is participating. | 9 |
| 2022_094 | As a Participant, I want to assess reputation of others so that I can decide to engage again | 3 |
| 2022_095 | As a Participant, I want to provide evidence of/document my reputation to others so they can decide to engage with me | 2 |
| 2022_096 | As a Participant, I want to record/log my trust in/reputation of others so I can decide to engage again | 5 |
| 2022_097 | As a Participant I want to organize (create, define) my own groups of other Participants so that I can communicate successfully, participate fully and understand their requirements. | 3 |
| 2022_098 | As a Participant I want to communicate with all Participants associated with this case. | 3 |
| 2022_099 | As a Participant I want to communicate with non-vendor Participants, primarily other defenders, providers, CSIRTs, regulators, etc., important information. | 2 |
| 2022_100 | As a vendor, coordinator or other I want to be included on a distribution list for advisories which must be clearly identified as public or non-public | 2 |
| 2022_101 | As a Coordinator I want to validate the report received from Reporter or Finder before deciding CERT's active involvement for the potential Case | 23 |
| 2022_102 | As a Coordinator I want to collect artifacts such as PoC Proof-of-Concept exploit, code control flow analysis (static or dynamic) that can enabled our validation of the security flaw being reported | 5 |
| 2022_103 | As a Participant, I want to give the Finder/Reporter an opportunity to confirm that the fix addresses the vulnerability prior to publication. | 3 |
| 2022_104 | As a Participant, I want to address multiple related vulnerabilities across multiple vendors simultaneously. | 50 |
| 2022_105 | As a Vendor, I want to address the same vulnerability in multiple products but on different timelines so that I can avoid delaying the delivery of a ready fix to a subset of my user base. | 20 |
| 2022_106 | As a Participant, I want the coordination process to be decentralized so that it is robust against individual Participant actions. | 22 |
| 2022_107 | As a Vendor, I want to convey the vulnerability status of my component(s), product(s), or service(s) to other Participants. | 24 |
| 2022_108 | As a Vendor, I want to convey the vulnerability status of my component(s), product(s), or service(s) to Users / the Public | 2 |
| 2022_109 | As a Vendor, I want to convey the reason my component is not affected by a vulnerability to other Participants | 2 |
| 2022_110 | As a Vendor, I want to convey the reason my component is not affected by a vulnerability to Users / the Public | 1 |
| 2022_111 | As a Vendor, I need to know which of my products, components, or services are affected by a vulnerability report so that I know what to fix. | 5 |
| 2026_001 | As a Case Owner, I want each Participant's Embargo Consent recorded separately for each version of the embargo, so that I know who agreed to the terms in force and no Participant is bound by terms it did not see | 23 |
| 2026_002 | As a Participant, I want every change to the case recorded in one hash-chained case ledger that every Participant holds a copy of, so that a dispute about who knew what, and when, is settled by the record | 10 |
| 2026_003 | As a Case Owner, I want to transfer case ownership to another Participant inside the case, so that the case keeps its Participants, its embargo and its ledger history, and no Participant has to report the vulnerability again | No mapped requirements |
| 2026_004 | As a Participant with limited response capacity, I want to let software make routine case decisions for me, such as accepting an invitation or answering an embargo proposal, so that I can use that capacity where it matters most | 3 |
| 2026_005 | As a Participant, I want to keep an up-to-date record of the case, whatever order the messages arrive in, so that I do not have to log in to another organization's platform to see updates | 17 |
| 2026_006 | As a Reporter, I want each request I send to get an explicit answer, and I want to see which Participant owes an answer and by when, so that I never have to guess whether my message arrived | 13 |
| 2026_007 | As a Participant in a community of interest, I want to exercise our coordination process with the other members before a real case needs it, so that we can trust the process to scale and to work when it matters | No mapped requirements |
| 2026_008 | As a Vendor that publishes each Advisory as a Common Security Advisory Framework (CSAF) document, I want the Participants of a case and their states to map onto the Advisory, so that I do not rebuild the record of who took part and what each did | No mapped requirements |
| 2026_009 | As a Participant that chooses a Vultron implementation, I want to test its conformance claim against the protocol specification, so that I know the implementation follows the protocol and does not only claim to | No mapped requirements |
| 2026_010 | As a Peer Implementer, I want every response activity (Accept, Reject, TentativeReject) to have one specified wire encoding, so that my peer interoperates with others without guessing | 2 |
| 2026_011 | As a Peer Implementer, I want the wire mapping of every message semantic to be specified, including the acknowledgments and error signals that change no state, so that I know which activities carry them and what receiving one obliges me to do | 18 |
| 2026_012 | As a Peer Implementer, I want datetimes and durations to have one canonical wire serialization, so that interoperability does not rest on implementation choices | 14 |
| 2026_013 | As a Peer Implementer, I want an unrecognized or malformed activity to be handled by a specified rule, whether it is classified as unknown, kept as a dead letter for review, or refused with a defined status, so that two conforming peers fail the same way | 8 |
| 2026_014 | As a Peer Implementer, I want message handling to be idempotent, so that duplicate delivery and retries converge on the same case state | 23 |
| 2026_015 | As a Peer Implementer, I want a ledger entry to be committed before the message announcing it is delivered, so that no recipient holds an announcement that the canonical record lacks | 4 |
| 2026_016 | As a Peer Implementer, I want every object reference to resolve to a full Uniform Resource Identifier (URI) that round-trips through storage, so that identity stays stable across peers and restarts | 3 |
| 2026_017 | As a Node Operator, I want malformed, oversized or undecryptable requests to be refused with specified HTTP statuses and structured error bodies, so that clients can diagnose faults without my help | No mapped requirements |
| 2026_018 | As a Node Operator, I want every log entry to carry the identifiers of the activity and actor it concerns, so that I can follow one protocol event through the system | 2 |
| 2026_019 | As a Node Operator, I want pending assertions and retries to time out on documented defaults, so that stale state does not accumulate on my node | 4 |
| 2026_020 | As a Tool Author, I want the semantic pattern registry to be complete, ordered and discriminating by rule, so that a conformance suite can verify that an implementation routes every activity to the right handler | 1 |
| 2026_021 | As a Tool Author, I want every endpoint to be discoverable in the published OpenAPI schema, so that I can generate a client without reading the source | No mapped requirements |
| 2026_022 | As a Protocol Author, I want the case state machine's forbidden states, ephemeral states and forced successors to be stated as invariants, so that an implementation is checked against the model rather than against examples | 18 |
| 2026_023 | As an Auditor, I want the case ledger to be append-only, tamper-evident and written by one authority, so that disputes about what happened, and when, are settled by the record | 27 |
| 2026_024 | As a Participant, I want embargo deadlines to be computed from one timezone-aware formula, so that expiry is unambiguous for every party | 5 |
| 2026_025 | As a Contributor, I want every requirement to state why it exists and to link to what motivated it, so that I can change the system without breaking an intent that nobody wrote down | No mapped requirements |
| 2026_026 | As a Maintainer, I want lint and ratchet gates to fail on new debt and not on inherited debt, so that the corpus improves without blocking unrelated work | No mapped requirements |
| 2026_027 | As a Contributor, I want the traceability record to be generated and checked, so that no one hand-edits a matrix that drifts | No mapped requirements |
| 2026_028 | As an Auditor, I want the case ledger to number its entries in one gapless sequence, in the order the CASE_MANAGER recorded them, each stamped with the time it was committed, so that I can rebuild the order of case events from the ledger alone | 10 |
| 2026_029 | As a Participant, I want the activities I send to reach the CASE_MANAGER in the order I acted, each carrying the time I state for it unchanged, so that the case record shows what I did and when I say I did it | 8 |
| 2026_030 | As a Participant, I want my copy of a case to change only on messages from a CASE_MANAGER I already had reason to trust, so that an actor posing as the CASE_MANAGER cannot plant a case in my records or change one | 20 |
| 2026_031 | As a Participant, I want my own progress on a case kept apart from the state that the whole case shares, so that my progress never changes the embargo or public state that binds everyone, and a case-wide event never erases my progress | 12 |
| 2026_032 | As a Peer Implementer, I want each case object, such as a report, a case, a vulnerability record, a case reference, a case participant and a participant status, to be its own type, so that my peer knows which object's rules apply to what it receives | 2 |
| 2026_033 | As a Participant, I want an embargo to hold only while secrecy still protects users, so that no one is asked to keep a secret that the public or attackers already have | 22 |
| 2026_034 | As a Participant, I want whether a reply authorizes an action to follow from the case record and from a rule the protocol fixes for each kind of request, so that no Participant can extend its own authority and every Participant agrees on which actions were authorized | 8 |
| 2026_035 | As a Node Operator, I want my node to explain a processing failure only to an authenticated sender, and without its internal diagnostics, so that the explanation helps a peer fix its message without helping an attacker probe my node | 2 |
| 2026_036 | As a Participant, I want each status message I receive to update my record of its sender's state at once, so that I know where every participant and the case stand before I act | 18 |
| 2026_037 | As a Participant, I want each state change that a message carries to be recorded against the participant that the message is about, so that no participant gains or loses progress through a message about someone else | 4 |
| 2026_038 | As a Participant, I want my node to refuse to record a move of a state machine that the machine does not permit, so that my own record of the case never holds a state that the case cannot be in | 12 |
| 2026_039 | As a Participant, I want a status that another party reports to be judged against the state machines before it is recorded, accepting a forward move and refusing a backward move or an impossible state, so that a status sent in good faith is kept and an impossible one never enters the case | 11 |
| 2026_040 | As a Participant, I want the CASE_MANAGER either to record what I assert exactly as I sent it or to refuse it whole and tell me why, so that I know whether the case record holds my action and it never shows an action I did not take | 13 |
| 2026_041 | As a Participant, I want the case's shared embargo and public state to change only when the case adopts a change that a participant reports, and each adopted change to be recorded once in the case ledger without losing a public fact already known, so that every participant sees the same shared state and the ledger shows when it changed | 8 |
| 2026_042 | As a Participant, I want the CASE_MANAGER's own progress on a case recorded the way every participant's is, so that I can tell from the case record whether the case is being evaluated, is being coordinated or is closed | 7 |
| 2026_043 | As a Participant, I want an invitee's state in a case to show only what it has agreed to, joining and consenting to the embargo when it accepts the invitation and committing to the case only when it later joins it, so that no participant appears more committed than it is | 3 |
| 2026_044 | As a Participant, I want to ask which actions are open to me in a case now, and why the others are not, so that I do not attempt a step that the case does not allow | 4 |
| 2026_045 | As a Participant, I want my copy of a case to refuse any ledger entry that does not follow from the entries it holds, and to tell the CASE_MANAGER how far it got, so that a lost, reordered or conflicting entry is found at once and never silently absorbed | 22 |
| 2026_046 | As a Participant, I want my node to check each ledger entry's hash against its content before it keeps the entry, and to tell the CASE_MANAGER when the check fails, so that a damaged entry never enters my copy of the case | 5 |
| 2026_047 | As a Participant, I want the CASE_MANAGER to answer a report that my copy has fallen behind by sending me what I lack, the missing entries in order or a fresh copy of the case, so that my copy catches up without anyone stepping in | 13 |
| 2026_048 | As a Participant, I want an entry that arrives ahead of a gap, or before I hold its case, to be held and applied as soon as the gap is filled, so that out-of-order delivery costs no entry and no second delivery | 7 |
| 2026_049 | As a Participant, I want every copy of a case and every message about it to name the ledger position it reflects, so that any two parties can tell which of them is behind | 18 |
| 2026_050 | As a Participant, I want a full case copy from the CASE_MANAGER to replace my case file only when the copy is ahead of mine and agrees with the entries I hold, so that a late or conflicting copy never rolls my case back or forks it | 7 |
| 2026_051 | As a Node Operator, I want replays and replay requests between a CASE_MANAGER and a peer that is out of step to be rate-bounded, so that a peer that stays out of sync cannot flood either node | 12 |
| 2026_052 | As a Node Operator, I want a ledger conflict that the protocol cannot reconcile to be logged at ERROR, so that a real divergence between copies reaches me and is not lost among routine recovery | 3 |
| 2026_053 | As a Participant, I want my node to hold back new case actions until my copy of the case has caught up with the CASE_MANAGER, after a restart or while my copy has a gap, and to show that it is catching up, so that I never act on a stale view of the case | 5 |
| 2026_054 | As a Participant, I want a case's full details to reach only the participants that have joined it, so that an invitee decides from the invitation alone and nobody obtains the case by asking to resynchronize | 18 |
| 2026_055 | As a Participant, I want the CASE_MANAGER to give me a complete copy of each case I take part in, from the moment the case is introduced to me, so that I hold the whole case and not a fragment of it | 14 |
| 2026_056 | As a Participant, I want to receive a case before any ledger entry about it, so that every entry I receive can be anchored to a case I already hold | 4 |
| 2026_057 | As a Participant, I want my copy of a case to be computed only from the CASE_MANAGER's committed ledger entries, so that my copy and every other participant's reach the same case file whatever order the messages arrived in | 17 |
| 2026_058 | As a Participant, I want each change to my copy of a case to happen whole or not at all, so that a failure part-way through never leaves my copy recording a change whose effects are missing | 7 |
| 2026_059 | As a Participant, I want every change to a case to go through its CASE_MANAGER and to enter the case only by the one message that records it, so that the case has one order of events and one record that every copy follows | 44 |
| 2026_060 | As a Participant, I want everything that follows from an event to happen when the event is processed, without anyone having to ask, so that the case never waits on a step that nobody knows to take | 3 |
| 2026_061 | As a Node Operator, I want actors that I host together to keep separate stores and to deal with each other only through protocol messages, so that a case runs the same whether its actors share a host or not | 7 |
| 2026_062 | As a Peer Implementer, I want every case-scoped message to arrive at the participant's one inbox and to name its case in context, so that my peer files each message under the right case without a separate address for each case |
3 |
| 2026_063 | As a Node Operator, I want every change to a case's state committed to my node's store before it counts as done, so that a restart loses no case state and no replication progress | 7 |
| 2026_064 | As a Participant, I want an answer that arrives after the case has moved past what it answers to change nothing, so that a delayed message never revives a finished embargo or undoes a later state | 6 |
| 2026_065 | As a Participant, I want a role in a case to change hands only through an offer that the Case Owner makes by way of the CASE_MANAGER and that the target accepts, with both recorded in the case ledger, so that every participant knows who holds which role and nobody grants a role to itself | 16 |
| 2026_066 | As a Participant, I want the CASE_MANAGER to remove a note only for its author or the Case Owner, and to add a report only for the Case Owner, so that no participant can take away what another contributed or add to the case's reports without authority | 4 |
| 2026_067 | As a Reporter, I want each offer of my report to name one recipient and to carry its own id, so that I can tell apart the cases that different recipients open from the same report | 2 |
| 2026_068 | As a Participant, I want what a case's stage allows to be judged from the case's current data at the moment I act, so that I never act on an embargo or other stage that has already ended | 3 |
| 2026_069 | As a Participant, I want every event in a case recorded in the case ledger, including a rejection, an ask, an expired invitation, a processing fault attributed to the case and the CASE_MANAGER's own acts, so that the record leaves out nothing that bears on the case | 14 |
| 2026_070 | As a Participant, I want each change to a case recorded as its own ledger entry, one entry for each change and no change without one, so that the record counts every change once and the case file never holds a change that the record lacks | 4 |
| 2026_071 | As a Participant, I want the case ledger to hold only the case events that the CASE_MANAGER admitted, never a refusal, a fault in applying a ledger entry or the CASE_MANAGER's own working records, so that the record states what happened in the case and nothing else | 9 |
| 2026_072 | As a Participant, I want each ledger entry to hold the activity exactly as its asserter sent it, under the asserter's own name, so that the record shows who said what in their own words and never credits an act to an actor that did not make it | 9 |
| 2026_073 | As a Participant, I want each case's ledger chain to start from a value bound to that case, its creation time and its owner, so that a chain from another case, or one made up for a case that does not exist, cannot pass as this case's history | 5 |
| 2026_074 | As a Participant, I want the CASE_MANAGER to check each ledger entry's hash before it sends the entry, and to send no later entry of that send after an entry that fails, so that a damaged entry in its store never reaches my copy of the case | 4 |
| 2026_075 | As a Participant, I want the CASE_MANAGER to send each change it records in a case to every active participant, so that every participant holds the same record of the case and none of them depends on another to pass a change on | 13 |
| 2026_076 | As a Participant, I want the case ledger to record a message only after the message has been sent or received, so that the record never claims an exchange that did not happen | 2 |
| 2026_077 | As a Participant, I want my record of a case to show that an exploit became public, or that attacks were seen, before it shows the embargo ending because of it, so that the record shows why the embargo ended | 4 |
| 2026_078 | As a Participant, I want the CASE_MANAGER to commit an act, the ledger entries it carries and everything that follows from it together or not at all, so that the case record never holds half an act | 2 |
| 2026_079 | As a Participant, I want the CASE_MANAGER to resend an invitation that I still owe an answer to whenever my node reports its position in the case ledger, unchanged and at a bounded rate, so that an invitation lost in delivery still reaches me without flooding my node | 7 |
| 2026_080 | As a Participant, I want a case whose vulnerability is still secret to be under an embargo from the moment the case is created, on the Case Owner's default terms or else on a protocol default of three to five days, so that the vulnerability is protected before anyone has negotiated | 17 |
| 2026_081 | As a Reporter, I want to propose embargo terms when I submit a report, and to have the shorter of my terms and the Case Owner's default take effect at once while the longer stays open as a revision, so that the case is protected now and neither party's terms are lost | 11 |
| 2026_082 | As a Participant, I want each embargo to name the report or case it covers, and my node to refuse an embargo that names some other case, so that terms agreed for one case never bind another | 5 |
| 2026_083 | As a Participant, I want to propose embargo terms, counter-propose terms I can accept and propose a revision of the embargo in force while the vulnerability is still secret, so that the embargo can change as the case does | 16 |
| 2026_084 | As a Participant, I want embargo negotiation to follow the report's progress, going ahead while the report is valid and the case is open and pausing once the report is found invalid, deferred or closed, so that nobody negotiates terms for a report that is not being worked | 7 |
| 2026_085 | As a Participant, I want each embargo proposal to be recorded by the CASE_MANAGER and sent to every other participant as an invitation that names who proposed it, so that every participant answers the same terms and none depends on the proposer to reach it | 12 |
| 2026_086 | As a Participant, I want each embargo proposal, decision and ending to move the case's embargo state along one fixed transition, from none to proposed, to active, to revise and back, and to exited, so that every participant that holds the same record reads the same embargo stage | 13 |
| 2026_087 | As a Case Owner, I want my acceptance or rejection of an embargo proposal to decide the case's embargo, and every answer to an embargo invitation, my own included, to record only the answerer's consent, so that the case has one embargo in force at a time and everyone knows who decided it | 28 |
| 2026_088 | As a Participant, I want several open embargo proposals to be decided in order of their end times, earliest first, so that the case takes the shortest terms on the table and longer ones stay open as revisions | 4 |
| 2026_089 | As a Participant, I want my agreement to an embargo to carry over to a revision that ends no later than it, and not to one that ends later, and a revision proposal to leave everyone's consent to the embargo in force as it is until the Case Owner activates the revision, so that I am never bound for longer than I agreed to | 10 |
| 2026_090 | As a Participant, I want to withdraw from the embargo in force by an explicit withdrawal, and my refusal of a proposed revision never to count as one, so that I can leave terms I can no longer keep and refusing new terms never releases me from the terms in force | 9 |
| 2026_091 | As a Participant, I want each embargo invitation to carry a deadline for my answer, set by the CASE_MANAGER, no shorter than a minimum window and never after the embargo ends, so that I have time to answer and everyone knows by when I owe it | 15 |
| 2026_092 | As a Participant, I want an invitation that passes its deadline unanswered to be recorded by the CASE_MANAGER as timed out, never as a refusal, before the Case Owner's next decision on the embargo, so that silence is never read as no and the decision sees who has answered | 11 |
| 2026_093 | As a Participant, I want an acceptance I send after my invitation's deadline still to count while the case can answer the embargo I accepted, and otherwise, when the case holds terms of its own, to bring me a fresh invitation to those terms, so that a late yes is never lost | 9 |
| 2026_094 | As a Participant, I want every party to answer an embargo proposal promptly, and to be free to proceed as if no embargo were agreed when an answer does not come in time, so that a stalled negotiation never holds the case | 4 |
| 2026_095 | As a Participant, I want an embargo's ending to record why it ended, such as a ready fix, a deployed fix or another stated reason, and to close every proposal still open on it, so that every participant knows why the secrecy ended and nobody negotiates terms that no longer exist | 8 |
| 2026_096 | As a Participant, I want to be told when an embargo I agreed to ends or is shortened even after I have left the case or closed my part in it, so that I am never held to terms that no longer apply | 8 |
| 2026_097 | As a Participant, I want an invitation to join a case to carry the embargo in force, and to be replaced by one that names it when that embargo changes before I answer, so that I agree to join under the terms that actually apply | 7 |
| 2026_098 | As a Peer Implementer, I want an object that a message names by reference to be fetched from the actor that holds it, with the message held until the fetch settles, so that my peer never processes a message without the object it names and never drops it | 8 |
| 2026_099 | As a Reporter whose tools write each report as a Common Security Advisory Framework (CSAF) 2.1 vulnerability report, I want to attach that document to the report I offer, so that the case the receiver creates starts with its title, its intended disclosure date and its exploitation status without anyone typing them in again | 18 |
| 2026_100 | As a Vendor that receives reports and exchanges CSAF documents during a case, I want a CSAF document to set up a case only when it arrives with the first report, so that a draft advisory or a projection that participants pass around later never changes the case without a Vultron activity | 1 |
Reading path: You handle vulnerability reports and coordinate cases with other organizations
This page is part of Map it onto what you already do.
Next — pick one
Reading path: You study how vulnerability disclosure works and want the models behind it
This page is part of Go to the formal definition.