Skip to content
Treaty

dev.agentpod.decision.pulled_back.v2

The reply posted when a held approval was pulled back before its release time, returned for changes. pulled_back_by is a label, never a principal id or an mxid. Readers ignore properties they do not know.

How it rides

Section titled “How it rides”

Content that carries suite_event_type: "dev.agentpod.decision.pulled_back.v2".

Who sends it, who reads it

Section titled “Who sends it, who reads it”

The carrier is whichever service carries the board’s chat: AgentPod’s hub, or SuperExchange for a board that has moved to it.

Fields

Section titled “Fields”
Field Type Required Description Constraints
suite_event_type "dev.agentpod.decision.pulled_back.v2" yes
schema_version integer yes at least 1
gate_id string yes at least 1 character; at most 200 characters
board_id string yes at least 1 character; at most 200 characters
card_id string yes at least 1 character; at most 200 characters
pulled_back_by string or null yes
comment string yes pattern \S
at string yes pattern ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}(:\d{2}(\.\d{1,9})?)?(Z|[+-]\d{2}:\d{2})$; at most 40 characters
m.relates_to object yes
m.relates_to.rel_type "m.reference" yes
m.relates_to.event_id string yes at least 1 character

Example

Section titled “Example”

From fixtures/matrix-events/examples.json, case “release: pulled back with a comment”:

{
  "suite_event_type": "dev.agentpod.decision.pulled_back.v2",
  "schema_version": 1,
  "gate_id": "gate_6e19",
  "board_id": "brd_7c1f",
  "card_id": "crd_8a40",
  "pulled_back_by": "rakesh",
  "comment": "wrong image",
  "at": "2026-11-16T08:40:00.000Z",
  "m.relates_to": {
    "rel_type": "m.reference",
    "event_id": "$gateEventId"
  }
}

The corpus has 2 valid cases in all:

built: pulled back with a comment 
{
  "suite_event_type": "dev.agentpod.decision.pulled_back.v2",
  "schema_version": 1,
  "gate_id": "gate_8f3a",
  "board_id": "brd_7c1f",
  "card_id": "crd_6b40",
  "pulled_back_by": "rakesh",
  "comment": "wrong image",
  "at": "2030-01-01T09:00:00.000Z",
  "m.relates_to": {
    "rel_type": "m.reference",
    "event_id": "$gateEvent"
  }
}

Refused

Section titled “Refused”

Each of these must fail. The corpus says why:

  • a blank comment: a pull-back always says why (refused by schema)
  • no reference to the gate’s event (refused by schema)

Source

Section titled “Source”