Skip to content
Treaty

check.overridden v1

A workspace owner or admin passed a check by hand (charter 2026-11-09, a gate may be decided by checks §5). by is a principal id. Mirrors SuperPipeline’s CheckOverriddenBody (apps/api/src/board/views.ts). Readers ignore properties they do not know.

CloudEvents

Section titled “CloudEvents”

Every event below carries dataschema https://raw.githubusercontent.com/SuperJackfruitLabs/treaty/main/schemas/superpipeline/check.overridden.v1.json.

Body event CloudEvents type Subject
check.overridden com.superjackfruit.superpipeline.check.overridden.v1 evt.<workspace>.superpipeline.check.overridden

The subject is the NATS subject the relay files it under; <workspace> is the board’s workspace. See the envelope and subjects.

Who sends it, who reads it

Section titled “Who sends it, who reads it”
  • Produced by SuperPipeline, through the relay.
  • Consumed by:
    • SuperExchange: Posts it to the board’s room, for the boards it carries. Receives it through the relay.
    • AgentPod: The hub’s board chat posts it, for the boards it still carries.
    • SuperDispatch: Takes it as a nudge to look at the board soon, on a board opted into scheduling. Reads nothing from its data.

Fields

Section titled “Fields”

Readers ignore properties they do not know, so a field may be added without a new version.

Field Type Required Description Constraints
event "check.overridden" yes
boardId string or null yes Null only on a board not yet initialised; a carrier needs it to route the event.
cardId string yes
cardTitle string yes
stageKey string yes
arrivalId string yes The card’s arrival at the stage this check belongs to: one per arrival, so a carrier says each once.
check object yes
check.name string yes
check.provider one of "ci", "verdict" yes
check.status "overridden" yes
by string yes
comment string yes Why, as the person wrote it; the board refuses a blank one. pattern \S
at string yes format date-time

Example

Section titled “Example”

From fixtures/superpipeline-events/examples.json, case “overridden”:

{
  "event": "check.overridden",
  "boardId": "brd_134a0ddb6d434478",
  "cardId": "crd_0f3c9a2b7d4e4a11",
  "cardTitle": "Ship the login page",
  "stageKey": "review",
  "arrivalId": "arr_7e8f9a0b1c2d3e4f",
  "check": {
    "name": "build",
    "provider": "ci",
    "status": "overridden"
  },
  "by": "usr_admin",
  "comment": "flaky runner",
  "at": "2026-11-10T09:50:00.000Z"
}

Refused

Section titled “Refused”

Each of these must fail. The corpus says why:

  • the check’s status is overridden
  • an override says why
  • at is a date-time

Source

Section titled “Source”