Skip to content

User Story Traceability Matrix

This page maps each user story under docs/reference/user_stories/ to the requirements that cite it in their stories: field. The spec files are the authoritative side of the story graph (ADR-0072), so this page is generated from them and a hand edit fails uv run docs-site --check. To change an entry, change the citing requirement's stories: field in specs/ and regenerate.

A story that no requirement cites is marked No mapped requirements (TRACE-01-002). Each requirement links the row that defines its anchor: the Requirements Catalog for a protocol or foundation requirement, its tier page for any other kind.

story_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

Spec file Citing requirements
EP — Embargo Policy EP-01-001
IE — Inbox Endpoint IE-02-001
VP — Vultron Protocol VP-02-001, VP-02-005

story_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 

Spec file Citing requirements
HP — Handler Protocol HP-00-001, HP-09-001, HP-09-002, HP-10-001
HTTP — HTTP Protocol Requirements HTTP-01-001, HTTP-01-002, HTTP-01-003, HTTP-01-004
IE — Inbox Endpoint IE-02-002, IE-02-003
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-01-008
RMB — Report Management Behavioral Requirements RMB-01-001
TB — Testability TB-03-001, TB-03-003
VAM — Vultron Semantic–AS2 Mapping VAM-02-001, VAM-02-003
VP — Vultron Protocol VP-03-001, VP-03-002, VP-06-007

story_2022_003

As a Participant I want to Discover others' policies

Spec file Citing requirements
EP — Embargo Policy EP-01-001, EP-02-001, EP-02-002, EP-02-004, EP-02-005, EP-02-006, EP-02-007, EP-02-008, EP-02-009, EP-02-010, EP-02-011, EP-02-012, EP-02-013
VP — Vultron Protocol VP-02-001, VP-02-005

story_2022_004

As a Participant I want to parse/evaluate others' policies

Spec file Citing requirements
DUR — Duration DUR-03-002, DUR-03-004
EP — Embargo Policy EP-01-002, EP-01-003, EP-01-004, EP-02-002, EP-02-006
VP — Vultron Protocol VP-07-001, VP-07-002, VP-07-014

story_2022_005

As a Participant I want to optimize all of the policies involved

Spec file Citing requirements
EP — Embargo Policy EP-03-001, EP-03-002
VP — Vultron Protocol VP-07-003, VP-07-004, VP-07-005, VP-07-007, VP-07-012, VP-07-013

story_2022_006

As a Participant I want to decide if I will/can engage

Spec file Citing requirements
CFG — Configuration Management CFG-07-002
CM — Case Management CM-11-002, CM-11-007, CM-11-010, CM-11-011, CM-11-014, CM-11-020, CM-11-022, CM-11-031, CM-11-032, CM-11-033, CM-11-034, CM-11-041, CM-11-051
CP — CaseProposal Protocol CP-05-002, CP-05-004, CP-05-008, CP-05-020, CP-06-002
EMB — Embargo Management Behavioral Requirements EMB-15-001, EMB-15-005, EMB-15-013
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-01-002, MSM-01-003, MSM-01-004, MSM-01-005, MSM-01-006
PCR — Participant Case Replica PCR-08-012, PCR-08-014, PCR-08-020
RMB — Report Management Behavioral Requirements RMB-09-001, RMB-13-001, RMB-14-004, RMB-14-005, RMB-14-007, RMB-14-008, RMB-14-009
VAM — Vultron Semantic–AS2 Mapping VAM-02-005, VAM-02-006, VAM-03-003, VAM-03-004, VAM-04-006, VAM-04-013, VAM-04-014
VP — Vultron Protocol VP-02-003, VP-02-006, VP-02-014, VP-02-016, VP-02-021

story_2022_007

As a Participant I want to throw a flag if policy trouble detected

Spec file Citing requirements
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-02-004, MSM-02-006
VP — Vultron Protocol VP-03-008, VP-06-001, VP-11-002

story_2022_008

As a Participant I want to warn Participants and need to invoke other channels/humans.

Spec file Citing requirements
VP — Vultron Protocol VP-03-008, VP-11-003, VP-11-005

story_2022_009

As a Participant I want to want to post/publish/advertise my policy

Spec file Citing requirements
EP — Embargo Policy EP-01-001, EP-02-001, EP-02-002, EP-02-004, EP-02-005, EP-02-006, EP-02-007, EP-02-008, EP-02-009, EP-02-010, EP-02-011, EP-02-012, EP-02-013
VP — Vultron Protocol VP-02-001, VP-02-005, VP-07-002, VP-07-006, VP-07-010

story_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

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-01-001, ASK-01-005, ASK-03-001, ASK-08-001
DUR — Duration DUR-01-001, DUR-01-002, DUR-01-003, DUR-06-001, DUR-06-004, DUR-07-001, DUR-07-002, DUR-07-003
EMB — Embargo Management Behavioral Requirements EMB-13-003, EMB-13-006, EMB-13-007, EMB-13-008
EP — Embargo Policy EP-01-002, EP-01-006, EP-01-007, EP-04-002, EP-04-003
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-02-001
VAM — Vultron Semantic–AS2 Mapping VAM-05-004
VP — Vultron Protocol VP-04-003, VP-04-004, VP-05-001, VP-05-017, VP-06-004b, VP-06-010, VP-07-006, VP-08-019, VP-11-010

story_2022_011

As a Participant, I want to provide information about my bug bounty program to entice reporters to use it

Spec file Citing requirements
EP — Embargo Policy EP-01-001

story_2022_012

As a Participant, I want to report a (new) vulnerability

Spec file Citing requirements
BT — Behavior Tree Integration BT-10-001, BT-10-002, BT-10-007, BT-10-008
CBT — Case Bootstrap Trust CBT-01-001, CBT-01-019
CFG — Configuration Management CFG-07-002
CM — Case Management CM-02-008, CM-02-017, CM-12-001, CM-12-002, CM-14-001, CM-14-004, CM-14-008, CM-14-011, CM-22-006
CP — CaseProposal Protocol CP-04-001, CP-04-003, CP-05-001, CP-05-002, CP-05-003, CP-05-005, CP-05-008, CP-05-011, CP-05-012, CP-05-016, CP-05-017, CP-05-020, CP-06-001, CP-09-001, CP-09-002, CP-09-006, CP-09-011
HP — Handler Protocol HP-01-010, HP-01-030, HP-09-001, HP-09-002, HP-10-001
IE — Inbox Endpoint IE-02-002
LST — Lifecycle-Staged Domain Types LST-02-001, LST-02-002
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-01-001
MV — Message Validation MV-01-001
RMB — Report Management Behavioral Requirements RMB-08-003
SYNC — Case Event Log Synchronization SYNC-15-005
VAM — Vultron Semantic–AS2 Mapping VAM-02-001, VAM-02-002, VAM-02-004, VAM-03-001, VAM-03-005, VAM-04-012
VP — Vultron Protocol VP-02-015, VP-03-001

story_2022_013

As a Participant I want to Add a Participant? (de-duplicate)

Spec file Citing requirements
BT — Behavior Tree Integration BT-10-005
BTND — Behavior Tree Node Design BTND-05-001, BTND-05-003
CBT — Case Bootstrap Trust CBT-01-004, CBT-01-008, CBT-01-018, CBT-04-001, CBT-05-005
CM — Case Management CM-02-008, CM-02-017, CM-11-001, CM-12-002, CM-14-005, CM-14-012, CM-16-009, CM-16-022, CM-25-001
CP — CaseProposal Protocol CP-09-002, CP-09-004, CP-09-006, CP-09-009
EMB — Embargo Management Behavioral Requirements EMB-17-001, EMB-17-002, EMB-17-003, EMB-17-004, EMB-17-009, EMB-17-012, EMB-17-013, EMB-17-014, EMB-17-015, EMB-17-016, EMB-17-017, EMB-17-018
LST — Lifecycle-Staged Domain Types LST-02-002
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-01-005
PRM — Participant Role Management PRM-02-002
RMB — Report Management Behavioral Requirements RMB-13-001
VAM — Vultron Semantic–AS2 Mapping VAM-03-003, VAM-04-001, VAM-04-004, VAM-04-005, VAM-04-011, VAM-06-004
VP — Vultron Protocol VP-02-003, VP-05-004, VP-08-001, VP-08-004, VP-08-013

story_2022_014

As a Participant, I want to negotiate embargo/disclosure schedules, modify/renegotiate them, and know when others have published

No mapped requirements (TRACE-01-002).

story_2022_015

As a Participant, I want to notify others of my intent (date) to publish

Spec file Citing requirements
EMB — Embargo Management Behavioral Requirements EMB-11-005, EMB-12-003
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-02-007
VP — Vultron Protocol VP-05-014, VP-09-001, VP-11-008

story_2022_016

As a Participant, I want limited/ACK of vulnerability/and have full/proper advisory

Spec file Citing requirements
CP — CaseProposal Protocol CP-05-003, CP-05-004
CSB — CVD Case State Behavioral Requirements CSB-04-004, CSB-05-005, CSB-06-005
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-01-008
RF — Response Format RF-02-001, RF-08-001
RMB — Report Management Behavioral Requirements RMB-01-001, RMB-08-001, RMB-08-003, RMB-08-004, RMB-08-005, RMB-08-006, RMB-08-007, RMB-08-008
VAM — Vultron Semantic–AS2 Mapping VAM-02-003
VP — Vultron Protocol VP-03-009

story_2022_017

As a Participant, I want to share my draft publication with others

Spec file Citing requirements
RF — Response Format RF-01-001
VP — Vultron Protocol VP-05-006

story_2022_018

As a Participant, I become aware of the existence of of public exploit (e.g. PoC) and want to tell others

Spec file Citing requirements
CM — Case Management CM-04-004
CSB — CVD Case State Behavioral Requirements CSB-05-001, CSB-05-002, CSB-05-003, CSB-05-004, CSB-13-001, CSB-13-006
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-03-005
RSH — Received-Side Status Authorization RSH-03-001, RSH-09-009
VP — Vultron Protocol VP-06-001, VP-09-003, VP-09-004, VP-09-006, VP-11-002, VP-11-011, VP-11-012

story_2022_019

As a Participant, I become aware of exploitation in the wild and want to tell others

Spec file Citing requirements
CM — Case Management CM-04-004
CSB — CVD Case State Behavioral Requirements CSB-06-001, CSB-06-002, CSB-06-003, CSB-06-004, CSB-14-004
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-03-006
RSH — Received-Side Status Authorization RSH-03-001, RSH-09-009
VP — Vultron Protocol VP-06-001, VP-09-002, VP-11-003, VP-11-006, VP-11-007, VP-12-002, VP-12-002c, VP-14-004

story_2022_020

As a Participant, I want to publish a vulnerability (external to protocol)

Spec file Citing requirements
VP — Vultron Protocol VP-05-005, VP-05-020, VP-06-015, VP-09-001

story_2022_021

As a Participant, I want to advertise the locale (language, location, geo-scope, area of authority), aspects of my policy

Spec file Citing requirements
EP — Embargo Policy EP-01-002, EP-01-003
VP — Vultron Protocol VP-02-001

story_2022_022

As a Participant, I want to advertise the scope (e.g., products, version ranges, sites/domains) of my CVD capability

Spec file Citing requirements
EP — Embargo Policy EP-01-002
VP — Vultron Protocol VP-02-001, VP-02-005

story_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.

Spec file Citing requirements
CM — Case Management CM-03-003, CM-04-003, CM-04-008, CM-09-001, CM-10-001, CM-10-004, CM-10-005, CM-10-006, CM-10-008, CM-11-001, CM-11-008, CM-11-016, CM-12-004, CM-14-003, CM-14-005, CM-14-010, CM-17-002, CM-17-005, CM-17-010, CM-17-013, CM-17-020, CM-17-021, CM-17-022, CM-17-023, CM-18-001, CM-18-019, CM-18-020, CM-18-021, CM-28-003, CM-31-001, CM-31-003, CM-31-004, CM-31-005, CM-31-006, CM-31-007, CM-31-008, CM-31-013, CM-31-015, CM-31-016, CM-31-017, CM-31-020, CM-31-021, CM-31-022, CM-31-023, CM-31-024, CM-31-025, CM-31-026, CM-31-027, CM-31-028, CM-31-029, CM-31-040
CP — CaseProposal Protocol CP-09-003
CSB — CVD Case State Behavioral Requirements CSB-04-002, CSB-04-003, CSB-04-005, CSB-04-007, CSB-05-002, CSB-05-003, CSB-05-006, CSB-05-008, CSB-06-002, CSB-06-003, CSB-06-006, CSB-06-008, CSB-12-001, CSB-12-002, CSB-12-004, CSB-12-005, CSB-13-002, CSB-13-003, CSB-13-004, CSB-13-005
EMB — Embargo Management Behavioral Requirements EMB-01-001, EMB-02-001, EMB-03-003, EMB-03-004, EMB-04-002, EMB-05-002, EMB-07-001, EMB-07-002, EMB-11-001, EMB-11-002, EMB-16-001, EMB-16-003, EMB-16-004, EMB-16-005
EP — Embargo Policy EP-04-001, EP-04-005, EP-04-018, EP-04-019
LST — Lifecycle-Staged Domain Types LST-02-001, LST-02-003
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-02-002, MSM-02-005
MV — Message Validation MV-10-005
PCR — Participant Case Replica PCR-06-005, PCR-06-006
VAM — Vultron Semantic–AS2 Mapping VAM-05-003, VAM-05-005
VP — Vultron Protocol VP-05-006, VP-05-007, VP-05-019, VP-06-016, VP-08-002, VP-08-006, VP-11-009, VP-13-001, VP-13-010, VP-13-011, VP-13-012, VP-14-005, VP-16-001

story_2022_024

As a Finder/Reporter, I want to constrain whom I communicate with because I want to maintain my anonymity.

Spec file Citing requirements
AKM — Actor Knowledge Model AKM-02-003
CM — Case Management CM-09-002, CM-09-003
VP — Vultron Protocol VP-08-017

story_2022_025

As a Vendor/Deployer, I want to constrain whom I communicate with until a patch or mitigation has been published and released.

Spec file Citing requirements
CM — Case Management CM-10-004, CM-10-005, CM-10-006, CM-10-008
VP — Vultron Protocol VP-05-006, VP-05-014, VP-06-002, VP-06-008, VP-06-008b, VP-14-007, VP-14-008, VP-14-010, VP-14-015

story_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.

Spec file Citing requirements
CM — Case Management CM-11-001
EMB — Embargo Management Behavioral Requirements EMB-13-003, EMB-13-004, EMB-13-005, EMB-13-006, EMB-13-007, EMB-13-008, EMB-13-009, EMB-13-010, EMB-13-011, EMB-13-012, EMB-13-013, EMB-13-014, EMB-13-015, EMB-13-016, EMB-13-017
VP — Vultron Protocol VP-05-006, VP-05-007, VP-08-006

story_2022_027

As a Participant, I want to Address Participants constraints, e.g., entity lists

Spec file Citing requirements
CM — Case Management CM-04-008, CM-10-001, CM-18-002, CM-18-022, CM-18-023, CM-28-001, CM-28-002, CM-28-012, CM-28-013, CM-28-014, CM-28-015, CM-28-017, CM-28-018, CM-28-019, CM-28-020, CM-28-023, CM-28-024, CM-28-025, CM-28-026, CM-28-027, CM-28-028, CM-28-029
EMB — Embargo Management Behavioral Requirements EMB-15-004
EP — Embargo Policy EP-05-001, EP-05-003, EP-07-001, EP-07-002, EP-07-003, EP-07-006, EP-07-009, EP-07-010, EP-07-011
VP — Vultron Protocol VP-05-013, VP-08-010, VP-08-021

story_2022_028

As a vendor or coordinator, I want others to find my information and reporting intake (duplicate of X)

Spec file Citing requirements
AR — Agentic Readiness AR-10-001
CM — Case Management CM-06-003
HTTP — HTTP Protocol Requirements HTTP-04-001
IE — Inbox Endpoint IE-02-001
VP — Vultron Protocol VP-02-001

story_2022_029

As a Vendor, Deployer, and Other, I want to assign my own ID to a case

Spec file Citing requirements
CM — Case Management CM-02-001
OID — Object ID OID-01-001, OID-01-002, OID-01-003, OID-01-013, OID-01-014

story_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)

Spec file Citing requirements
CLP — Case Ledger Processing CLP-07-007, CLP-08-006
CM — Case Management CM-05-003, CM-05-008, CM-05-009, CM-05-010, CM-05-018, CM-05-019, CM-05-020, CM-05-021, CM-34-001, CM-34-002, CM-34-004, CM-34-005, CM-34-006, CM-34-007, CM-34-008, CM-34-009, CM-34-010, CM-34-011
MV — Message Validation MV-05-001, MV-05-002
OID — Object ID OID-01-001, OID-01-002
PCR — Participant Case Replica PCR-05-001, PCR-05-002
VP — Vultron Protocol VP-16-002, VP-16-003

story_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

Spec file Citing requirements
AR — Agentic Readiness AR-07-001
CM — Case Management CM-02-001
PCR — Participant Case Replica PCR-05-001
VP — Vultron Protocol VP-01-001

story_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.

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-03-002, ASK-03-004, ASK-03-008, ASK-05-004, ASK-05-005
VP — Vultron Protocol VP-01-001, VP-08-004, VP-08-009

story_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.

Spec file Citing requirements
CM — Case Management CM-09-002, CM-09-003
VP — Vultron Protocol VP-08-017

story_2022_034

As a Participant I want to use my global/federated user ID to interact with other Participants

Spec file Citing requirements
AR — Agentic Readiness AR-10-001, AR-10-003
CM — Case Management CM-24-002, CM-24-020, CM-24-021
EP — Embargo Policy EP-01-005
MV — Message Validation MV-05-001
OID — Object ID OID-01-001, OID-01-005, OID-01-010, OID-01-013, OID-01-014
VP — Vultron Protocol VP-15-002, VP-15-003

story_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)

Spec file Citing requirements
BT — Behavior Tree Integration BT-10-004, BT-10-009
CBT — Case Bootstrap Trust CBT-01-005, CBT-01-011, CBT-01-017, CBT-02-003
CM — Case Management CM-02-016, CM-11-017, CM-11-047, CM-16-019, CM-21-011, CM-24-007, CM-24-016, CM-24-017, CM-24-018, CM-24-019, CM-30-001, CM-30-002, CM-30-003, CM-30-004, CM-30-005, CM-30-006, CM-33-001, CM-33-002, CM-33-003, CM-33-004, CM-33-005, CM-33-006, CM-33-007, CM-33-008, CM-33-009, CM-33-010, CM-33-011, CM-33-012, CM-33-013, CM-33-014, CM-33-015, CM-33-016, CM-33-017, CM-33-018, CM-33-019, CM-33-021
CP — CaseProposal Protocol CP-05-010, CP-05-022, CP-06-005, CP-06-007, CP-06-008
ENC — Encryption ENC-01-001, ENC-01-002
EP — Embargo Policy EP-01-005
HP — Handler Protocol HP-01-006, HP-01-018
OID — Object ID OID-01-005
SIG — Signing SIG-01-001, SIG-02-001, SIG-02-002, SIG-02-003, SIG-02-004, SIG-04-002
SYNC — Case Event Log Synchronization SYNC-03-005, SYNC-03-011
VP — Vultron Protocol VP-15-002

story_2022_036

As a non-vendor Participant I want to determine how integrated authentication/authorization is in the CVD protocol

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-07-005, ASK-07-013
BT — Behavior Tree Integration BT-10-004, BT-10-009
CM — Case Management CM-02-006, CM-24-001, CM-26-001
CSB — CVD Case State Behavioral Requirements CSB-15-001, CSB-15-002, CSB-15-007, CSB-15-009
ENC — Encryption ENC-01-001
HP — Handler Protocol HP-01-006, HP-01-018
VP — Vultron Protocol VP-15-002

story_2022_037

As a vendor I want to publish vulnerability advisories

Spec file Citing requirements
VP — Vultron Protocol VP-05-020, VP-12-001

story_2022_038

As a vendor or coordinator, I want to receive vulnerability reports

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-01-008, CBT-01-018, CBT-05-007, CBT-06-001, CBT-06-003
CM — Case Management CM-12-001, CM-14-011
HP — Handler Protocol HP-01-010, HP-01-030, HP-09-001, HP-09-002
IE — Inbox Endpoint IE-02-002, IE-02-003
LST — Lifecycle-Staged Domain Types LST-02-002
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-01-001
MV — Message Validation MV-01-001
RMB — Report Management Behavioral Requirements RMB-01-001, RMB-01-002
VP — Vultron Protocol VP-02-001, VP-03-002

story_2022_039

As a Participant I want to ask questions/generally communicate with another case Participant

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-07-001, ASK-07-003, ASK-07-004, ASK-07-005, ASK-07-007, ASK-07-010, ASK-07-012, ASK-07-013, ASK-07-014, ASK-07-015, ASK-07-019
BT — Behavior Tree Integration BT-10-003, BT-11-001
EMB — Embargo Management Behavioral Requirements EMB-08-001
HTTP — HTTP Protocol Requirements HTTP-01-003
IE — Inbox Endpoint IE-11-001, IE-11-004
MV — Message Validation MV-09-001, MV-10-001, MV-10-007, MV-10-008, MV-10-009, MV-10-011, MV-10-012, MV-10-013
PCR — Participant Case Replica PCR-08-005, PCR-08-011
RF — Response Format RF-01-001, RF-06-001
RMB — Report Management Behavioral Requirements RMB-07-001
RSH — Received-Side Status Authorization RSH-06-005
TB — Testability TB-03-001
TRIG — Triggerable Behaviors TRIG-07-001
VAM — Vultron Semantic–AS2 Mapping VAM-07-002
VM — Vocabulary Model VM-10-001, VM-10-002, VM-10-003, VM-10-004
VP — Vultron Protocol VP-03-012

story_2022_040

As a Participant I want to ask questions/generally communicate with another case Participant unicast/point-to-point

Spec file Citing requirements
HTTP — HTTP Protocol Requirements HTTP-01-001, HTTP-01-002, HTTP-01-004, HTTP-04-001
IE — Inbox Endpoint IE-11-001, IE-11-003, IE-11-004
RF — Response Format RF-06-001, RF-06-002

story_2022_041

As a Participant I want to ask questions/generally communicate with all the Participants in a case (broadcast)

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-06-001, ASK-06-003
CLP — Case Ledger Processing CLP-04-004
CM — Case Management CM-06-005, CM-14-013
IE — Inbox Endpoint IE-11-002
OX — Outbox OX-03-001
VP — Vultron Protocol VP-03-012, VP-10-003, VP-18-001

story_2022_042

As a Participant I want to ask questions/generally communicate with a subset of case Participants

Spec file Citing requirements
IE — Inbox Endpoint IE-11-003
OX — Outbox OX-03-001
VP — Vultron Protocol VP-05-007

story_2022_043

As a Participant, I want to communicate in a common case channel

Spec file Citing requirements
CM — Case Management CM-06-001
IE — Inbox Endpoint IE-11-002
OX — Outbox OX-03-001

story_2022_044

As a Participant I want to communicate with selected case Participants

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-06-002
IE — Inbox Endpoint IE-11-003
OX — Outbox OX-03-001
VP — Vultron Protocol VP-08-006

story_2022_045

As a Participant, I want to produce a shared verified public record of case activity

No mapped requirements (TRACE-01-002).

story_2022_046

As a Participant, I want the case to have a leader (global case owner, CVD leader)

Spec file Citing requirements
BT — Behavior Tree Integration BT-10-002, BT-10-007, BT-10-008, BT-19-003, BT-19-005
BTND — Behavior Tree Node Design BTND-05-001
CBT — Case Bootstrap Trust CBT-01-003, CBT-01-013, CBT-01-014, CBT-01-015, CBT-01-016
CFG — Configuration Management CFG-07-002
CLP — Case Ledger Processing CLP-09-001, CLP-09-004, CLP-10-001
CM — Case Management CM-02-003, CM-02-004, CM-14-001, CM-14-002, CM-14-009, CM-16-004, CM-16-016, CM-21-001, CM-21-023, CM-22-006
CP — CaseProposal Protocol CP-04-001, CP-04-003, CP-05-001, CP-09-001, CP-09-011
EMB — Embargo Management Behavioral Requirements EMB-15-013, EMB-19-001, EMB-19-003, EMB-19-004
EP — Embargo Policy EP-09-006
PCR — Participant Case Replica PCR-01-002, PCR-08-005
RSH — Received-Side Status Authorization RSH-01-001, RSH-01-002, RSH-04-001, RSH-04-005, RSH-04-007, RSH-04-012
SYNC — Case Event Log Synchronization SYNC-02-003, SYNC-06-001, SYNC-06-003, SYNC-09-003, SYNC-09-004, SYNC-13-005
VP — Vultron Protocol VP-08-003, VP-10-002, VP-13-019, VP-17-001

story_2022_047

As a Participant, I want to propose a case leader, possibly myself

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-01-001, ASK-01-005
CM — Case Management CM-02-004
RF — Response Format RF-02-001
VAM — Vultron Semantic–AS2 Mapping VAM-04-007
VP — Vultron Protocol VP-08-012

story_2022_048

As a Participant, I want to vote/accept a proposed case leader

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-01-004, ASK-03-001
CM — Case Management CM-02-005, CM-21-002, CM-21-024
RF — Response Format RF-02-001, RF-02-002, RF-02-004, RF-02-005, RF-03-001, RF-03-003
TRIG — Triggerable Behaviors TRIG-11-002
VAM — Vultron Semantic–AS2 Mapping VAM-04-008, VAM-04-009

story_2022_049

As a Participant I want to announce the case leader to all Participants

Spec file Citing requirements
CM — Case Management CM-21-007, CM-21-030
VP — Vultron Protocol VP-03-012

story_2022_050

As a Participant I want to transfer case leadership to a different Participant

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-02-003
CM — Case Management CM-02-004, CM-02-005, CM-21-001, CM-21-002, CM-21-003, CM-21-005, CM-21-006, CM-21-007, CM-21-008, CM-21-009, CM-21-010, CM-21-011, CM-21-012, CM-21-013, CM-21-014, CM-21-015, CM-21-016, CM-21-017, CM-21-019, CM-21-021, CM-21-022, CM-21-023, CM-21-024, CM-21-025, CM-21-026, CM-21-027, CM-21-028, CM-21-029, CM-21-030, CM-21-031, CM-21-032, CM-21-033, CM-21-034, CM-21-035, CM-21-036, CM-21-037, CM-21-038, CM-21-039, CM-21-040, CM-21-041, CM-21-043, CM-21-044, CM-21-045, CM-21-046, CM-24-007, CM-24-016, CM-24-017, CM-24-018, CM-24-019
RF — Response Format RF-02-001
TRIG — Triggerable Behaviors TRIG-11-001, TRIG-11-002, TRIG-11-005, TRIG-11-006, TRIG-11-007
VAM — Vultron Semantic–AS2 Mapping VAM-03-007, VAM-04-007, VAM-04-008, VAM-04-009, VAM-04-015, VAM-04-018, VAM-06-005

story_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

Spec file Citing requirements
CM — Case Management CM-02-004, CM-21-003, CM-21-008, CM-21-009
RF — Response Format RF-02-001
VP — Vultron Protocol VP-08-011

story_2022_052

As a Participant I want to add (declare and notify others) new Participants to a case

Spec file Citing requirements
BTND — Behavior Tree Node Design BTND-05-003
CBT — Case Bootstrap Trust CBT-01-004
CM — Case Management CM-11-001, CM-11-006, CM-11-007, CM-11-013, CM-11-014, CM-11-015, CM-11-018, CM-11-019, CM-11-021, CM-11-023, CM-11-024, CM-11-025, CM-11-026, CM-11-027, CM-11-028, CM-11-038, CM-11-039, CM-11-040, CM-11-042, CM-11-043, CM-11-048, CM-11-049, CM-11-050, CM-11-052, CM-14-007, CM-16-001, CM-16-006, CM-17-004, CM-17-009, CM-20-001, CM-31-005, CM-31-006, CM-31-007, CM-31-011, CM-31-012, CM-31-024, CM-31-025, CM-31-026, CM-31-027, CM-31-028, CM-31-029, CM-31-034, CM-31-035, CM-31-036, CM-31-037, CM-31-038, CM-31-039, CM-31-040, CM-31-041, CM-31-043, CM-31-044, CM-31-045
PCR — Participant Case Replica PCR-08-007, PCR-08-008
VAM — Vultron Semantic–AS2 Mapping VAM-04-004
VP — Vultron Protocol VP-05-004, VP-05-015, VP-08-001, VP-08-004, VP-08-005, VP-08-008, VP-08-009

story_2022_053

As a Participant, I want to propose new Participants to a case

Spec file Citing requirements
AKM — Actor Knowledge Model AKM-02-001, AKM-02-003, AKM-02-006, AKM-02-008, AKM-03-001, AKM-05-005, AKM-05-017, AKM-05-018, AKM-05-019
ASK — Protocol Asks and Outstanding-Ask Registers ASK-01-001, ASK-01-004, ASK-01-005, ASK-02-003, ASK-02-005, ASK-02-006, ASK-08-001
CM — Case Management CM-16-001, CM-16-002, CM-16-004, CM-16-005, CM-16-008, CM-16-009, CM-16-010, CM-16-016, CM-16-018, CM-16-020, CM-17-001, CM-20-002, CM-20-003, CM-20-006, CM-20-007, CM-20-008, CM-20-009, CM-25-002, CM-25-006
PCR — Participant Case Replica PCR-08-007, PCR-08-019
VAM — Vultron Semantic–AS2 Mapping VAM-04-001, VAM-04-010
VP — Vultron Protocol VP-08-001, VP-08-004, VP-08-012

story_2022_054

As a Participant I want to vote/accept new Participants to a case

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-04-003, CBT-05-004
CM — Case Management CM-11-001, CM-11-004, CM-11-017, CM-16-006, CM-16-007, CM-16-018, CM-16-019, CM-16-021, CM-16-023, CM-17-001, CM-17-004, CM-25-002
PCR — Participant Case Replica PCR-08-008, PCR-08-009, PCR-08-012, PCR-08-020
RF — Response Format RF-02-001, RF-02-002, RF-02-004, RF-02-005, RF-03-001, RF-03-003
VAM — Vultron Semantic–AS2 Mapping VAM-04-002, VAM-04-003, VAM-04-005, VAM-04-011, VAM-04-012, VAM-04-016, VAM-04-017
VP — Vultron Protocol VP-08-015

story_2022_055

As a Participant, I want to state that I paid or received a bounty

No mapped requirements (TRACE-01-002).

story_2022_056

As a Participant, I want to ask if another Participant paid a reporter

No mapped requirements (TRACE-01-002).

story_2022_057

As a Participant, I want to ask a reporter if they were paid

No mapped requirements (TRACE-01-002).

story_2022_058

As a Participant I want to share a draft advisory with others

Spec file Citing requirements
RF — Response Format RF-01-001
VP — Vultron Protocol VP-05-006

story_2022_059

As a Participant I want to share a draft advisory with others and request feedback (including status)

Spec file Citing requirements
RF — Response Format RF-02-001, RF-08-001
VP — Vultron Protocol VP-05-006

story_2022_060

As a Participant I want to request advisory (draft) from a Participant

Spec file Citing requirements
RF — Response Format RF-01-001
VP — Vultron Protocol VP-03-012

story_2022_061

As a Participant, I want to request someone else’s (vendor) status so I can note changes in others status

Spec file Citing requirements
CM — Case Management CM-07-002, CM-11-006, CM-11-009, CM-11-026, CM-11-029
PRM — Participant Role Management PRM-06-003, PRM-06-004, PRM-06-007, PRM-06-008
VP — Vultron Protocol VP-01-001, VP-01-002, VP-03-012

story_2022_062

As a Participant, I want to state my status so others are aware of it.

Spec file Citing requirements
CM — Case Management CM-04-002, CM-11-011
CSB — CVD Case State Behavioral Requirements CSB-01-001, CSB-09-002, CSB-10-002, CSB-11-002
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-03-001, MSM-03-002
PRM — Participant Role Management PRM-06-001, PRM-06-002, PRM-06-006
RMB — Report Management Behavioral Requirements RMB-10-003, RMB-11-001, RMB-12-001, RMB-13-002, RMB-14-001
RSH — Received-Side Status Authorization RSH-08-001, RSH-08-007, RSH-08-008, RSH-08-009, RSH-08-014
SDO — Status Dimension Objects SDO-03-001
VAM — Vultron Semantic–AS2 Mapping VAM-08-002, VAM-08-004
VP — Vultron Protocol VP-02-010, VP-02-017, VP-02-018, VP-02-019, VP-02-027, VP-02-031, VP-02-035, VP-03-005, VP-03-006, VP-03-007, VP-03-012, VP-13-008

story_2022_063

As a Participant, I want to include a non-vendor role Participant in a case

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-05-005
CM — Case Management CM-14-012, CM-20-001, CM-20-002, CM-20-003, CM-20-006, CM-20-007, CM-20-008, CM-20-009, CM-25-001, CM-25-002, CM-25-003, CM-25-005, CM-25-006, CM-25-007, CM-26-001
CP — CaseProposal Protocol CP-01-011, CP-01-012, CP-09-007, CP-09-008
PRM — Participant Role Management PRM-01-001, PRM-01-002, PRM-02-001, PRM-02-002, PRM-02-004, PRM-02-005
VP — Vultron Protocol VP-08-004, VP-08-014

story_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.

Spec file Citing requirements
VP — Vultron Protocol VP-08-014

story_2022_065

As a Participant, I want to include the Industry/trade group so that they may participate in the case.

Spec file Citing requirements
VP — Vultron Protocol VP-08-014

story_2022_066

As a Participant, I want to stop participating in the case.

Spec file Citing requirements
CM — Case Management CM-04-007, CM-04-011, CM-23-001, CM-23-002, CM-23-003, CM-23-010, CM-23-011, CM-23-012, CM-23-013, CM-23-014, CM-23-015, CM-23-016, CM-23-018, CM-23-019, CM-23-021, CM-23-022, CM-23-023, CM-23-024, CM-23-025, CM-23-026, CM-23-027, CM-23-029, CM-23-030, CM-23-034, CM-23-035, CM-23-036, CM-23-037, CM-23-038, CM-23-039, CM-23-040, CM-23-041, CM-23-042, CM-23-043, CM-23-044, CM-23-048, CM-23-049, CM-23-050, CM-23-051, CM-23-052, CM-23-053
EMB — Embargo Management Behavioral Requirements EMB-11-003, EMB-11-004, EMB-12-002
PRM — Participant Role Management PRM-02-004, PRM-02-005
RMB — Report Management Behavioral Requirements RMB-06-002, RMB-11-004, RMB-14-006
VAM — Vultron Semantic–AS2 Mapping VAM-02-006, VAM-03-006, VAM-04-014, VAM-06-003
VP — Vultron Protocol VP-05-010, VP-05-011, VP-05-012, VP-05-018, VP-13-017, VP-13-018

story_2022_067

As a Participant, I want to stop participating in the case and inform others that I am no longer participating.

Spec file Citing requirements
CM — Case Management CM-23-001, CM-23-002, CM-23-003, CM-23-019, CM-23-021, CM-23-022, CM-23-023, CM-23-024, CM-23-025, CM-23-026, CM-23-030, CM-23-051, CM-23-052, CM-23-053
RMB — Report Management Behavioral Requirements RMB-14-003
VAM — Vultron Semantic–AS2 Mapping VAM-03-006, VAM-06-003
VP — Vultron Protocol VP-05-010, VP-05-011, VP-13-005, VP-13-006, VP-13-007, VP-13-009

story_2022_068

As a Participant, I want to stop participating in the case and no longer will receive or reply to forwarded queries.

Spec file Citing requirements
CM — Case Management CM-23-004, CM-23-031, CM-23-032
RMB — Report Management Behavioral Requirements RMB-14-002
VP — Vultron Protocol VP-03-013, VP-05-010, VP-05-012

story_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.

Spec file Citing requirements
CM — Case Management CM-04-004, CM-05-004, CM-05-005, CM-05-007, CM-05-011, CM-05-012, CM-05-021, CM-34-003
CSB — CVD Case State Behavioral Requirements CSB-04-001, CSB-15-003, CSB-15-011
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-03-004
VP — Vultron Protocol VP-03-012, VP-09-001, VP-12-001

story_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.

Spec file Citing requirements
VP — Vultron Protocol VP-05-006, VP-16-001

story_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.

Spec file Citing requirements
VP — Vultron Protocol VP-05-006, VP-16-001

story_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.

Spec file Citing requirements
EP — Embargo Policy EP-01-002
VP — Vultron Protocol VP-05-007

story_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.

Spec file Citing requirements
EP — Embargo Policy EP-01-003

story_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.

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-02-003, ASK-03-002, ASK-03-004, ASK-03-008, ASK-05-004, ASK-05-005, ASK-07-007, ASK-07-008
BT — Behavior Tree Integration BT-03-001, BT-03-004, BT-07-003
CLP — Case Ledger Processing CLP-02-001, CLP-02-006, CLP-02-008, CLP-03-001, CLP-09-003, CLP-09-005, CLP-14-011, CLP-14-013, CLP-15-008, CLP-15-009
CM — Case Management CM-02-009, CM-02-018, CM-10-002, CM-23-005, CM-23-007, CM-23-033, CM-28-005, CM-28-009, CM-28-022
CP — CaseProposal Protocol CP-06-003, CP-06-004, CP-06-005, CP-06-006
CSB — CVD Case State Behavioral Requirements CSB-05-010, CSB-06-010, CSB-16-001, CSB-16-002, CSB-16-005, CSB-16-007, CSB-17-001, CSB-17-002, CSB-17-005, CSB-17-006, CSB-17-007, CSB-17-008, CSB-17-010, CSB-17-011, CSB-17-014, CSB-17-015
DUR — Duration DUR-07-001, DUR-07-003, DUR-07-004
EP — Embargo Policy EP-07-005
HP — Handler Protocol HP-00-002
RMB — Report Management Behavioral Requirements RMB-10-004
RSH — Received-Side Status Authorization RSH-06-001, RSH-06-002, RSH-06-003, RSH-06-004, RSH-06-005, RSH-06-006, RSH-06-007
SM — State Machine SM-05-002, SM-06-002, SM-10-001
SYNC — Case Event Log Synchronization SYNC-01-001, SYNC-01-002
TRIG — Triggerable Behaviors TRIG-10-001, TRIG-10-005
VAM — Vultron Semantic–AS2 Mapping VAM-07-002, VAM-07-003
VP — Vultron Protocol VP-01-001, VP-01-002, VP-02-026, VP-02-032, VP-05-001, VP-05-003

story_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.

Spec file Citing requirements
CLP — Case Ledger Processing CLP-15-010
CM — Case Management CM-03-002, CM-29-004, CM-29-005, CM-29-007
RMB — Report Management Behavioral Requirements RMB-02-001, RMB-03-001, RMB-04-001, RMB-05-001, RMB-06-001
VAM — Vultron Semantic–AS2 Mapping VAM-08-004
VP — Vultron Protocol VP-01-001, VP-01-002, VP-03-012

story_2022_076

As a VDP operator, I want the CVD protocol to also support VDP

Spec file Citing requirements
EP — Embargo Policy EP-01-001
VP — Vultron Protocol VP-02-001

story_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.

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-07-001, ASK-07-010, ASK-07-014, ASK-07-015, ASK-07-019
RMB — Report Management Behavioral Requirements RMB-09-002, RMB-11-003
RSH — Received-Side Status Authorization RSH-06-003, RSH-06-004, RSH-06-005, RSH-06-007
VP — Vultron Protocol VP-02-012, VP-02-025, VP-03-008, VP-03-011

story_2022_078

As a coordinator, I want to drive better (shorter?) embargo timelines, to ensure they are feasible.

Spec file Citing requirements
EP — Embargo Policy EP-09-006
VP — Vultron Protocol VP-05-002, VP-05-008, VP-05-009, VP-05-021, VP-08-003

story_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.

Spec file Citing requirements
EP — Embargo Policy EP-04-003, EP-04-011, EP-04-016, EP-04-024, EP-04-025, EP-04-026, EP-04-027, EP-09-006
VP — Vultron Protocol VP-07-001, VP-07-003, VP-07-004, VP-07-005, VP-07-008, VP-07-009, VP-07-014, VP-08-003

story_2022_080

As a Participant, I want to publicly disclose sooner than others but minimize their (the others) exposure/risk

Spec file Citing requirements
EMB — Embargo Management Behavioral Requirements EMB-03-003, EMB-03-004, EMB-04-002, EMB-05-002, EMB-13-004, EMB-13-005, EMB-13-009, EMB-13-010, EMB-13-011, EMB-13-012, EMB-13-013, EMB-13-014, EMB-13-015, EMB-13-016, EMB-13-017, EMB-14-001, EMB-14-005, EMB-14-006, EMB-16-001, EMB-16-003, EMB-16-004, EMB-16-005
VAM — Vultron Semantic–AS2 Mapping VAM-05-011, VAM-05-013, VAM-05-014, VAM-05-015, VAM-05-016
VP — Vultron Protocol VP-05-020, VP-14-011, VP-14-012, VP-14-014

story_2022_081

As a Participant I want to communicate important public state change message/information with all Participants.

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-01-001
CM — Case Management CM-14-004
CSB — CVD Case State Behavioral Requirements CSB-04-001, CSB-04-002, CSB-04-003, CSB-05-001, CSB-06-001, CSB-12-001, CSB-12-003, CSB-12-004, CSB-12-005, CSB-13-001, CSB-13-006
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-03-001, MSM-03-002, MSM-03-003, MSM-03-004, MSM-03-005, MSM-03-006
RMB — Report Management Behavioral Requirements RMB-01-002
RSH — Received-Side Status Authorization RSH-03-001, RSH-03-003, RSH-03-004, RSH-03-005, RSH-03-006, RSH-04-003, RSH-07-001, RSH-07-006, RSH-09-009
SM — State Machine SM-10-002
SYNC — Case Event Log Synchronization SYNC-09-002
TRIG — Triggerable Behaviors TRIG-07-001
VAM — Vultron Semantic–AS2 Mapping VAM-05-004, VAM-08-002
VP — Vultron Protocol VP-03-012, VP-12-001

story_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.

Spec file Citing requirements
CM — Case Management CM-25-003, CM-25-004
VP — Vultron Protocol VP-03-012, VP-08-004, VP-08-014

story_2022_083

As a Participant, I want to contribute to the creation, modification and publication of an advisory.

Spec file Citing requirements
CM — Case Management CM-02-007, CM-06-005
VP — Vultron Protocol VP-05-020

story_2022_084

As a vendor I want to reward the reporter by paying a bounty.

No mapped requirements (TRACE-01-002).

story_2022_085

As a reporter I want to be rewarded with a bounty.

No mapped requirements (TRACE-01-002).

story_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

Spec file Citing requirements
AR — Agentic Readiness AR-07-002
CM — Case Management CM-07-003
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-01-004
RMB — Report Management Behavioral Requirements RMB-10-001, RMB-10-002, RMB-13-003
TRIG — Triggerable Behaviors TRIG-05-001
VAM — Vultron Semantic–AS2 Mapping VAM-03-004
VP — Vultron Protocol VP-02-002, VP-02-004, VP-02-014, VP-02-024, VP-02-029, VP-02-030, VP-02-034, VP-02-036, VP-14-004

story_2022_087

As a Participant I want to share and receive information I can use to prioritize my work regarding the vulnerability report.

Spec file Citing requirements
RMB — Report Management Behavioral Requirements RMB-10-001, RMB-12-002
VP — Vultron Protocol VP-01-001, VP-02-014, VP-02-024

story_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 (TRACE-01-002).

story_2022_089

As a Participant I want a mechanism which with assure me of the authentication and verify integrity of messages.

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-01-005, CBT-01-011, CBT-01-017, CBT-05-002
CLP — Case Ledger Processing CLP-03-002, CLP-04-003, CLP-07-003, CLP-07-017, CLP-08-001, CLP-08-002
CM — Case Management CM-06-002, CM-06-004, CM-24-001, CM-24-002, CM-24-020, CM-24-021
CS — Code Style Specifications CS-13-007
ENC — Encryption ENC-01-001, ENC-01-002
IE — Inbox Endpoint IE-04-001, IE-04-002
PCR — Participant Case Replica PCR-03-001, PCR-03-003, PCR-03-007, PCR-03-008, PCR-03-009, PCR-03-010, PCR-08-010
SIG — Signing SIG-01-001, SIG-01-002, SIG-01-003, SIG-02-001, SIG-02-003, SIG-02-004, SIG-03-001, SIG-03-002, SIG-04-001, SIG-04-002
SYNC — Case Event Log Synchronization SYNC-01-003, SYNC-01-007, SYNC-01-008, SYNC-02-002, SYNC-08-001, SYNC-08-006
TB — Testability TB-03-002
VP — Vultron Protocol VP-15-004, VP-15-005

story_2022_090

As a Participant we need a mechanism which will ensure the appropriate level of authentication of all Participants

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-01-001, CBT-01-002, CBT-01-005, CBT-01-010, CBT-01-011, CBT-01-019, CBT-03-003, CBT-04-001, CBT-04-002, CBT-05-001, CBT-05-002, CBT-05-003, CBT-05-004
CM — Case Management CM-06-004
ENC — Encryption ENC-01-001, ENC-01-005, ENC-01-006
PCR — Participant Case Replica PCR-03-003
SIG — Signing SIG-03-002
VP — Vultron Protocol VP-15-002

story_2022_091

As a Participant we need a mechanism which will ensure the confidential transport and storage of information.

Spec file Citing requirements
ENC — Encryption ENC-01-004, ENC-01-005, ENC-01-006, ENC-01-007, ENC-02-001, ENC-02-002
VP — Vultron Protocol VP-15-004

story_2022_092

As a Participant, I want to know who else is participating in a case to ensure I don't void an embargo.

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-01-003, CBT-01-007, CBT-01-013, CBT-01-014, CBT-01-016, CBT-04-002, CBT-05-006
CM — Case Management CM-19-001
PCR — Participant Case Replica PCR-01-001, PCR-02-002, PCR-02-006, PCR-04-002
VP — Vultron Protocol VP-01-001, VP-08-004, VP-08-009

story_2022_093

As a Participant, in an effort to ensure the Participant list is complete I want to know who else is participating.

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-05-006
CM — Case Management CM-19-001, CM-19-002, CM-19-003, CM-19-004
CP — CaseProposal Protocol CP-09-007
VP — Vultron Protocol VP-01-001, VP-08-004, VP-08-009

story_2022_094

As a Participant, I want to assess reputation of others so that I can decide to engage again

Spec file Citing requirements
VP — Vultron Protocol VP-05-013, VP-08-010, VP-08-021

story_2022_095

As a Participant, I want to provide evidence of/document my reputation to others so they can decide to engage with me

Spec file Citing requirements
EP — Embargo Policy EP-01-001
VP — Vultron Protocol VP-05-013

story_2022_096

As a Participant, I want to record/log my trust in/reputation of others so I can decide to engage again

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-01-006, CBT-06-002, CBT-06-004
VP — Vultron Protocol VP-05-013, VP-08-010

story_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.

Spec file Citing requirements
VP — Vultron Protocol VP-08-004, VP-08-012, VP-08-014

story_2022_098

As a Participant I want to communicate with all Participants associated with this case.

Spec file Citing requirements
CM — Case Management CM-06-001
OX — Outbox OX-03-001
VP — Vultron Protocol VP-03-012

story_2022_099

As a Participant I want to communicate with non-vendor Participants, primarily other defenders, providers, CSIRTs, regulators, etc., important information.

Spec file Citing requirements
OX — Outbox OX-03-001
VP — Vultron Protocol VP-08-014

story_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

Spec file Citing requirements
OX — Outbox OX-03-001
VP — Vultron Protocol VP-12-001

story_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

Spec file Citing requirements
BT — Behavior Tree Integration BT-10-001
CP — CaseProposal Protocol CP-01-006, CP-05-002, CP-05-008, CP-05-014, CP-05-018, CP-05-019
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-01-002, MSM-01-003, MSM-01-006
VAM — Vultron Semantic–AS2 Mapping VAM-02-005, VAM-04-013
VP — Vultron Protocol VP-02-006, VP-02-007, VP-02-008, VP-02-009, VP-02-010, VP-02-022, VP-02-023, VP-02-025, VP-02-033, VP-03-003, VP-03-004

story_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

Spec file Citing requirements
CM — Case Management CM-05-002
TRIG — Triggerable Behaviors TRIG-10-001, TRIG-10-005
VP — Vultron Protocol VP-02-025, VP-02-028

story_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.

Spec file Citing requirements
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-03-003
VP — Vultron Protocol VP-02-011, VP-02-013

story_2022_104

As a Participant, I want to address multiple related vulnerabilities across multiple vendors simultaneously.

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-06-002, CBT-06-004
CM — Case Management CM-05-006, CM-05-017, CM-32-001, CM-32-002, CM-32-003, CM-32-004, CM-32-005, CM-32-006, CM-32-009, CM-32-010, CM-32-011, CM-32-012, CM-32-016, CM-32-017, CM-32-018, CM-32-019, CM-32-020, CM-32-021, CM-32-022, CM-32-023, CM-32-024, CM-32-025, CM-32-030, CM-32-031, CM-32-032, CM-32-033, CM-32-034, CM-32-035, CM-32-036, CM-32-037, CM-32-038, CM-32-039, CM-32-045
VAM — Vultron Semantic–AS2 Mapping VAM-03-005
VP — Vultron Protocol VP-08-004, VP-08-007, VP-08-020, VP-09-005, VP-09-007, VP-10-001, VP-10-002, VP-10-003, VP-10-004, VP-10-005, VP-10-006, VP-10-007, VP-10-008, VP-14-009

story_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.

Spec file Citing requirements
CM — Case Management CM-05-006, CM-32-001, CM-32-007, CM-32-008, CM-32-013, CM-32-014, CM-32-015, CM-32-017, CM-32-026, CM-32-027, CM-32-028, CM-32-029, CM-32-040, CM-32-041, CM-32-042, CM-32-043, CM-32-044
VP — Vultron Protocol VP-10-001, VP-10-004, VP-14-014

story_2022_106

As a Participant, I want the coordination process to be decentralized so that it is robust against individual Participant actions.

Spec file Citing requirements
AKM — Actor Knowledge Model AKM-01-003
BT — Behavior Tree Integration BT-09-001
CLP — Case Ledger Processing CLP-01-003, CLP-02-011
CM — Case Management CM-02-014, CM-24-014
EDF — Event-Driven Control Flow EDF-03-001, EDF-03-004
MV — Message Validation MV-09-001
PCR — Participant Case Replica PCR-03-005
RSH — Received-Side Status Authorization RSH-09-006, RSH-09-013
SYNC — Case Event Log Synchronization SYNC-01-004, SYNC-06-003, SYNC-08-002, SYNC-09-003, SYNC-09-004
TRIG — Triggerable Behaviors TRIG-06-001
VP — Vultron Protocol VP-01-003, VP-15-001, VP-15-002, VP-18-003

story_2022_107

As a Vendor, I want to convey the vulnerability status of my component(s), product(s), or service(s) to other Participants.

Spec file Citing requirements
BTND — Behavior Tree Node Design BTND-10-001
CM — Case Management CM-03-001, CM-03-004, CM-03-005, CM-04-001, CM-04-002
CSB — CVD Case State Behavioral Requirements CSB-02-001, CSB-03-001, CSB-15-001, CSB-15-002, CSB-15-003, CSB-15-007, CSB-15-009, CSB-15-011
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-03-002, MSM-03-003
PRM — Participant Role Management PRM-06-005
RMB — Report Management Behavioral Requirements RMB-01-003
RSH — Received-Side Status Authorization RSH-09-003
SDO — Status Dimension Objects SDO-03-002
SM — State Machine SM-10-001
VP — Vultron Protocol VP-02-019, VP-03-012, VP-12-001

story_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

Spec file Citing requirements
VP — Vultron Protocol VP-09-001, VP-12-001

story_2022_109

As a Vendor, I want to convey the reason my component is not affected by a vulnerability to other Participants

Spec file Citing requirements
VP — Vultron Protocol VP-03-003, VP-03-012

story_2022_110

As a Vendor, I want to convey the reason my component is not affected by a vulnerability to Users / the Public

Spec file Citing requirements
VP — Vultron Protocol VP-12-001

story_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.

Spec file Citing requirements
CM — Case Management CM-05-006
RMB — Report Management Behavioral Requirements RMB-01-002
VP — Vultron Protocol VP-02-011, VP-02-015, VP-02-025

story_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

Spec file Citing requirements
CM — Case Management CM-10-001, CM-18-001, CM-18-003, CM-18-004, CM-18-019, CM-18-020, CM-18-021
EMB — Embargo Management Behavioral Requirements EMB-13-001, EMB-17-005, EMB-17-006, EMB-17-007, EMB-17-008
EP — Embargo Policy EP-06-001, EP-09-004
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-07-002, MSM-07-003, MSM-07-004, MSM-07-005, MSM-07-007, MSM-07-017, MSM-07-018
VAM — Vultron Semantic–AS2 Mapping VAM-05-014, VAM-05-015

story_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

Spec file Citing requirements
AKM — Actor Knowledge Model AKM-01-002
CLP — Case Ledger Processing CLP-01-004, CLP-04-007, CLP-05-003, CLP-07-004, CLP-10-004
PCR — Participant Case Replica PCR-03-002, PCR-08-002
VP — Vultron Protocol VP-10-002, VP-18-002

story_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 (TRACE-01-002).

story_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

Spec file Citing requirements
EMB — Embargo Management Behavioral Requirements EMB-15-001, EMB-15-005
RMB — Report Management Behavioral Requirements RMB-12-003

story_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

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-03-001
CLP — Case Ledger Processing CLP-04-005, CLP-07-012, CLP-14-012
CM — Case Management CM-04-005
CSB — CVD Case State Behavioral Requirements CSB-19-001, CSB-19-002, CSB-19-003
PCR — Participant Case Replica PCR-06-001, PCR-06-002
SYNC — Case Event Log Synchronization SYNC-10-003, SYNC-10-005, SYNC-15-002, SYNC-15-006, SYNC-15-007, SYNC-17-008
VP — Vultron Protocol VP-17-002

story_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

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-03-007, ASK-04-010, ASK-04-013
CP — CaseProposal Protocol CP-05-007
CSB — CVD Case State Behavioral Requirements CSB-08-001
EMB — Embargo Management Behavioral Requirements EMB-09-001
RMB — Report Management Behavioral Requirements RMB-02-002, RMB-03-002, RMB-04-002, RMB-05-002, RMB-06-003, RMB-07-002, RMB-08-002

story_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 (TRACE-01-002).

story_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 (TRACE-01-002).

story_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 (TRACE-01-002).

story_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

Spec file Citing requirements
RF — Response Format RF-04-001, RF-04-003

story_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

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-01-009
CLP — Case Ledger Processing CLP-01-002, CLP-02-014
CM — Case Management CM-03-007
EP — Embargo Policy EP-09-009
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-03-001, MSM-05-001, MSM-05-002, MSM-05-003, MSM-05-006, MSM-07-001
RF — Response Format RF-05-001
SM — State Machine SM-08-001
VAM — Vultron Semantic–AS2 Mapping VAM-01-008, VAM-08-002, VAM-08-004
VP — Vultron Protocol VP-03-010, VP-11-004

story_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

Spec file Citing requirements
CS — Code Style Specifications CS-13-005, CS-13-007
DUR — Duration DUR-01-001, DUR-01-002, DUR-01-003, DUR-02-001, DUR-02-002, DUR-03-001, DUR-03-003, DUR-04-001, DUR-04-002, DUR-04-003, DUR-04-004
VM — Vocabulary Model VM-03-005

story_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

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-05-008
MV — Message Validation MV-03-001, MV-03-002, MV-04-001, MV-10-002
VM — Vocabulary Model VM-03-006, VM-03-007, VM-09-001

story_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

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-08-002
CLP — Case Ledger Processing CLP-05-004, CLP-06-001
CM — Case Management CM-13-005, CM-16-017, CM-33-018
CP — CaseProposal Protocol CP-05-006, CP-05-013, CP-05-015
CSB — CVD Case State Behavioral Requirements CSB-04-004, CSB-05-005, CSB-06-005
EMB — Embargo Management Behavioral Requirements EMB-07-003
EP — Embargo Policy EP-06-001
RF — Response Format RF-09-001
RMB — Report Management Behavioral Requirements RMB-01-004
RSH — Received-Side Status Authorization RSH-08-002
SYNC — Case Event Log Synchronization SYNC-03-003, SYNC-08-003, SYNC-12-003, SYNC-13-004, SYNC-13-009, SYNC-14-007

story_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

Spec file Citing requirements
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-05-005
OX — Outbox OX-14-002
SYNC — Case Event Log Synchronization SYNC-09-002
VM — Vocabulary Model VM-08-003

story_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

Spec file Citing requirements
AKM — Actor Knowledge Model AKM-02-002
CM — Case Management CM-11-003
OID — Object ID OID-01-001

story_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 (TRACE-01-002).

story_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

Spec file Citing requirements
BT — Behavior Tree Integration BT-07-003
MV — Message Validation MV-04-002

story_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

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-03-003
SYNC — Case Event Log Synchronization SYNC-05-001, SYNC-05-004, SYNC-05-005

story_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

Spec file Citing requirements
SE — Semantic Extraction SE-08-003

story_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 (TRACE-01-002).

story_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

Spec file Citing requirements
CSB — CVD Case State Behavioral Requirements CSB-15-004, CSB-17-001, CSB-17-002, CSB-17-003, CSB-17-004, CSB-17-005, CSB-17-006, CSB-17-007, CSB-17-008, CSB-17-009, CSB-17-010, CSB-17-011, CSB-17-012, CSB-17-013, CSB-17-014, CSB-17-015, CSB-18-001
SM — State Machine SM-09-002

story_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

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-07-009
CLP — Case Ledger Processing CLP-01-003, CLP-02-009, CLP-02-018, CLP-04-001, CLP-04-003, CLP-04-007, CLP-08-007, CLP-09-001, CLP-09-004, CLP-14-004, CLP-14-007, CLP-14-008, CLP-14-014, CLP-14-015
CM — Case Management CM-20-004, CM-20-005, CM-22-003
RSH — Received-Side Status Authorization RSH-08-006
SYNC — Case Event Log Synchronization SYNC-01-003, SYNC-01-004, SYNC-01-005, SYNC-01-007, SYNC-01-008, SYNC-08-001, SYNC-08-006, SYNC-13-005

story_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

Spec file Citing requirements
DUR — Duration DUR-06-001, DUR-06-002, DUR-06-003, DUR-07-001
VP — Vultron Protocol VP-04-001

story_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 (TRACE-01-002).

story_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 (TRACE-01-002).

story_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 (TRACE-01-002).

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-02-008, CLP-02-011, CLP-14-001, CLP-14-002, CLP-14-003, CLP-14-005, CLP-14-006, CLP-14-010, CLP-15-005
CM — Case Management CM-02-009

story_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

Spec file Citing requirements
BT — Behavior Tree Integration BT-11-001
CLP — Case Ledger Processing CLP-15-001, CLP-15-002, CLP-15-003, CLP-15-004, CLP-15-006, CLP-15-007, CLP-15-011

story_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

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-01-006, CBT-01-010, CBT-02-002, CBT-03-002, CBT-05-001, CBT-05-003
CM — Case Management CM-06-002, CM-30-003, CM-30-005, CM-33-004
PCR — Participant Case Replica PCR-03-001, PCR-03-004, PCR-03-007, PCR-03-008, PCR-03-009, PCR-03-010, PCR-06-003, PCR-06-006
RSH — Received-Side Status Authorization RSH-04-005, RSH-04-012

story_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

Spec file Citing requirements
CM — Case Management CM-01-002, CM-03-002, CM-03-003, CM-03-004, CM-03-005, CM-04-006, CM-04-010
SDO — Status Dimension Objects SDO-03-001, SDO-03-002
SM — State Machine SM-10-002, SM-10-003, SM-10-004

story_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

Spec file Citing requirements
CM — Case Management CM-05-001, CM-05-015

story_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

Spec file Citing requirements
CSB — CVD Case State Behavioral Requirements CSB-04-005, CSB-04-007, CSB-05-006, CSB-06-006, CSB-10-001, CSB-11-001, CSB-12-002, CSB-13-002, CSB-13-003, CSB-14-001, CSB-14-003, CSB-18-002, CSB-18-003, CSB-18-004
EMB — Embargo Management Behavioral Requirements EMB-01-002, EMB-02-002, EMB-02-004, EMB-13-002, EMB-15-010
EP — Embargo Policy EP-09-021
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-07-032
VAM — Vultron Semantic–AS2 Mapping VAM-05-013

story_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

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-02-004, ASK-03-003, ASK-03-006, ASK-03-009
CLP — Case Ledger Processing CLP-11-001
CM — Case Management CM-33-005, CM-33-016, CM-33-017

story_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

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-07-002, ASK-07-006

story_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

Spec file Citing requirements
CM — Case Management CM-06-003
CP — CaseProposal Protocol CP-06-001, CP-06-002, CP-06-003, CP-06-004
CSB — CVD Case State Behavioral Requirements CSB-01-001, CSB-02-001, CSB-03-001, CSB-04-001, CSB-05-001, CSB-05-004, CSB-06-001, CSB-06-004
HP — Handler Protocol HP-00-002
SM — State Machine SM-05-002
TB — Testability TB-03-003
VP — Vultron Protocol VP-01-001, VP-01-002

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-10-015, CLP-10-016
RSH — Received-Side Status Authorization RSH-08-008
SM — State Machine SM-10-001

story_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

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-02-005, ASK-02-006
BTND — Behavior Tree Node Design BTND-10-001
CSB — CVD Case State Behavioral Requirements CSB-16-001, CSB-16-002, CSB-16-005, CSB-16-007
RSH — Received-Side Status Authorization RSH-08-012, RSH-08-013
SDO — Status Dimension Objects SDO-02-001, SDO-02-002, SDO-02-004

story_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

Spec file Citing requirements
RSH — Received-Side Status Authorization RSH-06-001, RSH-06-002, RSH-06-006, RSH-08-009, RSH-09-003, RSH-09-004, RSH-09-005, RSH-09-006, RSH-09-012, RSH-09-013
SM — State Machine SM-09-004

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-01-001, CLP-02-005, CLP-05-001, CLP-05-005, CLP-05-006, CLP-05-007, CLP-05-008, CLP-05-009
CSB — CVD Case State Behavioral Requirements CSB-07-001
RSH — Received-Side Status Authorization RSH-09-001, RSH-09-002, RSH-09-010, RSH-09-011

story_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

Spec file Citing requirements
RSH — Received-Side Status Authorization RSH-01-001, RSH-01-002, RSH-01-003, RSH-01-005, RSH-04-002, RSH-04-003, RSH-04-004, RSH-04-009

story_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

Spec file Citing requirements
CM — Case Management CM-23-005, CM-23-006, CM-23-007, CM-23-008, CM-23-009, CM-23-010, CM-23-033

story_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

Spec file Citing requirements
CM — Case Management CM-11-001, CM-11-004
PCR — Participant Case Replica PCR-08-009

story_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

Spec file Citing requirements
AR — Agentic Readiness AR-07-001, AR-07-002
CM — Case Management CM-07-002, CM-07-003

story_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

Spec file Citing requirements
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-05-007, MSM-05-008, MSM-05-009, MSM-05-010
RF — Response Format RF-08-004
SYNC — Case Event Log Synchronization SYNC-02-002, SYNC-02-004, SYNC-02-006, SYNC-02-007, SYNC-02-008, SYNC-02-009, SYNC-02-010, SYNC-03-001, SYNC-08-004, SYNC-08-005, SYNC-08-007, SYNC-14-002, SYNC-15-001, SYNC-16-001, SYNC-16-007, SYNC-16-027, SYNC-16-028

story_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

Spec file Citing requirements
SYNC — Case Event Log Synchronization SYNC-03-006, SYNC-03-007, SYNC-03-008, SYNC-03-012, SYNC-03-013

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-08-005, CLP-08-008
SYNC — Case Event Log Synchronization SYNC-03-002, SYNC-04-001, SYNC-15-010, SYNC-16-003, SYNC-16-029, SYNC-17-001, SYNC-17-003, SYNC-17-004, SYNC-17-010, SYNC-18-007, SYNC-18-012

story_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

Spec file Citing requirements
SYNC — Case Event Log Synchronization SYNC-14-001, SYNC-14-003, SYNC-14-008, SYNC-14-010, SYNC-15-004, SYNC-15-005, SYNC-16-009

story_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

Spec file Citing requirements
SYNC — Case Event Log Synchronization SYNC-16-005, SYNC-16-015, SYNC-16-016, SYNC-16-017, SYNC-16-018, SYNC-16-019, SYNC-17-005, SYNC-18-001, SYNC-18-002, SYNC-18-003, SYNC-18-004, SYNC-18-005, SYNC-18-008, SYNC-18-009, SYNC-18-010, SYNC-18-015, SYNC-18-016, SYNC-18-017

story_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

Spec file Citing requirements
SYNC — Case Event Log Synchronization SYNC-16-006, SYNC-16-020, SYNC-16-021, SYNC-16-022, SYNC-16-023, SYNC-16-024, SYNC-16-025

story_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

Spec file Citing requirements
SYNC — Case Event Log Synchronization SYNC-15-003, SYNC-15-008, SYNC-15-012, SYNC-15-013, SYNC-15-014, SYNC-15-016, SYNC-15-017, SYNC-15-018, SYNC-15-019, SYNC-15-026, SYNC-16-004, SYNC-16-012

story_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

Spec file Citing requirements
SYNC — Case Event Log Synchronization SYNC-16-008, SYNC-16-026, SYNC-18-011

story_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

Spec file Citing requirements
CM — Case Management CM-11-012, CM-11-035
SYNC — Case Event Log Synchronization SYNC-10-001, SYNC-10-002, SYNC-10-004

story_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

Spec file Citing requirements
CM — Case Management CM-11-036
MV — Message Validation MV-10-005, MV-12-001, MV-12-002, MV-12-003, MV-12-004, MV-12-005, MV-12-006
PCR — Participant Case Replica PCR-06-005
SYNC — Case Event Log Synchronization SYNC-03-005, SYNC-03-011, SYNC-03-014, SYNC-16-010, SYNC-16-011, SYNC-17-002, SYNC-17-009, SYNC-18-013, SYNC-18-014

story_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

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-01-002, CBT-01-007, CBT-02-001, CBT-04-003, CBT-05-007
CM — Case Management CM-11-008
CP — CaseProposal Protocol CP-09-004, CP-09-006
PCR — Participant Case Replica PCR-01-007, PCR-02-001, PCR-02-003, PCR-02-004, PCR-02-005, PCR-05-002

story_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

Spec file Citing requirements
CM — Case Management CM-17-004, CM-17-009
CP — CaseProposal Protocol CP-09-009
SYNC — Case Event Log Synchronization SYNC-15-015

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-02-003, CLP-04-002, CLP-04-006, CLP-07-022
CM — Case Management CM-28-023, CM-28-024
EP — Embargo Policy EP-09-003
SYNC — Case Event Log Synchronization SYNC-02-001, SYNC-08-002, SYNC-13-006, SYNC-19-002, SYNC-19-003, SYNC-19-004, SYNC-19-005, SYNC-19-006, SYNC-19-007
VP — Vultron Protocol VP-17-003

story_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

Spec file Citing requirements
BT — Behavior Tree Integration BT-19-003, BT-19-005
SYNC — Case Event Log Synchronization SYNC-12-001, SYNC-12-002, SYNC-12-004, SYNC-13-001, SYNC-14-004

story_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

Spec file Citing requirements
BT — Behavior Tree Integration BT-10-003
CLP — Case Ledger Processing CLP-10-001
CM — Case Management CM-02-002
CSB — CVD Case State Behavioral Requirements CSB-13-005, CSB-14-006
EMB — Embargo Management Behavioral Requirements EMB-16-002, EMB-16-006
EP — Embargo Policy EP-09-008, EP-09-017
PCR — Participant Case Replica PCR-03-005, PCR-03-006, PCR-08-001
RSH — Received-Side Status Authorization RSH-04-001, RSH-04-007, RSH-04-008
SYNC — Case Event Log Synchronization SYNC-02-003, SYNC-19-001, SYNC-21-001, SYNC-21-002, SYNC-21-003, SYNC-21-005, SYNC-21-006, SYNC-21-007, SYNC-21-008, SYNC-21-009, SYNC-21-010, SYNC-21-011, SYNC-21-012, SYNC-21-013, SYNC-21-014, SYNC-21-015, SYNC-21-016, SYNC-21-017, SYNC-21-018, SYNC-21-019, SYNC-21-023, SYNC-21-024, SYNC-21-025
VAM — Vultron Semantic–AS2 Mapping VAM-01-011, VAM-01-019, VAM-01-020
VP — Vultron Protocol VP-17-001, VP-18-001, VP-18-003

story_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

Spec file Citing requirements
EDF — Event-Driven Control Flow EDF-03-004
PCR — Participant Case Replica PCR-08-003, PCR-08-013

story_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

Spec file Citing requirements
BT — Behavior Tree Integration BT-09-001
CM — Case Management CM-01-001
PCR — Participant Case Replica PCR-01-003, PCR-01-004, PCR-01-005, PCR-01-006
TRIG — Triggerable Behaviors TRIG-06-001

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-07-007
PCR — Participant Case Replica PCR-04-001, PCR-04-003

story_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

Spec file Citing requirements
BT — Behavior Tree Integration BT-03-001, BT-03-004
LST — Lifecycle-Staged Domain Types LST-05-003
SM — State Machine SM-06-002
SYNC — Case Event Log Synchronization SYNC-04-002, SYNC-09-001, SYNC-09-005

story_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

Spec file Citing requirements
EMB — Embargo Management Behavioral Requirements EMB-17-004, EMB-17-015, EMB-17-016, EMB-17-017
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-07-012, MSM-07-039

story_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

Spec file Citing requirements
CM — Case Management CM-02-016, CM-33-001, CM-33-002, CM-33-003, CM-33-006, CM-33-007, CM-33-008, CM-33-009, CM-33-010, CM-33-011, CM-33-012, CM-33-013, CM-33-014, CM-33-015, CM-33-019, CM-33-021

story_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

Spec file Citing requirements
CM — Case Management CM-30-001, CM-30-002, CM-30-004, CM-30-006

story_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

Spec file Citing requirements
CBT — Case Bootstrap Trust CBT-06-001, CBT-06-003

story_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

Spec file Citing requirements
LST — Lifecycle-Staged Domain Types LST-02-001, LST-02-003, LST-05-002b

story_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

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-06-001, ASK-07-008
CLP — Case Ledger Processing CLP-02-001, CLP-02-013, CLP-02-016, CLP-02-017, CLP-09-003, CLP-09-005, CLP-09-006, CLP-10-031
CM — Case Management CM-16-008, CM-21-007, CM-28-005, CM-28-009

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-07-001, CLP-07-002, CLP-07-013, CLP-07-021

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-02-004, CLP-02-012, CLP-03-001, CLP-03-002, CLP-04-001, CLP-04-007, CLP-07-014
SYNC — Case Event Log Synchronization SYNC-16-002, SYNC-17-006

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-02-002, CLP-07-003, CLP-07-006, CLP-07-011, CLP-07-017, CLP-07-018
CM — Case Management CM-28-022
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-07-016
SYNC — Case Event Log Synchronization SYNC-18-006

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-08-001, CLP-08-002, CLP-08-003, CLP-08-004, CLP-08-006

story_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

Spec file Citing requirements
SYNC — Case Event Log Synchronization SYNC-03-009, SYNC-03-017, SYNC-03-018, SYNC-03-019

story_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

Spec file Citing requirements
ASK — Protocol Asks and Outstanding-Ask Registers ASK-06-003
CLP — Case Ledger Processing CLP-04-004, CLP-10-032
CM — Case Management CM-14-013, CM-16-002, CM-21-030
EMB — Embargo Management Behavioral Requirements EMB-19-001, EMB-19-002, EMB-19-003, EMB-19-004
PCR — Participant Case Replica PCR-08-003
SYNC — Case Event Log Synchronization SYNC-02-001, SYNC-02-003

story_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

Spec file Citing requirements
CM — Case Management CM-16-010
SYNC — Case Event Log Synchronization SYNC-09-002

story_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

Spec file Citing requirements
CSB — CVD Case State Behavioral Requirements CSB-05-010, CSB-06-010, CSB-13-004, CSB-14-005

story_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

Spec file Citing requirements
CLP — Case Ledger Processing CLP-07-015, CLP-07-023

story_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

Spec file Citing requirements
SYNC — Case Event Log Synchronization SYNC-20-001, SYNC-20-002, SYNC-20-003, SYNC-20-004, SYNC-20-005, SYNC-20-007, SYNC-20-008

story_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

Spec file Citing requirements
CM — Case Management CM-12-004, CM-14-002, CM-14-003, CM-14-007, CM-14-010, CM-14-014
CP — CaseProposal Protocol CP-09-003
DUR — Duration DUR-07-003, DUR-07-004
EP — Embargo Policy EP-04-001, EP-04-005, EP-04-006, EP-04-008, EP-04-018, EP-04-019, EP-04-020
VAM — Vultron Semantic–AS2 Mapping VAM-05-016

story_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

Spec file Citing requirements
EP — Embargo Policy EP-04-003, EP-04-004, EP-04-007, EP-04-011, EP-04-016, EP-04-024, EP-04-025, EP-04-026, EP-04-027
VP — Vultron Protocol VP-06-007, VP-07-002

story_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

Spec file Citing requirements
EMB — Embargo Management Behavioral Requirements EMB-18-004, EMB-18-012
EP — Embargo Policy EP-04-009, EP-04-017, EP-04-021

story_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

Spec file Citing requirements
CSB — CVD Case State Behavioral Requirements CSB-09-001
EMB — Embargo Management Behavioral Requirements EMB-10-001, EMB-12-001
VP — Vultron Protocol VP-04-003, VP-04-005, VP-05-016, VP-06-003, VP-06-005, VP-06-006, VP-06-009, VP-06-011, VP-06-012, VP-06-017, VP-07-011, VP-08-016, VP-08-018

story_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

Spec file Citing requirements
EMB — Embargo Management Behavioral Requirements EMB-01-004, EMB-01-005, EMB-02-003, EMB-10-002
VP — Vultron Protocol VP-13-013, VP-13-014, VP-13-015

story_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

Spec file Citing requirements
EP — Embargo Policy EP-09-001, EP-09-002, EP-09-010, EP-09-011, EP-09-020, EP-09-022, EP-09-025, EP-09-026, EP-09-027, EP-09-032
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-02-001
VAM — Vultron Semantic–AS2 Mapping VAM-05-005

story_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

Spec file Citing requirements
EMB — Embargo Management Behavioral Requirements EMB-01-001, EMB-01-003, EMB-02-001, EMB-03-001, EMB-03-002, EMB-04-001, EMB-04-003, EMB-05-001, EMB-05-003, EMB-06-001, EMB-07-001, EMB-07-002, EMB-18-005

story_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

Spec file Citing requirements
CM — Case Management CM-04-003
EMB — Embargo Management Behavioral Requirements EMB-15-004, EMB-15-009
EP — Embargo Policy EP-09-005
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-02-002, MSM-02-004, MSM-02-005, MSM-02-006, MSM-02-010, MSM-07-008, MSM-07-009, MSM-07-011, MSM-07-013, MSM-07-027, MSM-07-028, MSM-07-029, MSM-07-030, MSM-07-031, MSM-07-033, MSM-07-037, MSM-07-038
VAM — Vultron Semantic–AS2 Mapping VAM-05-006, VAM-05-007, VAM-05-008, VAM-05-009
VP — Vultron Protocol VP-04-002, VP-04-006, VP-05-003

story_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

Spec file Citing requirements
EP — Embargo Policy EP-08-001, EP-08-002, EP-08-003, EP-08-005

story_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

Spec file Citing requirements
EP — Embargo Policy EP-05-001, EP-05-002, EP-05-003, EP-09-023, EP-09-024
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-07-020, MSM-07-021, MSM-07-022, MSM-07-023, MSM-07-024

story_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

Spec file Citing requirements
EP — Embargo Policy EP-09-013, EP-09-028
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-07-010, MSM-07-014, MSM-07-015, MSM-07-034, MSM-07-035, MSM-07-036
VAM — Vultron Semantic–AS2 Mapping VAM-05-011

story_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

Spec file Citing requirements
CM — Case Management CM-28-001, CM-28-002, CM-28-012, CM-28-013, CM-28-017, CM-28-018, CM-28-019
EP — Embargo Policy EP-07-001, EP-07-002, EP-07-003, EP-07-004, EP-07-006, EP-07-009, EP-07-010, EP-07-011

story_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

Spec file Citing requirements
CM — Case Management CM-18-002, CM-28-003, CM-28-014, CM-28-015, CM-28-020, CM-28-025, CM-28-026, CM-28-027, CM-28-028, CM-28-029
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-07-026

story_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

Spec file Citing requirements
EMB — Embargo Management Behavioral Requirements EMB-17-001, EMB-17-002, EMB-17-003, EMB-17-009, EMB-17-012, EMB-17-013, EMB-17-014, EMB-17-018
EP — Embargo Policy EP-09-012

story_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

Spec file Citing requirements
VP — Vultron Protocol VP-06-004, VP-06-013, VP-06-014, VP-14-006

story_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

Spec file Citing requirements
EMB — Embargo Management Behavioral Requirements EMB-14-001, EMB-14-005, EMB-14-006
EP — Embargo Policy EP-08-004
MSM — Protocol Shorthand to MessageSemantics Mapping MSM-02-007, MSM-07-006, MSM-07-025
VAM — Vultron Semantic–AS2 Mapping VAM-05-003

story_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

Spec file Citing requirements
CM — Case Management CM-31-008, CM-31-009, CM-31-010, CM-31-030, CM-31-031, CM-31-032, CM-31-033, CM-31-042

story_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

Spec file Citing requirements
CM — Case Management CM-11-016, CM-11-044, CM-11-045, CM-11-046, CM-17-002, CM-17-010, CM-17-014

story_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

Spec file Citing requirements
AKM — Actor Knowledge Model AKM-05-003, AKM-05-004, AKM-05-007, AKM-05-010, AKM-05-011, AKM-05-012
CP — CaseProposal Protocol CP-01-009
EMB — Embargo Management Behavioral Requirements EMB-18-007

story_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

Spec file Citing requirements
CSAF — CSAF Documents in Reports CSAF-01-001, CSAF-01-002, CSAF-01-003, CSAF-02-001, CSAF-02-003, CSAF-02-004, CSAF-02-005, CSAF-02-006, CSAF-02-007, CSAF-03-001, CSAF-03-002, CSAF-03-003, CSAF-03-004, CSAF-03-005, CSAF-03-006, CSAF-03-007, CSAF-03-008, CSAF-03-009

story_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

Spec file Citing requirements
CSAF — CSAF Documents in Reports CSAF-02-002