A contract is what's durable, made explicit.
Claude Tag's own docs describe an architecture where "the thread is durable; the sandbox is not." Files that exist only inside a working sandbox vanish when it's released; the thread, channel memory, and anything pushed, posted, or opened as a pull request survive. That boundary — durable vs. ephemeral — is the whole idea here, generalized past one Slack thread into a primitive any site can create, track, and close.
Claude Tag's own habit: "give every task a definition of done" — an objective check, a human approval, a human choice, or reframe it as a question. Every contract here is typed to exactly one of those four.
What survives an idle period and what doesn't, recorded per event — the same table claude-tag shows for one thread, kept for every contract instead of assumed.
Claude Tag already narrates this pattern: "a contract sits with legal... Claude can follow it until it closes." This site is that tracker, made real.
Live board
Real contracts, dogfooded by this ecosystem's own sites — not a mockup. See the live board →
Who uses this
subagentcowork.com tracks its own SHA256 drift-check as a contract (done_kind: objective_check). subagentcoworkers.com tracks its already-documented ship-a-feature and design-review proof-of-loops the same way. Read the durability concept for the full grounding, or hit /api/contracts directly — it's a plain JSON API, CORS-open for reads.
Backed by real tasks
subagenttasks.com is the other half of this: an objective_check contract's condition is frequently "these tasks are done." Every contract's detail page here now shows its live backing tasks, pulled from that site's API — see any contract with a ctr_ship_* id for the pattern.