Matrix events
The board-room contract, published as @superjackfruitlabs/treaty-matrix-events: 29 schemas, one per event type. A type string never changes; a breaking change is a new type beside the old one (.v1 to .v2).
What the carrier posts for a person to decide.
dev.agentpod.checks.waiting.v2dev.superpipeline.attention.v2dev.superpipeline.delivery.v2dev.superpipeline.elicitationdev.superpipeline.gatedev.superpipeline.gate.v1dev.superpipeline.gate.v2dev.superpipeline.question.v2
Answers
Section titled “Answers”What a person sends back from a client.
dev.superpipeline.attention.answer.v2dev.superpipeline.check.override.v2dev.superpipeline.delivery.answer.v2dev.superpipeline.gate.decision.v1dev.superpipeline.gate.decision.v2dev.superpipeline.gate.pull_back.v2dev.superpipeline.question.answer.v2
Receipts
Section titled “Receipts”What closes a card once the board accepted a decision.
Notices
Section titled “Notices”Replies that report progress on a card.
dev.agentpod.check.failed.v2dev.agentpod.check.overridden.v2dev.agentpod.decision.pulled_back.v2dev.agentpod.decision.released.v2dev.agentpod.gate.progress.v2dev.superpipeline.decision.escalated.v1dev.superpipeline.decision.reminded.v1
Permissions
Section titled “Permissions”AgentPod’s harness permission prompts, in a station room.