Embargo Management (EM) Messages
The EM process is global to the case.
A Participant emits an EM message when the case's EM state changes.
The AS2 wire vocabulary collapses the revision-negotiation shorthands onto their initial-negotiation counterparts: EV is sent as EP, EJ as ER, and EC as EA.
The EM state context, not a payload field, discriminates them (MSM-02).
EA, EC, ER, and EJ are the Case Owner's decision on a proposal (see The Case Owner's Decision).
A participant's Accept or Reject of an embargo Invite is that participant's consent, so it carries no shorthand (MSM-02-010).
An embargo proposal carries its EmbargoEvent inline on the Invite that proposes it.
The protocol names Invite(EmbargoEvent) as the one form.
A received Create(EmbargoEvent) is not a protocol message, and its receiver must not change the case file because of it (ADR-0137, VAM-01-019).
The inbox of this implementation recognizes a Create(EmbargoEvent), reports "no use case found" and changes nothing (VAM-01-018).
Occasions
| When… | Send | Send to | Sent by | Distinguished by | Details |
|---|---|---|---|---|---|
| the Case Owner terminates the active embargo | Remove(EmbargoEvent) |
the CASE_MANAGER | the CASE_MANAGER or the Case Owner | — | Embargo Termination (ET) |
| the CASE_MANAGER ends the active embargo, on its own decision or on the Case Owner's | Remove(EmbargoEvent) |
a participant | the CASE_MANAGER | — | Tell a participant the embargo has ended |
| the CASE_MANAGER states the terms of the embargo in force | Announce(EmbargoEvent)[context=VulnerabilityCase] |
a participant | the CASE_MANAGER | register status of the named embargo ACTIVE |
Announce embargo |
| the CASE_MANAGER has applied an Embargo Termination a Case Owner sent before the end time | Announce(EmbargoEvent)[context=VulnerabilityCase] |
a participant | the CASE_MANAGER | register status of the named embargo TERMINATED |
Announce embargo termination |
| a Participant proposes embargo terms for a case with no active embargo | Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase] |
the CASE_MANAGER | the CASE_MANAGER or an active participant | EM state NONE or PROPOSED |
Embargo Proposal (EP) |
| a Participant proposes revised terms for the active embargo | Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase] |
the CASE_MANAGER | the CASE_MANAGER or an active participant | EM state ACTIVE or REVISE |
Embargo Revision Proposal (EV) |
| the CASE_MANAGER asks a Participant to answer embargo terms another Participant proposed | Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase] |
a participant | the CASE_MANAGER | — | Ask a participant about proposed embargo terms |
| a Participant agrees to proposed embargo terms | Accept(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) |
the CASE_MANAGER | the invitee | EM state PROPOSED |
Agree to proposed embargo terms |
| a Participant agrees to a proposed embargo revision | Accept(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) |
the CASE_MANAGER | the invitee | EM state REVISE |
Agree to an embargo revision |
| a Participant refuses proposed embargo terms | Reject(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) |
the CASE_MANAGER | the invitee | EM state PROPOSED |
Refuse proposed embargo terms |
| a Participant refuses a proposed embargo revision | Reject(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) |
the CASE_MANAGER | the invitee | EM state REVISE |
Refuse an embargo revision |
| the CASE_MANAGER abandons an open embargo proposal it received once the case is public, an exploit is public or attacks are observed | Reject(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) |
a participant | the CASE_MANAGER | — | Abandon embargo proposal |
| the CASE_MANAGER abandons an open embargo proposal once the case is public, an exploit is public or attacks are observed | Undo(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) |
a participant | internal to the CASE_MANAGER | — | Withdraw an embargo invitation |
| the Case Owner decides to activate a proposed embargo for a case with no active embargo | Add(EmbargoEvent)[target=VulnerabilityCase] |
the CASE_MANAGER | the Case Owner | EM state PROPOSED |
Embargo Proposal Acceptance (EA) |
| the Case Owner decides to replace the active embargo with a proposed revision | Add(EmbargoEvent)[target=VulnerabilityCase] |
the CASE_MANAGER | the Case Owner | EM state REVISE |
Embargo Revision Acceptance (EC) |
| the Case Owner decides to reject a proposed embargo for a case with no active embargo | Reject(EmbargoEvent)[target=VulnerabilityCase] |
the CASE_MANAGER | the Case Owner | EM state PROPOSED |
Reject embargo proposal |
| the Case Owner decides to reject a proposed revision | Reject(EmbargoEvent)[target=VulnerabilityCase] |
the CASE_MANAGER | the Case Owner | EM state REVISE |
Embargo Revision Rejection (EJ) |
| a Participant bound by the active embargo stops complying with it | Leave(EmbargoEvent)[context=VulnerabilityCase] |
the CASE_MANAGER | a participant | — | Withdraw from embargo |
| the CASE_MANAGER has created a case and, with it, an embargo such as the default embargo | Create(EmbargoEvent) |
a participant | internal to the CASE_MANAGER | — | Create embargo event |
| the CASE_MANAGER creates a participant's consent row for an embargo, such as the UNINVITED row a proposal writes | Create(EmbargoConsent) |
a participant | internal to the CASE_MANAGER | — | Create embargo consent |
| the CASE_MANAGER changes a participant's consent row, such as an invitation timing out, the rows carried over at activation or a change of its own consent | Update(EmbargoConsent) |
a participant | internal to the CASE_MANAGER | — | Update embargo consent |
Embargo Proposal (EP)
Proposes embargo terms, such as an end date and time.
- When… a Participant proposes embargo terms for a case with no active embargo
- Send:
Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase] - Send to: the CASE_MANAGER
- Sent by: the CASE_MANAGER or an active participant
- Distinguished by: EM state
NONEorPROPOSED - Seen in: How to Establish an Embargo
- Formal definition: Embargo Proposal (EP)
- Mapping status: collapse
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Invite",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"name": "https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"summary": "We propose to embargo case 1 for 90 days.",
"to": [
"https://vultron.example/case-actors/vendorco-case-actor"
],
"actor": "https://vultron.example/organizations/vendorco",
"target": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z2w35AsPXqt8F9A1xc7tjdSWM3faz4oPGDKQEP2arYH3uBFgv1MhkEfyhkkpHHd8QzFUC4nYDZE8CJUsBgphPA9NV"
}
}
- Triggering transition: None or Proposed → Proposed ({N,P} → P).
- Wire form:
Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase], and no other (MSM-02-001). - Invitee: the Invite's
targetnames the invitee, the one actor it is addressed to, as ActivityStreams 2.0 places an Invite's invitee (ADR-0205, EP-09-010). A proposal goes to the CASE_MANAGER alone, so itstargetnames the CASE_MANAGER.
Ask a participant about proposed embargo terms
Asks one participant to accept or reject proposed embargo terms, or a proposed revision. The CASE_MANAGER sends one to each participant other than the proposer, naming the proposer in attributedTo and the proposer's Invite in inReplyTo, and the participant's answer names this Invite.
- When… the CASE_MANAGER asks a Participant to answer embargo terms another Participant proposed
- Send:
Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase] - Send to: a participant
- Sent by: the CASE_MANAGER
- Seen in: How to Establish an Embargo
- Mapping status: collapse
The wire form is the Embargo Proposal (EP) or Embargo Revision Proposal (EV) a participant sends; only its sender and addressee differ.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Invite",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1/invites/coordinator",
"name": "https://vultron.example/case-actors/vendorco-case-actor Invite Embargo for VendorCo Case #20260601 to https://vultron.example/organizations/coordinator",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"endTime": "2026-06-08T19:12:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"summary": "The vendor proposes to embargo case 1 for 90 days.",
"to": [
"https://vultron.example/organizations/coordinator"
],
"attributedTo": "https://vultron.example/organizations/vendorco",
"actor": "https://vultron.example/case-actors/vendorco-case-actor",
"target": "https://vultron.example/organizations/coordinator",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/case-actors/vendorco-case-actor#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z3nyYjgbiqjLagMC2mrbFEo8MzCLtD4ty3rjybGR78vafqGTXrDNhQ68jqsSjKMCxvZCTTwER2VMcNcEHkWkreh9X"
}
}
- Recipient: one Invite per participant other than the proposer, each addressed to that participant alone and naming it in
target, so its answer names the Invite it received (EP-09-002, EP-09-010).
Announce embargo
Tells participants the terms of the active embargo. It proposes nothing.
- When… the CASE_MANAGER states the terms of the embargo in force
- Send:
Announce(EmbargoEvent)[context=VulnerabilityCase] - Send to: a participant
- Sent by: the CASE_MANAGER
- Distinguished by: register status of the named embargo
ACTIVE - Seen in: How to Establish an Embargo, How to Revise or Terminate an Embargo
- Mapping status: none
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Announce",
"id": "urn:uuid:69214ea7-3c09-4982-98b8-c3bfa77b4da4",
"name": "https://vultron.example/organizations/vendorco Announce Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/participants",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z4yCvpQfmqbpZokzy9Z6A4RQf8Yk94DYG1WGuPqKgoReWW9a7uw38iGw8PAr75HDjjjx6uvHUVdnamW6nFXaQSdRK"
}
}
When the CASE_MANAGER activates a revision that ends no later than the embargo it replaces, it sends Announce(EmbargoEvent) with the new terms.
It sends this activity directly to each bound signatory that no longer receives ledger entries (removed, or at Report Management (RM) CLOSED).
Each such signatory applies the new terms only when the CASE_MANAGER sent them.
A revision that ends later causes no such notice, because those participants never agreed to it.
Announce embargo termination
Tells the active participants other than the CASE_MANAGER and any Closed Participant that the embargo it names is terminated. It proposes nothing.
- When… the CASE_MANAGER has applied an Embargo Termination a Case Owner sent before the end time
- Send:
Announce(EmbargoEvent)[context=VulnerabilityCase] - Send to: a participant
- Sent by: the CASE_MANAGER
- Distinguished by: register status of the named embargo
TERMINATED - Seen in: How to Revise or Terminate an Embargo
- Mapping status: none
A termination the CASE_MANAGER starts itself, or one at the end time, sends no announcement: after the end time, the CASE_MANAGER's own end-time check ends the embargo before it applies a Case Owner's termination.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Announce",
"id": "urn:uuid:1dbd4608-ec99-4fbc-9b55-caf8512cd9b8",
"name": "https://vultron.example/case-actors/vendorco-case-actor Announce Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": [
"https://vultron.example/organizations/vendorco",
"https://vultron.example/organizations/coordinator",
"https://vultron.example/users/finndervul"
],
"actor": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/case-actors/vendorco-case-actor#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "zVhkFEbgoWa4yDaTamkQWChf6Gyn3khE1HEB9vAQN1KLUTPZz6vTqRQag9f1kKicfrTPzrhWrGokSeBRuKKNUeGc"
}
}
- Recipient: every active participant other than the CASE_MANAGER and any Closed Participant.
The CASE_MANAGER sends the
Announce(EmbargoEvent)after it applies a Case Owner'sRemove(EmbargoEvent)that arrives before the end time (EMB-19-001, CM-10-004, CM-23-004). A termination the CASE_MANAGER starts itself, or one at the end time, sends noAnnounce(EmbargoEvent). A bound signatory that no longer receives ledger entries receives the CASE_MANAGER's ownRemove(EmbargoEvent)instead (CM-31-009).
Refuse proposed embargo terms
Records the sender's own refusal of the proposed terms. The proposal is rejected for the case only when the Case Owner sends its decision.
- When… a Participant refuses proposed embargo terms
- Send:
Reject(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) - Send to: the CASE_MANAGER
- Sent by: the invitee
- Distinguished by: EM state
PROPOSED - Seen in: How to Establish an Embargo
- Mapping status: expansion
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Reject",
"id": "urn:uuid:9eaaf5d5-b885-423e-868d-1ba6e71f759e",
"name": "https://vultron.example/organizations/vendorco Reject https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": "https://vultron.example/cases/1/participants",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"type": "Invite",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"name": "https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"summary": "We propose to embargo case 1 for 90 days.",
"to": [
"https://vultron.example/case-actors/vendorco-case-actor"
],
"actor": "https://vultron.example/organizations/vendorco",
"target": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
}
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z38UseN8RTysqY6Tkjgm8phxhz9rroTuY79gnZPnTjszmhiQbQqPz8q5ijLqzEALAE1YBySEKhZKJ9K4q4fEWTe95"
}
}
- Triggering transition: none in EM.
The sender's consent to those terms moves to
DECLINED(MSM-07-004). - Who decides: a participant's
Rejectof the Invite is its own refusal of those terms, the Case Owner's included. ThisRejectchanges no embargo on the case (see The Case Owner's Decision). - Refusal on a public case: a receiver answers an
EPwith aRejectof the Invite when the case is public, an exploit is public, or attacks are observed (EMB-01-002). TheRejectnames the Invite by id. The receiver therefore sends theRejecteven when the Invite named its terms only by URI. A receiver sends oneRejectper Invite and skips a re-delivered Invite. - Malformed Invite: an
EPthat names notorecipient, or several, or whosetargetnames an actor other than its recipient (EP-09-026). The receiver does not answer such anEPwith aReject. TheEPis received but not understood, so the receiver sendsCreate(ProcessingFault)to the sender. AnEPwith notargetmatches no embargo Invite form, so its receiver does not recognize it as anEPat all.
Abandon embargo proposal
Cancels the proposal for the case. The CASE_MANAGER then withdraws each Invite it relayed for the proposal. This Reject is not the CASE_MANAGER's consent.
- When… the CASE_MANAGER abandons an open embargo proposal it received once the case is public, an exploit is public or attacks are observed
- Send:
Reject(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) - Send to: a participant
- Sent by: the CASE_MANAGER
- Formal definition: Embargo Proposal Rejection (ER)
- Mapping status: expansion
Each participant learns of it from the case ledger, so it is addressed to nobody.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Reject",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1/abandon",
"name": "https://vultron.example/case-actors/vendorco-case-actor Reject https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"actor": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"type": "Invite",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"name": "https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"summary": "We propose to embargo case 1 for 90 days.",
"to": [
"https://vultron.example/case-actors/vendorco-case-actor"
],
"actor": "https://vultron.example/organizations/vendorco",
"target": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
}
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/case-actors/vendorco-case-actor#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z2NbJq2KADRQnkTYVd4mg78VMf4JaVuUDSKSFk4Vfag6ogtCDUS5rKXcTZmqiGUjXy8VYwtx5tjfmMZfbjonf8jqm"
}
}
- Triggering transition: Proposed → None (P → N) with the last open proposal (EMB-16-001).
- Why it is sent: when the case becomes public, an exploit is public or attacks are observed while a proposal is open, the CASE_MANAGER rejects each proposal it received.
That
Rejectcancels the proposal. - Not consent: a replica distinguishes the CASE_MANAGER's
Rejectfrom a participant'sRejectby theactorof the activity. The CASE_MANAGER never sends aRejectof an Invite as its own consent. A CASE_MANAGER with a stake in the embargo records its answer as an update of its own consent row.
Withdraw an embargo invitation
Withdraws an Invite the CASE_MANAGER sent for the abandoned proposal. The CASE_MANAGER first rejects the proposal it received, which cancels it, then withdraws each Invite it relayed for it. When the CASE_MANAGER made the proposal itself, withdrawing that proposal is the cancel.
- When… the CASE_MANAGER abandons an open embargo proposal once the case is public, an exploit is public or attacks are observed
- Send:
Undo(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) - Send to: a participant
- Sent by: internal to the CASE_MANAGER
- Mapping status: none
Each participant learns of it from the case ledger, so it is addressed to nobody.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Undo",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1/invites/coordinator/undo",
"name": "https://vultron.example/case-actors/vendorco-case-actor Undo https://vultron.example/case-actors/vendorco-case-actor Invite Embargo for VendorCo Case #20260601 to https://vultron.example/organizations/coordinator",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"actor": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"type": "Invite",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1/invites/coordinator",
"name": "https://vultron.example/case-actors/vendorco-case-actor Invite Embargo for VendorCo Case #20260601 to https://vultron.example/organizations/coordinator",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"endTime": "2026-06-08T19:12:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"summary": "The vendor proposes to embargo case 1 for 90 days.",
"to": [
"https://vultron.example/organizations/coordinator"
],
"attributedTo": "https://vultron.example/organizations/vendorco",
"actor": "https://vultron.example/case-actors/vendorco-case-actor",
"target": "https://vultron.example/organizations/coordinator",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
}
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/case-actors/vendorco-case-actor#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "zKusNhKjA1vbz4dnMDgyDp8QBxZX82e5B7fw8KBYUjKVqGxW5kXLfXqmPGNcLwe9297Gcw6uwMjWzgEu8D19Sjvu"
}
}
- Triggering transition: Proposed → None (P → N) with the last open proposal, when the
Undowithdraws the CASE_MANAGER's own proposal. In all other cases, none. - Order: for each abandoned proposal, the cancel comes first: the CASE_MANAGER's
Rejectof a proposal it received, or itsUndoof one it made itself. Then comes anUndoof each invitation that the CASE_MANAGER relayed for the proposal. TheseUndoactivities change nothing more. The CASE_MANAGER commits all of them together, or commits none. - Who sends it: only the CASE_MANAGER, which undoes only invitations it sent. No use case handles it on receipt.
Create embargo event
Carries the new embargo in full, its start and end times included. It follows the case's genesis entry.
- When… the CASE_MANAGER has created a case and, with it, an embargo such as the default embargo
- Send:
Create(EmbargoEvent) - Send to: a participant
- Sent by: internal to the CASE_MANAGER
- Mapping status: none
Each participant learns of it from the case ledger, so it is addressed to nobody.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Create",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00/create",
"name": "https://vultron.example/case-actors/vendorco-case-actor Create Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"actor": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/case-actors/vendorco-case-actor#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z5vwey9uwJnN1qmuKWXx2T1VAvTwkjF4nsYCgGp6nD1AmizkuDmuqVjg4NmGTyWDFpwFYXLXjPGd2miuFsrdv46kG"
}
}
- Protocol role: each embargo that the creation of a case writes, such as the default embargo, is its own ledger entry. This entry comes right after the genesis entry of the case and carries the embargo in full (CLP-07-021). A replica built from the ledger alone reads the embargo's start and end times from this entry.
- Who commits it: only the CASE_MANAGER, as a ledger entry. No use case handles it on receipt. Each replica stores the embargo from the ledger entry.
Create embargo consent
Carries the new consent row in full: the embargo it answers, the participant it belongs to and its state.
- When… the CASE_MANAGER creates a participant's consent row for an embargo, such as the UNINVITED row a proposal writes
- Send:
Create(EmbargoConsent) - Send to: a participant
- Sent by: internal to the CASE_MANAGER
- Mapping status: none
Each participant learns of it from the case ledger, so it is addressed to nobody.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Create",
"id": "urn:uuid:4bc281de-9275-525f-b4e1-2671dcace1bb/create",
"name": "https://vultron.example/case-actors/vendorco-case-actor Create urn:uuid:4bc281de-9275-525f-b4e1-2671dcace1bb",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"actor": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:4bc281de-9275-525f-b4e1-2671dcace1bb",
"type": "EmbargoConsent",
"attributedTo": "https://vultron.example/organizations/vendorco",
"embargoId": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"state": "UNINVITED"
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/case-actors/vendorco-case-actor#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "zQkQWRDB4cQBGntH6v83vpwd3Tu6EB9un352Tz6tCPQ1sLTykNZA5ovV11yuttR7rHqMnAttZ9t5q1LHZE2GujPo"
}
}
- Protocol role: each consent row that the CASE_MANAGER creates is its own ledger entry.
This entry comes after the act that caused the row and carries the row in full (CLP-07-021).
A proposal writes an
UNINVITEDrow for each participant this way. - Who sends it: only the CASE_MANAGER. No use case handles it on receipt: each replica writes the row from the ledger entry.
Update embargo consent
Carries the changed consent row in full. A CASE_MANAGER with an embargo stake of its own records a change of its own consent this way, never as a Reject of the Invite.
- When… the CASE_MANAGER changes a participant's consent row, such as an invitation timing out, the rows carried over at activation or a change of its own consent
- Send:
Update(EmbargoConsent) - Send to: a participant
- Sent by: internal to the CASE_MANAGER
- Mapping status: none
Each participant learns of it from the case ledger, so it is addressed to nobody.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Update",
"id": "urn:uuid:4bc281de-9275-525f-b4e1-2671dcace1bb/update",
"name": "https://vultron.example/case-actors/vendorco-case-actor Update urn:uuid:4bc281de-9275-525f-b4e1-2671dcace1bb",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"actor": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:4bc281de-9275-525f-b4e1-2671dcace1bb",
"type": "EmbargoConsent",
"attributedTo": "https://vultron.example/organizations/vendorco",
"embargoId": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"state": "TIMED_OUT"
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/case-actors/vendorco-case-actor#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z5b81wLDQxggaZ5YwB4GMB8oDNuGDDzQh4VQnVdEQ547ydZF82XKuyaXhSNLCNg9uWhvuVSqwiqzdxqZbw8EAqRHN"
}
}
- Protocol role: each consent row that the CASE_MANAGER changes is its own ledger entry, which carries the changed row in full (CLP-07-021).
An invitation whose deadline passes unanswered moves to
TIMED_OUTthis way. The CASE_MANAGER writes the rows carried over at activation the same way. - The CASE_MANAGER's own consent: a CASE_MANAGER with a stake in the embargo records a change of its own consent as this
Update, never as aRejectof the Invite (MSM-07-017). - Who sends it: only the CASE_MANAGER. No use case handles it on receipt: each replica writes the row from the ledger entry.
Agree to proposed embargo terms
Records the sender's own consent to the proposed terms. The embargo becomes active only when the Case Owner sends its decision.
- When… a Participant agrees to proposed embargo terms
- Send:
Accept(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) - Send to: the CASE_MANAGER
- Sent by: the invitee
- Distinguished by: EM state
PROPOSED - Seen in: How to Establish an Embargo
- Mapping status: none
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Accept",
"id": "urn:uuid:82cf2abf-bf15-4d52-bfb3-12ec359ebc3a",
"name": "https://vultron.example/organizations/vendorco Accept https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": "https://vultron.example/cases/1/participants",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"type": "Invite",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"name": "https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"summary": "We propose to embargo case 1 for 90 days.",
"to": [
"https://vultron.example/case-actors/vendorco-case-actor"
],
"actor": "https://vultron.example/organizations/vendorco",
"target": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
}
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z2EHfokSGGiiQwuupDsuzyP6HAQZwpjpWb42Hd9PYdjd6E3bK37rfbRBGnaskawmcATGkLif3w2tH3R92mHwJ9BCF"
}
}
- Triggering transition: none in EM.
The sender's consent to those terms moves to
AGREED(MSM-07-003). - Who decides: an
Acceptof the Invite is always the sender's own consent to those terms, the Case Owner's included. ThisAcceptchanges no embargo on the case (see The Case Owner's Decision, MSM-07-011). - The embargo in force: an
AcceptorRejectmay answer an Invite for the embargo already in force, while the sender's consent to that embargo isINVITEDorTIMED_OUT(EP-09-012). Examples are a proposal that was activated before the sender answered it, an invitation whose deadline has passed, and a re-invitation after a lapse. The answer names that Invite by id.
Embargo Revision Proposal (EV)
Proposes a revision to the terms of the active embargo. The wire form is the same as a first proposal; the receiver's EM state makes it a revision.
- When… a Participant proposes revised terms for the active embargo
- Send:
Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase] - Send to: the CASE_MANAGER
- Sent by: the CASE_MANAGER or an active participant
- Distinguished by: EM state
ACTIVEorREVISE - Seen in: How to Revise or Terminate an Embargo
- Formal definition: Embargo Revision Proposal (EV)
- Mapping status: collapse
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Invite",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
"name": "https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"summary": "We propose to extend the embargo on case 1 to 120 days.",
"to": [
"https://vultron.example/case-actors/vendorco-case-actor"
],
"actor": "https://vultron.example/organizations/vendorco",
"target": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-09-29T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-09-29T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 120 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z28Ts1Ti5BTXXvPx2U6s2HesycG8QcgVLvEmFYpShXecUKAPwbfW9sVu5v6CmmFc5ewFjppxVhDTKxhVP6SMoLA3s"
}
}
- Triggering transition: Active → Revise (A → R).
Refuse an embargo revision
Records the sender's own refusal of the revision. The Case Owner keeps the prior terms by sending its decision.
- When… a Participant refuses a proposed embargo revision
- Send:
Reject(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) - Send to: the CASE_MANAGER
- Sent by: the invitee
- Distinguished by: EM state
REVISE - Seen in: How to Revise or Terminate an Embargo
- Mapping status: expansion
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Reject",
"id": "urn:uuid:f928d8ab-7019-4574-914a-1b6b377eac24",
"name": "https://vultron.example/organizations/vendorco Reject https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": "https://vultron.example/cases/1/participants",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"type": "Invite",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
"name": "https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"summary": "We propose to extend the embargo on case 1 to 120 days.",
"to": [
"https://vultron.example/case-actors/vendorco-case-actor"
],
"actor": "https://vultron.example/organizations/vendorco",
"target": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-09-29T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-09-29T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 120 days."
}
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z4nry1wXgKo9hQ2uf9ih51Ys7FuAobE7TJtvsNBQXZihLmRo3Eao19Y2vC4cCwD88erjbGryMeQS74Vn7f2mxzm4J"
}
}
- Triggering transition: none in EM.
The sender's consent to the revision moves to
DECLINED, and its consent to the embargo in force does not change (MSM-07-015). - Who decides: as for proposed terms, the
Rejectis the sender's own refusal (see The Case Owner's Decision).
Agree to an embargo revision
Records the sender's own consent to the revision. The revision replaces the active embargo only when the Case Owner sends its decision.
- When… a Participant agrees to a proposed embargo revision
- Send:
Accept(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]) - Send to: the CASE_MANAGER
- Sent by: the invitee
- Distinguished by: EM state
REVISE - Seen in: How to Revise or Terminate an Embargo
- Mapping status: none
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Accept",
"id": "urn:uuid:b87bd5e5-e4c3-46dc-ab5b-bb0cea856ce9",
"name": "https://vultron.example/organizations/vendorco Accept https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": "https://vultron.example/cases/1/participants",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"type": "Invite",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
"name": "https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"summary": "We propose to extend the embargo on case 1 to 120 days.",
"to": [
"https://vultron.example/case-actors/vendorco-case-actor"
],
"actor": "https://vultron.example/organizations/vendorco",
"target": "https://vultron.example/case-actors/vendorco-case-actor",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-09-29T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-09-29T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 120 days."
}
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "zAZLAytcYfxXJDm7oAvFcgbQ24xyR9WHf3qv91TXJ9je8Ryoa8AXzBJPPcDUig5JVSfk6nfT1TdkNRuJJwdroQzc"
}
}
- Triggering transition: none in EM.
The sender's consent to the revision moves to
AGREED, which binds the sender to nothing new until the Case Owner activates the revision (MSM-07-003). - Who decides: as for proposed terms, the
Acceptis the sender's own consent (see The Case Owner's Decision).
The Case Owner's Decision
The Case Owner decides each embargo proposal for the case with an activity of its own.
To activate a proposal, the Case Owner adds the embargo to the case with Add(EmbargoEvent), as Remove(EmbargoEvent) takes an embargo in force away.
To reject a proposal, it sends Reject(EmbargoEvent).
The object of each activity is the proposed EmbargoEvent itself, not the Invite that proposed it.
Its target is the case.
Its inReplyTo names the Invite(EmbargoEvent) that proposed the embargo, so a reader links the decision to the proposal it decides (RF-08-001).
A participant's consent is an Accept of the Invite, so the activation and a consent differ by type.
Only the Case Owner may send either activity, and it sends them to the CASE_MANAGER. The CASE_MANAGER refuses any other sender. The CASE_MANAGER records the decision in the case ledger. Every participant learns the decision from the ledger.
These two activities carry the shorthands EA, EC, ER, and EJ.
The EM state of the case tells them apart: a decision on a revision of the embargo in force is EC or EJ (MSM-02).
The Accept and Reject of each Invite record the consent of each participant and carry no shorthand (MSM-02-010).
Embargo Proposal Acceptance (EA)
Activates the proposal for the case. Any other open proposal stays open as a revision.
- When… the Case Owner decides to activate a proposed embargo for a case with no active embargo
- Send:
Add(EmbargoEvent)[target=VulnerabilityCase] - Send to: the CASE_MANAGER
- Sent by: the Case Owner
- Distinguished by: EM state
PROPOSED - Seen in: How to Establish an Embargo
- Formal definition: Embargo Proposal Acceptance (EA)
- Mapping status: collapse
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Add",
"id": "urn:uuid:d783f4e7-82b7-472b-98b8-4c898d642904",
"name": "https://vultron.example/organizations/vendorco Add Embargo for VendorCo Case #20260601 to urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"actor": "https://vultron.example/organizations/vendorco",
"target": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z4feocJcW6TSAiaGUL7k4UweDSYKFJYjEAE2dY6aoxyHHVvvG8KPtCRTsMC3quAi33GxP8QCs9vBHpghJxqjLrYTq"
}
}
- Triggering transition: Proposed → Active (P → A), or Proposed → Revise (P → R) while another proposal stays open as a revision (EMB-18-005).
Embargo Revision Acceptance (EC)
Activates the revision for the case. It replaces the active embargo in the same register step.
- When… the Case Owner decides to replace the active embargo with a proposed revision
- Send:
Add(EmbargoEvent)[target=VulnerabilityCase] - Send to: the CASE_MANAGER
- Sent by: the Case Owner
- Distinguished by: EM state
REVISE - Seen in: How to Revise or Terminate an Embargo
- Formal definition: Embargo Revision Acceptance (EC)
- Mapping status: collapse
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Add",
"id": "urn:uuid:1f3c5c2a-3890-47b4-a2b2-ff90df1e0966",
"name": "https://vultron.example/organizations/vendorco Add Embargo for VendorCo Case #20260601 to urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"actor": "https://vultron.example/organizations/vendorco",
"target": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-09-29T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-09-29T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 120 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z3HRjnq2WZvnKodwEsUnEndQPrJkd42JyYZkLQgciqFsojfjV4TApxLXtkrf6GsxYJZKPQVBfKBp4xJgtKpErxyfB"
}
}
- Triggering transition: Revise → Active (R → A), or Revise → Revise (R → R) while another proposal stays open (EMB-18-005).
For both EA and EC, the activation supersedes the embargo in force, if there is one, in the same register step.
Any other open proposal stays open as a revision.
The Case Owner's own consent to the activated terms is recorded with the activation, as AGREED, when it had given no answer to them, or its invitation timed out (MSM-07-028).
A Case Owner that declined those terms cannot activate them.
It first accepts the invitation with Accept(Invite(EmbargoEvent)), and then activates the terms, so that each answer is recorded as it was given (MSM-07-037).
When the new terms end no later than the terms they replace, every participant that agreed to the old terms is carried over to the new terms. When the new terms end later, a participant that has not agreed to them is no longer bound (MSM-07-020).
The CASE_MANAGER refuses an activation once the case is public, an exploit is public, or attacks are observed.
It also refuses an activation whose EmbargoEvent is not an open proposal of the case, or whose terms the Case Owner declined.
Reject embargo proposal
Rejects the proposal for the case. The case has no embargo once no other proposal is open.
- When… the Case Owner decides to reject a proposed embargo for a case with no active embargo
- Send:
Reject(EmbargoEvent)[target=VulnerabilityCase] - Send to: the CASE_MANAGER
- Sent by: the Case Owner
- Distinguished by: EM state
PROPOSED - Seen in: How to Establish an Embargo
- Formal definition: Embargo Proposal Rejection (ER)
- Mapping status: collapse
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Reject",
"id": "urn:uuid:ea20455d-6b29-43fe-991d-28ddd3ccd558",
"name": "https://vultron.example/organizations/vendorco Reject Embargo for VendorCo Case #20260601 to urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/1",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"actor": "https://vultron.example/organizations/vendorco",
"target": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z2W3DgdMzjCKSTggCLp5kxufNVkahwgZnSsRMUPfXRQCftmT95n64FH7N3Xvo5YYS3myrjMjZ3Frnn7Xka4Hdwvoq"
}
}
- Triggering transition: Proposed → None (P → N), or Proposed → Proposed (P → P) while another proposal is open (EMB-18-005).
Embargo Revision Rejection (EJ)
Rejects the revision for the case. The active embargo stays in force on its prior terms, unless the case is public, an exploit is public or attacks are observed, when the CASE_MANAGER also ends it.
- When… the Case Owner decides to reject a proposed revision
- Send:
Reject(EmbargoEvent)[target=VulnerabilityCase] - Send to: the CASE_MANAGER
- Sent by: the Case Owner
- Distinguished by: EM state
REVISE - Seen in: How to Revise or Terminate an Embargo
- Formal definition: Embargo Revision Rejection (EJ)
- Mapping status: collapse
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Reject",
"id": "urn:uuid:9bc8e575-53b1-4788-8328-855d64c5ebe8",
"name": "https://vultron.example/organizations/vendorco Reject Embargo for VendorCo Case #20260601 to urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"actor": "https://vultron.example/organizations/vendorco",
"target": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-09-29T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-09-29T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 120 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "z3rCVev1krWPyaHokqwU72KxJ5pWSaaZ2e3xU8Rfboo2aojnWYxZkC9ys797YK9nNqcYxf56gycoaFYaAAPQ266Ef"
}
}
- Triggering transition: Revise → Active (R → A), or Revise → Revise (R → R) while another proposal is open (EMB-18-005). On a public case it is Revise → eXited (R → X) instead, as described below (EMB-04-002).
After a rejection, an active embargo stays in force on its current terms (EJ), except as described below for a public case.
If no embargo was active, the case has no embargo (ER).
While another proposal is still open, the case stays in negotiation.
No participant's consent changes, the Case Owner's included.
If the case is public, an exploit is public, or attacks are observed when the Case Owner rejects the last open revision, the CASE_MANAGER also ends the embargo in the same act (ET).
The ledger then holds two entries: the Reject, which leaves the revision rejected, and the CASE_MANAGER's own Remove, which leaves the embargo terminated.
If the CASE_MANAGER refuses the termination, it commits neither entry.
Embargo Termination (ET)
Terminates the embargo with immediate effect.
- When… the Case Owner terminates the active embargo
- Send:
Remove(EmbargoEvent) - Send to: the CASE_MANAGER
- Sent by: the CASE_MANAGER or the Case Owner
- Seen in: How to Revise or Terminate an Embargo
- Formal definition: Embargo Termination (ET)
- Mapping status: direct
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Remove",
"id": "urn:uuid:7eff95a9-44a6-4079-8313-aa90e5526cdd",
"name": "https://vultron.example/organizations/vendorco Remove Embargo for VendorCo Case #20260601 from urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "EARLY",
"summary": "The embargo ended before its end time.",
"actor": "https://vultron.example/organizations/vendorco",
"origin": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
},
"terminationCause": {
"kind": "FIX_DEPLOYED"
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "zVuueqE4HwQ8imN8DY6qXgnYBJktQL9nQ5CsQk6idMBrgEzEaPxqhUi3VhSyyzhWDfJ14JkFZBySE5akUCcjbLrw"
}
}
- Triggering transition: Active or Revise → eXited ({A,R} → X). The same register step cancels every open proposal and writes no participant's consent (EP-08-004, MSM-07-025).
- Reason:
contentstates what ended the embargo. Its value is exactlyEND_TIME_REACHEDorEARLY. A receiver refuses aRemovewhosecontentis anything else.summaryis a human-readable account that the protocol does not read. - Why it ended:
terminationCausegives the cause, when the sender names one. The CASE_MANAGER's embargo register records the cause beside the reason (EMB-13-010, EMB-13-005). ItskindisTHREAT_SIGNAL(with thesignalsP,XorA),FIX_READY(with thevendorswhose readiness made the quorum),FIX_DEPLOYED, orOTHER(whose account is thesummary). Every cause goes withEARLY. ARemovethat carriesEND_TIME_REACHEDnames no cause. A receiver refuses aRemovewith an unknownkind, a missing or malformed detail, or a cause onEND_TIME_REACHED. The Case Owner'sRemovemay nameFIX_READY,FIX_DEPLOYEDorOTHER. The CASE_MANAGER records the cause as given. Only the CASE_MANAGER's ownRemovemay nameTHREAT_SIGNAL. A Case Owner reports public awareness, a public exploit or observed attacks as a case status update that setsP,XorA. The CASE_MANAGER then ends the embargo with the signals the case carries. Each replica copies the cause from the ledger entry onto its own register. A replica never derives a cause from its own case state. - At the end time: when the end time of the embargo in force has passed, the CASE_MANAGER ends that embargo with
END_TIME_REACHED. The CASE_MANAGER does this the next time it handles the case, or when an outside service such as a Sentinel asks it to. Whichever of the two comes second finds the embargo already ended and sends nothing. ARemovethat claimsEND_TIME_REACHEDbefore the embargo's end time is refused. - Bound participants that are no longer active: a signatory that was removed from the case, or that left it and is at RM
CLOSED, stays bound by the embargo. Such a signatory no longer receives ledger entries. The CASE_MANAGER sends each such participantETdirectly, one activity per participant, outside the ledger stream. The notice carries the embargo, the reason and the cause the CASE_MANAGER recorded, and nothing else. The notice is not a ledger entry. The participant applies the notice only when the CASE_MANAGER sent it. A termination on or after the agreed end date of the embargo is expiry. Expiry causes no notice.
Tell a participant the embargo has ended
Tells one participant that the embargo has ended, with immediate effect. The CASE_MANAGER sends one to each participant other than itself, naming the Case Owner in attributedTo and the Case Owner's request in inReplyTo when the Case Owner asked for the termination.
- When… the CASE_MANAGER ends the active embargo, on its own decision or on the Case Owner's
- Send:
Remove(EmbargoEvent) - Send to: a participant
- Sent by: the CASE_MANAGER
- Seen in: How to Revise or Terminate an Embargo
- Mapping status: direct
The wire form is the Embargo Termination (ET) a Case Owner sends; only its sender and addressee differ.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Remove",
"id": "urn:uuid:bf0aab95-bcd6-4b3e-ac09-554ffbc3243a",
"name": "https://vultron.example/case-actors/vendorco-case-actor Remove Embargo for VendorCo Case #20260601 from urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"inReplyTo": "urn:uuid:6c3be136-e8db-4a8f-91e6-c8a97aa0b7b7",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "EARLY",
"summary": "The embargo ended before its end time.",
"to": [
"https://vultron.example/organizations/coordinator"
],
"attributedTo": "https://vultron.example/organizations/vendorco",
"actor": "https://vultron.example/case-actors/vendorco-case-actor",
"origin": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/case-actors/vendorco-case-actor#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "zJvydv4hcqsqaiKinphYB17ApHayqHDC6aryz8Km4JmDamuVrLucn7DTgy4VaQjw5rQBzicDkvzhBFdtRjQwDM1X"
}
}
- Recipient: one
Remove(EmbargoEvent)per participant other than the CASE_MANAGER, never the CASE_MANAGER itself (EMB-19-001).
Withdraw from embargo
Ends the sender's own consent to the embargo in force, and to any revision it had agreed to. The embargo stays in force for every other participant.
- When… a Participant bound by the active embargo stops complying with it
- Send:
Leave(EmbargoEvent)[context=VulnerabilityCase] - Send to: the CASE_MANAGER
- Sent by: a participant
- Seen in: How to Revise or Terminate an Embargo
- Mapping status: none
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "Leave",
"id": "urn:uuid:51c5ebbb-9095-47be-b49c-b854df2a2ec6",
"name": "https://vultron.example/users/finndervul Leave Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": "https://vultron.example/case-actors/vendorco-case-actor",
"actor": "https://vultron.example/users/finndervul",
"object": {
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
"type": "EmbargoEvent",
"name": "Embargo for VendorCo Case #20260601",
"context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
"startTime": "2026-06-01T19:12:00.000000+00:00",
"endTime": "2026-08-30T00:00:00.000000+00:00",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We propose to embargo VendorCo Case #20260601 for 90 days."
},
"proof": {
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://certcc.github.io/Vultron/ns/context.jsonld",
"https://w3id.org/security/data-integrity/v2"
],
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"verificationMethod": "https://vultron.example/users/finndervul#main-key",
"proofPurpose": "assertionMethod",
"created": "2026-06-01T19:12:00.000000+00:00",
"proofValue": "zgcq1sCotoFPHUiEh52q2mTCXJEu2cj4Vz99Wc4qWkNLHZEPaUC6sEPK5avq1TNtKV4yRWLTcufd8TfcRns71XE4"
}
}
- Triggering transition: none.
The EM state of the case does not move.
The sender's consent to the embargo in force moves from
AGREEDtoDECLINED(MSM-07-010). - Who sends it: a participant that agreed to the embargo in force.
The participant sends it to the CASE_MANAGER.
This
Leaveanswers no Invite. A participant whose consent was recorded when the case was created, or when the participant joined, can therefore send it too. - Open revisions: every open revision that the sender had agreed to is declined with the
Leave, because each revision would replace the embargo that the sender left. - Refused: a
Leaveof an embargo that is not in force, from a sender whose consent to it is notAGREED, or from the Case Owner, which ends an embargo by terminating it (ET). - Not a Reject: a
Rejectof the Invite for the embargo in force, sent by a participant that agreed to it, is refused. Withdrawal is this activity (MSM-07-010, MSM-07-014).
When the CASE_MANAGER Refuses a Message
When the CASE_MANAGER refuses an embargo message because the case cannot take it, the CASE_MANAGER commits nothing.
The CASE_MANAGER tells the sender why with the refusal notice (CLP-02-005, CLP-05-001).
The notice is a Refuse whose object is the refused activity, inline, whose inReplyTo names that activity's id, and whose summary gives the reason.
The notice goes to the sender alone.
The sender closes its pending request when the notice arrives.
| Message | Refused, with the notice, when |
|---|---|
Invite(EmbargoEvent) (EP, EV) |
the embargo has ended (EM EXITED), which admits no proposal. The notice is a Refuse of the Invite, which the proposer reads as a refusal, not as a decline (ADR-0196). |
Accept(Invite(EmbargoEvent)) |
the case held the EmbargoEvent, but it is no longer available: it was decided, replaced, canceled or terminated, or its end time has passed, on time or late (CM-18-003, MSM-07-012). When the case holds current terms, a fresh Invite to them goes with the notice (EMB-17-003). |
Reject(Invite(EmbargoEvent)) |
the EmbargoEvent is neither the embargo in force nor an open proposal, or the sender agreed to the embargo in force, since withdrawal is Leave(EmbargoEvent) (MSM-07-014). |
Add(EmbargoEvent)[target=VulnerabilityCase] (EA, EC) |
the EmbargoEvent is not an open proposal of the case, or the case is public, an exploit is public, or attacks are observed (MSM-07-029, EMB-02-002), or the Case Owner declined the terms. The notice tells the Case Owner to accept the invitation first (MSM-07-037). |
Reject(EmbargoEvent)[target=VulnerabilityCase] (ER, EJ) |
the EmbargoEvent is not an open proposal of the case, or the termination the rejection would cause is refused (MSM-07-033, MSM-07-032). |
Remove(EmbargoEvent) (ET) |
it claims END_TIME_REACHED before the embargo's end time, or a Case Owner's Remove names a THREAT_SIGNAL cause (EMB-13-005). |
Leave(EmbargoEvent) |
no embargo is in force, the EmbargoEvent is not the embargo in force, the sender's consent to it is not AGREED, or the sender is the Case Owner (MSM-07-036). |
Some deliveries get no notice:
- A message that the sender has no standing to send is refused with no answer (HP-01-006).
- An
Acceptof an embargo the case never held is answered withCreate(ProcessingFault)instead, because the sender's view of the case is wrong (MSM-07-039, MSM-05-001). - A repeat of an answer already recorded, under a new id or the same one, is skipped and gets no notice (CM-13-005).
- A repeated proposal of terms the case already holds is skipped and gets no notice (EP-09-032).
Its end time equals that of a pending proposal, or, with no revision pending, that of the embargo in force.
The CASE_MANAGER registers nothing, commits nothing and relays no
Invite, whoever sent it and whatever its ids. The proposer's pending ask for it closes when its timeout window ends (SYNC-11-005). - An
InviteorAcceptthat arrives once the case is public, an exploit is public, or attacks are observed is answered with aRejectof the Invite instead (EMB-01-002, EMB-02-004). The CASE_MANAGER'sRejectof anAcceptreaches the participant. The participant then closes its pendingAccept. - A late
Acceptof an available embargo, the embargo in force or an open proposal before its end time, is recorded in the same way as an on-timeAccept(EMB-17-002). AnAcceptof replaced terms, late or on time, gets the notice and a relayed invitation to the case's current terms — the embargo in force, or the earliest-expiring open proposal whose embargo has not ended when none is in force (EMB-17-003, EP-08-002). No invitation is sent when the accepting actor's row for those terms is alreadyINVITEDorAGREED(CM-18-003). In a case that holds no such terms, the notice is the only reply (EMB-17-004). - A failure inside the CASE_MANAGER is not a refusal, and is never answered with a notice.
Formal messages with no dedicated wire activity
EK — Embargo Acknowledgment
- Protocol role: Acknowledges receipt of an EM message.
- Triggering transition: any valid EM message.
- Wire activity: none dedicated.
Acknowledgment of ledger-replicated state is cumulative and implicit through hash-chain continuity.
A per-message
EKwould be redundant (ADR-0083). - Formal definition: Message Types.
EE — Embargo Error
- Protocol role: Indicates that a Participant received an unexpected EM message.
- Triggering transition: any unexpected EM message.
- Wire activity: none dedicated.
Faults are conveyed by
Create(ProcessingFault),as:Reject, orAdd(Note), partitioned by failure mode (ADR-0083). - Formal definition: Message Types.