Case Tracking Models
This page is normative
This page is considered a core part of the Vultron Protocol. This is a normative section of the documentation.
The whole specification on one page
The specification is also published as a single page that holds every section and annex in order, for printing or for searching the whole text at once.
This page holds sections 6 to 9 of the Vultron Protocol Specification: the state machines each participant uses to track a shared case. They are Report Management (RM), Embargo Management (EM), the Case State (CS) dimensions Vendor aware, Fix ready, fix Deployed (VFD) and Public aware, eXploit public, Attacks observed (PXA), and Participant Embargo Consent (PEC).
6. Report Management (RM) State Machine [N]
Report Management is the first of the five state machines, and every case starts with it. Before there is an embargo to negotiate or a fix to track, a participant receives a report and decides what to do with it. This section specifies the states of that decision and the transitions between them.
Behavioral Layer — §6 through §12
§6 Report Management (RM) State Machine through §12 Participant Lifecycle Within a Case together specify the five state machines of the Vultron protocol: RM (§6 Report Management (RM) State Machine), EM (§7 Embargo Management (EM) State Machine), VFD and PXA (§8 Case State (CS) Dimensions, together the CS dimension), and PEC (§9 Participant Embargo Consent (PEC) State Machine). How the CASE_MANAGER coordinates a case is in §10 Case Coordination. Model interactions and cascade rules are in §11 Model Interactions and Cascade Rules. The participant lifecycle is in §12 Participant Lifecycle Within a Case.
On scope: PEC. The Participant Embargo Consent machine was not part of the original four-machine design. It is fully normative here. Its definition site records its provenance (§9 Participant Embargo Consent (PEC) State Machine).
Two conventions apply throughout §6 Report Management (RM) State Machine through §12 Participant Lifecycle Within a Case:
- A participant maintains its own state and a model of the states of other participants. Where a transition rule applies to only one of the two, the rule says so explicitly (§8.4 Receiving CS Messages: Own State vs. Model of Others).
- For a transition listed without a named trigger, the corresponding protocol message from §4 Messages drives it.
6.1 States
Report Management tracks one report inside one participant, from the moment the report arrives until that participant is finished with it. Every participant runs its own RM machine and is the authority on its own value. Two participants that work on the same case are often at different RM states. This difference is expected, and it is not a disagreement to reconcile.
| State | Meaning |
|---|---|
| Start | No report has been received |
| Received | A report has arrived; triage is not yet complete |
| Invalid | This participant assessed the report as invalid |
| Valid | This participant assessed the report as valid |
| Deferred | This participant is deferring further action |
| Accepted | This participant accepted the report for active work |
| Closed | This participant closed the report |
The states divide into three groups. Start and Received come before any assessment. Invalid and Valid record the outcome of triage. Deferred, Accepted and Closed record what the participant decided to do about a report that it considers valid. The exception is that a participant can also close a report directly from Received or Invalid.
See also
6.2 Transitions and Guards
A participant drives its own RM transitions. Each transition below is a participant-level state change. It records an action of that participant, and it does not change the RM state of any other participant.
---
title: Report Management State Diagram
---
stateDiagram-v2
direction LR
S: Start
R: Received
I: Invalid
V: Valid
D: Deferred
A: Accepted
C: Closed
[*] --> S
S --> R : receive
R --> I: invalidate
R --> V : validate
I --> V : validate
V --> A : accept
V --> D : defer
A --> D : defer
D --> A : accept
R --> C : close
A --> C : close
D --> C : close
I --> C : close
C --> [*]
| From | Trigger | Message | To |
|---|---|---|---|
| Start | receive | receipt of RS |
Received |
| Received | validate | RV |
Valid |
| Received | invalidate | RI |
Invalid |
| Received | close | RC |
Closed |
| Invalid | validate | RV |
Valid |
| Valid | accept | RA |
Accepted |
| Valid | defer | RD |
Deferred |
| Deferred | accept | RA |
Accepted |
| Accepted | defer | RD |
Deferred |
| Invalid | close | RC |
Closed |
| Deferred | close | RC |
Closed |
| Accepted | close | RC |
Closed |
These twelve transitions are the complete set. Three consequences follow. Each one corrects a plausible assumption that is not true:
-
A report cannot be closed from every state. Only Received, Invalid, Deferred and Accepted are closable. A participant at Start or Valid has to reach one of those states before it can close. A
Rejectsent from Received is the Received → Closed transition, and a participant at Valid that leaves a case is recorded as Valid → Deferred → Closed. -
Valid does not return to Invalid. Invalidation is available only from Received. When a participant has assessed a report as valid, it does not invalidate it again. If the participant decides to stop work, it defers or closes.
-
Accepted and Deferred are mutually reachable. A participant can defer work it had accepted and accept work it had deferred, without passing through Valid again.
Closed has no transition out of it. A participant that expects to resume work on a report defers it instead of closing it.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
RMB-14-004 |
MUST | The RM transition function MUST permit closing from Received (q^rm R → C), as well as I → C, A → C and D → C. A Reject sent from RM Received, of a report Offer, a stub Invite (CM-11-007) or a full-case Invite (CM-11-011), is the R → C transition.Reject means close and TentativeReject means invalid, so a hard no from Received needs its own edge rather than a bypass of the transition table. |
Uses definition from: CM-11-007 Uses definition from: CM-11-011 |
RMB-14-008 |
MUST NOT | The RM transition function MUST NOT permit closing from Valid (VP-02-004). Valid keeps no close edge: a participant that found a report valid decides to engage or defer before it leaves (ADR-0114). |
Refines: VP-02-004 |
RMB-14-005 |
MUST | Every RM closure MUST be written as transitions the RM transition function permits, with no closure path that overrides the transition table. An override that skips the RM transition table lets a closure write a state that no permitted sequence reaches. The write-boundary check (RMB-15-001) and every replica then disagree with that state. R to C is in the table (RMB-14-004), and Valid goes through Deferred (RMB-14-009). Thus every closure is an ordinary transition, and no closure path needs the override (ADR-0114). |
|
RMB-14-009 |
MUST | An actor MUST record a participant at RM Valid that leaves the case (Leave(VulnerabilityCase), CM-23-038) as V → D → C.V → C is not in the RM transition table (RMB-14-008), so a closure from Valid that keeps to the table (RMB-14-005) goes through Deferred. |
Refines: RMB-14-005 Refines: CM-23-038 |
RMB-14-006 |
MUST NOT | The RM state machine MUST NOT define any transition out of RM.CLOSED to a different RM state. RM.CLOSED is terminal: once a participant's RM state reaches CLOSED, no further RM progression is possible for that participant on that case.RM.CLOSED being terminal is what gives the closure act finality. A participant that anticipates returning to the case SHOULD instead move to RM.DEFERRED (resumable via DEFERRED → ACCEPTED) rather than close; once closed, the participant has no path back in, because a re-invite to a participant at RM.CLOSED is refused (CM-11-043, ADR-0085). Rejoin mechanics are deferred to a future design; the interim workaround is defer-not-close (RMB-14-007). |
|
RMB-14-007 |
SHOULD | A participant that anticipates returning to active coordination on a case SHOULD move to RM.DEFERRED (the resumable parking state) rather than RM.CLOSED. RM.DEFERRED supports both DEFERRED → ACCEPTED (resume) and DEFERRED → CLOSED (abandon) transitions; RM.CLOSED supports neither. Because RM.CLOSED is terminal (RMB-14-006), a participant that closes and later wants back in has no protocol path. RM.DEFERRED preserves optionality: the participant can accept the case later or close it once it confirms there is nothing more to do (ADR-0085). Full rejoin mechanics (reactivation via re-invitation, multiple lifecycle arcs per actor) are deferred to a future design Idea. |
|
VP-02-004 |
MUST NOT | Participants MUST NOT close cases or reports from the Valid state Valid means the report is real and in scope but no engage-or-defer decision has been made. Closing straight from Valid would let a confirmed vul be dropped without that prioritization decision ever being taken or announced, so the report must pass through Accepted or Deferred first. |
See also
6.3 Per-Participant RM Tracking
Each participant tracks its own RM state independently. A participant is the authority on its own RM state (§10.1 Single-Writer Authority). A receiver that processes an RM transition records it on the sender's participant record, never on its own.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-01-002 |
MUST | Each actor's RM state MUST be maintained independently per case RM is a process for each participant. Each participant receives, validates, accepts, defers and closes a report on its own schedule (CM-03-002). One RM state for each actor in each case lets an actor be at different RM stages in different cases. It also stops the progress of one actor from counting as the progress of another actor. |
|
CM-03-002 |
MUST | RM state MUST be participant-specific Each participant moves through report handling on its own. One participant can accept a report that another has not yet validated. A single shared RM state cannot show this, and one participant's transition would overwrite the state of another (CM-01-002). |
|
CM-04-001 |
MUST | A receiver of a participant-status message MUST record the declared RM state on the sending actor's CaseParticipant, as its model of the sender (SM-10-001).RM state is self-declared: each participant reports its own report-handling progress (CM-03-002). A participant-status message updates the receiver's model of its sender. A record on any other participant would give one participant the progress of another. Other messages move the receiver's own state instead (SM-10-001). RSH-08-003 says which receiver writes the record directly. |
Refines: SM-10-001 Implements: VP-01-002 |
Received is the entry state for a participant in a case. A participant reaches it by several paths:
- Invited participant — the CASE_MANAGER creates an inert participant record at RM Received when it sends the stub
Invite. - Direct report recipient — on receiving a report.
- Case proposal recipient — on receiving a
CaseProposal.
An invited participant answers the stub Invite before it has seen more than a case stub.
Accept(Invite) activates the inert record, recording willingness to join and, where an embargo is active, consent to it, unless the participant has already declined that embargo.
RM stays at Received.
Reject(Invite) closes the record (RM Received → Closed) and retains it as history.
Neither answer is a validation of the report.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-11-006 |
MUST | When the CASE_MANAGER sends a stub Invite (Invite(Actor)[target=VulnerabilityCaseStub]), it MUST create the invitee's CaseParticipant in the same step. The participant is inert (CM-10-004).The CASE_MANAGER needs to track every invitee from the moment it is invited — whether it has been told and how it answered — including the invitees that decline (ADR-0114). |
Uses definition from: CM-10-004 |
CM-11-026 |
MUST | The CaseParticipant a stub Invite creates MUST hold the Invite's roles, RM RECEIVED, VF v (VENDOR), and an INVITED row for an active embargo.The invitee has been told of the case and has decided nothing. RM RECEIVED and VF v record exactly that. The INVITED row records that it was asked about the embargo in force and has not answered (CM-18-001). |
Extends: CM-11-006 |
CM-11-023 |
MUST | When it sends a stub Invite, the CASE_MANAGER MUST commit its own create_case_participant (Create(CaseParticipant)) entry, separate from the Invite's invite_actor_to_case entry.The ledger holds the wire messages that the actors exchanged, and every state change has a message. The Invite is one message. Creating the invitee's record is the CASE_MANAGER's own act, so it is a second message with its own entry (ADR-0114, ADR-0124). |
Extends: CM-11-006 |
CM-11-024 |
MUST | The create_case_participant entry MUST carry the whole participant record as stored: its statuses and consent rows, with their ids and times.A replica copies the record from the entry and derives nothing (CM-11-025, ADR-0124). The entry must therefore carry every field the CASE_MANAGER holds, or the replica's record differs from the CASE_MANAGER's. |
Extends: CM-11-023 |
CM-11-025 |
MUST | A replica MUST store an invitee's record exactly as the create_case_participant entry carries it, and derive none of it from the Invite's entry.Replicas copy; they never mint ids, read clocks or run lifecycle logic (ADR-0124). A record a replica derived could differ from the CASE_MANAGER's in an id or a time, and the copies of the case would then disagree. |
Depends on: CM-11-024 |
CM-11-001 |
MUST | When a participant accepts the stub Invite (Accept(Invite(Actor)[target=VulnerabilityCaseStub])), the CASE_MANAGER MUST leave the participant's RM state at RM.RECEIVED, set its VF state to V when it holds the VENDOR role, and, when an embargo is active, mark its consent row for that embargo AGREED, making it a signatory. A DECLINED row is the exception, and the CASE_MANAGER leaves it unchanged: an explicit refusal outranks the consent that joining implies. Accepting the stub is joining the case and, unless the row is DECLINED, consenting to the active embargo. It is not a judgement of the case.The invitee has seen only the stub. It judges the case later, in its replies to the full-case Invite (CM-11-010, CM-11-011), so the record of the CASE_MANAGER shows no decision that the invitee has not made. To join under an active embargo is to take part under it. Thus no participant becomes active without a recorded answer to the embargo, and the delivery gate of MV-10-005 relies on this. |
Uses definition from: CM-10-001 Extends: BT-10-005 |
CM-11-007 |
MUST | A stub Invite has exactly two valid replies, Accept (CM-11-001) and Reject. On Reject(Invite(Actor)[target=VulnerabilityCaseStub]), the CASE_MANAGER MUST close the participant and keep its record, which stays inert. Closing it moves its RM state to RM.CLOSED, sets VF V for a VENDOR, and records consent DECLINED when an embargo is active.A stub reject is a hard no to joining. Keeping the record keeps the history that the actor was told and declined, which is what the early record exists for. |
See also: CM-11-001 — context for the reader |
CM-11-027 |
MUST | A replica MUST apply a stub Reject from two entries: the invitee's reject_invite_actor_to_case, which carries the DECLINED row, and the CASE_MANAGER's add_participant_status_to_participant closing status.The invitee's Reject is a message, so it is its own ledger entry, and it is the entry for the DECLINED row. A replica applies that row through the same write the CASE_MANAGER uses. The closing status is the CASE_MANAGER's own act, with an entry of its own that a replica stores. Each replica then holds the record the CASE_MANAGER holds (ADR-0114, ADR-0124). |
Extends: CM-11-007 |
CM-11-028 |
MUST | The CASE_MANAGER MUST refuse TentativeReject(Invite(Actor)[target=VulnerabilityCaseStub]).Accepting the stub is not a judgement of the case, so there is nothing for a tentative reject to say. Only the full-case Invite asks for a judgement (CM-11-011). |
Derives from: CM-11-007 |
After the participant joins, the CASE_MANAGER sends the case and the ledger.
It then sends a second Invite, the full-case Invite, which carries the ledger position of the CASE_MANAGER as a floor.
The participant judges the case when it answers this Invite with its own ledger position.
The answer is Accept (RV, Received → Valid), TentativeReject (RI, Received → Invalid) or Reject (RC, Received → Closed).
A reply behind the floor, or naming a ledger entry the CASE_MANAGER does not hold, is refused.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-11-010 |
MUST | After CM-11-008, the CASE_MANAGER MUST send the participant the full-case Invite, Invite(Actor)[target=VulnerabilityCase], queued after the last replayed ledger entry.The participant already holds the case from the Announce, so the Invite only asks the question and carries no copy of the case. Delivery to each recipient is ordered (ADR-0112), so queuing the Invite after the replay means it usually arrives once the participant can answer it. The protocol does not rely on that order (ADR-0161): CM-11-033 covers an Invite that arrives first. |
Depends on: CM-11-008 |
CM-11-031 |
MUST | The full-case Invite MUST name the case by ID and carry the log_index and entry_hash of the CASE_MANAGER's ledger tail when it issued the Invite.The Invite's ledger position is the floor the participant must reach before answering (ADR-0121). It travels as the Invite's ledgerPosition, the property every case activity carries (VAM-04-011, SYNC-18-001, ADR-0156). |
Extends: CM-11-010 |
CM-11-032 |
MUST | A receiver MUST refuse a full-case Invite whose sender is not the CASE_MANAGER on its replica of the case. Only the case's CASE_MANAGER may ask a participant to judge the case. The receiver judges the Invite only when it holds the replica (CM-11-033), so the replica's CASE_MANAGER is the only record the sender check needs. The stub-Invite trust anchor decides an earlier question: whether the Announce may create that replica (PCR-03-004). |
|
CM-11-033 |
MUST | A receiver MUST NOT judge a full-case Invite for a case it holds no replica of. The protocol does not rely on delivery order (ADR-0161), so the Invite can arrive before the Announce (CM-11-010). It is case-scoped: the inbox's defer check holds it until the Announce creates the replica, then replays it (HP-01-041). With no trust anchor, no Announce can create the replica (PCR-03-004), so the held Invite expires unprocessed (CBT-03-003) and the receiver fails closed. |
Extends: CM-11-032 Depends on: HP-01-041 |
CM-11-011 |
MUST | The CASE_MANAGER MUST record each full-case Invite reply as a move from RM.RECEIVED: RV Accept to RM.VALID, RI TentativeReject to RM.INVALID, RC Reject to RM.CLOSED.Each reply is the participant's own judgement of the case (ADR-0121). The three replies map to the three RM triage outcomes, so every replica records the judgement the participant made. |
|
CM-11-034 |
MUST | A reply to the full-case Invite MUST carry the replier's own ledger position: the log_index and entry_hash of its tail when it decided.The position is the reply's ledgerPosition, the property every case activity carries (VAM-04-012..014, SYNC-18-001, ADR-0156), so the CASE_MANAGER judges it against the Invite's floor (CM-11-012) from the one field it reads on every case activity. |
Extends: CM-11-011 |
CM-11-012 |
MUST | The CASE_MANAGER MUST refuse a full-case Invite reply whose position is behind the Invite's, or names an entry missing from its ledger at that index. The Invite's position is a floor. A reply behind it was made without seeing what the participant was asked to judge. A reply that names an entry the CASE_MANAGER's ledger does not hold was not made on its ledger. |
Supersedes: SYNC-18-004 |
CM-11-035 |
MUST | The CASE_MANAGER MUST accept a full-case Invite reply whose position is at or beyond the Invite's. The Invite's position is a floor, not a pin. A reply beyond it is better informed. Pinning the reply to the Invite's position would make every reply on a busy case stale (ADR-0121). |
Extends: CM-11-012 |
CM-11-036 |
MUST | The CASE_MANAGER MUST refuse a full-case Invite reply from a participant that has not joined the case (an inert participant), writing nothing. Only a joined participant judges the case. An inert participant has not received the case or its history, so it has nothing to judge (CM-10-004). |
Extends: CM-11-012 |
The triage cycle (RECEIVED → VALID | INVALID → ACCEPTED | DEFERRED) is a different, later step.
The participant runs it after it receives the full case replica.
Two Invites, two different acts
Joining a case and judging a case are different protocol acts, and each has its own Invite.
The stub Invite asks whether the actor will join.
Accept(Invite) joins the case and consents to the embargo, and leaves RM at Received.
The full-case Invite asks whether the case is valid.
Its Accept is RV (Received → Valid), and only a later Join(VulnerabilityCase) reaches RM Accepted.
A participant cannot accept what it has not seen, so the CASE_MANAGER does not treat a participant as having committed to the case until that participant sends Join(VulnerabilityCase).
See §9.7 Gating Full Case Delivery for why this matters to case delivery.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-11-002 |
SHOULD | After joining a case, a participant SHOULD judge the case by replying to the full-case Invite (CM-11-010, CM-11-011). The CASE_MANAGER cannot count a joined participant as engaged until the participant says so (CM-11-004). The other participants plan their work from the list of engaged participants. The participant receives the full-case Invite, examines the case and its history, and then engages or defers. Every replica then records the RM decision of the participant itself, not a decision that the CASE_MANAGER infers from silence. |
Uses definition from: CM-11-001 Uses definition from: CM-11-010 See also: CM-11-011 — context for the reader |
CM-11-022 |
SHOULD | After it replies to the full-case Invite, a participant SHOULD engage with Join(VulnerabilityCase) (RM.ACCEPTED) or defer with Ignore(VulnerabilityCase) (RM.DEFERRED).Judging the case says whether the report is valid. It does not say whether the participant will work on the case. Only the participant can make that choice, and Join or Ignore records it, so no replica has to infer it from silence (CM-11-004). |
Extends: CM-11-002 |
CM-11-004 |
MUST | The CASE_MANAGER MUST NOT treat a joined participant as having committed to the case (RM.ACCEPTED) until it receives Join(VulnerabilityCase) from that participant.Only the participant can say it has chosen to engage. Neither accepting the stub Invite (joining) nor accepting the full-case Invite (RM.VALID) is an engagement decision. |
Uses definition from: CM-11-001 |
7. Embargo Management (EM) State Machine [N]
An embargo is an agreement among the participants of a case not to disclose the vulnerability publicly before an agreed point. Embargo Management tracks the progress of that agreement for the case as a whole. It records whether an embargo has been proposed, is in force, is under renegotiation, or has ended.
There is exactly one embargo state per case. It is shared case state, so only the CASE_MANAGER writes it (§10.1 Single-Writer Authority). The CASE_MANAGER does not set the EM state directly either. The CASE_MANAGER changes the case's embargo register, and the EM state is computed from the register (§7.1.2 Deriving EM from the Register). Embargo consent tracks a separate question, per participant and per embargo: whether each participant has agreed to the current terms (§9 Participant Embargo Consent (PEC) State Machine).
7.1 States
The five states below describe the case's collective position, not any one participant's, and not any one embargo's.
| State | Meaning | Embargo register entries |
|---|---|---|
| None | No embargo is in effect for this case, and none is proposed | none ACTIVE, PROPOSED or TERMINATED |
| Proposed | At least one embargo is proposed, and none is in force | one or more PROPOSED, none ACTIVE |
| Active | An embargo is in force, and no revision is open | one ACTIVE, none PROPOSED |
| Revised | An embargo is in force, and at least one revision of it is open | one ACTIVE, one or more PROPOSED |
| Exited | The embargo has been torn down | one TERMINATED |
None here means no embargo is in effect for the case.
A participant's consent row for an embargo has a separate start state, UNINVITED, meaning the participant has not been asked about that embargo (§9.1 States).
The case state and a consent row can legitimately disagree.
A case at Active can hold a participant whose row for the embargo in force is INVITED or DECLINED.
In that example, the row is INVITED because the participant has been invited to the case and has not yet accepted.
7.1.1 The Embargo Register
A case keeps one embargo register entry for every embargo ever proposed on it. An entry names the embargo, holds its status, and, for an activated revision, names the embargo it replaced. Entries are appended and never removed, so the register is the whole embargo history of the case, including rejected and canceled proposals.
| Status | Meaning |
|---|---|
PROPOSED |
An open proposal, awaiting the Case Owner's decision |
ACTIVE |
In force |
REJECTED |
The Case Owner declined the proposal |
SUPERSEDED |
Was in force, then a revision replaced it |
CANCELLED |
Closed with no owner decision, because the embargo question became moot |
TERMINATED |
Was in force when the case's embargo ended |
REJECTED, SUPERSEDED, CANCELLED and TERMINATED are final.
Six triggers move an entry:
| Trigger | Change |
|---|---|
PROPOSE |
new entry → PROPOSED |
ACTIVATE |
PROPOSED → ACTIVE |
REJECT |
PROPOSED → REJECTED |
SUPERSEDE |
ACTIVE → SUPERSEDED, in the step that activates another entry |
TERMINATE |
ACTIVE → TERMINATED, recording what ended the embargo and, when known, why |
CANCEL |
PROPOSED → CANCELLED, in the step that terminates the embargo in force, or on a threat signal while no entry is ACTIVE |
A register step is the whole change that one act causes. A termination and the cancellation of every open proposal therefore happen in one step and are checked together. Every step keeps these invariants:
- At most one entry is
ACTIVEand at most one isTERMINATED, and never one of each. - A
SUPERSEDEDentry exists only alongside exactly oneACTIVEorTERMINATEDentry. - No entry is
PROPOSEDwhile an entry isTERMINATED. - Once a step has left an entry
TERMINATED, no later step adds or changes an entry.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EP-08-004 |
MUST | When an embargo terminates (EM ACTIVE or REVISE → EXITED), the implementation MUST close every open proposal, cancelling it in the same embargo register step that terminates the embargo (ADR-0122), not only the entry for the terminated embargo itself. Every proposal open while EM is ACTIVE or REVISE is a revision of the active embargo, and a revision of an embargo that no longer exists cannot be accepted.A case has at most one active embargo (VP-04-002), so while EM is ACTIVE or REVISE every open proposal is by construction a revision of that embargo; no field linking a revision to the embargo it revises is needed to know which proposals a termination decides. EP-08-003's text reaches the terminated embargo; this entry reaches the proposals about it. |
Refines: EP-08-003 |
A termination records two things.
What ended the embargo is END_TIME_REACHED or EARLY.
Why it ended, when known, is a structured cause.
The kind of the cause is one of these values:
THREAT_SIGNAL, with the signalsP,XorAFIX_READY, with the vendors whose readiness made the quorumFIX_DEPLOYEDOTHER
Every cause is EARLY, and an END_TIME_REACHED termination has none.
The termination message carries the what as content and the why as terminationCause.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EMB-13-004 |
MUST | A termination Remove(EmbargoEvent) MUST carry what ended the embargo in content, exactly END_TIME_REACHED or EARLY. Its summary carries a human-readable account the protocol does not read.The what is all a receiver needs to apply a termination and to check it against the end time; the why records the decision. A cause is a kind with its own details, so a new cause (adversary awareness, exploit code held by adversaries, a participant's leak) is a new kind rather than a change to a closed list (ADR-0122). |
|
EMB-13-009 |
MUST | A receiver MUST refuse, at the parse edge, a termination Remove(EmbargoEvent) whose content is anything other than END_TIME_REACHED or EARLY (EMB-13-004).The what is all a receiver needs to apply a termination and to check it against the end time, so a termination without a valid what cannot be applied. |
Extends: EMB-13-004 |
EMB-13-010 |
MUST | The TERMINATED register entry MUST record the termination's reason (the what) and, when known, a structured cause (the why). The cause is an object discriminated on kind, whose details depend on the kind. One kind is THREAT_SIGNAL, with the signals (P, X, A) that ended the embargo, distinct and in that order. Another, FIX_READY, has the vendor participants whose readiness made the quorum (VP-09-007). The other kinds are FIX_DEPLOYED, and OTHER, whose account is the summary.The why records the decision. A cause is a kind with its own details, so a new cause (adversary awareness, exploit code held by adversaries, a participant's leak) is a new kind rather than a change to a closed list (ADR-0122). |
Extends: EMB-13-004 See also: VP-09-007 — context for the reader |
EMB-13-011 |
MUST NOT | An END_TIME_REACHED termination MUST NOT record a cause (EMB-13-010). Every cause kind is EARLY, and an EARLY termination with no cause is valid and records the what alone.A cause explains why an embargo ended before its end time. An embargo that ran to its end time has no such cause. |
Extends: EMB-13-010 |
EMB-13-005 |
MUST | A termination Remove(EmbargoEvent) whose termination has a cause (EMB-13-010) MUST carry it as terminationCause.One ledger entry is one activity, and the termination's entry is the whole TERMINATE register step (ADR-0124), so the why reaches a replica replaying the ledger only if the Remove carries it. A threat signal is a fact about the case that every participant learns from a status entry; naming it on a Remove while the case status does not show it would leave the register and the status disagreeing, and reading the Remove as a status change would commit one no participant sent (ADR-0122). |
Uses definition from: EMB-13-010 — Carries the recorded cause on the wire so replicas can copy it |
EMB-13-012 |
MUST | At the parse edge, a receiver MUST refuse a bad terminationCause (EMB-13-005). A cause is bad when its kind is unknown, when a detail is missing or malformed, or when the termination is END_TIME_REACHED.A cause the receiver cannot read, or one on a termination that can have none (EMB-13-011), would put a TERMINATED entry in the register that no other node can reproduce. |
Extends: EMB-13-005 |
EMB-13-013 |
MUST | A FIX_READY, FIX_DEPLOYED or OTHER cause on the Case Owner's Remove to the CASE_MANAGER is the owner's claim. The CASE_MANAGER MUST record it as given.These causes are the owner's account of its own decision, which the CASE_MANAGER has no grounds to check against its own view of the case. |
Extends: EMB-13-005 |
EMB-13-014 |
MUST | The CASE_MANAGER MUST refuse a THREAT_SIGNAL cause on the Case Owner's Remove before it is committed. The refusal's reason directs the sender to a case status update that sets P, X or A, the way a threat signal ends an embargo.A threat signal is a fact about the case that every participant learns from a status entry. Naming it on a Remove while the case status does not show it would leave the register and the status disagreeing, and reading the Remove as a status change would commit one no participant sent (ADR-0122). |
Extends: EMB-13-005 |
EMB-13-015 |
MAY | A Remove that the CASE_MANAGER sends MAY name THREAT_SIGNAL as its cause. No other Remove names it (EMB-13-014).The CASE_MANAGER ends an embargo on a threat signal it has adopted into the case status, so its Remove and the status agree. |
See also: EMB-13-014 — context for the reader |
EMB-13-016 |
MUST | A replica MUST record, on its TERMINATED entry, the cause that the termination's ledger entry carries.One ledger entry is one activity, and the termination's entry is the whole TERMINATE register step (ADR-0124), so the why reaches a replica replaying the ledger only if the Remove carries it. |
Extends: EMB-13-005 |
EMB-13-017 |
MUST NOT | A replica MUST NOT work a termination cause out from its own case state. A replica's own view can differ from the CASE_MANAGER's, such as threat signals its PXA does not carry. A cause it worked out would then disagree with the CASE_MANAGER's TERMINATED entry (CM-23-016). |
Extends: EMB-13-016 |
Register status is not EM state
The register statuses and the EM states share the words proposed and active, but they name different things.
Register status ACTIVE is one embargo in force.
EM ACTIVE is the case with an embargo in force and no revision open.
A case whose register holds one ACTIVE entry and one PROPOSED entry is at EM Revised, not EM Active.
7.1.2 Deriving EM from the Register
The case's EM state is a read of its register's statuses, never set directly:
ACTIVE entries |
PROPOSED entries |
TERMINATED entries |
EM |
|---|---|---|---|
| 0 | 0 | 0 | None |
| 0 | ≥1 | 0 | Proposed |
| 1 | 0 | 0 | Active |
| 1 | ≥1 | 0 | Revised |
| 0 | 0 | 1 | Exited |
REJECTED, SUPERSEDED and CANCELLED entries do not move EM.
A register that breaks an invariant matches no row, and the derivation refuses it.
The case's status carries a copy of the derived EM, stamped from the register.
A received status can report EM, but only a register step moves it.
Because EM aggregates over every entry, the case moves from Proposed or Revised to None or Active only when no proposal remains open.
Rejecting one of several open proposals leaves the others open, so EM stays where it was.
Activating one of several open proposals leaves the rest open as revisions of the embargo now in force, so EM moves to Revised rather than Active.
An ACTIVE entry leaves that status only when another entry supersedes it or when it is terminated.
A case that has had an embargo in force therefore never returns to None or Proposed.
7.2 Transitions and Guards
Four triggers drive the machine: propose, accept, reject and terminate. The register computes EM, and the table below constrains how EM moves. Every register step names its EM trigger, and a step whose EM move is not in the table writes nothing. Register steps map to EM triggers as follows:
- A proposal is propose. A proposal of terms the case already holds is not propose, and changes nothing (EP-09-032). Its end time repeats that of a pending proposal, or, with no revision pending, that of the embargo in force.
- An activation is accept.
- A rejection is reject. The cancellation of open proposals with no embargo in force is also reject.
- A termination is terminate.
Every transition is a change to shared case state, so the CASE_MANAGER applies it. Every replica applies the same check when it copies the step from the case ledger. A participant causes a transition by sending the corresponding message, not by writing the state itself.
---
title: Embargo Management State Diagram
---
stateDiagram-v2
direction LR
[*] --> None
state Pre-Embargo {
None --> Proposed : propose
Proposed --> Proposed : propose
Proposed --> Proposed : reject
Proposed --> None : reject
}
state Active_Embargo {
Active --> Revise : propose
Revise --> Active : accept
Revise --> Active : reject
Revise --> Revise : propose
Revise --> Revise : accept
Revise --> Revise : reject
Revise --> eXited : terminate
Active --> eXited : terminate
}
state Post-Embargo {
eXited
}
Proposed --> Active : accept
Proposed --> Revise : accept
eXited --> [*]
The diagram shows every move of the EM transition table. A self-loop on reject or accept is the move made while another proposal is still open, and accept from Proposed reaches Revise when the other open proposals become revisions of the embargo now in force.
| From | Trigger | To | Notes |
|---|---|---|---|
| None | propose | Proposed | |
| Proposed | propose | Proposed | A further proposal is added beside the open ones |
| Proposed | reject | None | The last open proposal is rejected, and no terms were ever in force |
| Proposed | reject | Proposed | Another proposal is still open |
| Proposed | accept | Active | No other proposal is open |
| Proposed | accept | Revised | The other open proposals become revisions of the embargo now in force |
| Active | propose | Revised | Proposing against an active embargo opens a revision |
| Revised | propose | Revised | |
| Revised | reject | Active | The last open revision is rejected, and the prior terms stand |
| Revised | reject | Revised | Another revision is still open |
| Revised | accept | Active | The revised terms replace the prior ones, and no other revision is open |
| Revised | accept | Revised | The revised terms replace the prior ones, and another revision is still open |
| Active | terminate | Exited | |
| Revised | terminate | Exited | Every open revision is canceled in the same step |
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EMB-18-005 |
MUST | Every change to a case's embargo register MUST move the case's EM state only along an EM transition for the change's EM trigger: a proposal is propose, an activation is accept, a rejection, or the cancellation of open proposals with no embargo in force, is reject, and a termination is terminate. The EM transitions are propose: N→P, P→P, A→R, R→R; reject: P→N, P→P, R→A, R→R; accept: P→A, P→R, R→A, R→R; and terminate: A→X, R→X. A rejection leaves Proposed, and a rejection or an acceptance leaves Revise, only when no proposal remains open; an acceptance from Proposed moves to Active, or to Revise while another proposal stays open.EM is computed from the embargo register (ADR-0122), not replaced by it: the EM state machine remains the protocol's model, and the register is a layer beneath it. With several proposals open, rejecting or activating one leaves the others open: a rejection keeps EM in Proposed or Revise until the last one is off the table, and an activation from Proposed puts the embargo in force with the others pending as revisions, in Revise (ADR-0130). |
Extends: EMB-18-001 |
Each participant's replica of the case moves along the same table when it copies a step from the case ledger. The requirements below state each move from the side of a participant that receives the message, with the CASE_MANAGER's ledger commit as the acknowledgment.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EMB-01-001 |
MUST | A Participant in EM None (q^em ∈ N) with CS not yet public/exploit/attack (q^cs ∈ ···pxa) receiving EP MUST transition their EM state to Proposed (q^em N → P). "Emit EK" is discharged by the CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry); no EK message is emitted (EP-09-009).EP is the EM message that initiates embargo negotiation. When no embargo exists and the case is still pre-public, the receiver transitions to Proposed to signal they are evaluating the proposal. ECA DetailsPreconditions - EM state is None; CS matches pattern ...pxa - EM state: NONE- CS pattern: ...pxaSteps 1. [receiver] Transition EM state from NONE to PROPOSED → Receiver EM state is PROPOSED 2. [receiver] CASE_MANAGER commits the received EP and announces the ledger entry (discharges EK) → Ledger entry committed and fanned out; no EK message exists Postconditions - Receiver EM state is PROPOSED; EK discharged by the ledger commit |
Uses definition from: MSM-02-001 — EP shorthand wire-type mapping Uses definition from: EP-09-009 |
EMB-01-003 |
MUST | A Participant already in EM Proposed (q^em ∈ P) with CS not yet public/exploit/attack (q^cs ∈ ···pxa) receiving a second or counter EP MUST stay in Proposed with no additional state transition. "Emit EK" is discharged by the CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry); no EK message is emitted (EP-09-009, MSM-02-009).Multiple EP messages can arrive during negotiation. When already in Proposed, no additional state transition is needed. The receiver evaluates the counter-proposal: it may answer the Invite with an Accept or a Reject of it, or counter, and the Case Owner decides the proposal for the case with EA or ER.ECA DetailsPreconditions - EM state is Proposed; CS matches pattern ...pxa - EM state: PROPOSED- CS pattern: ...pxaSteps 1. [receiver] CASE_MANAGER commits the counter EP and announces the ledger entry (discharges EK) → Ledger entry committed and fanned out; no EK message exists; EM state remains PROPOSED Postconditions - EM state remains PROPOSED; counter-proposal terms available for evaluation; EK discharged by the ledger commit |
Uses definition from: MSM-02-001 — EP shorthand wire-type mapping Uses definition from: EP-09-009 See also: MSM-02-009 — context for the reader |
EMB-02-001 |
MUST | A Participant in EM Proposed (q^em ∈ P) with CS not yet public/exploit/attack (q^cs ∈ ···pxa) receiving EA MUST move their EM state along the accept transition of EMB-18-005: to Active (q^em P → A) when the accepted proposal was the last one open, and to Revise (q^em P → R) while another proposal stays open. "Emit EK" is discharged by the CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry); no EK message is emitted (EP-09-009, MSM-02-009).Every participant must agree on whether an embargo is in force. If the receiver kept EM at Proposed after the EA, it would act as if no embargo binds the case, and it could disclose while the other participants keep the vulnerability private. Another open proposal stays open as a revision of the embargo now in force, because the consent already given to its terms stays valid (ADR-0130). Revise records both facts. The ledger commit of the EA acknowledges it. ECA DetailsPreconditions - EM state is Proposed; CS matches pattern ...pxa - EM state: PROPOSED- CS pattern: ...pxaSteps 1. [receiver] Transition EM state from PROPOSED to ACTIVE → Receiver EM state is ACTIVE 2. [receiver] CASE_MANAGER commits the received EA and announces the ledger entry (discharges EK) → Ledger entry committed and fanned out; no EK message exists Postconditions - Receiver EM state is ACTIVE, or REVISE while another proposal is open; EK discharged by the ledger commit |
Implements: VP-05-003 — An embargo SHALL begin at the moment it is accepted Uses definition from: MSM-02-002 — EA shorthand wire-type mapping Uses definition from: EP-09-009 Refines: EMB-18-005 See also: MSM-02-009 — context for the reader |
EMB-06-001 |
MUST | A Participant in EM Proposed (q^em ∈ P) receiving ER MUST move their EM state along the reject transition of EMB-18-005: back to None (q^em P → N) when the rejected proposal was the last one open, and staying in Proposed (q^em P → P) while another proposal is open. "Emit EK" is discharged by the CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry); no EK message is emitted (EP-09-009, MSM-02-009).If the receiver stayed in Proposed after the last open proposal is rejected, it would wait for an answer that does not come, and it would show an embargo negotiation that has ended. None tells every participant that no embargo binds the case. While another proposal is open, EM stays in Proposed, because that proposal still waits for an answer (ADR-0130). The ledger commit of the ER acknowledges it. ECA DetailsPreconditions - EM state is Proposed - EM state: PROPOSEDSteps 1. [receiver] Transition EM state from PROPOSED to NONE → Receiver EM state is NONE 2. [receiver] CASE_MANAGER commits the received ER and announces the ledger entry (discharges EK) → Ledger entry committed and fanned out; no EK message exists Postconditions - Receiver EM state is NONE (proposal rejected), or PROPOSED while another proposal is open; EK discharged by the ledger commit |
Uses definition from: MSM-02-006 — ER shorthand wire-type mapping Uses definition from: EP-09-009 Refines: EMB-18-005 See also: MSM-02-009 — context for the reader |
EMB-03-001 |
MUST | A Participant in EM Active (q^em ∈ A) with CS not yet public/exploit/attack (q^cs ∈ ···pxa) receiving EV MUST transition their EM state to Revise (q^em A → R). "Emit EK" is discharged by the CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry); no EK message is emitted (EP-09-009, MSM-02-009).A participant must know that a change to the embargo is open while the current terms still bind it. Revise records both facts: an embargo is in force, and a revision of it waits for an answer. If the receiver stayed in Active, it could not tell that a later EC or EJ decides a revision. The revision does not change any participant's consent to the embargo in force until the Case Owner activates it (EP-05-002). ECA DetailsPreconditions - EM state is Active; CS matches pattern ...pxa - EM state: ACTIVE- CS pattern: ...pxaSteps 1. [receiver] Transition EM state from ACTIVE to REVISE → Receiver EM state is REVISE 2. [receiver] CASE_MANAGER commits the received EV and announces the ledger entry (discharges EK) → Ledger entry committed and fanned out; no EK message exists Postconditions - Receiver EM state is REVISE; original embargo remains in force; EK discharged by the ledger commit |
Uses definition from: MSM-02-003 — EV shorthand wire-type mapping Uses definition from: EP-09-009 See also: MSM-02-009 — context for the reader |
EMB-03-002 |
MUST | A Participant already in EM Revise (q^em ∈ R) with CS not yet public/exploit/attack (q^cs ∈ ···pxa) receiving a counter EV (counter-revision) MUST stay in Revise with no additional state transition. "Emit EK" is discharged by the CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry); no EK message is emitted (EP-09-009, MSM-02-009).Multiple revision proposals can arrive. When already in Revise, no further state transition is needed; the receiver evaluates the counter-revision and answers its Invite with an Accept or a Reject of it, and the Case Owner decides the revision for the case with EC or EJ.ECA DetailsPreconditions - EM state is Revise; CS matches pattern ...pxa - EM state: REVISE- CS pattern: ...pxaSteps 1. [receiver] CASE_MANAGER commits the counter EV and announces the ledger entry (discharges EK) → Ledger entry committed and fanned out; no EK message exists; EM state remains REVISE Postconditions - EM state remains REVISE; EK discharged by the ledger commit |
Uses definition from: MSM-02-003 — EV shorthand wire-type mapping Uses definition from: EP-09-009 See also: MSM-02-009 — context for the reader |
EMB-04-001 |
MUST | This rule covers a Participant in EM Revise (q^em ∈ R) whose CS is not yet public/exploit/attack (q^cs ∈ ···pxa). When it receives EJ for the last open proposal, it MUST move its EM state back to Active (q^em R → A). The CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry), discharges "Emit EK". No EK message is emitted (EP-09-009, MSM-02-009).EJ says that a revision proposal is rejected. A rejected revision leaves the embargo in force and the consent to it unchanged (EP-05-002), so when no other proposal is open, EM returns to Active under the terms it had. The CASE_MANAGER's commit and fan-out of the received activity tell every participant of the change, so no separate EK message is necessary (ADR-0113). ECA DetailsPreconditions - EM state is Revise; CS matches pattern ...pxa - EM state: REVISE- CS pattern: ...pxaSteps 1. [receiver] Transition EM state from REVISE back to ACTIVE → Receiver EM state is ACTIVE 2. [receiver] CASE_MANAGER commits the received EJ and announces the ledger entry (discharges EK) → Ledger entry committed and fanned out; no EK message exists Postconditions - Receiver EM state is ACTIVE (revision rejected); EK discharged by the ledger commit |
Uses definition from: MSM-02-004 — EJ shorthand wire-type mapping Uses definition from: EP-09-009 See also: MSM-02-009 — context for the reader |
EMB-04-003 |
MUST | This rule covers a Participant in EM Revise (q^em ∈ R) whose CS is not yet public/exploit/attack (q^cs ∈ ···pxa). When it receives EJ while another proposal is open, it MUST remain in Revise (q^em R → R) (EMB-18-005). While another proposal stays open, EM stays in Revise, because the register still holds an open proposal (ADR-0130). ECA DetailsPreconditions - EM state is Revise; CS matches pattern ...pxa; another proposal is open - EM state: REVISE- CS pattern: ...pxaPostconditions - Receiver EM state is REVISE |
Refines: EMB-18-005 |
EMB-05-001 |
MUST | This rule covers a Participant in EM Revise (q^em ∈ R) whose CS is not yet public/exploit/attack (q^cs ∈ ···pxa). When it receives EC for the last open proposal, it MUST move its EM state back to Active (q^em R → A) with the revised terms. The CASE_MANAGER's commit of the Case Owner's Add(EmbargoEvent)[target=VulnerabilityCase], fanned out as Announce(CaseLedgerEntry), discharges "Emit EK". No EK message is emitted (EP-09-009, MSM-02-009).EC says that the Case Owner activates a revision. The revised terms replace the terms in force, so when no other proposal is open, EM returns to Active under the revised terms. The CASE_MANAGER's commit and fan-out of the owner's Add tell every participant of the change, so no separate EK message is necessary (ADR-0113). ECA DetailsPreconditions - EM state is Revise; CS matches pattern ...pxa - EM state: REVISE- CS pattern: ...pxaSteps 1. [receiver] Transition EM state from REVISE to ACTIVE with revised embargo terms → Receiver EM state is ACTIVE; revised terms recorded 2. [receiver] CASE_MANAGER commits the Case Owner's Add(EmbargoEvent)[target=VulnerabilityCase] and announces the ledger entry (discharges EK) → Ledger entry committed and fanned out; no EK message existsPostconditions - Receiver EM state is ACTIVE with new terms; EK discharged by the ledger commit |
Uses definition from: MSM-02-005 — EC shorthand wire-type mapping Uses definition from: EP-09-009 See also: MSM-02-009 — context for the reader |
EMB-05-003 |
MUST | This rule covers a Participant in EM Revise (q^em ∈ R) whose CS is not yet public/exploit/attack (q^cs ∈ ···pxa). When it receives EC while another proposal is open, it MUST remain in Revise (q^em R → R) under the revised terms (EMB-18-005). The revised terms replace the terms in force at once. While another proposal stays open, EM stays in Revise, because the register still holds an open proposal (ADR-0130). ECA DetailsPreconditions - EM state is Revise; CS matches pattern ...pxa; another proposal is open - EM state: REVISE- CS pattern: ...pxaPostconditions - Receiver EM state is REVISE with the revised terms |
Refines: EMB-18-005 |
EMB-07-001 |
MUST | A Participant in EM Active (q^em ∈ A) receiving ET MUST transition their EM state to Exited (q^em A → X). "Emit EK" is discharged by the CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry); no EK message is emitted (EP-09-009, MSM-02-009).ET is the message that terminates an active embargo. The receiver records that the embargo has ended. ET has immediate effect regardless of other pending messages. ECA DetailsPreconditions - EM state is Active - EM state: ACTIVESteps 1. [receiver] Transition EM state from ACTIVE to EXITED → Receiver EM state is EXITED 2. [receiver] CASE_MANAGER commits the received ET and announces the ledger entry (discharges EK) → Ledger entry committed and fanned out; no EK message exists Postconditions - Receiver EM state is EXITED; EK discharged by the ledger commit |
Uses definition from: MSM-02-007 — ET shorthand wire-type mapping Uses definition from: EP-09-009 See also: MSM-02-009 — context for the reader |
EMB-07-002 |
MUST | A Participant in EM Revise (q^em ∈ R) receiving ET MUST transition their EM state to Exited (q^em R → X). "Emit EK" is discharged by the CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry); no EK message is emitted (EP-09-009, MSM-02-009).ET terminates the embargo regardless of whether a revision is pending. The revision proposal is abandoned upon termination. ECA DetailsPreconditions - EM state is Revise - EM state: REVISESteps 1. [receiver] Transition EM state from REVISE to EXITED → Receiver EM state is EXITED 2. [receiver] CASE_MANAGER commits the received ET and announces the ledger entry (discharges EK) → Ledger entry committed and fanned out; no EK message exists Postconditions - Receiver EM state is EXITED; pending revision abandoned; EK discharged by the ledger commit |
Uses definition from: MSM-02-007 — ET shorthand wire-type mapping Uses definition from: EP-09-009 See also: MSM-02-009 — context for the reader |
EMB-07-003 |
MUST | A Participant already in EM Exited (q^em ∈ X) receiving ET MUST remain in Exited with no state transition. "Emit EK" is discharged by the CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry); no EK message is emitted (EP-09-009, MSM-02-009).Exited is already the terminal state, so a duplicate termination message needs no additional transition and no acknowledgment of its own. ECA DetailsPreconditions - EM state is Exited - EM state: EXITEDSteps 1. [receiver] Make no state change for the duplicate ET → EM state remains EXITED; no EK message exists Postconditions - EM state remains EXITED; no EK message emitted |
Uses definition from: MSM-02-007 — ET shorthand wire-type mapping Uses definition from: EP-09-009 See also: MSM-02-009 — context for the reader |
Rejecting a revision does not end the embargo
Reject behaves differently depending on where it arrives. The difference is easy to get backwards.
From Proposed, rejecting the last open proposal returns the case to None. No terms were ever in force, so refusing them leaves the case with no embargo.
From Revised, rejecting the last open revision returns the case to Active, not to None. The Case Owner is refusing the proposed change, not the embargo. The previously agreed terms remain in force. An implementation that returns to None here silently drops an embargo that everyone still expects to hold.
Reaching Exited.
Exited means that the embargo has ended at the case level.
A participant does not put the case into Exited by deciding to stop observing the embargo.
A participant can instead withdraw its own consent, report that it intends to exit, propose a shorter embargo, or propose an earlier end date.
The CASE_MANAGER then terminates the embargo and records the termination (§11.2 Embargo Revision and Termination Cascades).
An early termination takes Case Owner authorization by default, on the same terms as any other change to canonical case state (§11.3 Status Adoption: One Authorization Gate).
The one exception is an embargo whose end time has passed: the CASE_MANAGER itself terminates it, with the reason END_TIME_REACHED.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-02-005 |
MUST | CASE_MANAGER MUST restrict the following activities to the Case Owner: case closure, approving an embargo proposal to become active on the case and terminating an active embargo, approving or rejecting participant invitations, case ownership transfer, and offering a participant an additional role (CM-33-002) (see CM-02-006 for the authorisation mechanism). These actions decide who learns about the vulnerability, under what embargo, and who is responsible for the case. In CVD, the Case Owner makes these decisions. If any participant can start them through the CASE_MANAGER, a participant can close the case, change the embargo, admit a party that nobody checked, or take the case. |
See also: CM-02-006 — context for the reader |
EMB-13-003 |
MUST | When the end time of the embargo in force has passed, the CASE_MANAGER MUST end it with the reason END_TIME_REACHED, through one idempotent termination path. Two ways reach that path. One is the CASE_MANAGER's own lazy check when it next handles the case, for an inbound activity or one of its own triggers. The other is an outside request to end the embargo at its end time, such as from a Sentinel that monitors embargo timers. A request to end the embargo early, made after its end time, takes the same path. Each way commits the CASE_MANAGER's Remove(EmbargoEvent) with content END_TIME_REACHED and runs the full termination cascade. The outside request is made to the CASE_MANAGER itself. A Remove from the Case Owner is the owner's own message, ledgered on receipt like any other.VP-04-001 requires every accepted embargo to have an end time, so every embargo reaches one; recording the end as a termination keeps EM derived from the register, and lets the content gate stop withholding content under an embargo that has expired. The lazy check needs no scheduler; the outside request lets a deployment end an embargo on time without waiting for the next activity on the case. One path keeps the two from both committing: a register with a TERMINATED entry accepts no further change (ADR-0122).ECA DetailsPreconditions - An embargo is in force and its end time has passed - EM state: ACTIVE, REVISEPostconditions - The register's ACTIVE entry is TERMINATED with reason END_TIME_REACHED, every open proposal CANCELLED, EM EXITED, and the teardown announced |
|
EMB-13-006 |
MUST | Whichever of the lazy check and the outside request (EMB-13-003) arrives after the embargo has ended MUST commit nothing. One path keeps the two from both committing: a register with a TERMINATED entry accepts no further change (ADR-0122). |
Extends: EMB-13-003 |
EMB-13-007 |
MUST | The CASE_MANAGER MUST answer an end-time request (EMB-13-003) that arrives after the embargo has ended as already done. The requester asked for an outcome the case already holds, so the answer tells it the embargo is ended rather than refusing it. |
Extends: EMB-13-003 |
EMB-13-008 |
MUST | An END_TIME_REACHED termination claimed before the embargo's end time MUST be refused, by the CASE_MANAGER before it commits and by a replica that replays it.An END_TIME_REACHED reason claims the end time has passed. A claim made before then is false, and the content gate would stop withholding content under an embargo that is still in force. |
Extends: EMB-13-003 |
EMB-14-001 |
MUST | An actor that ends an active embargo early of its own accord MUST name its reason: a deployed fix, a ready fix, or another reason. Voluntary termination requires an auditable reason. ECA DetailsPreconditions - EM state is Active or Revise - EM state: ACTIVE, REVISESteps 1. [actor] Choose the termination reason (fix deployed, fix ready, or other) → Reason chosen Postconditions - A termination reason is chosen |
|
EMB-14-005 |
MUST NOT | An actor that names no reason MUST NOT end an active embargo early of its own accord. A termination with no reason gives the other participants nothing to audit (EMB-14-001). ECA DetailsPostconditions - EM state is unchanged |
Derives from: EMB-14-001 |
EMB-14-006 |
MUST | An actor that ends an active embargo early of its own accord MUST record its reason as the termination's cause (EMB-13-010). The cause is FIX_DEPLOYED, FIX_READY or OTHER respectively, never an EARLY termination with no cause.Recording the chosen reason as the cause carries it to every participant through the termination's ledger entry, where a cause-less EARLY termination would tell them only that the embargo ended.ECA DetailsSteps 1. [actor] Terminate the embargo, recording the chosen reason as its cause → ET emitted carrying the cause; EM transitions to EXITED Postconditions - EM state is EXITED; ET queued; termination cause recorded |
Extends: EMB-14-001 Uses definition from: EMB-13-010 |
Termination once P, X or A is canonical. The Case Owner uses its authority over this termination when the reported value is adopted, not after. Adopting a P, X or A value is the one authorization, and the CASE_MANAGER act that adopts the value also ends the embargo (§11.3 Status Adoption: One Authorization Gate, ADR-0166). So the Case Owner cannot keep an embargo once one of these values is canonical, and there is no decision to keep the embargo to record. A policy that must delay the termination decides at adoption, by not adopting the value yet. Attacks Observed differs from Public Aware and Exploit Public only at adoption: the CASE_MANAGER is recommended, not required, to adopt an A value and end the embargo.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
RSH-03-001 |
MUST | The CASE_MANAGER MUST trigger embargo teardown when the canonical CaseStatus carries CS.P (public awareness), CS.X (exploit public), or CS.A (attacks observed). All three flags signal a breach of the conditions that justify an active embargo. Covering only CS.P (as the prior PublicDisclosureBranchNode did) leaves exploit and attack signals without a teardown trigger. |
|
CSB-12-001 |
MUST | This rule covers the CASE_MANAGER when it adopts a P value (q^cs → ···P··) while an embargo is active (q^em ∈ {A, R}). Acting for the Case Owner, it MUST end the embargo immediately, by emitting ET in the act that adopts the value. VP-09-001 requires immediate embargo termination upon public disclosure. Ending an embargo is the Case Owner's decision, and only the CASE_MANAGER writes shared EM state; it can be the Case Owner itself (EMB-03-003, ADR-0118). Adopting P also authorizes the termination (ADR-0166). A non-manager Participant reports P instead (CSB-12-005), and CSB-04-007 covers a received CP. CSB-12-004 orders the CS transition before the teardown. ECA DetailsPreconditions - EM state is Active or Revise; CS matches pattern ...P.. - EM state: ACTIVE, REVISE- CS pattern: ...P..Steps 1. [CASE_MANAGER] Adopt the P value into the canonical case status → Case CS public bit set to P 2. [CASE_MANAGER] Emit ET to terminate the embargo, in the same act → ET queued for participants; EM transitions to EXITED Postconditions - CS public bit is P; the CASE_MANAGER has emitted ET; EM is EXITED |
Refines: VP-09-001 — Embargoes SHALL terminate immediately when information becomes public |
CSB-13-002 |
MUST | This rule covers the CASE_MANAGER when it adopts an X value (q^cs → ···PX·) while an embargo is active (q^em ∈ {A, R}). Acting for the Case Owner, it MUST end the embargo immediately, by emitting ET in the act that adopts the value. VP-09-001 requires immediate embargo termination upon exploit publication. Ending an embargo is the Case Owner's decision, and only the CASE_MANAGER writes shared EM state; it can be the Case Owner itself (EMB-03-003, ADR-0118). Adopting X also authorizes the termination (ADR-0166). A non-manager Participant reports X instead (CSB-13-005), and CSB-05-008 covers a received CX. CSB-13-004 orders the CS transition before the teardown. ECA DetailsPreconditions - EM state is Active or Revise; CS matches pattern ...PX. - EM state: ACTIVE, REVISE- CS pattern: ...PX.Steps 1. [CASE_MANAGER] Adopt the X value into the canonical case status → Case CS exploit bit set to X 2. [CASE_MANAGER] Emit ET to terminate the embargo, in the same act → ET queued for participants; EM transitions to EXITED Postconditions - CS exploit bit is X; the CASE_MANAGER has emitted ET; EM is EXITED |
Refines: VP-09-001 — Embargoes SHALL terminate immediately when exploit becomes public |
CSB-14-001 |
SHOULD | This rule covers the CASE_MANAGER when it learns of an A value (q^cs → ·····A) while an embargo is active (q^em ∈ {A, R}). Acting for the Case Owner, it SHOULD end the embargo by adopting the value, in an act that emits ET. VP-09-003 recommends ending the embargo when attacks are observed. It is SHOULD, not SHALL, to leave room for judgment. Under ADR-0166 that judgment is whether to adopt A: an adopted A ends the embargo in the same act (CSB-06-008, RSH-03-001). The Case Owner may delegate that decision in advance (RSH-07-003) and keeps the authority (VP-11-006). A non-manager Participant reports A instead (CSB-14-006). ECA DetailsPreconditions - EM state is Active or Revise; CS matches pattern .....A - EM state: ACTIVE, REVISE- CS pattern: .....ASteps 1. [CASE_MANAGER] Adopt the A value into the canonical case status → Case CS attacks bit set to A 2. [CASE_MANAGER] Emit ET to terminate the embargo, in the same act → ET queued for participants; EM transitions to EXITED Postconditions - CS attacks bit is A; the CASE_MANAGER has emitted ET; EM is EXITED |
Refines: VP-09-003 — Embargoes SHOULD terminate immediately when there is evidence of active exploitation |
Open question: may the Case Owner delegate activating an embargo to the CASE_MANAGER?
Activating a proposed embargo is the Case Owner's decision for the case.
The owner sends Add(EmbargoEvent) with target naming the VulnerabilityCase, and inReplyTo naming the Invite(EmbargoEvent) that proposed it.
Ending an embargo can already be delegated: the CASE_MANAGER may send the Remove(EmbargoEvent) on the owner's behalf.
Activation has no such path.
What is settled is how the owner's own answer bears on any activation.
The owner's Accept(Invite(EmbargoEvent)) or Reject(Invite(EmbargoEvent)) is its consent as a participant, and its decision for the case never rewrites that answer.
An owner that declined a proposal accepts it before it activates it.
So if activation is ever delegated, only an owner that has accepted the proposal can authorize the CASE_MANAGER's Add.
Open: whether the owner may delegate activation at all; how a delegation is expressed on the wire, for example as part of the owner's published embargo policy or as an instruction for one case; and whether the CASE_MANAGER's Add names the owner's Accept or the proposal's Invite in inReplyTo.
Once a resolution is reached, it will be reflected in this reference and in the embargo message requirements.
Embargo duration selection. Where several proposals are outstanding, the protocol recommends that participants accept the shortest and propose the remainder as revisions. The rule is a recommendation, so other policies remain admissible. An implementation can defer the choice to the Case Owner, or apply its own organizational policy. This specification does not mandate shortest-wins.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EP-08-001 |
SHOULD | This rule covers a case with two or more open embargo proposals and none accepted. A Participant SHOULD accept the proposal whose embargo end_time is earliest, and propose the remainder as revisions.Two parties proposing 30 and 60 days agree on days 1–30 and disagree only beyond that, so accepting the shorter proposal captures all mutual agreement immediately and leaves the contested remainder to negotiate as a revision. This is the Shortest Embargo Proposed Wins heuristic stated in docs/topics/process_models/em/defaults.md, derived in docs/topics/process_models/em/formal_model.md, and applied to case growth in docs/topics/process_models/em/working_with_others.md. |
|
EP-08-005 |
SHOULD | This rule covers two or more revisions open against an active embargo. A Participant SHOULD accept or reject them one at a time, in earliest-to-latest end_time order.Taking revisions shortest first applies the Shortest Embargo Proposed Wins heuristic (EP-08-001) to revisions: each accepted revision captures the agreement the longer ones also contain. |
Tacit acceptance. A receiver can publish a default embargo policy, its actor default. Where it has, a sender that submits a report without proposing terms accepts that default, and the case begins with that embargo active.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EP-01-001 |
MAY | An Actor profile MAY include an embargo_policy field containing the Actor's structured embargo policy record inline. The policy is part of the profile: an Actor has at most one, and it is published, read and replaced as a field of the profile, not as a separate object.Whoever holds an Actor's profile then holds its embargo terms, so carrying the profile (CP-01-010) carries the policy, and no lookup has to choose among several records. |
|
EP-04-001 |
MUST | When the CASE_OWNER's actor default embargo applies at case creation and the sender submitted no explicit embargo proposal, the case's initial EM state MUST be EM.ACTIVE, not EM.PROPOSED. The sender's report submission without a counter-proposal constitutes tacit acceptance of the CASE_OWNER's actor default embargo.A sender that submits a report without terms of its own has nothing to object to in the receiver's default, so nobody is left to accept it. A case left at EM.PROPOSED would wait for an answer nobody owes, with no embargo in force at the moment the report is most sensitive. |
Refines: DUR-07-003 |
A protocol default applies when nobody proposes anything. Where neither party proposes terms and the receiver has published no default, an embargo-eligible case still begins with an active embargo, at a short duration fixed by the protocol rather than by either party. The duration is no less than 72 hours and no more than 5 days. Where the case is not embargo-eligible (the vulnerability is public, an exploit is public, or attacks are observed), no embargo is established and the case remains in None.
The protocol default is not a proposal. It takes no part in the shortest-wins comparison above. If it did, a default short enough to be useful would win against every longer proposal and cap every embargo at its own length. The protocol default is also not a minimum. A party that proposes a shorter duration gets the duration it proposed.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EP-04-005 |
MUST | A protocol default embargo duration MUST exist. The goal of the EM process is to lock in an embargo as early as possible ( docs/topics/process_models/em/principles.md). Without a protocol default, a case with no embargo proposal and no actor default would have no embargo at all. |
|
EP-04-018 |
MUST | The protocol default embargo duration MUST be no less than 72 hours and no more than 5 days. The 72-hour floor equals the default EP-07-002 minimum RSVP window, so the shortest embargo the protocol produces is as long as the shortest answer window it grants. The 5-day ceiling keeps a deployment from restoring a default generous enough to make publishing nothing better than publishing a policy. |
Extends: EP-04-005 |
EP-04-019 |
MUST | This rule covers an embargo-eligible case created with no embargo proposal and no actor default. The CASE_MANAGER MUST activate an embargo of the protocol default duration, so the case begins at EM.ACTIVE.A case with no embargo is the outcome the process exists to avoid, and reaching it through mutual silence is the least deliberate way to arrive there. |
Extends: EP-04-005 |
EP-04-006 |
MUST NOT | The protocol default MUST NOT participate in the shortest-wins comparison of EP-04-003. It is the value applied when no proposal and no actor default applies, never a candidate within that comparison. A 72-hour protocol default that competed under shortest-wins would win against every longer proposal and cap every embargo in the system at 72 hours, so no longer embargo could ever be agreed. The protocol default answers "what if nobody said anything", not "whose terms are shortest". See ADR-0096. |
Derives from: EP-04-003 |
EP-04-007 |
MUST NOT | The CASE_MANAGER MUST NOT clamp a proposal or actor default that is shorter than the protocol default up to it. It honors that term at its stated duration.em/principles.md requires embargo duration be "limited to the shortest duration possible", and a Participant is free to set their own terms. EP-04-005's range bounds what the fallback may be configured to; it does not constrain what parties may agree. A reporter who proposes 12 hours gets 12 hours. See ADR-0096. |
|
EP-04-008 |
MUST NOT | The CASE_MANAGER MUST NOT apply the protocol default to a case that is not embargo-eligible. Such a case has P, X or A set at creation. VP-06-001 already forbids proposing or accepting an embargo negotiation once the vulnerability is public, exploit code is public, or attacks are observed (EMB-01-002 is the accept half of the same prohibition). An embargo on an already-public vulnerability protects nothing, so the protocol default inherits that guard rather than bypassing it. See ADR-0096. |
Refines: VP-06-001 |
EP-04-020 |
MUST | When any of P, X or A is set at case creation, the CASE_MANAGER MUST leave the case at EM.NONE.VP-06-001 forbids proposing or accepting an embargo once the vulnerability is public, exploit code is public, or attacks are observed. An embargo on an already-public vulnerability protects nothing, so the case starts with none. |
Refines: VP-06-001 |
Outside these two default paths, the protocol recommends that participants accept or reject embargo proposals explicitly, within the period their disclosure policy defines or 14 days, whichever is shorter.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
VP-06-004 |
SHOULD | Participants SHOULD explicitly accept or reject embargo proposals within the period defined in their VDP or within 14 calendar days of receipt, whichever is shorter. An open proposal leaves everyone unsure whether information may be shared. A bounded reply time, never more than 14 days, makes the outcome known soon enough for participants to plan. |
7.3 Relationship to Embargo Consent
The two machines answer different questions. Embargo Management says whether the case has an embargo. Embargo consent (§9 Participant Embargo Consent (PEC) State Machine) says whether a given participant has agreed to a given embargo. Neither machine determines the other, so both are needed.
Both read the same register. A participant has one consent row per register entry. Whether the participant is a signatory or has lapsed is read from its rows and the register, not stored (§9.3 Signatory and Lapsed). Two register steps change who is bound. Only one of them writes rows:
- Activating a revision that ends later than the terms it replaces binds only participants that agreed to the revision.
A signatory to the replaced terms that has not agreed to the revision has lapsed.
Its agreement covered the previous, shorter terms.
A revision that ends no later than the terms it replaces carries every signatory over.
The step writes a
CARRY_OVERon the row of each signatory for the revision. Proposing a revision changes no one's consent to the embargo in force. - Terminating the embargo leaves no entry
ACTIVE, so nobody is a signatory and nobody has lapsed. The termination writes no consent row, and every row for a final entry is frozen as it stood.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EP-05-001 |
MUST NOT | This rule covers the Case Owner's activation of a revised embargo that ends later than the embargo it replaces (REVISE → ACTIVE). The CASE_MANAGER MUST NOT carry any participant's consent over to it.A participant who signed for terms T1 has not consented to longer terms T2; treating them as a signatory once T2 is in force would imply consent they never gave. A participant is bound by the revised embargo only through an AGREED consent row for it, so each signatory to the replaced embargo that has not agreed to the revised one has lapsed (CM-18-001), and no write is needed to lapse them. The rule applies at activation rather than at proposal because the participant remains bound by T1 for as long as T1 is the active embargo (ADR-0093, ADR-0122). |
Uses definition from: CM-18-001 |
EP-05-003 |
MUST | This rule covers the Case Owner's activation of a revised embargo that ends no later than the one it replaces. The CASE_MANAGER MUST apply CARRY_OVER to the revised embargo's row of each participant with an AGREED row for the replaced embargo. That includes a participant whose row for the revision is DECLINED (CM-10-001, CM-18-003, MSM-07-005).Shorter terms ask nothing new: agreeing to N days is agreeing to every shorter period, the same containment that makes shortest-wins (EP-04-003) safe without asking anyone, so their agreement is carried over by writing the row. That holds for a participant that declined the shorter revision too: its decline objected to losing time, not to keeping the embargo, and the decline stays in the ledger (ADR-0122). |
Uses definition from: CM-18-001 Uses definition from: CM-18-003 Refines: MSM-07-005 See also: CM-10-001 — context for the reader |
EP-05-002 |
MUST NOT | A revision proposal (ACTIVE → REVISE) and any further counter-revision (REVISE → REVISE) MUST NOT change any participant's consent to the embargo in force. The proposer's row for the proposed embargo becomes AGREED (MSM-07-022). Every other participant gets an UNINVITED row for it (CM-18-001). Every other row stays as it is until the Case Owner activates a revision (EP-05-001, EP-05-003). Until then the prior embargo stays in force, and every signatory to it remains one.A participant cannot lapse until the embargo on the case differs from the one they agreed to. Lapsing on proposal would strand signatories when the revision is rejected, report participants who are still bound and still receive embargoed content as not bound, and lapse the proposer of the revision (ADR-0093). With per-embargo rows a proposal only ever adds rows for the proposed embargo. |
Uses definition from: CM-18-001 Refines: MSM-07-022 See also: EP-05-001 — scope boundary: a different transition See also: EP-05-003 — context for the reader |
MSM-07-006 |
MUST | When an ET / REMOVE_EMBARGO_EVENT_FROM_CASE wire activity terminates the embargo register's ACTIVE entry, implementations MUST leave the case with no active embargo. The same step cancels every open proposal, so the derived EM becomes EXITED. No separate outbound wire activity is emitted; the participant position is derived from the case. A register with a TERMINATED entry accepts no further change (ADR-0122), so a terminated embargo can never be invited to again. That is a fact about the case, which every replica holds once it replays the teardown. |
Uses definition from: MSM-02-007 |
MSM-07-025 |
MUST NOT | When an ET terminates the embargo register's ACTIVE entry, implementations MUST NOT write any participant's consent rows. With no active embargo no participant is a signatory and no row binds anyone. An Accept or Reject that arrives afterwards records nothing (EMB-17-004). The termination is a fact about the case, so it does not need copying onto each participant record as a terminal consent state. Leaving the rows as they were also keeps the history of who agreed to what, and every row of a final entry is frozen (CM-18-003). |
Extends: MSM-07-006 See also: EMB-17-004 — context for the reader |
§11.2 Embargo Revision and Termination Cascades specifies both cascades.
8. Case State (CS) Dimensions [N]
Case State records what is known about the vulnerability. It answers two different questions, and it is a compound of two machines because those questions have different owners.
The first is what each vendor has done about the vulnerability: is it aware, does it have a fix, has the fix been deployed? That is participant-specific — each participant answers for itself. The second is what the world knows: is the vulnerability public, is there a public exploit, are attacks happening? That is a fact about the world, shared by the whole case.
The two are tracked separately, as VFD and PXA. Confusing them is the most consequential error in this part of the model: it leads an implementation to record one participant's action as a change to the state of the world, or to treat a world event as though some participant caused it.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-03-004 |
MUST | CS (PXA sub-state) MUST be participant-agnostic (shared per case) Public awareness, exploit publication and attacks in the wild are facts about the world, not about one participant. When the vulnerability is public, it is public for all participants. A copy for each participant can only disagree with the facts. |
|
CM-03-005 |
MUST | VFD (Vendor Fix Deployment) state MUST be participant-specific Fix readiness and deployment are different for each participant. One vendor can ship a fix before another vendor, and a deployer has its own deployment state. A shared VFD state would let the progress of one participant show as the progress of another (ADR-0075). |
|
CM-04-006 |
MUST NOT | A participant-specific transition (RM or VFD) MUST NOT change any case-level (participant-agnostic) state (EM or PXA). Participant-specific state and case-level state are separate by design (CM-03-002 through CM-03-005). If an RM or VFD transition of one participant wrote across this boundary, it could change the shared embargo or public state. |
Satisfies: VP-13-009 |
CM-04-010 |
MUST NOT | A case-level transition (EM or PXA) MUST NOT change any participant-specific state (RM or VFD). Participant-specific state and case-level state are separate by design (CM-03-002 through CM-03-005). If a shared event wrote across this boundary, it could overwrite the progress of one participant. |
Extends: CM-04-006 |
8.1 VFD — Vendor Aware, Fix Ready, Fix Deployed
VFD records what a specific participant has done, so each participant has its own value. It moves in one direction only, and through its states in a fixed order: a vendor is aware before a fix can be ready, and a fix is ready before it can be deployed. That ordering leaves four reachable states rather than eight.
| State | Vendor Aware | Fix Ready | Fix Deployed |
|---|---|---|---|
vfd |
no | no | no |
Vfd |
yes | no | no |
VFd |
yes | yes | no |
VFD |
yes | yes | yes |
Because the axes are ordered, the state is written as a single three-letter token in which case indicates progress: Vfd means the vendor is aware, the fix is not ready, and nothing is deployed.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CSB-17-006 |
MUST | An implementation MUST NOT allow a fix to be ready while the vendor is unaware (the vF compound state is impossible). Fix readiness presupposes vendor awareness; the vF combination is structurally excluded from the 32 valid compound CS states. |
|
CSB-17-007 |
MUST | An implementation MUST NOT allow a fix to be deployed that was never ready (the fD compound state is impossible). Fix deployment presupposes fix readiness; the fD combination is structurally excluded from the 32 valid compound CS states. |
Which participant can cause which VFD transition depends on the roles it holds, and is specified at §13.4.1 Participant-Specific CS Transitions (VFD).
See also
8.2 PXA — Public Aware, Exploit Public, Attacks Observed
PXA records the state of the world, not the state of any participant. There is one PXA value for the case, it is shared case state, and only the CASE_MANAGER writes it (§10.1 Single-Writer Authority).
Unlike VFD, the three axes are independent: any combination can occur, in any order.
| Axis | Not yet | Set | Meaning when set |
|---|---|---|---|
| Public Aware | p |
P |
The vulnerability is known outside the case participants |
| Exploit Public | x |
X |
An exploit for the vulnerability has been published |
| Attacks Observed | a |
A |
Attacks exploiting the vulnerability have been seen |
Independence gives PXA eight states — every combination of the three, written by setting each letter to upper or lower case: pxa, Pxa, pXa, pxA, PXa, PxA, pXA, PXA.
---
title: pxa State Diagram
---
stateDiagram-v2
direction LR
[*] --> pxa
pxa --> Pxa : P
pxa --> pXa : X
pxa --> pxA : A
pXa --> PXa : P
pXa --> pXA : A
pxA --> PxA : P
pxA --> pXA : X
Pxa --> PxA : A
Pxa --> PXa : X
pXA --> PXA : P
PXa --> PXA : A
PxA --> PXA : X
PXA --> [*]
A PXA observation is not tied to any participant's role, because a PXA fact is not any participant's to own — anyone can notice that an exploit has appeared. Reporting is not the same as the case adopting the observation (§13.4.2 Participant-Agnostic CS Transitions (PXA), §11.3 Status Adoption: One Authorization Gate).
Two PXA states are passed through, not rested in
Publishing an exploit makes the vulnerability public.
The two states in which an exploit is public while the public is unaware — pXa and pXA — therefore describe a situation that does not persist: they resolve to PXa and PXA.
A participant that records an exploit as public records public awareness in the same step, so a case never rests in either state.
The reverse does not hold.
Attacks being observed does not by itself make the vulnerability public: an attack can be detected without its mechanism being understood or disclosed.
pxA is a state a case can legitimately rest in.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CSB-13-001 |
MUST | A Participant whose CS sets the exploit bit while the public bit is unset (···px·) MUST also trigger CS→P (the pX→PX invariant). It triggers CS→P before or with the exploit transition. The ephemeral state ···pX· (exploit public without public awareness) cannot exist as a stable state. Constraint C-15 requires the transition to be ···px· → ···PX·, not ···px· → ···pX· → ···PX·. Observable consequence: CX emitted from ···px· state must be accompanied by CP. The precondition uses the post-transition pattern ···pX· (X uppercase, P lowercase) since state_entered fires after the X bit is set. ECA DetailsPreconditions - CS matches pattern ...pX. - CS pattern: ...pX.Steps 1. [participant] Emit CX to announce exploit public transition → CX queued for case participants 2. [participant] Emit CP to announce public aware transition (C-15 constraint) → CP queued for case participants Postconditions - CS is ···PX·; CX and CP both emitted; pX→PX invariant satisfied |
|
CSB-13-006 |
MUST | A Participant MUST treat the compound transition of CSB-13-001 as atomic, so that it sets the P and X bits together. If the P and X bits were set in two steps, the participant would pass through the ephemeral state ···pX·, which cannot exist as a stable state (C-15). The write is the exception CSB-17-002 names, and it loses no ordering: ···pX· has one forced successor (CSB-17-012), so a replay recovers X, then P. ECA DetailsPreconditions - CS matches pattern ...pX. - CS pattern: ...pX.Steps 1. [participant] Transition CS to ···PX· (set both public bit P and exploit bit X atomically) → Receiver CS public bit P and exploit bit X both set Postconditions - CS is ···PX·, with no stored ···pX· state |
Refines: CSB-13-001 Supersedes: CSB-17-002 Supersedes: CSB-17-008 |
CSB-17-003 |
MUST | An implementation MUST treat the compound states vP (public aware while the vendor is unaware) and pX (exploit public while the public is unaware) as ephemeral. Neither condition can persist in reality: public awareness reaches the vendor, and a published exploit makes the public aware. Modelling these as ephemeral rather than invalid preserves the causal ordering of the events while forbidding the case from progressing in any other direction first. The pX ephemeral rule is the pX to PX invariant of CSB-13-001 generalised from the entry cascade to every successor of a pX state. ECA DetailsPreconditions - The case is in one of the 12 ephemeral compound CS states Postconditions - Each ephemeral state has exactly one valid successor state |
Extends: CSB-13-001 |
CSB-17-012 |
MUST | From a pX state the next CS event MUST be P. The forced-successor rule for pX states enforces the pX→PX invariant; pX is ephemeral and P is the only valid continuation. |
Refines: CSB-17-003 |
CSB-17-013 |
MUST | Any CS event other than the forced successor MUST be rejected when the current state is ephemeral (vP or pX). Accepting any other event would break the vP→VP and pX→PX invariants that the forced-successor rule exists to enforce. |
Refines: CSB-17-003 |
8.3 Case State as a Compound Tuple
Case State is the pair CS = (VFD, PXA), giving 4 × 8 = 32 compound states.
Not every ordering among them is reachable.
Each CS event changes one of the six dimensions, once, from not yet happened to happened.
The VFD order of §8.1 VFD — Vendor Aware, Fix Ready, Fix Deployed holds in every compound state.
Two compound states are ephemeral, and each one has a single forced next event.
vP, public awareness while the vendor is unaware, is resolved by Vendor Aware.
pX, a public exploit while the public is unaware, is resolved by Public Aware.
When a participant writes its own status and the write would enter an ephemeral state, the write also applies the forced event, so that single write changes more than one dimension.
A write that sets X while P is unset also sets P, and a write that sets P while V is unset also sets V.
This compound write is the one exception to the one-dimension rule.
It loses no ordering, because each ephemeral state has only one possible next event.
A status received from another participant is that participant's claim, and the receiver records it exactly as sent.
When the CASE_MANAGER adopts the claim, the case status it records is in the forced form: a claim of pXa makes the case PXa.
A reported CS history is checked by replaying its events in order from vfdpxa, not by comparing timestamps.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CSB-17-001 |
MUST | An implementation MUST treat exactly 32 compound CS states as valid: the cross product of the 4 valid VFD states (vfd, Vfd, VFd, VFD) and the 8 PXA states. The VFD dimension is a linear chain, not a free product of three bits: readiness presupposes awareness and deployment presupposes readiness. Enumerating only the reachable combinations makes the two impossible combinations unrepresentable rather than merely rejected at runtime, which is why CS_vfd has four members and not eight.ECA DetailsPostconditions - The CS enum has exactly 32 members, one per valid compound state |
Refines: SM-09-002 — SM-09-002 states the vF/fD prohibition as a rejection rule; this refines it to a structural guarantee by enumerating only the 32 reachable combinations, so the impossible ones are unrepresentable. |
CSB-17-002 |
MUST | A CS transition MUST change exactly one of the six CS dimensions. The one exception is a compound transition, as in CSB-13-006. It applies an event together with the forced successor of the ephemeral state (CSB-17-003) that the event would enter. CS events are irreversible and are observed one at a time; a compound state change of Hamming distance greater than one conflates two distinct events and loses their ordering, which is exactly the information history validity depends on. These two conditions alone admit 72 transitions; applying the ephemeral-state rule of CSB-17-003 leaves exactly 58 valid CS transitions. ECA DetailsPreconditions - A (source, destination) pair of compound CS states Steps 1. [validator] Identify the single dimension that differs between source and destination; reject if more than one differs. If none differs, the write is a same-state re-assertion, which CSB-16-001 and CSB-16-002 permit as a status confirmation: accept it only when the caller has opted in (the allow_null parameter), and reject it otherwise, because a transition validator's default answer for "no change" must be "that is not a transition". → A single CS event accounts for the change, or the caller has explicitly asked for same-state writes to pass 2. [validator] Delegate to the changed dimension's own transition table (is_valid_vfd_transition or is_valid_pxa_transition). → Monotonicity and VFD prerequisite ordering are enforced 3. [validator] Apply the ephemeral-state rule of CSB-17-003 to the source state. → A transition out of a vP or pX state fires only the event that state requires Postconditions - Only Hamming-distance-1 monotone transitions are accepted |
Constrains: CSB-16-001 — Adds the one-dimension-at-a-time and monotonicity constraints that a per-dimension write validator cannot see. The same-state write CSB-16 permits is preserved via the opt-in described in step 1. Constrains: CSB-16-002 Uses definition from: CSB-17-003 |
CSB-17-014 |
MUST | A CS transition MUST change its one dimension from the not-yet-happened value to the happened value. CS events are irreversible, so a change from the happened value back to the not-yet-happened value describes no event. With CSB-17-002 this condition admits 72 transitions, and the ephemeral-state rule of CSB-17-003 leaves 58. ECA DetailsPostconditions - Only monotone transitions are accepted |
Extends: CSB-17-002 |
CSB-17-008 |
MUST | A CS transition that changes two or more dimensions at once, that reverses a dimension, or that skips a VFD prerequisite MUST be rejected. The compound transition of CSB-13-006 is exempt from the multi-dimension form only. Each of the three prohibited forms conflates or reorders distinct causal events; rejecting them enforces the one-event-at-a-time and monotonicity invariants. |
|
CSB-17-009 |
MUST | From a vP state the next CS event MUST be V. The forced-successor rule is the operational consequence of CSB-17-003's ephemeral classification: each ephemeral state has exactly one valid continuation, enforcing the vP→VP invariant. |
|
CSB-17-004 |
SHOULD | A consumer validating a reported CS history SHOULD validate it causally by replaying the event sequence through CSB-17-002 and CSB-17-003 from the initial state vfdpxa, rather than checking states point-in-time or comparing wall-clock timestamps. A complete history contains all six CS events exactly once; there are exactly 70 valid complete histories out of 720 orderings. Validity of a case trajectory is a property of the whole ordered sequence, not of any single state: VFDPXA and VFDXAP visit only valid states, but only the first is a possible case history. Wall-clock timestamps cannot substitute, because they may be missing, skewed, or recorded by different participants. SHOULD rather than MUST because a consumer holding only a current state, with no event log to replay, cannot do better. ECA DetailsPreconditions - An ordered sequence of CS events, possibly incomplete Steps 1. [validator] Reject any event that occurs more than once in the sequence → Each CS event happens at most once 2. [validator] Replay the sequence from vfdpxa, requiring each step to satisfy CSB-17-002 and CSB-17-003 given every event that preceded it. → Causally impossible orderings are rejected Postconditions - A complete valid history terminates in VFDPXA |
Uses definition from: CSB-17-002 Uses definition from: CSB-17-003 |
CSB-17-005 |
MUST | An incomplete CS history MUST be validated as a prefix. Real cases are usually still in progress, so requiring six events would reject every live case. Ending in an ephemeral state is unavoidable at the prefix level: CSB-17-003's forced successor has not happened yet when the prefix is cut, which is different from an actor persisting an ephemeral state as its own — SM-09-003 still forbids that. Pinning acceptance to CSB-17-004's prefix closure keeps both directions honest: a validator that merely never rejects a genuine prefix could still accept dead ends. ECA DetailsPreconditions - An ordered sequence of CS events with fewer than six entries Steps 1. [validator] Apply CSB-17-004's replay to the sequence without requiring that it terminate in VFDPXA. → The prefix is accepted iff it is a prefix of at least one valid complete history Postconditions - A prefix ending in an ephemeral state is accepted, and its forced successor per CSB-17-003 is the only legal continuation |
Refines: CSB-17-004 |
The orderings also constrain the embargo. Public awareness, a public exploit and observed attacks each end an active embargo. When the CASE_MANAGER adopts a status that sets one of them while an embargo is active, it terminates the embargo, and it records the CS change before the termination (§11.3 Status Adoption: One Authorization Gate). The embargo therefore ends after the CS change that ends it is recorded, not before.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CSB-18-002 |
MUST NOT | Once a CASE_MANAGER act commits, a participant's composite state MUST NOT have the PXA P-bit set (q^cs ∈ ···P··) while an active embargo exists (q^em ∈ {ACTIVE, REVISE}). Public awareness of a vulnerability while an embargo is active is causally impossible in a well-functioning coordination — the P event causes embargo termination, so EM cannot remain ACTIVE once P has occurred. The P event (public awareness) makes the embargo end. An embargo that stays ACTIVE or REVISE after P is recorded is therefore a causal contradiction, and it misstates the case to every participant that reads it. The emit path does not refuse a P report while an embargo is active, because that report is what causes the embargo to end. The rule is judged per act, not per entry (ADR-0166): the adopting act writes its snapshot before the teardown (RSH-01-004). ECA DetailsPreconditions - A PXA state and an EM state are both available for the same case |
|
CSB-18-003 |
MUST NOT | Once a CASE_MANAGER act commits, a participant's composite state MUST NOT have the PXA X-bit set (q^cs ∈ ···X·) while an active embargo exists (q^em ∈ {ACTIVE, REVISE}). Public exploit availability while an embargo is active is causally impossible — the X event entails embargo termination. A public exploit lets attackers use the vulnerability, so secrecy no longer protects users. An embargo that stays ACTIVE or REVISE after X tells participants to keep a secret that attackers already have. It also holds back information that defenders need now, and it misstates the case to every participant that reads it. It is judged when an act commits, as CSB-18-002 is (ADR-0166). ECA DetailsPreconditions - A PXA state and an EM state are both available for the same case |
Derives from: CSB-18-002 |
CSB-18-004 |
MUST NOT | Once a CASE_MANAGER act commits, a participant's composite state MUST NOT have the PXA A-bit set (q^cs ∈ ···A) while an active embargo exists (q^em ∈ {ACTIVE, REVISE}). Observed attacks while an embargo is active is causally impossible — the A event entails embargo termination. Observed attacks show that the vulnerability is in use. An embargo that stays ACTIVE or REVISE after A holds back the information that defenders need to protect themselves while the attacks go on. It also misstates the case to every participant that reads it. It is judged when an act commits, as CSB-18-002 is (ADR-0166). ECA DetailsPreconditions - A PXA state and an EM state are both available for the same case |
Extends: CSB-18-002 |
CSB-04-007 |
MUST | This rule covers a CASE_MANAGER whose RM state is not Closed (q^rm ∉ C) and whose EM is Active or Revise (q^em ∈ {A, R}). Its CS is not yet public (q^cs ∈ ···p··). On receiving CP, it MUST initiate embargo termination by emitting ET in the act that adopts the P value. VP-09-001 requires immediate embargo termination when public awareness occurs. Only the CASE_MANAGER writes shared EM state, so it emits the ET when it records the P/X/A status (RSH-03-001, EP-09-008); it can be the Case Owner itself. A non-manager Participant reports the CS change and emits no ET (EMB-03-003, ADR-0118). Adopting P also authorizes the termination, so no second approval is asked (ADR-0166). |
Refines: CSB-12-001 — The adoption of a received CP |
CSB-05-008 |
MUST | This rule covers a CASE_MANAGER whose RM state is not Closed (q^rm ∉ C) and whose EM is Active or Revise (q^em ∈ {A, R}). Its CS is not yet public and not yet exploit-public (q^cs ∈ ···px·). On receiving CX, it MUST initiate embargo termination by emitting ET in the act that adopts the X value. VP-09-001 requires immediate embargo termination when exploit publication occurs. Only the CASE_MANAGER writes shared EM state, so it emits the ET when it records the P/X/A status (RSH-03-001, EP-09-008); it can be the Case Owner itself. A non-manager Participant reports the CS change and emits no ET (EMB-03-003, ADR-0118). Adopting X also authorizes the termination, so no second approval is asked (ADR-0166). |
Refines: CSB-13-002 — The adoption of a received CX |
CSB-06-008 |
MUST | This rule covers a CASE_MANAGER whose RM state is not Closed (q^rm ∉ C) and whose EM is Active or Revise (q^em ∈ {A, R}). Its CS is not yet public and has no attacks observed (q^cs ∈ ···p·a). On receiving CA, it MUST initiate embargo termination by emitting ET in the act that adopts the A value. Observed attacks warrant embargo termination (VP-09-003), and an active embargo cannot coexist with the attacks bit (CSB-18-004). Only the CASE_MANAGER writes shared EM state, so it emits the ET when it records the P/X/A status (RSH-03-001, EP-09-008); it can be the Case Owner itself. A non-manager Participant reports the CS change and emits no ET (EMB-03-003, ADR-0118). Adopting A also authorizes the termination, so no second approval is asked (ADR-0166). |
Refines: CSB-14-001 — The adoption of a received CA |
CSB-12-004 |
MUST | This rule covers the CASE_MANAGER when it adopts a P value (q^cs → ···P··) while an embargo is active (q^em ∈ {A, R}). It MUST record the adopted P value before it ends the embargo under CSB-12-001. Every replica replays the ledger in order, so a teardown committed ahead of its cause would show the embargo ending for no recorded reason. CSB-04-003 is the received transition this rule orders; the ledger mechanism is CLP-10-006. |
Extends: CSB-12-001 |
CSB-13-004 |
MUST | This rule covers the CASE_MANAGER when it adopts an X value (q^cs → ···PX·) while an embargo is active (q^em ∈ {A, R}). It MUST record the adopted X value before it ends the embargo under CSB-13-002. Every replica replays the ledger in order, so a teardown committed ahead of its cause would show the embargo ending for no recorded reason. The received form of this rule is CSB-05-010; the ledger mechanism is CLP-10-006. |
Extends: CSB-13-002 |
CSB-14-005 |
SHOULD | This rule covers the CASE_MANAGER when it adopts an A value (q^cs → ·····A) while an embargo is active (q^em ∈ {A, R}). It SHOULD record the adopted A value before it ends the embargo under CSB-14-001. Every replica replays the ledger in order, so a teardown committed ahead of its cause would show the embargo ending for no recorded reason. The received form of this rule is CSB-06-010; the ledger mechanism is CLP-10-006. |
Extends: CSB-14-001 |
CSB-05-010 |
MUST | A Participant in a non-Closed RM state (q^rm ∉ C) with CS not yet public and not yet exploit-public (q^cs ∈ ···px·) and EM Active or Revise (q^em ∈ {A, R}) receiving CX MUST record the CS transition to ···PX· before embargo teardown is initiated. The ledger commits the CS state change before any effect acts on it (CLP-10-006), so every replica sees the cause before its effect. |
|
CSB-06-010 |
MUST | A Participant in a non-Closed RM state (q^rm ∉ C) with CS not yet public and attacks not yet observed (q^cs ∈ ···p·a) and EM Active or Revise (q^em ∈ {A, R}) receiving CA MUST record the CS transition to ···p·A before embargo teardown is initiated. The ledger commits the CS state change before any effect acts on it (CLP-10-006), so every replica sees the cause before its effect. |
8.4 Receiving CS Messages: Own State vs. Model of Others
A participant holds its own case state and a model of what it believes the other participants' states to be. Different events update each one.
- Receiving a VFD message (
CV,CF,CD) updates the receiver's model of the sender's VFD state. The receiver's own VFD state does not change. No acknowledgment is sent: a participant confirms it has the case history by the fact that its ledger replica is unbroken, not by acknowledging each entry (§4.11 Faults and Acknowledgments). - Driving one's own VFD transition happens locally, subject to the role requirements of §13.4.1 Participant-Specific CS Transitions (VFD), and is then announced.
- PXA is shared case state, so an adopted PXA observation updates the case's canonical status rather than any per-participant model (§11.3 Status Adoption: One Authorization Gate).
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CSB-01-001 |
MUST | A Participant in a non-Closed RM state (q^rm ∉ C) receiving CV MUST update their model of the sending Participant's CS state to Vendor Aware (q^cs ∈ Vfd···). No CK message is emitted (MSM-03-008). The CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry), records it. Each replica acknowledges that entry by its unbroken hash chain (MSM-05-002).CV announces a Vendor-specific CS transition. The receiver does not change their own CS state; they update their awareness model for the sender. ECA DetailsPreconditions - Participant is in an active RM state (Received/Invalid/Valid/Deferred/Accepted) - RM state: RECEIVED, INVALID, VALID, DEFERRED, ACCEPTEDSteps 1. [receiver] Update model of sender's CS state to Vendor Aware (Vfd···) — receiver's own CS state is unchanged → Receiver's awareness model for sender reflects CS=Vfd 2. [receiver] CASE_MANAGER commits the received CV and announces the ledger entry (discharges CK) → Ledger entry committed and fanned out; no CK message exists Postconditions - Sender's CS state recorded as Vfd; CK discharged by the ledger commit; receiver CS unchanged |
Uses definition from: MSM-03-001 — CV shorthand wire-type mapping Uses definition from: MSM-03-008 See also: MSM-05-002 — the acknowledgment by hash chain, reached through the link to MSM-03-008 |
CSB-02-001 |
MUST | A Participant in a non-Closed RM state (q^rm ∉ C) receiving CF MUST update their model of the sending Participant's CS state to Fix Ready (q^cs ∈ VFd···). No CK message is emitted (MSM-03-008). The CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry), records it. Each replica acknowledges that entry by its unbroken hash chain (MSM-05-002).CF announces a Vendor-specific CS transition. The receiver does not change their own CS state; they update their awareness model for the sender. ECA DetailsPreconditions - Participant is in an active RM state (Received/Invalid/Valid/Deferred/Accepted) - RM state: RECEIVED, INVALID, VALID, DEFERRED, ACCEPTEDSteps 1. [receiver] Update model of sender's CS state to Fix Ready (VFd···) — receiver's own CS state is unchanged → Receiver's awareness model for sender reflects CS=VFd 2. [receiver] CASE_MANAGER commits the received CF and announces the ledger entry (discharges CK) → Ledger entry committed and fanned out; no CK message exists Postconditions - Sender's CS state recorded as VFd; CK discharged by the ledger commit; receiver CS unchanged |
Uses definition from: MSM-03-002 — CF shorthand wire-type mapping Uses definition from: MSM-03-008 See also: MSM-05-002 — the acknowledgment by hash chain, reached through the link to MSM-03-008 |
CSB-03-001 |
MUST | A Participant in a non-Closed RM state (q^rm ∉ C) receiving CD MUST update their model of the sending Participant's CS state to Fix Deployed (q^cs ∈ VFD···). No CK message is emitted (MSM-03-008). The CASE_MANAGER's commit of the received activity, fanned out as Announce(CaseLedgerEntry), records it. Each replica acknowledges that entry by its unbroken hash chain (MSM-05-002).CD announces a Vendor-specific CS transition. The receiver does not change their own CS state; they update their awareness model for the sender. ECA DetailsPreconditions - Participant is in an active RM state (Received/Invalid/Valid/Deferred/Accepted) - RM state: RECEIVED, INVALID, VALID, DEFERRED, ACCEPTEDSteps 1. [receiver] Update model of sender's CS state to Fix Deployed (VFD···) — receiver's own CS state is unchanged → Receiver's awareness model for sender reflects CS=VFD 2. [receiver] CASE_MANAGER commits the received CD and announces the ledger entry (discharges CK) → Ledger entry committed and fanned out; no CK message exists Postconditions - Sender's CS state recorded as VFD; CK discharged by the ledger commit; receiver CS unchanged |
Uses definition from: MSM-03-003 — CD shorthand wire-type mapping Uses definition from: MSM-03-008 See also: MSM-05-002 — the acknowledgment by hash chain, reached through the link to MSM-03-008 |
CM-04-002 |
MUST | A receiver processing a VFD state transition MUST update the VFD state in the participant status of the sending actor's CaseParticipantVFD state is participant-specific (CM-03-005). A VFD message reports the fix readiness or deployment of the sender. A record on any other participant would claim a fix that this participant did not make. |
Refines: SM-10-001 |
CM-04-004 |
MUST | When the CASE_MANAGER adopts a PXA transition (public disclosure, exploit publication or attack observation), it MUST record the case-level PXA state in the case's CaseStatus. Every other replica takes that state from the CASE_MANAGER's ledger (RSH-08-003).PXA state is a case-level fact (CM-03-004). A record of a reported disclosure, exploit or attack on the shared CaseStatus makes it visible to all participants at the same time. This is important because each of these events can end an embargo early. Only the CASE_MANAGER writes canonical case state (ADR-0108). |
Refines: SM-10-002 See also: RSH-08-003 — context for the reader |
CM-04-005 |
MUST | A receiver processing a VFD or PXA transition MUST validate the requested transition against the authoritative current state before recording it A transition is valid only from the current state of the case or participant. If the receiver records a transition without a check against the authoritative current state, a stale or out-of-order message can move the state backward or skip a necessary step. Every replica then copies the incorrect state. |
See also
9. Participant Embargo Consent (PEC) State Machine [N]
An embargo binds the participants who agreed to it. Embargo Management (§7 Embargo Management (EM) State Machine) records whether the case has an embargo. It cannot record who has agreed, because that answer differs per participant. Participant Embargo Consent records it.
This distinction has practical consequences. A participant invited to a case that already has an active embargo has not yet agreed to anything. The CASE_MANAGER does not send that participant embargoed content until the participant agrees (§9.7 Gating Full Case Delivery). A participant that declines is still in the case and still receives the negotiation traffic (§9.5 Embargo Traffic Reaches Non-Signatories). The case-level embargo state cannot express either position.
Consent is per participant, but the CASE_MANAGER writes it. The CASE_MANAGER records consent on the participant's record in the case, next to the participant's other case state.
Informative: provenance
The original protocol design had four state machines and no consent machine. This machine emerged during implementation, when the case-level embargo state could not distinguish "no embargo exists" from "this participant has not yet agreed". This machine is normative here, because correct embargo behavior cannot be specified without it.
9.1 States
Consent applies to specific terms. A participant therefore has one consent row for every entry in the case's embargo register (§7 Embargo Management (EM) State Machine), and each row holds one of the five states below. A row answers one question: what has this participant said about this one embargo? A participant can therefore be bound by the embargo in force and have already agreed to a proposed revision of it, on two different rows.
| State | Meaning |
|---|---|
UNINVITED |
Not asked about this embargo; the start state of every row |
INVITED |
Asked, with no answer yet; carries that invitation's RSVP deadline |
AGREED |
Agreed to this embargo: explicitly, as its proposer, by seeding, or by carry-over |
DECLINED |
Explicitly refused this embargo, or withdrew from it |
TIMED_OUT |
Invited, and the RSVP deadline passed with no answer; not a refusal |
Every row is written.
Proposing an embargo writes an UNINVITED row for it on every current participant.
Creating a participant record writes an UNINVITED row for every entry already in the register.
No state is read from a missing row.
A missing row is a defect, and an attempt to read one raises an error.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-18-001 |
MUST | Each participant record MUST hold one embargo consent row for every entry in the case's embargo register. Each row holds one of five states. The UNINVITED state means not asked, and is the start state. The INVITED state means asked, with no answer yet. The AGREED state records agreement, and DECLINED records an explicit refusal or a withdrawal. The TIMED_OUT state means invited, with the RSVP deadline passed and no answer. A participant is a signatory when its row for the register's ACTIVE entry is AGREED. A participant has lapsed when three things hold. An entry is ACTIVE, and the participant's row for it is neither AGREED nor DECLINED. Following replaces back from the ACTIVE entry, the first entry whose row is AGREED or DECLINED has an AGREED row. Both positions are read from the rows and the register, never stored (CM-18-016). With no ACTIVE entry, nobody is a signatory and nobody has lapsed.One row for each pair of participant and embargo records each answer one time. To find if a participant is bound by the active embargo, a reader looks at the row for the active embargo. Thus there is no second record to reconcile, and a first proposal and a revision use the same rules (ADR-0122). TIMED_OUT is different from DECLINED, so that every reader can tell silence from a refusal (ADR-0118). A terminated embargo is a fact of the register, not a fact about each participant. A lapse follows the replaces chain. Thus only an embargo that was in force can bind, and a withdrawal from a later embargo ends the binding of an earlier embargo. |
|
CM-18-019 |
MUST | Proposing an embargo MUST write an UNINVITED consent row for it on every current participant.A participant that was not asked holds a row that says so. Thus no reader infers "not asked" from a missing record, and a check can use the register to find a row for each participant and each embargo (CM-18-001). |
Implements: CM-18-001 |
CM-18-020 |
MUST | Creating a participant record MUST write an UNINVITED consent row on it for every entry already in the case's embargo register.A participant that joins after embargoes were proposed was asked about none of them. A row for each entry records that, so the participant holds a row for every entry from its creation on (CM-18-001), and no reader meets a missing row. |
Implements: CM-18-001 |
CM-18-021 |
MUST NOT | A reader MUST NOT read a missing consent row as any consent state. A missing row is a defect. Every row is written (CM-18-019, CM-18-020), so a missing row comes only from a fault. A reader that treated it as UNINVITED, or as any other state, would hide the fault, and could count a participant as asked, bound or free when it is not. |
Extends: CM-18-001 |
CM-10-001 |
MUST | CaseParticipant MUST record its consent per embargo: one consent row for every entry in the case's embargo register, naming the embargo and the participant's answer to it, UNINVITED until it is asked (CM-18-001). A participant agrees to an embargo explicitly, by an Accept, as its proposer, by seeding (CM-14-003, CM-14-005), or by containment, when the Case Owner activates a revision that ends no later than terms the participant had agreed to (EP-05-001). Each invitation's RSVP deadline is stored on that invitation's INVITED row (CM-28-013). No other record of embargo consent may exist on the participant.Consent is per embargo (ADR-0093, ADR-0122), so a revision does not inherit an agreement given to an earlier version (CM-18-001). The CM-10-004 content gate reads the rows, so they must name every embargo that binds the participant, including one that containment carries over: an agreement to N days is an agreement to every shorter period, so no explicit Accept is needed for it. A second record of consent beside the rows can disagree with them, and a reader cannot know which is correct. |
Uses definition from: CM-18-001 See also: CM-14-003 — context for the reader See also: CM-14-005 — context for the reader See also: CM-28-013 — context for the reader See also: EP-05-001 — context for the reader |
A participant that joins late stays UNINVITED on embargoes that are no longer in force.
That participant is invited only to the embargo in force and to open revisions.
UNINVITED and DECLINED both leave the participant unbound by the embargo that the row answers.
They are distinct states, because it matters whether the participant gave an answer.
The lapsed read stops at a DECLINED row and passes over an UNINVITED row (§9.3 Signatory and Lapsed).
The CASE_MANAGER relays an open proposal to a joiner only while the joiner's row for that proposal is UNINVITED.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-11-006 |
MUST | When the CASE_MANAGER sends a stub Invite (Invite(Actor)[target=VulnerabilityCaseStub]), it MUST create the invitee's CaseParticipant in the same step. The participant is inert (CM-10-004).The CASE_MANAGER needs to track every invitee from the moment it is invited — whether it has been told and how it answered — including the invitees that decline (ADR-0114). |
Uses definition from: CM-10-004 |
CM-11-026 |
MUST | The CaseParticipant a stub Invite creates MUST hold the Invite's roles, RM RECEIVED, VF v (VENDOR), and an INVITED row for an active embargo.The invitee has been told of the case and has decided nothing. RM RECEIVED and VF v record exactly that. The INVITED row records that it was asked about the embargo in force and has not answered (CM-18-001). |
Extends: CM-11-006 |
CM-11-023 |
MUST | When it sends a stub Invite, the CASE_MANAGER MUST commit its own create_case_participant (Create(CaseParticipant)) entry, separate from the Invite's invite_actor_to_case entry.The ledger holds the wire messages that the actors exchanged, and every state change has a message. The Invite is one message. Creating the invitee's record is the CASE_MANAGER's own act, so it is a second message with its own entry (ADR-0114, ADR-0124). |
Extends: CM-11-006 |
CM-11-024 |
MUST | The create_case_participant entry MUST carry the whole participant record as stored: its statuses and consent rows, with their ids and times.A replica copies the record from the entry and derives nothing (CM-11-025, ADR-0124). The entry must therefore carry every field the CASE_MANAGER holds, or the replica's record differs from the CASE_MANAGER's. |
Extends: CM-11-023 |
CM-11-025 |
MUST | A replica MUST store an invitee's record exactly as the create_case_participant entry carries it, and derive none of it from the Invite's entry.Replicas copy; they never mint ids, read clocks or run lifecycle logic (ADR-0124). A record a replica derived could differ from the CASE_MANAGER's in an id or a time, and the copies of the case would then disagree. |
Depends on: CM-11-024 |
EP-09-011 |
MUST | When the CASE_MANAGER admits a participant (Accept(Invite(Actor)[target=VulnerabilityCaseStub])) while an embargo proposal is open, it MUST relay an Invite(EmbargoEvent) for every open proposal to the joiner and commit each as a ledger entry, after the joiner holds the case and the prior ledger. Each Invite has actor set to the CASE_MANAGER's ID and attributedTo set to the proposal's original proposer (EP-09-002). A proposal whose consent row for the joiner has already left UNINVITED is not relayed again. Every participant holds a row for every register entry (CM-18-001). The row's state, not its presence, says whether the joiner was asked. The joiner's row for the active embargo is unchanged (EP-09-004), so a joiner that accepts the revision is a signatory of it at activation and one that does not lapses (ADR-0093, EP-05-001).A joiner is seated after the relay of a proposal (EP-09-002), so it was never on the roster when the Invite went out, and nothing else would ask it. A new participant becomes a signatory to the embargo in effect when it joins, and is asked about a revision on the table exactly like the participants who were present when it was proposed. |
Uses definition from: EP-09-002 Uses definition from: CM-18-001 See also: EP-05-001 — context for the reader See also: EP-09-004 — context for the reader |
INVITED carries the invitation's RSVP Deadline on the row itself (§9.4 Deadlines and the Pocket Veto).
Each deadline belongs to one invitation.
A participant can therefore hold several INVITED rows with different deadlines.
When one deadline passes, it times out only its own row.
---
title: Participant Embargo Consent State Machine (one row per participant and embargo)
---
stateDiagram-v2
direction LR
[*] --> UNINVITED
UNINVITED --> INVITED: INVITE
UNINVITED --> AGREED: AGREE
UNINVITED --> DECLINED: DECLINE
INVITED --> AGREED: AGREE
INVITED --> DECLINED: DECLINE
INVITED --> TIMED_OUT: TIME_OUT
AGREED --> DECLINED: DECLINE
DECLINED --> INVITED: INVITE
DECLINED --> AGREED: AGREE
TIMED_OUT --> INVITED: INVITE
TIMED_OUT --> AGREED: AGREE
TIMED_OUT --> DECLINED: DECLINE
The diagram shows the five states of one consent row and the triggers INVITE, AGREE, DECLINE and TIME_OUT that move it.
CARRY_OVER also moves every state except AGREED to AGREED, when the Case Owner activates a revision that ends no later than the embargo it replaces; those edges are omitted for legibility.
No state is terminal: a row stops accepting triggers when its embargo's register entry reaches a final status.
See also
9.2 Transitions and Guards
Five triggers drive each row. INVITE records an invitation. AGREE and DECLINE record an answer. TIME_OUT fires when the RSVP deadline of an invitation passes with no answer. CARRY_OVER agrees for a participant when the Case Owner activates a revision that asks nothing new of that participant.
| Trigger | From | To |
|---|---|---|
INVITE |
UNINVITED, DECLINED, TIMED_OUT |
INVITED |
AGREE |
UNINVITED, INVITED, DECLINED, TIMED_OUT |
AGREED |
DECLINE |
UNINVITED, INVITED, AGREED, TIMED_OUT |
DECLINED |
TIME_OUT |
INVITED |
TIMED_OUT |
CARRY_OVER |
every state except AGREED |
AGREED |
No other trigger is valid from any state.
A row for an embargo whose register entry is final (REJECTED, SUPERSEDED, CANCELLED or TERMINATED) accepts no trigger.
The consent given to an embargo that is no longer in play therefore stays frozen as it stood.
AGREED refuses INVITE.
A new request does not undo consent that a participant already gave.
If the terms change after a participant agrees, that participant is invited on its row for the new embargo.
This invitation leaves its AGREED row for the old embargo unchanged.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-18-003 |
MUST | The consent row machine MUST implement exactly the following valid triggers, each applied to the row for one embargo: INVITE (from UNINVITED, DECLINED or TIMED_OUT, to INVITED), AGREE (from UNINVITED, INVITED, DECLINED or TIMED_OUT, to AGREED), DECLINE (from UNINVITED, INVITED, AGREED or TIMED_OUT, to DECLINED), TIME_OUT (from INVITED only, to TIMED_OUT) and CARRY_OVER (from every state except AGREED, to AGREED). No other trigger is valid from any state, and a row for an entry in a final register status (SUPERSEDED, REJECTED, CANCELLED, TERMINATED) accepts no trigger at all.DECLINED and TIMED_OUT are not terminal. The CASE_MANAGER can invite again a participant that declined or that let an invitation time out, for example when the embargo terms change. AGREED does not accept a new invitation, so a second request does not cancel a consent that the participant gave. AGREE is valid from DECLINED, because an Accept after a decline is a change of answer by the participant. The participant has just said that it accepts. Thus its row moves directly, with no re-invite step. Only the participant's own answer moves a DECLINED row in this way. Seeding (CM-14-003, CM-14-005) and the Accept of the full-case Invite never cancel a decline. Per ADR-0048, AGREE and DECLINE are valid directly from UNINVITED, because consent does not always come through an invitation. A Finder who sets the embargo on its own case has no inviter. Participants added during case initialization already have an embargo in scope (ADR-0041). The reporter gives its consent when it submits the report (CM-14-005). A required synthetic INVITED step for these paths would record an invitation that did not occur. Per ADR-0093, DECLINE is also valid from AGREED. A participant bound by an embargo MAY withdraw its consent when it rejects the active embargo (VP-13-007, VP-13-008). A rejection of a proposed embargo declines only the row for that embargo. It does not change the participant's row for the embargo in force (MSM-07-004). Per ADR-0118, TIME_OUT is only the timer path (CM-18-002). A late Accept that the CASE_MANAGER honours moves TIMED_OUT → AGREED directly (EMB-17-002), and a late explicit Reject moves TIMED_OUT → DECLINED. Only the activation of a revision that ends at or before the end of the embargo it replaces causes CARRY_OVER (EP-05-003). CARRY_OVER also lifts a DECLINED row. An agreement to N days is an agreement to every shorter period. A decline of a shorter revision objects to the loss of time, not to the embargo. A row whose embargo is final records the past. Thus a participant cannot give more consent to it. The CASE_MANAGER answers a late Accept of such terms with an invitation to the case's current terms, which are the Active Embargo or, with none in force, the earliest-expiring open proposal (EMB-17-003, EP-08-002). A lapse and a termination are not triggers. They are derived (CM-18-001, CM-18-016). |
Uses definition from: CM-18-001 |
CM-18-004 |
MUST NOT | A participant's consent row MUST NOT move from AGREED to INVITED directly. The only paths back to INVITED from a resolved row are DECLINED → INVITED (re-invite after explicit decline) and TIMED_OUT → INVITED (re-invite after an unanswered invitation timed out); a participant that has lapsed is re-invited on its row for the new embargo (an INVITED row for it), which leaves its AGREED row for the old embargo alone.Consent already given cannot be withdrawn by re-inviting the participant. A signatory to the active embargo is bound by it; only replacing that embargo with longer terms (which lapses the participant by derivation — ADR-0093, ADR-0122) or the participant's own withdrawal ( DECLINE) ends that position. |
Derives from: CM-18-003 |
AGREE and DECLINE are valid directly from UNINVITED.
Consent does not always come through an invitation.
A finder that opens a case for its own finding and sets its default embargo received no invitation from anybody.
A reporter consents by reporting.
A required INVITED step on these paths would make the case history record an invitation that did not happen.
A repeated answer is not a transition.
When a participant sends the same answer to the same invitation again, the CASE_MANAGER changes nothing, records nothing in the case ledger and sends nothing, whatever activity id the repeat carries.
A different answer is a new answer, and the table above applies to it.
A participant that declined and then agrees has changed its answer, so its row moves directly to AGREED, with no new invitation.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-13-005 |
MUST | A repeated embargo answer is a second Accept, or a second Reject, of one embargo invitation by the same participant, whatever its activity id. The receiver of a repeated answer MUST change no state, add no ledger entry and send no message because of it. Answers from different participants are separate consents.Delivery is at least once. A participant can send the same answer again under a new activity id. If a repeat counted, the receiver would add a ledger entry and a fan-out for a consent that did not change. Every replica would then record an answer that was not a new decision. Each participant gives consent for itself. Thus the answer of one participant is never a repeat of the answer of a different participant. |
None of DECLINED, TIMED_OUT and AGREED is terminal.
A DECLINED or TIMED_OUT row can be invited again, and this re-invitation makes renegotiation possible.
An AGREED row can be declined.
What ends the life of a row is its register entry reaching a final status, not any state of the row.
9.3 Signatory and Lapsed
Two positions a participant can hold are not states. Each position is a read of the participant's rows and the case's register. Neither position is stored or drawn on the state machine.
| Read | Definition |
|---|---|
| Signatory | The participant's row for the register's ACTIVE entry is AGREED. |
| Lapsed | An entry is ACTIVE, the participant's row for it is neither AGREED nor DECLINED, and, following replaces back from the ACTIVE entry, the first entry whose row is AGREED or DECLINED has an AGREED row. |
With no ACTIVE entry nobody is a signatory and nobody has lapsed.
After an embargo is terminated, no entry is ACTIVE, so the termination writes no row.
The position of every participant follows from the register alone.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-18-001 |
MUST | Each participant record MUST hold one embargo consent row for every entry in the case's embargo register. Each row holds one of five states. The UNINVITED state means not asked, and is the start state. The INVITED state means asked, with no answer yet. The AGREED state records agreement, and DECLINED records an explicit refusal or a withdrawal. The TIMED_OUT state means invited, with the RSVP deadline passed and no answer. A participant is a signatory when its row for the register's ACTIVE entry is AGREED. A participant has lapsed when three things hold. An entry is ACTIVE, and the participant's row for it is neither AGREED nor DECLINED. Following replaces back from the ACTIVE entry, the first entry whose row is AGREED or DECLINED has an AGREED row. Both positions are read from the rows and the register, never stored (CM-18-016). With no ACTIVE entry, nobody is a signatory and nobody has lapsed.One row for each pair of participant and embargo records each answer one time. To find if a participant is bound by the active embargo, a reader looks at the row for the active embargo. Thus there is no second record to reconcile, and a first proposal and a revision use the same rules (ADR-0122). TIMED_OUT is different from DECLINED, so that every reader can tell silence from a refusal (ADR-0118). A terminated embargo is a fact of the register, not a fact about each participant. A lapse follows the replaces chain. Thus only an embargo that was in force can bind, and a withdrawal from a later embargo ends the binding of an earlier embargo. |
|
CM-18-019 |
MUST | Proposing an embargo MUST write an UNINVITED consent row for it on every current participant.A participant that was not asked holds a row that says so. Thus no reader infers "not asked" from a missing record, and a check can use the register to find a row for each participant and each embargo (CM-18-001). |
Implements: CM-18-001 |
CM-18-020 |
MUST | Creating a participant record MUST write an UNINVITED consent row on it for every entry already in the case's embargo register.A participant that joins after embargoes were proposed was asked about none of them. A row for each entry records that, so the participant holds a row for every entry from its creation on (CM-18-001), and no reader meets a missing row. |
Implements: CM-18-001 |
CM-18-021 |
MUST NOT | A reader MUST NOT read a missing consent row as any consent state. A missing row is a defect. Every row is written (CM-18-019, CM-18-020), so a missing row comes only from a fault. A reader that treated it as UNINVITED, or as any other state, would hide the fault, and could count a participant as asked, bound or free when it is not. |
Extends: CM-18-001 |
MSM-07-006 |
MUST | When an ET / REMOVE_EMBARGO_EVENT_FROM_CASE wire activity terminates the embargo register's ACTIVE entry, implementations MUST leave the case with no active embargo. The same step cancels every open proposal, so the derived EM becomes EXITED. No separate outbound wire activity is emitted; the participant position is derived from the case. A register with a TERMINATED entry accepts no further change (ADR-0122), so a terminated embargo can never be invited to again. That is a fact about the case, which every replica holds once it replays the teardown. |
Uses definition from: MSM-02-007 |
MSM-07-025 |
MUST NOT | When an ET terminates the embargo register's ACTIVE entry, implementations MUST NOT write any participant's consent rows. With no active embargo no participant is a signatory and no row binds anyone. An Accept or Reject that arrives afterwards records nothing (EMB-17-004). The termination is a fact about the case, so it does not need copying onto each participant record as a terminal consent state. Leaving the rows as they were also keeps the history of who agreed to what, and every row of a final entry is frozen (CM-18-003). |
Extends: MSM-07-006 See also: EMB-17-004 — context for the reader |
After the case is public, an exploit is public or attacks are observed, abandoning an open proposal also writes no row.
The CASE_MANAGER cancels the proposal with a Reject if it received the proposal, or with an Undo if it made the proposal itself.
Then the CASE_MANAGER withdraws each invitation that it relayed for the proposal, with an Undo.
Each row for the canceled proposal is frozen as it stood.
The CASE_MANAGER's Reject is its abandonment, not its consent.
A CASE_MANAGER that has a stake in an embargo therefore records its own answer as its own update of the row, never as a Reject.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EMB-16-001 |
MUST | A Participant in EM Proposed (q^em ∈ P) MUST abandon the proposed embargo when it detects a CS transition into P, X or A. The P state is public (q^cs ∈ ···P··), X is exploit-available (q^cs ∈ ····X·), and A is attacks-observed (q^cs ∈ ·····A). It cancels each open proposal in the case's embargo register, so EM derives None (q^em P → N). The CASE_MANAGER cancels a proposal it received with its ER, Reject(Invite(EmbargoEvent)), committed as reject_invite_to_embargo_on_case. It cancels a proposal it made itself with its Undo(Invite(EmbargoEvent)), committed as undo_invite_to_embargo_on_case. After either, it sends its Undo(Invite(EmbargoEvent)) of each Invite it relayed for that proposal. A proposal never relayed is cancelled all the same.EMB-01-002 establishes that embargo negotiation is not viable once public disclosure, exploit availability, or attacks have occurred. EMB-01-002 is framed as a guard on receiving EP, but the same viability constraint applies when a P/X/A state change arrives while a proposal is already in flight. Continuing to negotiate a proposed embargo in these conditions would be misleading to other Participants and counter to the purpose of coordinated disclosure. CANCEL records that nobody decided the proposal (ADR-0122). An actor undoes only an activity it performed, so withdrawing an Invite one sent is an Undo and declining one received is a Reject; a CASE_MANAGER act with a participant's verb and object carries the participant's semantic type (ADR-0152).ECA DetailsPreconditions - EM state is Proposed - EM state: PROPOSED- CS transitions to public (q^cs ∈ ···P··) - CS pattern: ...P..- CS transitions to exploit-available (q^cs ∈ ····X·) - CS pattern: ....X.- CS transitions to attacks-observed (q^cs ∈ ·····A) - CS pattern: .....ASteps 1. [system] Detect that CS has transitioned to a P/X/A state while EM is Proposed → An open proposal is recognised 2. [system] As the CASE_MANAGER, cancel each open proposal: commit its Reject of the proposal, or its Undo of an own proposal, then an Undo of each Invite relayed for it → Each proposal's register entry is CANCELLED and EM derives NONE; the entries are committed and replayed by every replica Postconditions - EM state is NONE; the abandonment is committed; proposed embargo abandoned |
|
EMB-16-003 |
MUST | A Participant that abandons a proposed embargo on a P/X/A transition (EMB-16-001) MUST notify the other Participants. Continuing to negotiate a proposed embargo that is no longer viable would mislead the other Participants. The CASE_MANAGER's committed entries are the notice to every other Participant (EP-09-007, EP-09-009). |
Extends: EMB-16-001 |
EMB-16-004 |
MUST | The CASE_MANAGER MUST commit the entries that abandon every open proposal (EMB-16-001) in one transaction (CLP-07-015). A partly committed abandonment would leave some proposals open after the case reached P/X/A, so the case's register and its replicas would disagree about which proposals are still open. |
Extends: EMB-16-001 Refines: CLP-07-015 |
EMB-16-005 |
MUST | A replica MUST apply each abandoned proposal's CANCEL once, from the entry that carries it (ADR-0152). The CASE_MANAGER's Reject cancels the proposal, and each Undo after it finds the proposal cancelled and changes nothing. Applying the CANCEL from its own entry keeps the replica's register equal to the CASE_MANAGER's. |
Extends: EMB-16-001 |
A participant lapses when the Case Owner activates a revision that ends later than the embargo that the participant agreed to, and the participant has not agreed to the revision.
The participant did agree, but the embargo in force has since become something that the participant did not agree to.
Only the embargoes that were once in force are on the replaces chain.
Agreement to a proposal that never took effect therefore gives the participant nothing to lapse from.
A participant that withdrew from a later embargo has a DECLINED row on the chain.
That participant has not lapsed when a further revision replaces that later embargo.
Lapsed is neither the proposal state nor the deadline state
A revision that is only proposed lapses nobody.
A revision that ends no later than the accepted terms also lapses nobody.
A participant that lets an invitation deadline pass reaches TIMED_OUT on that invitation's row, not lapsed.
A lapse is not timer-based and has no transition of its own.
A lapsed participant is re-invited on an INVITED row for the embargo in force, and the deadline attaches to that invitation.
A revision does not move anyone's consent to the embargo in force until it takes effect.
While a revision is only proposed, the prior embargo is in force and every signatory to it remains one.
The proposer's row for the revision is AGREED, because proposing terms is consenting to them.
Every other participant gets an UNINVITED row for the revision.
A signatory that agrees to the revision records that agreement on the revision's row.
A signatory that declines the revision refuses those terms and nothing more, on that row only.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EP-05-002 |
MUST NOT | A revision proposal (ACTIVE → REVISE) and any further counter-revision (REVISE → REVISE) MUST NOT change any participant's consent to the embargo in force. The proposer's row for the proposed embargo becomes AGREED (MSM-07-022). Every other participant gets an UNINVITED row for it (CM-18-001). Every other row stays as it is until the Case Owner activates a revision (EP-05-001, EP-05-003). Until then the prior embargo stays in force, and every signatory to it remains one.A participant cannot lapse until the embargo on the case differs from the one they agreed to. Lapsing on proposal would strand signatories when the revision is rejected, report participants who are still bound and still receive embargoed content as not bound, and lapse the proposer of the revision (ADR-0093). With per-embargo rows a proposal only ever adds rows for the proposed embargo. |
Uses definition from: CM-18-001 Refines: MSM-07-022 See also: EP-05-001 — scope boundary: a different transition See also: EP-05-003 — context for the reader |
MSM-07-003 |
MUST | The wire activity ACCEPT_INVITE_TO_EMBARGO_ON_CASE (wire form: Accept(Invite(EmbargoEvent)[context=VulnerabilityCase])) is always its sender's own consent, the Case Owner's included. An actor applying it MUST apply the PEC AGREE trigger to the sender's row for the accepted embargo. The row advances from UNINVITED, INVITED, DECLINED or TIMED_OUT to AGREED. The accepted embargo may be the active embargo, a first proposal (EM PROPOSED) or a proposed revision of an embargo still in force. Only the accepted embargo's row is marked. A participant is a signatory exactly when its row for the active embargo is AGREED. So accepting a proposed revision binds the participant to nothing new until the owner activates it (MSM-07-008). An Accept from a DECLINED row is the participant changing its answer, so the row moves directly to AGREED with no re-invite first (CM-18-003). An Accept of an embargo that is not available records nothing (CM-18-003): MSM-07-012 refuses it, and MSM-07-039 answers one the register never held. The Case Owner's decision for the case has its own activity (MSM-07-008, ADR-0122), so an Accept of an Invite means one thing whoever sends it and no handler branches on the sender to learn what it means. The PEC AGREE trigger is valid directly from UNINVITED because consent can be self-determined without an invitation (ADR-0048, ADR-0091, CM-18-003). Consent is per embargo (CM-10-001, ADR-0093, ADR-0122): an Accept is always a statement about the embargo it names, so it always marks that embargo's row and there is no first-proposal versus revision asymmetry to special-case. |
Uses definition from: CM-18-003 See also: MSM-07-008 — context for the reader |
MSM-07-004 |
MUST | The wire activity REJECT_INVITE_TO_EMBARGO_ON_CASE (wire form: Reject(Invite(EmbargoEvent)[context=VulnerabilityCase])) is its sender's own consent whenever a participant sends it, the Case Owner included. Unless MSM-07-014 refuses it, an actor applying it MUST apply the PEC DECLINE trigger to the sender's row for the rejected embargo. DECLINE is valid from UNINVITED, INVITED, AGREED or TIMED_OUT. A Reject of the active embargo from any row but AGREED refuses the terms in force and declines that row only. The CASE_MANAGER's own Reject of a proposal is not its consent but its abandonment (MSM-07-016). Symmetric with MSM-07-003: the Case Owner's rejection of a proposal for the case has its own activity (MSM-07-009, ADR-0122), so a Reject of an Invite is the sender's consent and nothing else. The PEC DECLINE trigger is valid directly from UNINVITED for symmetric reasons to AGREE (ADR-0048, ADR-0091, CM-18-003). |
Uses definition from: CM-18-003 |
MSM-07-015 |
MUST | An actor that applies a Reject of a proposed embargo that is not active MUST leave the sender's row for the active embargo unchanged. A signatory's rejection of a proposed revision refuses those terms; it is not withdrawal from the embargo in force. When no embargo is in force (EM PROPOSED), a Reject of a proposal declines that proposal's row only. It withdraws from nothing, and the participant's AGREED rows for other open proposals stay AGREED. Consent is per embargo, so a signatory who refuses proposed terms is still bound by, and still consents to, the embargo that remains active; only the Case Owner decides whether the proposal replaces it (MSM-07-009, ADR-0122). |
Extends: MSM-07-004 |
A signatory withdraws by leaving the embargo in force with Leave(EmbargoEvent), not by rejecting an invitation to it.
The withdrawal declines the signatory's row for the embargo in force.
The withdrawal also declines each open proposal's row that the signatory had agreed to, because every open proposal is a revision of the embargo that the signatory is leaving.
A Reject of the active embargo from an AGREED row is refused with a reported reason.
The Case Owner does not leave an embargo.
The Case Owner ends an embargo by terminating it.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
MSM-07-010 |
MUST | The wire activity Leave(EmbargoEvent)[context=VulnerabilityCase] is a participant's withdrawal of its consent to the case's active embargo. For a sender whose row for that embargo is AGREED, the receiver MUST apply the PEC DECLINE trigger to that row. A Leave changes no register entry.Accept and Reject answer an Invite; leaving an embargo one is bound by is a different act, as Leave(VulnerabilityCase) is for leaving the case. A dedicated activity covers every signatory, including those made signatories with no Invite (CM-14-005, CM-11-001), and keeps a Reject from meaning refusal or withdrawal by the state of the case. The rejected alternatives are recorded in ADR-0122. |
Uses definition from: VAM-05-011 Uses definition from: CM-18-003 Implements: VP-13-017 |
MSM-07-035 |
MUST NOT | A DECLINED participant MUST NOT hold an AGREED row for an embargo that can become active without re-invitation. A participant that has withdrawn from an embargo has to be asked again before terms bind it, or its withdrawal would be undone by an activation it took no part in. |
|
MSM-07-034 |
MUST | On a withdrawal (MSM-07-010), the receiver MUST also decline every open proposal's row that the sender had AGREED to. Every open proposal is a revision of the embargo withdrawn from (EP-08-004). An agreed revision left in place would make the withdrawer a signatory again as soon as the owner activated it (MSM-07-035). |
Implements: MSM-07-035 Extends: MSM-07-010 Derives from: EP-08-004 |
MSM-07-036 |
MUST | The receiver MUST refuse a Leave(EmbargoEvent), with a reported reason, in three cases. Its embargo is not the active one, the sender's row for it is not AGREED, or the sender is the Case Owner. The Case Owner ends an embargo by terminating it (CM-02-005). Only a signatory of the embargo in force can withdraw from it, and the Case Owner holds the termination instead. |
Extends: MSM-07-010 See also: CM-02-005 — context for the reader |
VAM-05-011 |
MUST | WITHDRAW_FROM_EMBARGO_ON_CASE MUST be represented as Leave(EmbargoEvent)[context=VulnerabilityCase], whose object is the embargo in force, carried inline or by reference, and not an Invite (ADR-0122).Withdrawal answers no Invite, so it names the embargo itself; it is told apart from Leave(VulnerabilityCase), which leaves the case, by its object (MSM-07-010). |
Only the Case Owner's decision changes the embargo on the case. The answers of the other participants inform that decision. When the owner activates a revision, the direction of the change decides what happens to the consent of the signatories to the old terms:
- A revision that ends no later than the terms it replaces asks nothing new of anyone who agreed to the old terms, because agreeing to N days is agreeing to every shorter period.
The CASE_MANAGER applies
CARRY_OVERto the revision's row of every participant whose row for the replaced embargo isAGREED. This rule includes aDECLINEDrow for the revision. - A revision that ends later asks for more than they promised.
No row is written.
By the definition above, a signatory to the old terms whose row for the revision is not
AGREEDhas lapsed.
In both cases, a participant that already holds an AGREED row for the revision is a signatory to the revision by lookup.
This is true for the proposer and for an early acceptor.
Only signatories to the old terms are carried over.
A participant that had lapsed from an earlier embargo stays lapsed until it is re-invited or agrees.
If the activation makes the invitation of an INVITED participant stale, that participant is re-invited to the current terms, as in §9.4 Deadlines and the Pocket Veto.
If the owner rejects the revision instead, the old terms stand and nobody's consent changes.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EP-09-005 |
MAY | The Case Owner MAY activate or reject an open revision at any time, without waiting for any other participant to answer the revision Invite. The owner's Add(EmbargoEvent)[target=VulnerabilityCase] activates the revision and the owner's Reject(EmbargoEvent)[target=VulnerabilityCase] keeps the prior terms (MSM-07-008, MSM-07-009); either is committed as a ledger entry and decides the embargo. The owner's Accept or Reject of the revision Invite is only its own consent (MSM-07-003, MSM-07-004).Only the Case Owner's answer changes the embargo on the case; the other participants' answers inform that decision, they do not make it (ADR-0093). The Invites are not a vote: they gather the consent records the activation cascade reads (EP-05-001). The owner's decision settles the embargo; the answers settle who is bound by it. |
Uses definition from: MSM-07-008 Uses definition from: MSM-07-009 See also: MSM-07-003 — context for the reader See also: MSM-07-004 — context for the reader |
MSM-07-008 |
MUST | The wire activity ACTIVATE_EMBARGO_ON_CASE (wire form: Add(EmbargoEvent)[target=VulnerabilityCase], the EmbargoEvent itself as the object, inReplyTo naming the Invite(EmbargoEvent) that proposed it) is the Case Owner's decision for the case. It MUST activate the named proposal's embargo register entry and supersede any entry in force in the same step. The derived EM becomes ACTIVE (EA, or EC for a revision). Giving the owner's decision its own activity retires the two-audience rule: an Accept of an Invite is always the sender's consent (MSM-07-003), and this activity is always the owner's decision for the case, so neither meaning depends on who sent the message (ADR-0122). The activity is an Add because the case gains the embargo, as the Remove that ends it takes it away, so the decision and a consent differ by verb (ADR-0180). When it replaces an embargo in force, the MSM-07-005 consent rule settles the rows. |
Uses definition from: VAM-05-008 |
MSM-07-027 |
MUST | The CASE_MANAGER MUST accept ACTIVATE_EMBARGO_ON_CASE only from the Case Owner. It refuses any other sender with REFUSED before any write (HP-01-006). Activating an embargo is the Case Owner's decision for the case (CM-02-005), so no other participant's activity may make it. |
Extends: MSM-07-008 Refines: HP-01-006 |
MSM-07-028 |
MUST | ACTIVATE_EMBARGO_ON_CASE MUST mark the Case Owner's row for the activated embargo AGREED when that row is UNINVITED, INVITED or TIMED_OUT. An AGREED row is left as it is, and an activation from a DECLINED row is refused (MSM-07-037). The owner that activates terms is bound by them, so its own row has to say so. A row that holds no answer the owner gave, or only a lapsed invitation, contradicts nothing when it becomes AGREED, so the owner need not accept before it activates (ADR-0180). |
Extends: MSM-07-008 Uses definition from: CM-18-003 |
MSM-07-029 |
MUST | The CASE_MANAGER MUST refuse ACTIVATE_EMBARGO_ON_CASE before committing it in two cases. One is a named embargo that is not an open proposal of the case. The other is CS that is public, exploited or attacked (EMB-02-002). Refusing a doomed activation before the commit keeps the ledger free of an entry that replicas, copying its step, would apply without the CASE_MANAGER's P/X/A check (CM-23-016). |
Extends: MSM-07-008 Refines: EMB-02-002 |
MSM-07-009 |
MUST | The wire activity REJECT_EMBARGO_PROPOSAL_ON_CASE (wire form: Reject(EmbargoEvent)[target=VulnerabilityCase], the EmbargoEvent itself as the object, inReplyTo naming the Invite(EmbargoEvent) that proposed it) is the Case Owner's decision for the case. It MUST reject the named proposal's embargo register entry. Once no other proposal is open, the derived EM becomes NONE (ER) or stays ACTIVE with the prior terms in force (EJ). It stays PROPOSED or REVISE while another proposal is open (EMB-18-005). The owner's rejection decides the proposal for the case; whether the owner, as a participant, also refuses those terms is a separate Reject of the Invite (MSM-07-004). The owner's own row does not constrain the rejection: an owner that accepted terms for itself may still reject them for the case (ADR-0180). Keeping the two apart lets the owner keep the prior terms without declining them (ADR-0122). |
Uses definition from: VAM-05-009 Uses definition from: EMB-18-005 |
MSM-07-030 |
MUST | The CASE_MANAGER MUST accept REJECT_EMBARGO_PROPOSAL_ON_CASE only from the Case Owner. It refuses any other sender with REFUSED before any write (HP-01-006). Deciding a proposal for the case is the Case Owner's authority, so no other participant's activity may reject it for the case. |
Extends: MSM-07-009 Refines: HP-01-006 |
MSM-07-032 |
MUST | This rule covers REJECT_EMBARGO_PROPOSAL_ON_CASE of the last open revision while CS is public, exploited or attacked. The CASE_MANAGER MUST also terminate the embargo in the same act (EMB-04-002). It trial-applies both steps before committing either. It commits the Reject's entry carrying the REJECT step, then its own ET Remove(EmbargoEvent) entry carrying the TERMINATE step. A refused termination commits neither.Reverting to the prior terms is not viable once disclosure has happened, so the rejection ends the embargo. Deciding both steps together means a replica copying both entries ends with the revision REJECTED and EM EXITED, as the CASE_MANAGER does. |
Extends: MSM-07-009 Refines: EMB-04-002 |
MSM-07-033 |
MUST | The CASE_MANAGER MUST refuse REJECT_EMBARGO_PROPOSAL_ON_CASE before committing it when the named embargo is not an open proposal of the case. There is nothing to decide, and a committed entry naming no open proposal would be applied by every replica that copies it. |
Extends: MSM-07-009 |
MSM-07-031 |
MUST NOT | REJECT_EMBARGO_PROPOSAL_ON_CASE MUST NOT change any participant's consent rows, the Case Owner's included. The owner's decision for the case is not its consent as a participant; that is a Reject of the Invite (MSM-07-004). |
Extends: MSM-07-009 |
EP-05-001 |
MUST NOT | This rule covers the Case Owner's activation of a revised embargo that ends later than the embargo it replaces (REVISE → ACTIVE). The CASE_MANAGER MUST NOT carry any participant's consent over to it.A participant who signed for terms T1 has not consented to longer terms T2; treating them as a signatory once T2 is in force would imply consent they never gave. A participant is bound by the revised embargo only through an AGREED consent row for it, so each signatory to the replaced embargo that has not agreed to the revised one has lapsed (CM-18-001), and no write is needed to lapse them. The rule applies at activation rather than at proposal because the participant remains bound by T1 for as long as T1 is the active embargo (ADR-0093, ADR-0122). |
Uses definition from: CM-18-001 |
EP-05-003 |
MUST | This rule covers the Case Owner's activation of a revised embargo that ends no later than the one it replaces. The CASE_MANAGER MUST apply CARRY_OVER to the revised embargo's row of each participant with an AGREED row for the replaced embargo. That includes a participant whose row for the revision is DECLINED (CM-10-001, CM-18-003, MSM-07-005).Shorter terms ask nothing new: agreeing to N days is agreeing to every shorter period, the same containment that makes shortest-wins (EP-04-003) safe without asking anyone, so their agreement is carried over by writing the row. That holds for a participant that declined the shorter revision too: its decline objected to losing time, not to keeping the embargo, and the decline stays in the ledger (ADR-0122). |
Uses definition from: CM-18-001 Uses definition from: CM-18-003 Refines: MSM-07-005 See also: CM-10-001 — context for the reader |
MSM-07-005 |
MUST | This rule covers the Case Owner's Add(EmbargoEvent)[target=VulnerabilityCase] (MSM-07-008) that replaces active embargo A with revision B. The register activates B and supersedes A, so the derived EM goes REVISE → ACTIVE, or stays REVISE while another proposal is open (EMB-18-005). Implementations MUST settle every participant's consent rows against B. Only the owner's acceptance changes the embargo on the case; other participants' accepts and rejects are recorded per embargo and inform that decision. When it replaces the embargo in force, each participant's standing has to be read again against the new terms (ADR-0093). |
Uses definition from: CM-18-003 Uses definition from: MSM-07-008 Uses definition from: EMB-18-005 |
MSM-07-021 |
MUST NOT | A revision proposal (EV, ACTIVE → REVISE, or a counter-revision REVISE → REVISE) MUST NOT change any participant's consent to the embargo in force. While a revision is merely proposed the prior embargo is still in force and every signatory to it is still bound by it, so nothing about their consent has changed (ADR-0093). |
|
MSM-07-022 |
MUST | When a participant proposes a revision, implementations MUST mark the proposer's row for the proposed embargo AGREED. Proposing terms is agreeing to them, so the proposer needs no Invite of its own proposal. |
Extends: MSM-07-021 |
MSM-07-023 |
MUST | The CASE_MANAGER MUST commit each carried-over row as its own CASE_MANAGER Update(EmbargoConsent) ledger entry, after the Accept's entry. The owner's own row is what its Accept states, applied from the Accept's entry.The CASE_MANAGER decides the carry-over. Committing each carried-over row as its own entry keeps every replica's consent rows in step with the CASE_MANAGER's. |
Implements: EP-05-003 |
MSM-07-024 |
MUST | Every replica MUST copy the CASE_MANAGER's carried-over consent entries rather than run the carry-over itself (ADR-0124, CLP-07-013, CM-23-016). A replica that ran the containment comparison on its own state could reach a different answer from the CASE_MANAGER's. |
Depends on: MSM-07-023 Refines: CM-23-016 See also: CLP-07-013 — context for the reader |
MSM-07-020 |
MUST NOT | This rule covers the owner's activation of revision B in place of active embargo A, where B ends later than A. Implementations MUST NOT write any consent row to lapse a participant. A participant whose row for B is not AGREED is not a signatory to B, and has lapsed if it had agreed to A (CM-18-001). Longer terms ask for more than the signatories of A promised, so only those who agreed to B are bound by B, and the rows say so without a write. |
Refines: MSM-07-005 Uses definition from: CM-18-001 |
9.4 Deadlines and the Pocket Veto
An embargo invitation does not stay open indefinitely.
If a participant neither agrees nor declines before the RSVP deadline, its row for that invitation moves to TIMED_OUT.
This move is the pocket veto.
The protocol does not treat silence as assent, because proceeding on an unanswered invitation would assert an agreement that the participant never gave.
The protocol also does not record silence as a refusal.
Only an explicit refusal reaches DECLINED.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-18-002 |
MUST | When an invitation's RSVP deadline passes with no answer, the CASE_MANAGER MUST apply the TIME_OUT trigger to that invitation's row only, recording TIMED_OUT, never DECLINED. A lapse has no timer and is not a stored transition (CM-18-001, CM-18-016). A lapsed participant's deadline is the one on its re-invitation to the embargo in force (CM-28-013).Per ADR-0093, ADR-0122 and notes/participant-embargo-consent.md, a participant has lapsed when the active embargo was replaced by longer terms it has not accepted. While a revision is only proposed, the prior embargo is still in force and binds every signatory, so nothing about their consent has changed. Per ADR-0118, a participant that did not answer has made no decision. Thus a timeout records TIMED_OUT, distinct from an explicit DECLINED, and both are re-invitable. Nothing stalls on a lapsed participant: the CM-10-004 gate already excludes it from embargoed content, and no invitation gives it a deadline. An RSVP deadline belongs to one invitation and is stored on that invitation's INVITED row (CM-28-013). Its passing times out only that row, never the participant's other invitations. Code, logs, demos and replicas read the consent row, not ledger provenance (ADR-0118), so the row itself carries the distinction. A late Accept the CASE_MANAGER honours returns a TIMED_OUT row to AGREED, a signatory only if that embargo is in force (EMB-17-002, MSM-07-003). ADR-0118 reverses ADR-0065's choice to record a lapsed invitation as DECLINED. |
Uses definition from: CM-18-001 Uses definition from: CM-18-003 Refines: CM-28-005 See also: CM-18-016 — context for the reader See also: CM-28-013 — context for the reader |
CM-18-022 |
MAY | A timer expiry (pocket veto) MAY drive a row's INVITED → TIMED_OUT transition, with no explicit participant action.A pocket veto exists so that an unanswered invitation cannot stall coordination. A participant that does not answer has made no decision, so the transition needs no act from it (ADR-0118). |
Refines: CM-18-002 |
CM-18-023 |
SHOULD | The pocket-veto timer period SHOULD be a policy window of 7 days. An Invite that names no deadline still needs one, or an unanswered invitation can stall coordination. A fixed default window gives every such invitation the same deadline, so every participant can predict when silence becomes TIMED_OUT. |
Extends: CM-18-022 |
CM-28-020 |
MUST | A consent row MUST reach DECLINED only by an explicit refusal.Reserving DECLINED for an explicit refusal lets the consent row tell "never responded" from "explicitly declined". Code, logs, demos and replicas read the row, not ledger provenance, so the row must carry the difference (ADR-0118). |
Extends: CM-18-002 |
MSM-07-007 |
MUST | The timer-based pocket-veto transition MUST be enforced lazily, with no outbound wire message for the consent change itself. That transition moves the row of the invitation whose deadline passed from INVITED to TIMED_OUT. A lapse has no timer path (CM-18-002): a lapsed participant is re-invited, and the deadline attaches to that invitation. Inaction cannot produce an outbound message because there is no actor-observable event to report. The expiry is a derived conclusion from (the row's rsvp_deadline, now). Requiring a wire message would demand the system speak on behalf of a participant who has said nothing, which contradicts the Actor Knowledge Model (AKM). |
Implements: CM-18-002 |
MSM-07-026 |
MUST | The CASE_MANAGER MUST author a case-ledger entry that records a pocket-veto expiry (CM-28-005), so the consent change is visible in the canonical ledger. No other protocol wire activity is required. The ledger entry is the record of the derived expiry, not a message sent by the silent participant. The entry already reaches every owner entitled to case content, so a second message would only duplicate it. |
Refines: CM-28-005 |
The deadline is explicit or defaulted:
- An embargo invitation can carry its own
endTime, giving an explicit RSVP Deadline. When present, thisendTimetakes precedence over the policy window. - When the invitation has no
endTime, a policy window applies. The default window is 7 days.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-28-001 |
MUST | An actor that reads an Invite(EmbargoEvent) MUST read its activity-level end_time, when present, as the RSVP-by deadline for that invitation. After that instant the invitation is no longer open.as_Object.end_time is inherited by as_Activity and therefore by every Vultron activity, so no vocabulary extension is required. On an Activity, AS2 end_time already means "valid until", making the RSVP reading idiomatic rather than a repurposing. Placing the deadline on the activity rather than on the embargo object is what allows the same embargo to be offered to several actors with different deadlines, and to one actor twice. See ADR-0065. |
|
CM-28-017 |
MAY | An Invite(EmbargoEvent) activity MAY carry an activity-level end_time.Every AS2 activity inherits end_time from as_Object, so a sender can state the RSVP-by deadline with no vocabulary extension. The field stays optional: without it, the CM-18-023 policy window sets the deadline (CM-28-019). See ADR-0065. |
Uses definition from: CM-28-001 |
CM-28-018 |
MUST NOT | An actor that reads an Invite(EmbargoEvent) MUST NOT read its activity-level end_time as the embargo's expiry.An embargo invitation carries two end_time fields one nesting level apart: the Invite's is the RSVP-by deadline, and the nested EmbargoEvent's is when the embargo ends. A reader that takes one for the other lapses the invitation or the embargo at the wrong instant. See ADR-0065. |
Extends: CM-28-001 |
CM-28-002 |
MUST | When an Invite(EmbargoEvent) carries an end_time, that value MUST be authoritative for the invitation's expiry, superseding the receiver's local policy window. The resulting deadline stays subject to the EP-07-006 ceiling.An explicit wire value lets both parties calculate the same lapse time from the same field, with no more messages. A window that only the receiver knows does not let the two parties agree if an invitation is still open. See ADR-0065. |
Supersedes: CM-18-023 Refines: EP-07-006 |
CM-28-019 |
MUST | When an Invite(EmbargoEvent) carries no end_time, the CM-18-023 policy window MUST set the invitation's expiry. The resulting deadline stays subject to the EP-07-006 ceiling.An Invite without a deadline still needs one, and a sender that predates ADR-0065 sends none. The policy window keeps the behaviour those invitations had before the wire value existed. See ADR-0065 and ADR-0096. |
Extends: CM-28-002 Refines: EP-07-006 Uses definition from: CM-18-023 |
EP-07-001 |
MUST | When an Invite(EmbargoEvent) carries no Invite.end_time, an implementation MUST apply a default RSVP window, measured from the invitation's published timestamp.An invitation with no deadline would leave the invitee's consent row INVITED for ever. A default window gives every invitation an end, so silence resolves. See ADR-0065. |
|
EP-07-009 |
SHOULD | The default RSVP window of EP-07-001 SHOULD be 7 days, matching CM-18-023. Aligning the fallback with the CM-18-023 policy window means an invitation that omits end_time gets the same answer window as the policy grants. See ADR-0065. |
Extends: EP-07-001 See also: CM-18-023 — context for the reader |
In both cases, two rules later in this section set a lower bound and an upper bound on the result.
The explicit endTime takes precedence over the policy window, but neither one escapes the minimum window or the embargo-end ceiling.
The pocket veto is the implicit form of this one mechanism, not a second mechanism alongside it.
One invitation carries two different end times
The invitation's endTime is the RSVP Deadline for the invitee.
The embargo event nested inside the invitation has its own endTime, which is when the embargo would expire.
They sit one nesting level apart and mean different things.
An implementation that reads the embargo's expiry as the RSVP deadline will hold invitations open for the embargo's full duration. An implementation that reads the RSVP deadline as the embargo expiry will end embargoes days after they were agreed.
Recording the deadline.
When the CASE_MANAGER relays an invitation, it sets the Invite's endTime and records the deadline on the invitee's INVITED row for the invited embargo.
Every replica records the same deadline by copying the CASE_MANAGER's ledger entry for that row.
A participant does not derive or store a deadline when it receives an Invite.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-28-012 |
MUST | When the CASE_MANAGER relays an Invite(EmbargoEvent) to a participant (EP-09-002) it MUST set the Invite's end_time to that Invite's published time plus the configured RSVP window, subject to the EP-07-002 minimum and the EP-07-006 ceiling. The Invites of one relay round are emitted in sequence and need not share one deadline.If the wire carries no deadline, each receiving store uses the EP-07-001 window from its own ActorConfig. Two replicas can then disagree about when the same invitation closes. The relaying CASE_MANAGER is the enforcement authority (CM-28-003). It states the deadline one time, and every participant reads the same value from the same object. ASK-03-004 requires the same of an ask (ADR-0065, ADR-0113). |
Uses definition from: EP-09-002 Refines: EP-07-002 Refines: EP-07-006 |
CM-28-013 |
MUST | The CASE_MANAGER MUST record an Invite's RSVP deadline on the invitee's INVITED row for that embargo, in an Update(EmbargoConsent) entry right after the Invite's (CLP-07-013).The deadline is case state about the invitee. As with all other case state, the CASE_MANAGER writes it one time, and it gets to replicas through the ledger (ADR-0108, ADR-0124). A deadline that a receiver writes would be in one store only. Replicas could then disagree about whether the invitation is open (ADR-0113). |
Extends: CM-28-012 Refines: CLP-07-013 |
CM-28-023 |
MUST | Every replica MUST record an Invite's RSVP deadline by copying the CASE_MANAGER's CM-28-013 Update(EmbargoConsent) entry (EP-09-007, ADR-0124).The deadline is case state about the invitee, so it reaches replicas through the ledger like all other case state (ADR-0108, ADR-0124). A replica that copies the entry holds the same deadline as the CASE_MANAGER, so the two agree on whether the invitation is open (ADR-0113). |
Depends on: CM-28-013 Refines: EP-09-007 |
CM-28-024 |
MUST NOT | A participant MUST NOT derive or store an RSVP deadline on receipt of an Invite (EP-09-003). A deadline that a receiver writes would be in one store only, and replicas could then disagree about whether the invitation is open. The CASE_MANAGER writes the deadline once (CM-28-013), and replicas copy it (CM-28-023; ADR-0113). |
Extends: CM-28-013 Refines: EP-09-003 |
Enforcing the deadline. Only the CASE_MANAGER enforces the deadline. It records each expiry as its own ledger entry, and a replica learns of the expiry from that entry, never by computing it.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-28-003 |
MUST | The actor holding CASE_MANAGER MUST be the enforcement authority for embargo invite expiry.Centralising enforcement at the CASE_MANAGER matches the case-communication model (PCR-08) and the CASE_MANAGER's role as canonical ledger author (ADR-0019, ADR-0021). See ADR-0065. |
|
CM-28-014 |
MUST | Only the CASE_MANAGER evaluates invite expiry (CM-28-003). Its Update(EmbargoConsent) carrying the invitee's TIMED_OUT row (CM-28-009) MUST be committed by the CASE_MANAGER before the row is written (ADR-0124, CLP-07-013), and reaches replicas as that ledger entry (CM-28-030). A replica learns an expiry from that entry, copying the row, and never computes one.Only the CASE_MANAGER can write a ledger entry. Thus an expiry that another store calculates has one of two results. It is an entry that the store has no authority to commit, or it is a private difference that no replica shares. The CASE_MANAGER commits the expiry first, and replicas copy it by replay. Thus the consent row of every replica is equal to that of the CASE_MANAGER, and one clock decides (ADR-0113, ADR-0124). |
Extends: CM-28-009 Refines: CLP-07-013 See also: CM-28-003 — context for the reader |
CM-28-009 |
MUST | When an RSVP deadline passes unanswered, the CASE_MANAGER MUST record the expiry as its own Update(EmbargoConsent) with the invitee's full TIMED_OUT row, committed as sent. The entry differs from the invitee's Reject(Invite(EmbargoEvent)), whose row is DECLINED.The expiry is the occasion and the Update is the CASE_MANAGER's act on it, a real AS2 activity (ADR-0140). The TIMED_OUT row it carries makes expiry-versus-refusal distinguishable in the ledger (CM-28-005), and it is how a replica learns the TIMED_OUT state without computing it (CM-28-014). A second, invitee-attributed entry would record an act nobody sent. See ADR-0065, ADR-0118. |
Refines: CM-28-005 |
CM-28-022 |
MUST NOT | The CASE_MANAGER MUST NOT record an invitation's expiry as an activity attributed to the invitee, which sent nothing. An invitee-attributed entry would record an act that nobody sent, and a reader of the ledger would take the silence for the invitee's answer. The expiry is the CASE_MANAGER's own act on its own clock (ADR-0140). See ADR-0065, ADR-0118. |
Extends: CM-28-009 |
Informative: when the CASE_MANAGER checks deadlines
The reference implementation enforces the deadline lazily. When the CASE_MANAGER next handles the case, it compares each deadline against its own clock, so no scheduler or timer service is needed.
Before it commits the Case Owner's decision on a proposal, whenever it processes any other received embargo activity for the case, and whenever it runs an embargo trigger of its own, it expires every INVITED row whose deadline has passed and whose embargo is an open proposal or the embargo in force.
A row of a replaced, rejected, canceled or ended embargo is frozen, so the sweep skips it.
The sweep runs after the activity's sender has been admitted and before the activity's own refusals.
An expiry is therefore recorded even when the activity is then refused.
A minimum window applies. The minimum window for an RSVP Deadline is the lesser of a configured window, 72 hours by default, and the time remaining in the embargo the invitation concerns. An inviting actor does not send an invitation whose deadline is shorter than the minimum. A receiver that gets one anyway extends the deadline to the minimum, and does not reject the invitation for this reason. A too-short deadline is the proposer's error, and a refusal of the invitation would penalize the invitee for that error.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EP-07-002 |
MUST | An inviting actor MUST set each Invite(EmbargoEvent)'s Invite.end_time at least the minimum RSVP window after the invitation's published timestamp. The minimum is the lesser of a fixed window and the time remaining in the embargo.An unbounded-downward deadline weaponises the mechanism: a one-minute RSVP window formally invites a participant while guaranteeing they cannot answer, excluding them with the appearance of due process. See ADR-0065. |
|
EP-07-010 |
SHOULD | The fixed window of the minimum RSVP window (EP-07-002) SHOULD be 72 hours. Seventy-two hours gives an invitee a realistic chance to answer across time zones and weekends, and it equals the floor of the protocol default embargo (EP-04-018). See ADR-0065. |
Extends: EP-07-002 |
EP-07-003 |
MUST | When a receiving actor receives an Invite(EmbargoEvent) whose Invite.end_time is earlier than the applicable minimum window, it MUST clamp the effective deadline up to that minimum. The applicable minimum is the one computed by EP-07-002, so the clamp never raises the deadline past the embargo's own end.Clamping makes a coercive deadline ineffective rather than fatal. Rejecting the invitation outright would hand the sender exactly what a hostile sender wants — an invite that never takes effect — and would punish the invitee for the inviter's misbehaviour. See ADR-0065. |
Uses definition from: EP-07-002 |
EP-07-004 |
MUST NOT | A receiving actor MUST NOT reject an Invite(EmbargoEvent) as malformed solely on the basis of a sub-minimum deadline.Rejecting the invitation would hand a hostile sender exactly what they want — an invite that never takes effect — and punishes the invitee for the inviter's misbehaviour. |
Derives from: EP-07-003 |
A deadline does not outlive its embargo.
An RSVP Deadline never falls after the end of the embargo it concerns.
If a computed deadline, whether from the invitation's explicit endTime or from the policy window, would fall after that end, it is clamped down to the embargo's end.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EP-07-006 |
MUST NOT | An RSVP deadline MUST NOT fall after the end of the embargo it concerns. An invitee must be able to answer while the embargo still exists. A deadline past the embargo's end asks the invitee to consent to an embargo that is already over, and records its silence as an expiry after the answer stopped mattering. See ADR-0096. |
Constrains: CM-18-023 Constrains: EP-07-002 |
EP-07-011 |
MUST | When a computed RSVP deadline would fall after the embargo's end_time, the actor that computes it MUST clamp it down to that end_time. This holds for a deadline from an explicit Invite.end_time and from the CM-18-023 policy window alike.Clamping is how a deadline is kept within the embargo (EP-07-006) without refusing the invitation: the invitee can still answer while the embargo exists. |
Implements: EP-07-006 Uses definition from: CM-18-023 |
An invitee needs to be able to answer while there is still something to answer about.
For example, a participant is invited to a 24-hour embargo with no explicit endTime, and the policy window is 7 days.
The participant's inaction would be recorded as a time-out on day 7, six days after the embargo ended.
This example is why the minimum window above is relative, not absolute.
A 12-hour embargo grants a 12-hour answer window.
That window is not an unreasonably short deadline when 12 hours is the whole embargo.
A late acceptance is not refused for being late. The CASE_MANAGER does not refuse a late accept on deadline grounds. What decides the answer, on time or late, is whether the accepted embargo is still available: the case's Active Embargo or one of its open proposals, before its end time. Three cases apply:
- If the accepted embargo is available, the CASE_MANAGER records the accept exactly as an on-time accept.
Its entry is the accept itself, and a
TIMED_OUTorDECLINEDrow moves toAGREEDdirectly. - If the case held the accepted embargo but it is no longer available, the CASE_MANAGER refuses the accept with the refusal notice and records nothing. An embargo is no longer available when it was replaced, rejected, canceled or terminated, or when its end time has passed. When the case holds current terms, the CASE_MANAGER also relays a fresh invitation carrying them, on behalf of their proposer.
- If the case never held the accepted embargo, the CASE_MANAGER answers with a processing fault,
Create(ProcessingFault), and sends no refusal notice. The sender's view of the case is wrong, so its accept was not understood.
The participant keeps its place in the case in every case.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
EMB-17-001 |
MUST | A CASE_MANAGER receiving an Accept(Invite(EmbargoEvent)) after the invitation's effective RSVP deadline MUST NOT reject it solely because the deadline has passed.Being liberal in what is accepted serves CVD outcomes. A late accepter is volunteering to coordinate; refusing them converts a missed deadline into a lost participant, which is worse for the case than a late consent. See ADR-0065. ECA DetailsPreconditions - The referenced invitation's effective RSVP deadline has passed Postconditions - The Accept is not refused on deadline grounds; one of EMB-17-002, EMB-17-003, or EMB-17-004 has been applied |
|
EMB-17-012 |
MUST | The CASE_MANAGER MUST check whether a late Accept(Invite(EmbargoEvent)) names an available embargo (MSM-07-012). Those are the case's Active Embargo and its open proposals (MSM-07-003), before their end time. It then applies EMB-17-002, EMB-17-003 or EMB-17-004.A late Accept can name the embargo in force, an open proposal, terms the case decided, replaced or let run out, or terms it never held. Each needs its own answer, read by the same test as for an on-time Accept. "Is this the Active Embargo" leaves out a case under proposal, and a test without the end time honours an Accept of terms that bind nobody. See ADR-0065. ECA DetailsPreconditions - The referenced invitation's effective RSVP deadline has passed Postconditions - One of EMB-17-002, EMB-17-003, or EMB-17-004 has been applied |
Extends: EMB-17-001 Refines: MSM-07-012 Uses definition from: MSM-07-003 See also: EMB-17-002 — context for the reader See also: EMB-17-003 — context for the reader See also: EMB-17-004 — context for the reader |
MSM-07-012 |
MUST | An available embargo is the case's Active Embargo or one of its open proposals, before its end time. An Accept, on time or late, may name an embargo the register holds but that is not available. That embargo was replaced, rejected, cancelled or terminated, or it is past its end time. The CASE_MANAGER MUST refuse that Accept before committing it, with the refusal notice that reports the reason (CLP-05-001). When the case holds terms of its own, the fresh Invite of EMB-17-003 goes with the notice. The embargo the Accept names decides the answer, not the clock: an RSVP deadline says whether the invitation is open, not whether the terms bind (ADR-0065). Terms that can no longer bind record nothing (CM-18-003), and an ACTIVE entry past its end time binds nobody before the clock ends it. Refusing before the commit keeps the Accept off the ledger, and the notice tells the sender its answer is moot. |
Supersedes: MSM-07-003 — In the case it names, the refusal replaces the AGREE Uses definition from: CLP-05-001 |
MSM-07-039 |
MUST | An Accept, on time or late, may name an embargo the case's register never held. The CASE_MANAGER MUST answer that Accept with Create(ProcessingFault) to its sender, not with the refusal notice (MSM-05-001). Nothing is ledgered for it, the fault included (ASK-07-008).A sender that names terms the case never held has a wrong view of the case. Its Accept was received but not understood, which MSM-05-001 answers with a processing fault. A refusal notice would tell it that its answer is moot, which presumes the case once held the terms. The fault tells it to resynchronise instead. |
Supersedes: MSM-07-003 — In the case it names, the fault replaces the AGREE Refines: MSM-05-001 See also: ASK-07-008 — the fault is not ledgered |
EMB-17-002 |
MUST | When the accepted embargo is available (MSM-07-012), the CASE_MANAGER MUST honour the late Accept. Available means the case's Active Embargo or one of its open proposals (MSM-07-003), before its end time. An ACTIVE entry past its end time is not available, so a late Accept of it is refused, not honoured. It marks the participant's consent row for that embargo AGREED, exactly as it would for an on-time Accept. A row at TIMED_OUT moves directly to AGREED (TIMED_OUT → AGREED, ADR-0118). So does one at DECLINED (DECLINED → AGREED, CM-18-003): the participant has changed its answer, so it is not re-invited first. The CASE_MANAGER honours it by committing the received Accept verbatim as accept_invite_to_embargo_on_case, carrying the row it states, as an on-time Accept is committed (EMB-17-009, ADR-0152).An answer the case can still record is sound whenever it arrives. The deadline governs whether the invitation is open, not whether the agreement is sound, and an open proposal's row takes an answer until the Case Owner decides it, so dropping a late Accept of an open proposal would hide a willing participant from that decision. See ADR-0065. The Accept states the change, so its entry is the change's entry (CLP-07-013), and a replica reaches the state an on-time Accept leaves. ECA DetailsPreconditions - EM state is Proposed, Active or Revise - EM state: PROPOSED, ACTIVE, REVISE- The accepted embargo is the case's Active Embargo or one of its open proposals, and its end time has not passed Steps 1. [system] Record the PEC AGREE transition for the accepting participant → The participant's consent row for the accepted embargo is AGREED Postconditions - The participant's consent row for the accepted embargo is AGREED, so it is a signatory when that embargo is the Active Embargo |
Refines: EMB-17-001 Uses definition from: MSM-07-012 Uses definition from: MSM-07-003 Uses definition from: CM-18-003 |
EMB-17-003 |
MUST | An Accept, late or on time, may name an embargo the register holds but that is not available. The CASE_MANAGER refuses it with the refusal notice (MSM-07-012). When the case holds terms of its own, the CASE_MANAGER MUST also send the accepter a fresh Invite(EmbargoEvent) naming those terms. The fresh Invite goes alongside the refusal notice. The terms are the case's Active Embargo, while it is available. Otherwise they are its earliest-expiring available open proposal (EP-08-002). An accepting participant at TIMED_OUT moves TIMED_OUT → INVITED for the invited embargo (ADR-0118). The fresh Invite is a relay (EP-09-002). Its actor is the CASE_MANAGER. Its attributedTo names the invited embargo's proposer, or the CASE_MANAGER itself when it made the embargo as the protocol default, without a proposal.Recording the stale Accept as consent binds the participant to terms it never saw; refusing it alone leaves a willing participant unasked. The re-invite asks about the terms that bind, in a relay's shape (ADR-0152). Naming the Active Embargo alone leaves a case under proposal with nothing to invite to. The earliest-expiring proposal is the one a participant answers first (EP-08-001); arrival order would ask about superseded terms. See ADR-0065. ECA DetailsPreconditions - The register holds the accepted embargo, but it is not available, and the case has an available Active Embargo or open proposal Steps 1. [system] Emit the refusal notice and a fresh Invite(EmbargoEvent) to the accepting actor carrying the case's current terms → Accepting participant's consent row for the invited embargo is INVITED; stale Accept is not recorded as consent Postconditions - A fresh invitation for the case's current terms has been sent; the actor remains a case participant |
Refines: EMB-17-001 Extends: MSM-07-012 Uses definition from: EP-08-002 Uses definition from: EP-09-002 |
EMB-17-013 |
MUST | Once it has queued the fresh Invite of EMB-17-003 (SYNC-09-002), the CASE_MANAGER MUST commit it as invite_to_embargo_on_case. The invitee's INVITED row with the Invite's deadline follows it (CM-28-013).The re-invite asks about terms somebody proposed, exactly as a relay does, so it carries the relay's semantic type (ADR-0152). Committing it after it is queued lets a rebuilt send keep the same id (SYNC-09-002). |
Extends: EMB-17-003 Refines: CM-28-013 Refines: SYNC-09-002 |
EMB-17-014 |
MUST | A replica MUST apply the CASE_MANAGER's re-invite (EMB-17-003) through the relay slot, so that the Invite proposes nothing and EM does not move. The replica's register already holds the embargo the Invite names, so the Invite asks for consent to it and changes no embargo state (ADR-0152). |
Extends: EMB-17-003 |
EMB-17-004 |
MUST | This rule covers a case with no Active and no Proposed Embargo (EM EXITED or NONE). There, the CASE_MANAGER MUST answer a late Accept of an embargo its register holds with the refusal notice alone (MSM-07-012). A redelivery of the same Accept gets the same result. Follows the EMB-07-003 precedent for post-terminal messages: no transition. There is nothing to invite the actor to, so a fresh invitation would manufacture a negotiation nobody requested — but the actor's case participation is independent of embargo consent and MUST survive. The sender is still owed word that its answer did not count, which the refusal notice gives (CLP-05-001). An Accept of terms the case never held gets a processing fault instead (MSM-07-039). See ADR-0065. ECA DetailsPreconditions - EM state is EXITED (embargo terminated) or NONE (no embargo started) - EM state: EXITED, NONESteps 1. [system] Refuse the Accept with the refusal notice, committing nothing and sending nothing else → Participant consent rows are unchanged; participant remains in the case; no ledger entry is committed and only the refusal notice is sent Postconditions - No embargo state change; accepting actor remains a case participant |
Refines: EMB-17-001 Refines: MSM-07-012 |
EMB-17-015 |
MUST NOT | The CASE_MANAGER MUST NOT commit any ledger entry for a late Accept that arrives when the case has no Active Embargo and no Proposed Embargo (EMB-17-004). An entry acknowledging the Accept would change nothing at any receiver. The Accept is refused, and a refusal is never written to the ledger (CLP-04-007). |
Part of: EMB-17-004 |
EMB-17-016 |
MUST NOT | This rule covers a late Accept of an embargo the register holds, in a case with no Active and no Proposed Embargo (EMB-17-004). The CASE_MANAGER MUST NOT send any activity in reply to it but the refusal notice. There is nothing to invite the actor to, so a fresh invitation would manufacture a negotiation nobody requested. The refusal notice is owed: it tells the sender its answer did not count (MSM-07-012). |
Part of: EMB-17-004 |
EMB-17-017 |
MUST | The CASE_MANAGER MUST leave the participant's consent rows unchanged for a late Accept that arrives when the case has no Active Embargo and no Proposed Embargo (EMB-17-004). Nothing is recorded after a termination (EM EXITED), and a TIMED_OUT row stays TIMED_OUT when no embargo has started (EM NONE) (ADR-0118). The Accept names an embargo that is no longer, or not yet, in force, so no row can bind to it. The actor's case participation is independent of embargo consent and survives. |
Part of: EMB-17-004 |
EMB-17-006 |
MUST NOT | When the accepted embargo is not available, the CASE_MANAGER refuses the Accept (MSM-07-012). It MUST NOT refuse the accepting actor's participation: the refusal is of the Accept alone. Refusing a willing participant discards coordination capacity. The refusal notice says the answer is moot, never that the actor is unwelcome, and re-inviting to the current terms is the rest of the answer. See ADR-0065. |
Extends: EMB-17-003 Refines: MSM-07-012 |
EMB-17-008 |
MUST NOT | When the case has no Active Embargo and no Proposed Embargo (EM state is EXITED or NONE), the CASE_MANAGER MUST NOT remove the accepting actor from the case. Case participation is independent of embargo consent; the actor's willingness to coordinate must not result in their removal. See ADR-0065. |
Derives from: EMB-17-004 |
A time-out and a refusal reach different states.
Silence records TIMED_OUT.
An explicit refusal records DECLINED.
The case ledger also distinguishes them, because it holds either the refusal that was sent or the CASE_MANAGER's record of the expiry.
But every reader of the consent rows can tell the two states apart without the ledger.
Both can be invited again, and both move to AGREED directly on a late accept of the current terms.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-28-005 |
MUST | An expired embargo invitation MUST be distinguishable from an explicit refusal both in the participant's consent row (TIMED_OUT versus DECLINED, CM-18-002) and in the canonical case ledger (CM-28-009).The canonical ledger is the project's history mechanism (ADR-0019), so expiry-versus-refusal is recoverable from it; since ADR-0118 the consent row carries the distinction too, so a reader that consults only the participant record also sees it. See ADR-0065, ADR-0118. |
9.5 Embargo Traffic Reaches Non-Signatories
Embargo consent gates case content. It does not gate the negotiation about the embargo itself.
The CASE_MANAGER delivers embargo meta-protocol activities addressed to a participant directly (an embargo Invite and its responses) to that participant, even when that participant declined, timed out or lapsed.
These activities are not ledger fan-out, which the content gate holds back from non-signatories.
A participant cannot agree to revised terms that nobody told it about.
A participant that declined the original terms can still accept the revision.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-10-005 |
MUST NOT | This rule covers each Announce(CaseLedgerEntry) the CASE_MANAGER sends, as fan-out of a new entry or as a replay answering a Reject(CaseLedgerEntry) (SYNC-03-002). While an embargo is active, the CASE_MANAGER MUST NOT send one to a participant that has not accepted that embargo (the CM-10-004 content gate).The ledger fan-out is how participants learn every accepted case change, and each entry carries its payload verbatim — an added report or note reaches the recipient whole. Fan-out is therefore "sharing case updates" in CM-10-004's sense. An entry cannot be redacted per recipient without breaking the hash chain. Skipping a single entry does not work either: the replica buffers the next one as a forward gap and Rejects to request the missing entry (SYNC-14-002), so the replay would deliver the withheld content anyway. The gate therefore pauses the participant's whole stream, replay included, rather than filtering entries; the replica stays at the last entry it was sent. |
Refines: CM-10-004 Uses definition from: SYNC-03-002 |
CM-10-008 |
MUST | While an embargo is active, the CASE_MANAGER MUST still deliver an embargo Invite, and its responses, to a participant that has not accepted the embargo. These are embargo meta-protocol activities addressed to the participant directly, not ledger fan-out.These activities are not ledger fan-out, so the CM-10-005 pause does not cover them. A participant that never receives the embargo Invite cannot accept the embargo, so its paused stream could never resume. |
Extends: CM-10-005 |
Only case content (report details, fix status, sensitive notes) is gated on being a signatory (§9.7 Gating Full Case Delivery).
9.6 Being Bound by the Embargo
Whether a participant is currently bound by the embargo is a single yes-or-no question.
The protocol answers this question from the consent rows.
A participant is bound exactly when it is a signatory, that is, when its row for the register's ACTIVE entry is AGREED (§9.3 Signatory and Lapsed).
This is a derived fact, not an independent one. Being bound is not recorded as a value that can be set separately from the rows it reports. Such a value and the rows could then disagree. A case that reports a participant as bound while its rows say otherwise has no correct reading.
Every change of consent is one of two kinds, so that every change is a valid one and is recorded as such:
- a consent trigger applied through the transitions of §9.2 Transitions and Guards
- a copy of the row that a ledger entry carries, after a check of its starting state, made the same way by the CASE_MANAGER and by every replica
The CASE_MANAGER commits every consent row that it changes as its own Update(EmbargoConsent) ledger entry.
For a row that it brings into existence, the entry is Create(EmbargoConsent).
Each such entry comes after the entry of the act that caused the change.
When the act's own activity states the row, the act's entry is also the row's entry.
Examples are a participant's Accept(Invite(EmbargoEvent)[context=VulnerabilityCase]) or, for the Case Owner's own row, its Add(EmbargoEvent)[target=VulnerabilityCase] that activates an embargo.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CLP-07-013 |
MUST | The CASE_MANAGER MUST commit every change it makes to the case file as its own CaseLedgerEntry, never making a change that has no committed entry. The act's entry comes first. When the act's own activity states a change, that entry is the change's entry, and applying it writes only what the activity states. Examples are Add(Note)[target=VulnerabilityCase] carrying the note, and an invitee's Accept of the stub Invite marking its own consent and joining. A decision the CASE_MANAGER takes from local policy or the clock may change the case file. Such a decision is committed as the change it makes, before the change is made. A decision that changes nothing is not committed, such as noticing that a deadline has passed or that a closure is complete (ADR-0152). Moving the case's ledger position (ledgerPosition) to an entry as it is committed (SYNC-16-005) is part of applying that entry. It is not a change to the case file of its own, and takes no entry.Two replicas at the same ledger position must hold the same case file, and a replica infers nothing. If a change is not in the ledger, it did not happen (ADR-0124). One act can cause several changes, such as a stub Invite and the participant record it creates for the invitee. If only the act is recorded, each replica must create the record itself, with its own ids and clock times. Full records are ledger content that the hash chain must cover (CLP-07-006). |
Extends: CLP-07-002 Uses definition from: SYNC-16-005 |
CLP-07-021 |
MUST | Each change an act causes, beyond what the act's own activity states, MUST follow the act's entry as its own CASE_MANAGER-authored entry. The entries follow in the order the CASE_MANAGER writes them. Each one's payloadSnapshot carries the object in full (CLP-07-006). A record the change adds to one of the case's content lists (its reports, notes, statuses, vulnerability items or case references) is recorded as an Add of the record with the case as its target. Any other record the CASE_MANAGER brings into existence is recorded as a Create, and a changed record as an Update.One act can cause several changes, such as a stub Invite and the participant record it creates for the invitee. If only the act is recorded, each replica must create the record itself, with its own ids and clock times, and replicas at one ledger position then differ. Full records are ledger content that the hash chain must cover (CLP-07-006). A record that belongs to a case list needs the case as the entry's target: a Create has none, so a replica would have to decide which list the record joins, which is lifecycle logic a replica must not run (CM-23-044). The one Add both brings the record and lists it. |
Extends: CLP-07-013 See also: CLP-07-006 — context for the reader |
CM-23-016 |
MUST | A participant's case replica is the case as it stood when the replica was seeded, plus the ledger entries since. A replica MUST apply the entries in ledger order by copying the objects they carry, so replicas at one ledger position hold identical case files. The CASE_MANAGER is the single writer (ADR-0108), and the ledger records each change when the CASE_MANAGER makes it (CLP-07-013). If each replica copies what the entries carry, in the same order, two replicas at the same position hold the same case file as each other and as the CASE_MANAGER. CM-23-023 gives the rule for closure. This requirement gives it for every replicated change (ADR-0124). |
|
CM-23-044 |
MUST NOT | A replica applying an entry MUST NOT mint an id, read a clock, read local policy or state outside the case, or run lifecycle logic. Walking the RM transition table from its own stored state to a target state is such logic. A replica can find its own path from its own state, which can be out of date. It can then write an RM state that the ledger never recorded. A replica that builds a record itself gives it an id and a time that differ from those of the CASE_MANAGER. In both cases, the replicas diverge from the CASE_MANAGER (ADR-0124). |
Extends: CM-23-016 |
Informative: how the reference implementation does this
The reference implementation exposes adherence as a computed lookup over the stored consent rows and the register, so there is no separate field that can disagree with the rows. Any mechanism with that property gives the same reading.
9.7 Gating Full Case Delivery
Before the CASE_MANAGER delivers full case content (Announce(VulnerabilityCase) carrying report details, vulnerability description, and sensitive notes), the recipient is an active participant:
- The participant has joined the case: the case initialization sequence seated it, or it accepted the stub Invite, and it has not been removed.
- The participant is a signatory to the active embargo (its row for the active embargo is
AGREED), or no embargo is in force (EM is notACTIVEorREVISE).
Content stops for a participant whose closure the ledger records, after the entries that record its own closure.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-10-004 |
MUST | The CASE_MANAGER MUST share case content only with active participants, never with an inert one. A participant is active when three conditions hold. First, the case initialization sequence seated it (CM-14-001: the Case Owner, the CASE_MANAGER and the reporter), or it accepted the stub Invite (Accept(Invite(Actor)[target=VulnerabilityCaseStub])). Second, it has not been removed (CM-31-001). Third, while an embargo is active, its consent row for that embargo is AGREED (CM-18-001). Every other participant is inert. Case content includes CaseLedgerEntry announcements, Announce(VulnerabilityCase), status broadcasts and embargo announcements (ADR-0114).Many cases have no active embargo: the embargo is not yet established, or it has already ended. Thus, "has accepted the active embargo" cannot be the only entitlement test. The stub Invite creates the participant record (ADR-0114), and a removed participant keeps its record (ADR-0116). Thus, the roster holds actors that have no entitlement. A sender must check entitlement, because membership does not show it. While an embargo is active, the AGREED row of the participant for that embargo is its agreement to protect what it receives (ADR-0122). |
Uses definition from: CM-14-001 Uses definition from: CM-18-001 Uses definition from: CM-31-001 |
CM-17-005 |
MUST NOT | Presence in the case participant list MUST NOT be treated as acceptance of the invitation or as entitlement to case content. An invitee is in the list from the stub Invite onward (CM-11-006); only an active participant (CM-10-004) is entitled to case content. The CASE_MANAGER tracks every invitee from the moment it is invited, including one that declines, so the participant list holds inert participants. Any consumer that reads membership as "accepted" would hand case content to an actor that has not consented. |
Uses definition from: CM-10-004 See also: CM-11-006 — context for the reader |
CM-23-004 |
MUST NOT | The CASE_MANAGER MUST NOT send any case content to a participant whose closure an earlier ledger entry records, except as CM-23-031, CM-31-009 and CM-31-030 allow. That entry is the participant's status entry with rmState=CLOSED. Case content is CaseLedgerEntry announcements, Announce(VulnerabilityCase), status broadcasts and embargo announcements. A participant that has left receives no entry after those that record its departure, the CASE_MANAGER's own closure included.RM.CLOSED is the participant's own statement that it stops its work on the case, possibly while the case is still open. Its replication process is then assumed to have stopped, as the CASE_MANAGER's is once the case is fully closed (CM-23-013). A closed participant receives no more content, so it does not see embargoed material after it leaves. Only the ledger advances a replica, so a closed replica does not converge on later closures, by design. |
Extends: CM-10-004 |
CM-23-031 |
MUST | The CASE_MANAGER MUST send each entitled leaver the entries that record its own closure, chosen by their subject, not by the leaver's status. These are the close_case entry and each status entry after it, up to the one reaching RM.CLOSED (CM-23-021, CM-23-022). They never widen entitlement (CM-10-004): an inert or removed leaver is not sent them. The entries that record a participant's own closure come before it stops, so its replica still receives every step, the one that reaches RM.CLOSED included. The leaver's status is already RM.CLOSED when the last of them is fanned out. Thus a choice by status would withhold that last step. |
Supersedes: CM-23-004 Uses definition from: CM-10-004 Uses definition from: CM-23-021 Uses definition from: CM-23-022 |
CM-23-032 |
MUST NOT | A closing participant MUST NOT write its own RM.CLOSED to its replica in place of the CASE_MANAGER's closure entries (CM-23-031). The CASE_MANAGER writes the leaver's closure and commits each step (CM-23-022). A participant that wrote its own RM.CLOSED would hold a step that no ledger entry records, and its replica would diverge from the CASE_MANAGER (ADR-0114). |
Extends: CM-23-031 |
Recall: report management states
| State | Meaning |
|---|---|
| Start | No report has been received |
| Received | A report has arrived; triage is not yet complete |
| Invalid | This participant assessed the report as invalid |
| Valid | This participant assessed the report as valid |
| Deferred | This participant is deferring further action |
| Accepted | This participant accepted the report for active work |
| Closed | This participant closed the report |
Full definitions are in §6.1 States.
The gate is joining plus consent — not RM progress
It is tempting to read the gate as an RM state: RM.ACCEPTED, or RM.RECEIVED as "admitted".
Both readings are wrong.
An invitee is at RM.RECEIVED from the stub Invite, before it has answered, and is still inert.
Being in the case's participant list at RM.RECEIVED is therefore not entitlement to case content.
The invitee reaches ACCEPTED only after it receives the full case and runs its triage cycle (§6.3 Per-Participant RM Tracking).
If delivery required ACCEPTED, a participant could never obtain the case that it needs to reach the state that gates delivery.
Joining and embargo consent — not RM progress — are the gate on case content. The ordering is: the invitee accepts the stub Invite, which joins the case and agrees to any active embargo it has not declined, and then the CASE_MANAGER delivers the full case.
This gate matters to the cascade ordering of §11 Model Interactions and Cascade Rules.
Accept(Invite) agrees to any active embargo on the joiner's row for that embargo, unless that row is DECLINED.
This agreement lets delivery proceed immediately, with no wait for a separate consent round-trip.
A joiner whose row for the active embargo is DECLINED stays declined, because an explicit refusal outranks the consent that joining implies.
That joiner is in the case but inert until it changes its answer.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CM-11-001 |
MUST | When a participant accepts the stub Invite (Accept(Invite(Actor)[target=VulnerabilityCaseStub])), the CASE_MANAGER MUST leave the participant's RM state at RM.RECEIVED, set its VF state to V when it holds the VENDOR role, and, when an embargo is active, mark its consent row for that embargo AGREED, making it a signatory. A DECLINED row is the exception, and the CASE_MANAGER leaves it unchanged: an explicit refusal outranks the consent that joining implies. Accepting the stub is joining the case and, unless the row is DECLINED, consenting to the active embargo. It is not a judgement of the case.The invitee has seen only the stub. It judges the case later, in its replies to the full-case Invite (CM-11-010, CM-11-011), so the record of the CASE_MANAGER shows no decision that the invitee has not made. To join under an active embargo is to take part under it. Thus no participant becomes active without a recorded answer to the embargo, and the delivery gate of MV-10-005 relies on this. |
Uses definition from: CM-10-001 Extends: BT-10-005 |