Report Management (RM) Messages
The RM shorthands inform other Participants of the sender's report-handling state. Report Submission is the only RM message whose receipt directly triggers an RM state change in the receiver. All other RM messages convey the sender's status.
The RM state ladder has two wire expressions: the dedicated report-scoped activities listed below, and the rmState field of an Add(ParticipantStatus, target=<participant>/statuses) broadcast, which adds the status to the participant's status history (ADR-0204; see Case State (CS)).
Report/Case Accepted (RA) and Report/Case Deferred (RD) also take case-scoped verbs: Join(VulnerabilityCase) and Ignore(VulnerabilityCase).
The reason is that engaging or deferring is a case-participation decision, not a report-validity judgment (MSM-01-004, MSM-01-005).
Both name the case by a typed reference, an inline object with only its id and type, and carry no copy of it: the CASE_MANAGER reads the case from its own store (AKM-03-004, ADR-0165).
The same holds for the Report/Case Closed Leave(VulnerabilityCase); see Close case.
The CASE_MANAGER applies one rule to an RM state whichever of these expressions carries it (RSH-06-006). The state is recorded for the sender, never for the receiver (RSH-08-001), and only when the sender is a participant of the case. A forward move is recorded even when it skips states, and the CASE_MANAGER then asks the sender in a note which path it took (RSH-06-001, RSH-06-004). A backward move is refused and the recorded state stands (RSH-06-002), and the CASE_MANAGER tells the sender in a note that it refused the move (RSH-06-004).
Each of these notes is recorded on the case as a case ledger entry.
The sender receives it from the ledger, as every active participant does, not as a message addressed to it alone (RSH-06-004).
An activity and an Add(ParticipantStatus) that report the same move record it once (RSH-08-002).
When the CASE_MANAGER refuses an RM message because a precondition does not hold, such as a backward move, it also sends the sender the refusal notice (CLP-02-005, CLP-05-001).
The notice is a Refuse of the refused message, with the reason in summary, and the CASE_MANAGER records nothing of the refused message in the ledger.
The note about a refused backward move is recorded alongside the notice, not instead of it (RSH-06-004).
The CASE_MANAGER sends no notice when the sender is not a participant of the case, or when the message restates a state already recorded (RSH-08-002).
Occasions
| When… | Send | Send to | Sent by | Distinguished by | Details |
|---|---|---|---|---|---|
| a Reporter has written up a vulnerability and is about to submit the report | Create(VulnerabilityReport) |
an actor outside any case | any actor (usually: reporter) | — | Create report |
| a Reporter submits a vulnerability report to a Vendor or Coordinator | Offer(VulnerabilityReport) |
an actor outside any case | any actor (usually: reporter) | — | Report Submission (RS) |
| a report receiver has received a submitted report | Read(Offer(VulnerabilityReport)) |
an actor outside any case | the addressee of the vulnerability report offer (usually: vendor, coordinator) | — | Report Acknowledgment (RK) |
| a report receiver judges the report valid | Accept(Offer(VulnerabilityReport)) |
the CASE_MANAGER | a participant (usually: vendor, coordinator) | — | Validate report |
| a report receiver judges the report invalid | TentativeReject(Offer(VulnerabilityReport)) |
the CASE_MANAGER | a participant (usually: vendor, coordinator) | — | Invalidate report |
| a report receiver closes a report no case holds | Reject(Offer(VulnerabilityReport)) |
an actor outside any case | the addressee of the vulnerability report offer (usually: vendor, coordinator) | — | Close report |
| a Participant accepts the case for further action | Join(VulnerabilityCase) |
the CASE_MANAGER | a participant | — | Report/Case Accepted (RA) |
| a Participant defers further action on the case | Ignore(VulnerabilityCase) |
the CASE_MANAGER | a participant | — | Report/Case Deferred (RD) |
Create report
Mints the vulnerability report object. It precedes the Offer that submits the report.
- When… a Reporter has written up a vulnerability and is about to submit the report
- Send:
Create(VulnerabilityReport) - Send to: an actor outside any case
- Sent by: any actor (usually: reporter)
- Seen in: How to Report a Vulnerability
- 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": "Create",
"id": "urn:uuid:fbfd8da0-40e0-4a2c-8794-b290cb971011",
"name": "https://vultron.example/users/finndervul Create FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"actor": "https://vultron.example/users/finndervul",
"object": {
"id": "https://demo.vultron.local/VulnerabilityReport/17a7b3e5-d74e-481e-ad90-2b9ab88c6dac",
"type": "VulnerabilityReport",
"name": "FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "I found a vulnerability!",
"attributedTo": "https://vultron.example/users/finndervul"
},
"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": "z3aRFCw9hXruBczo5AmLYTF45QW2N5AWGnbFyMvzeTweFyY5X79T6gk1dRLoTigDhnPs98AAjHrHJXbjXjHSSdwan"
}
}
- Triggering transition: none (object construction, not a state change).
Report Submission (RS)
Offers the report to a new Participant. The Offer may carry proposed embargo terms.
- When… a Reporter submits a vulnerability report to a Vendor or Coordinator
- Send:
Offer(VulnerabilityReport) - Send to: an actor outside any case
- Sent by: any actor (usually: reporter)
- Seen in: How to Report a Vulnerability
- Formal definition: Report Submission (RS)
- 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": "Offer",
"id": "urn:uuid:1f075842-1506-4058-b7b1-60fa31e9a619",
"name": "https://vultron.example/users/finndervul Offer FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": [
"https://vultron.example/organizations/vendorco"
],
"actor": "https://vultron.example/users/finndervul",
"object": {
"id": "https://demo.vultron.local/VulnerabilityReport/17a7b3e5-d74e-481e-ad90-2b9ab88c6dac",
"type": "VulnerabilityReport",
"name": "FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "I found a vulnerability!",
"attributedTo": "https://vultron.example/users/finndervul"
},
"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": "z2Ed1ifAniZwq2KJ67ze9A8ApVaCCCcfAXAHobg64cLZQyUfR8VzAgELhU3W519F1gDs26pGUdQqN8JqL472Smw78"
}
}
- Triggering transition: emitted when the sender is Accepted (sender ∈ A).
- Receiver: the receiver does not refuse a new report on the sender's standing; it acts only when it is in the Offer's
to(HP-01-010, HP-09-001). - Proposed embargo terms: the Offer may carry
proposedEmbargo, an inlineEmbargoEventwhosecontextis the report. At case creation, the Case Owner compares it with its own default, and the shorter embargo wins (EP-04-003, EP-04-004).
Report Acknowledgment (RK)
Acknowledges receipt of the submitted report. Report submission is not replicated through the case ledger, so the acknowledgment is an explicit message.
- When… a report receiver has received a submitted report
- Send:
Read(Offer(VulnerabilityReport)) - Send to: an actor outside any case
- Sent by: the addressee of the vulnerability report offer (usually: vendor, coordinator)
- Seen in: How to Acknowledge a Report, How to Report a Vulnerability
- Formal definition: Report Acknowledgment (RK)
- 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": "Read",
"id": "urn:uuid:28fc50c5-d5d5-4278-a718-99ef7bed2af7",
"name": "https://vultron.example/organizations/vendorco Read https://vultron.example/users/finndervul Offer FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We have received the report. We will get back to you soon.",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"type": "Offer",
"id": "urn:uuid:fb5efdcc-2a15-47e7-88b4-b46ed8bf7ca0",
"name": "https://vultron.example/users/finndervul Offer FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": [
"https://vultron.example/organizations/vendorco"
],
"actor": "https://vultron.example/users/finndervul",
"object": {
"id": "https://demo.vultron.local/VulnerabilityReport/17a7b3e5-d74e-481e-ad90-2b9ab88c6dac",
"type": "VulnerabilityReport",
"name": "FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "I found a vulnerability!",
"attributedTo": "https://vultron.example/users/finndervul"
}
},
"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": "z4HCohFfNtKP8HgFMRDnt6KtZTiMG5N4qbyD24ix19QzCqgbQHbjRBrHpXFdYNgRMDmw1tYFZczX6fAjTB6WZz5dC"
}
}
- Triggering transition: receipt of
RS; Vultron sendsRKonly to acknowledge a report submission (RMB-08-003). - Receiver: the reporter, which holds the Offer, accepts
RKonly from one of the Offer's addressees and refuses any other sender (RMB-08-004).RKmay go to the reporter at any time after the report arrives, whether or not a case exists (RMB-08-003).RKnever goes to the CASE_MANAGER, and it writes no ledger entry (RMB-08-005, RMB-08-007, PCR-08-001). - Object: the report's original
Offer, not the report itself; a bareRead(VulnerabilityReport)matches no pattern.RKsurvives as a dedicated wire activity because report submission is not ledger-replicated (MSM-01-008).
Validate report
Designates the report as valid, moving the sender's RM state to Valid.
- When… a report receiver judges the report valid
- Send:
Accept(Offer(VulnerabilityReport)) - Send to: the CASE_MANAGER
- Sent by: a participant (usually: vendor, coordinator)
- Seen in: How to Report a Vulnerability
- Formal definition: Report Valid (RV)
- 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": "Accept",
"id": "urn:uuid:f4740aec-67af-4680-b41a-2427e33edef3",
"name": "https://vultron.example/organizations/vendorco Accept https://vultron.example/users/finndervul Offer FDR-8675309",
"inReplyTo": "urn:uuid:0ff0a347-3e73-4af8-b221-af087d20f7b7",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We've validated the report. We'll be creating a case shortly.",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"type": "Offer",
"id": "urn:uuid:0ff0a347-3e73-4af8-b221-af087d20f7b7",
"name": "https://vultron.example/users/finndervul Offer FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": [
"https://vultron.example/organizations/vendorco"
],
"actor": "https://vultron.example/users/finndervul",
"object": {
"id": "https://demo.vultron.local/VulnerabilityReport/17a7b3e5-d74e-481e-ad90-2b9ab88c6dac",
"type": "VulnerabilityReport",
"name": "FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "I found a vulnerability!",
"attributedTo": "https://vultron.example/users/finndervul"
}
},
"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": "z65SsQSVRHLVY6XjhAUGfzKVxEtyfXenRCWPcmdDczm7iYowpjdwbw5mE3mAoRMdSJR59X6c184Cz8GrCn4Fm6zLk"
}
}
- Triggering transition: Received or Invalid → Valid ({R,I} → V).
- Second wire form: a participant that joined through an Invite sends
Accept(Invite(whole VulnerabilityCase)[target=Actor])instead, answering the full-case Invite (VAM-04-012); see Accept Full-Case Invite. It never validates the original report Offer (CM-11-020, CM-11-051).
Invalidate report
Designates the report as invalid, moving the sender's RM state to Invalid.
- When… a report receiver judges the report invalid
- Send:
TentativeReject(Offer(VulnerabilityReport)) - Send to: the CASE_MANAGER
- Sent by: a participant (usually: vendor, coordinator)
- Seen in: How to Report a Vulnerability
- Formal definition: Report Invalid (RI)
- 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": "TentativeReject",
"id": "urn:uuid:ca2ec341-edaa-4457-a200-5a8f1c13ac6b",
"name": "https://vultron.example/organizations/vendorco TentativeReject https://vultron.example/users/finndervul Offer FDR-8675309",
"inReplyTo": "urn:uuid:ee00d16a-4faf-40d3-9b00-104666aff73e",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We're declining this report as invalid. If you have a reason we should reconsider, please let us know. Otherwise we'll be closing it shortly.",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"type": "Offer",
"id": "urn:uuid:ee00d16a-4faf-40d3-9b00-104666aff73e",
"name": "https://vultron.example/users/finndervul Offer FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": [
"https://vultron.example/organizations/vendorco"
],
"actor": "https://vultron.example/users/finndervul",
"object": {
"id": "https://demo.vultron.local/VulnerabilityReport/17a7b3e5-d74e-481e-ad90-2b9ab88c6dac",
"type": "VulnerabilityReport",
"name": "FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "I found a vulnerability!",
"attributedTo": "https://vultron.example/users/finndervul"
}
},
"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": "z3bkeT7VXn8UMBnR4qhbixNv5YfYHttpDe5STJ7z7LAh8eD7A2h4Kfqt6fs2e8sQYKCWiZbvW6tXSJJ6VRofQy3L3"
}
}
- Triggering transition: Received → Invalid (R → I).
- Second wire form: a participant that joined through an Invite sends
TentativeReject(Invite(whole VulnerabilityCase)[target=Actor])instead, answering the full-case Invite (VAM-04-013); see Tentatively reject Full-Case Invite.
Close report
Closes the report, moving the sender's RM state to Closed. Once a case holds the report, its Case Owner closes the case with Leave(VulnerabilityCase) instead, and every receiver refuses a Reject(Offer(VulnerabilityReport)) for it.
- When… a report receiver closes a report no case holds
- Send:
Reject(Offer(VulnerabilityReport)) - Send to: an actor outside any case
- Sent by: the addressee of the vulnerability report offer (usually: vendor, coordinator)
- Seen in: How to Advance a Case Through Report Management, How to Report a Vulnerability
- Formal definition: Report Closed (RC)
- 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:1a976e03-b7a9-4c2a-a044-5e9569f4d867",
"name": "https://vultron.example/organizations/vendorco Reject https://vultron.example/users/finndervul Offer FDR-8675309",
"inReplyTo": "urn:uuid:9b449431-1c12-4239-bbe4-268fa648540c",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "We're closing this report.",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"type": "Offer",
"id": "urn:uuid:9b449431-1c12-4239-bbe4-268fa648540c",
"name": "https://vultron.example/users/finndervul Offer FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"to": [
"https://vultron.example/organizations/vendorco"
],
"actor": "https://vultron.example/users/finndervul",
"object": {
"id": "https://demo.vultron.local/VulnerabilityReport/17a7b3e5-d74e-481e-ad90-2b9ab88c6dac",
"type": "VulnerabilityReport",
"name": "FDR-8675309",
"published": "2026-06-01T19:12:00.000000+00:00",
"updated": "2026-06-01T19:12:00.000000+00:00",
"content": "I found a vulnerability!",
"attributedTo": "https://vultron.example/users/finndervul"
}
},
"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": "z4uYunf8AZSdNGeD5DkTJ7mSE9ry5jaLSfKyzT8ituo7FNbvf9oeBPEhtwFSV5ru4BP4cfEeJztK6zc58ZjukEDew"
}
}
- Triggering transition: Received, Invalid, Deferred, or Accepted → Closed ({R,I,D,A} → C).
- Second wire form: a participant that joined through an Invite closes with
Reject(Invite(whole VulnerabilityCase)[target=Actor])(VAM-04-014); see Reject Full-Case Invite. - Stub Invite decline: an invitee that declines its stub Invite sends
Reject(Invite(VulnerabilityCase preview)[target=Actor]), which is not anRCmessage. On receipt, the CASE_MANAGER moves the invitee's RM state to Closed (CM-11-007); see Reject invite to case. - Fault axis: the
Reject(Offer(VulnerabilityReport))activity also appears as an ordinary refusal in the fault-and-acknowledgment mapping (MSM-05-003); see Faults and Acknowledgments.
Report/Case Accepted (RA)
Joins the case, moving the sender's RM state to Accepted. Engaging is a case-participation decision, so the verb names the case rather than the report.
- When… a Participant accepts the case for further action
- Send:
Join(VulnerabilityCase) - Send to: the CASE_MANAGER
- Sent by: a participant
- Seen in: How to Advance a Case Through Report Management
- Formal definition: Report/Case Accepted (RA)
- 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": "Join",
"id": "urn:uuid:b7bdf598-2a01-4afb-8ac6-642c64da31d6",
"name": "https://vultron.example/organizations/vendorco Join 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": "We're engaging this case.",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"type": "VulnerabilityCase",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a"
},
"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": "zAvc7eAJiDbF6seQHDDT61bX1qoUg9PuP791mNTTAjAGunzf4s48qzw8YuzQmmhfhhiTED4Q8nPwBHtzWKaNeuTX"
}
}
- Triggering transition: Valid or Deferred → Accepted ({V,D} → A).
- Re-engagement: re-engaging a deferred case emits the same activity.
There is no separate re-engagement wire form, because
DEFERRED→ACCEPTEDis a forward transition rather than a retraction of the earlier deferral.
Report/Case Deferred (RD)
Ignores the case, moving the sender's RM state to Deferred. Deferring is a case-participation decision, so the verb names the case rather than the report.
- When… a Participant defers further action on the case
- Send:
Ignore(VulnerabilityCase) - Send to: the CASE_MANAGER
- Sent by: a participant
- Seen in: How to Advance a Case Through Report Management
- Formal definition: Report/Case Deferred (RD)
- 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": "Ignore",
"id": "urn:uuid:6c1ce9fe-f2eb-4665-874b-ff3c11216485",
"name": "https://vultron.example/organizations/vendorco Ignore 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": "We're deferring this case.",
"actor": "https://vultron.example/organizations/vendorco",
"object": {
"type": "VulnerabilityCase",
"id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a"
},
"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": "z3e76zSiBGrvMjNHx8rradi8iqaiLi75qkdnz388bWD6oHg526yfx2mYVUgeU3nD71HU8NqMZbD7z2J5YwMp5BK2F"
}
}
- Triggering transition: Valid or Accepted → Deferred ({V,A} → D).
- Why a case verb: deferring is a case-participation decision, not a report-validity judgment (MSM-01-004).
Formal messages with no dedicated wire activity
RE — Report Error
- Protocol role: Indicates a Participant received an unexpected RM message.
- Triggering transition: any unexpected RM message.
- Wire activity: none dedicated. Faults are conveyed by
Create(ProcessingFault)(not understood),as:Reject(understood but declined), orAdd(Note)(needing explanation), partitioned by failure mode rather than by state machine (ADR-0083). - Received in RM Start: a Participant in RM Start that receives a fault about an RM activity does not answer it with a fault (RMB-07-002).
- Formal definition: Message Types.