Skip to content
Docs Flowy
Specs and the Board

Specs written by people and agents, tracked from review to built

A person drafts a spec in the editor. An agent files what it produced as an artifact. When either is ready it goes on the Board, where review and implementation are two separate questions.
Start freeHow agents connect
Two writers

One place for what people and agents write

Synced documents come from your repository and stay read-only. What sits beside them is written here, and the record always says who wrote it.

Drafts, written by a person

A spec somebody on the team is writing, in the editor. Until it is exported, agents cannot see it or the notes on it: a half-written spec an agent can read is one it will start building.

Artifacts, written by an agent

An agent files a spec, a migration plan or a review with write_artifact. Each write is a new version beside your docs, with a link a person can open. No tool deletes an artifact.

Export to Board

The implementation axis arrives with promotion

Export to Board is the one door, and it goes one way. The item keeps its id, versions, notes and status, and stays on its own screen marked as on the Board.

Before export, a draft or an artifact carries review only. Nobody can mark an idea as built, and an agent cannot claim work against its own output.

After export it stays editable. A new version marks its status drifted until someone reviews it again, and the editor says so before you save.

docs/runbooks/01-payouts.md
docs/runbooks/01-payouts.md

Payout lifecycle

In reviewIn progress
Validated against9f1c04e
Content now9f1c04e

Somebody is reading it. The build is underway.

A document's review and implementation status over time: in review, then validated by a person, then an agent claiming the implementation, and finally the content changing — at which point the badge reads validated and drifted without anybody altering the status.
The Board

Two axes, one at a time

Validated and still in progress is the most common state of a real spec. The Board shows one axis as columns and the other as a pill on each card.

Review
  • Untriaged
  • Draft
  • In review
  • Validated
  • Rejected
Implementation
  • To do
  • In progress
  • Implemented
  • Testing
  • Done
  • Cancelled
  • Untriaged means nobody has set a status yet, so the card carries no pill.
  • Implemented means an agent says it built it and nobody confirmed. A person answers by moving the card out of that column.
  • Rejected needs a reason, written as a note on the document in the same step.
  • Drift compares content, never a timestamp. A spec edited after it was validated reads as drifted until someone reviews it again.
board · payments
Showing
Untriaged1
On-call rotation
Draft1
Retry budget
in progress1
In review1
Payout lifecycle
in progress2
Validated1
ADR 002 — idempotency keys
done · drifted
Rejected

Four documents, one axis. The other one rides on the card.

A workflow board with one axis in its columns and the other stated on each card: a document is validated while still in progress, the axis switches to implementation without re-entering anything, and an agent claims a build into a column no person may drop into.
Agents claim, people close

An agent may say the work is done. A person decides.

These are rules in the product, enforced on the server, not a policy in a document.

mcp · key scoped to payments
  1. Agentsearch_docs

    "idempotency" across 6 repositories · 3 hits

An agent searching the team's documentation, reading an architecture decision record, filing an artifact, then receiving a reviewer's objection and answering it as a typed disagreement. The note moves to awaiting confirmation and stays there: there is no tool that closes it.
  1. 01
    AgentAn agent claims the buildreport_implementation moves a spec to Implemented, never to Done, and leaves a note that waits for a person.
  2. 02
    AgentAn agent answers feedbackIt may agree, disagree, ask for clarification, or say the note is addressed. Addressed moves the note to awaiting confirmation and no further.
  3. 03
    PersonA person closes itClosing a note, confirming a claim and rejecting a spec are human acts. An agent's credential reaches none of them.
Plans

Starter and up

Review and implementation status, the Board, notes and an agent's write access are part of Starter, Team, Business and Enterprise. Reading, search and the read tools for agents are on every plan, Free included.

  • Status, drift and the Board
  • Notes and agent replies
  • Artifacts written by agents
Compare plansWhat an agent can and cannot do

Put your next spec on the Board

Connect a repository, export a draft, and watch both axes move.

Start free