Notify a participant of a quarantine (outbound)
Aerandil sends this request to participants affected by a federated-output quarantine. The request body is a CloudEvents JSON-format envelope with type = aerandil.participant_dispatch.quarantine_notice; data.quarantine identifies the output, incident, and operator follow-up actions.
Signature. Same data.signature Ed25519 detached signature contract as participant dispatch envelopes. Receivers treat this as an authenticated coordinator notice, not as an OAuth-protected Aerandil API call.
Receiver contract. Return any 2xx after recording the notice locally. Non-2xx responses mean the participant has not accepted custody of the quarantine notice and may be retried by the emitting delivery path.
Request Bodyrequired
Section titled “Request Bodyrequired”Coordinator-signed quarantine_notice envelope (proposal 0022 §7.5).
Envelope with type = aerandil.participant_dispatch.quarantine_notice (§7.5). Body of the outbound webhooks.aerandil_participant_quarantine_notice request.
object
Aerandil-specific payload (§5.5). Shape varies by type; the schema at dataschema is the contract.
object
URL of the schema describing data. v1 URLs are https://schema.aerandil.example/0022/...; receivers match on this to dispatch parsing.
UUID v7 per §5.1; reused across retries of the same logical dispatch.
Producer URI; e.g. aerandil://coordinator/tenant=T-1/program=... or aerandil://participant/....
CloudEvents specversion — pinned at 1.0.
Composite key (e.g. <run_id>/<participation_id>/<slot>).
RFC 3339; checked against the ±5-minute replay window.
Reverse-DNS message kind.
object
object
object
object
Ed25519 detached signature over the canonical bytes of the surrounding envelope (RFC 8785 JCS with the signature field elided). Proposal 0022 §8.2.
object
Signature algorithm — v1 supports ed25519 only.
Key identifier. Resolves against federated_participation.runner_signing_key_ref for participant-signed envelopes, or the coordinator signing config for coordinator-signed.
Base64 (RFC 4648 §4) detached signature bytes.
Stable schema URI for data; normally <dataschema_base>/quarantine_notice.v1.json.
Responses
Section titled “Responses”Receiver accepted the quarantine notice. Any 2xx status counts as success.
default
Section titled “default”Receiver did not accept the notice; the emitting delivery path decides whether to retry.