How to Establish an Embargo
Use this guide to put a case under embargo.
An embargo starts as a proposal, and the Case Owner activates it.
The Case Owner can activate it after collecting the answers of the other participants.
If the terms are already settled, the Case Owner can activate it at once.
You finish with the case at Embargo Management (EM) state EM.ACTIVE and the terms announced to every participant.
Prerequisites
- A running Vultron instance you can drive. The demo containers are the quickest route — see Tutorial: Run the Receive-Report Demo for the two steps that get you a container shell.
- An actor identity on that instance, holding the role each step names.
- Working knowledge of the ActivityStreams verb, object, and target shape, summarized in Vultron and ActivityPub.
-
Working knowledge of the case model: the objects a case is made of, in The Case Model, and who is allowed to change them, in The CASE_MANAGER and the Case Ledger. Where a guide's messages are case-scoped, they route through the CASE_MANAGER and their results appear on the case ledger.
-
An existing case with no active embargo. A case carries at most one.
- The Case Owner role, for activating an embargo. Any participant can propose one.
- The embargo terms you intend to propose — at minimum, an end date and time.
Embargo Management is a model of its own
The Vultron protocol gives much detail about Embargo Management and about how the protocol expects participants to interact with embargoes. Read that section before designing embargo behavior.
The exchange
The flowchart below shows the route to EM.ACTIVE.
The answer of each participant to the Invite records the consent of that participant.
The decision of the Case Owner is a separate activity on the embargo itself.
---
title: Establishing an Embargo
---
flowchart TB
subgraph as:Invite
EmProposeEmbargo["Embargo Proposal (EP) / Embargo Revision Proposal (EV)<br/>Invite(EmbargoEvent)"]
end
subgraph participant answers
EmAcceptEmbargo["Agree to the terms<br/>Accept(Invite(EmbargoEvent))"]
EmRejectEmbargo["Refuse the terms<br/>Reject(Invite(EmbargoEvent))"]
end
subgraph Case Owner decides
ActivateEmbargo["Embargo Proposal Acceptance (EA)<br/>Add(EmbargoEvent)[target=VulnerabilityCase]"]
RejectEmbargoProposal["Embargo Proposal Rejection (ER)<br/>Reject(EmbargoEvent)[target=VulnerabilityCase]"]
end
subgraph as:Announce
AnnounceEmbargo["Announce the embargo terms<br/>Announce(EmbargoEvent)"]
end
start([Start]) --> EmProposeEmbargo
EmProposeEmbargo --> EmAcceptEmbargo
EmProposeEmbargo --> EmRejectEmbargo
EmAcceptEmbargo --> d{Owner activates?}
EmRejectEmbargo --> d
d -->|y| ActivateEmbargo
d -->|n| RejectEmbargoProposal
ActivateEmbargo --> AnnounceEmbargo
Negotiate the terms
Embargo Proposal (EP) is implemented in ActivityStreams as Invite(EmbargoEvent).
The same activity also carries a revision, Embargo Revision Proposal (EV).
The receiver does not use the activity to distinguish a revision from an initial proposal.
The receiver uses the EM state of the case (MSM-02).
-
Send
Invite(EmbargoEvent)to the CASE_MANAGER, with the proposedEmbargoEventinline as itsobject, the CASE_MANAGER as itstargetand the case as itscontext. Thetargetnames the invitee, the one actor the Invite is addressed to. The case moves toEM.PROPOSED. The protocol namesInvite(EmbargoEvent)as the only form.A received
Create(EmbargoEvent)is not a protocol message (VAM-01-019). The inbox of this implementation does not process it (VAM-01-018). ACreateof anEmbargoEventis the CASE_MANAGER's own ledger record of a creation-time embargo. So the inbox reports it as "no use case found". The inbox refuses aCreateof any otherEventas an unrecognized activity.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 - Reference: Embargo Proposal (EP)
Example activity
{ "@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" } } -
The CASE_MANAGER asks each other participant about the terms with an
Invite(EmbargoEvent)of its own. This Invite is addressed to that participant, names it intarget, names the proposer inattributedToand names the proposal ininReplyTo. If you are the CASE_MANAGER, you send this Invite. If you are not the CASE_MANAGER, you answer this Invite.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
attributedToand the proposer's Invite ininReplyTo, 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
- Reference: Ask a participant about proposed embargo terms
Example activity
{ "@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" } } -
Each participant answers with Agree to proposed embargo terms,
Accept(Invite(EmbargoEvent)), or Refuse proposed embargo terms,Reject(Invite(EmbargoEvent)). Either answer records only the consent of that participant, so it carries no protocol shorthand. This rule also applies to an answer from the Case Owner. The case stays atEM.PROPOSED.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 - Reference: Agree to proposed embargo terms
Example activity
{ "@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" } }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 - Reference: Refuse proposed embargo terms
Example activity
{ "@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" } } -
When you judge that the proposal has carried, send Embargo Proposal Acceptance (EA),
Add(EmbargoEvent), as Case Owner, with the proposedEmbargoEventas itsobjectand the case as itstarget. Name the proposal'sInvite(EmbargoEvent)ininReplyTo. The case moves toEM.ACTIVE. Your own consent to the terms is recorded at the same time. If you refused the terms in step 3, accept them first withAccept(Invite(EmbargoEvent)). The CASE_MANAGER refuses the activation of terms you refused, and its refusal notice tells you to accept them first (MSM-07-037). Theaccept-embargotrigger does this for you: when you refused the terms, it sends theAccept. A later call sends theAddonce your copy of the case holds thatAccept.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 - Reference: Embargo Proposal Acceptance (EA)
Example activity
{ "@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" } } -
Send
Announce(EmbargoEvent)so every participant has the terms in hand.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 - Reference: Announce embargo
Example activity
{ "@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" } }
To reject the proposal, send Embargo Proposal Rejection (ER), Reject(EmbargoEvent), with the same object, target and inReplyTo as Case Owner instead.
The case returns to EM.NONE.
The negotiation is then open again.
Propose revised terms with another Invite(EmbargoEvent).
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 - Reference: Reject embargo proposal
Example activity
{
"@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"
}
}
Propose one set of terms at a time. This rule is how the protocol resolves competing terms. It is not a workaround. The protocol has no poll across candidate embargoes (ADR-0100).
You can put several sets of terms on the table.
To do this, send a separate Invite(EmbargoEvent) for each set.
Each set is then accepted or rejected on its own.
When more than one proposal is open, Participants take the one with the earliest end date first and treat the rest as revisions (EP-08).
See Default Embargoes.
Activate settled terms without waiting
The only way to put an embargo on a case is to propose it. A proposal is what adds an embargo to the case. When the terms need no negotiation, propose them as Case Owner and activate them at once, without waiting for any answer.
- Send
Invite(EmbargoEvent)as above. Proposing the terms records your consent to them. - Send
Add(EmbargoEvent)with the case as itstargetand your ownInvite(EmbargoEvent)ininReplyTo. - Send
Announce(EmbargoEvent).
Use this route when the terms need no negotiation:
- no other participant has joined the case yet, or
- your published
EmbargoPolicyapplies and nobody has proposed anything to the contrary.
The other participants still receive the Invite and answer it. Only the participants that agree are bound. So an immediate activation binds no participant that did not agree.
A new case may already be embargoed
An embargo-eligible case begins with an active embargo, even when no proposal exchange is visible.
The reason is that a Protocol Default applies when no proposal and no actor default applies.
A Reporter who wants other terms states them on the report Offer, not in a proposal exchange.
See How to Report a Vulnerability and the report-with-embargo demo there.
See Default Embargoes.
Answer an embargo already in force
The Case Owner can activate an embargo before every participant has answered its Invite. When the embargo is in force, it is no longer an open proposal. But a participant that has not answered can still answer it.
- Find the
Invite(EmbargoEvent)you received for the embargo in force. - Call
accept-embargoorreject-embargowith that Invite's ID asproposal_id. You send the sameAccept(Invite(EmbargoEvent))orReject(Invite(EmbargoEvent))as for an open proposal, addressed to the CASE_MANAGER.
You can answer this way while your consent row for the embargo in force is INVITED or TIMED_OUT.
An Accept sent after the reply deadline is honored, because the terms you agree to are the terms in force (EMB-17-002).
The trigger reports not found when you hold no such Invite, or when your row is already AGREED or DECLINED.
Name the Invite.
A call without proposal_id answers only an open proposal, and never the embargo in force (EP-09-030).
So the call reports not found when no proposal is open.
Verify
| What you sent | What to confirm |
|---|---|
Invite(EmbargoEvent) |
The case em_state is PROPOSED. |
Accept(Invite(EmbargoEvent)) |
Your embargo consent row for the embargo is AGREED, as §9 Participant Embargo Consent (PEC) State Machine in the specification defines it. You become a signatory once that embargo is the Active Embargo. |
Add(EmbargoEvent) with the case as target, as Case Owner |
The case em_state is ACTIVE, the case names one active embargo, and your consent row for it is AGREED. |
Reject(EmbargoEvent) with the case as target, as Case Owner |
The case em_state is NONE and no participant's consent row changed. |
Announce(EmbargoEvent) |
Every participant's replica carries the same active embargo ID. |
See it end to end
Try it: vultron-demo establish-embargo
vultron-demo establish-embargo
Or with Docker Compose:
DEMO=establish-embargo docker compose -f docker/docker-compose.yml run --rm demo
The scenario runs both the accepted and the rejected proposal.
Further reading
- Embargo Management (EM) Messages — the wire format and a rendered example for each activity above
- Embargo Management — the state machine these activities drive
- Negotiating Embargoes — how to choose terms other parties will accept
- §9 Participant Embargo Consent (PEC) State Machine in the specification — the Participant Embargo Consent (PEC) state machine that records each participant's own answer to a proposal
- How to Revise or Terminate an Embargo — what to do once the embargo is active
- Trigger API Reference — request schema and endpoint details for
propose-embargo,accept-embargo, andreject-embargo