Documentation

The spec drawer

The spec drawer is where you read and act on a single spec, the contract between intent and the tickets that implement it. Open it from Work or Complete (a spec row, or a ticket that belongs to that spec).

Reading sections

The compact navigation row opens Overview, Acceptance, Tickets, and Evidence. Overview shows the source, a bounded Completion screenshots strip when any exist, and the full spec document.

Overview places the screenshot strip after status, source, and PR metadata, and before the Details document. Two thumbnails on desktop, one on a narrow drawer, the unique count, and one View all screenshots action that opens the full-size viewer. Tiles keep the image's own aspect with object-fit: contain. There is no shared 16/10 cell. Capture at a viewport of at least 1440×900 with deviceScaleFactor: 2. Hub refuses smaller or soft/mushy screenshots (SCREENSHOT_TOO_SMALL / SCREENSHOT_TOO_SOFT). Do not re-shot a Complete tile. The spec body is not replaced or truncated. No screenshots means the strip is omitted, not an empty placeholder.
Acceptance counts all criteria. The number is not a completion score or a human verdict; read the checklist for each criterion's state.
Tickets counts current members, including open and done. Eight rows show initially; search, status filters and Show all keep every member reachable. Choose Archived explicitly to inspect archived members.
Edit order reveals Up/Down for Recommended order (hint). The hint never blocks Start; hard dependencies still apply.
Evidence shows totals and provenance plus every eligible structured screenshot (including supported older agent-provided proposals) as openable pictures in a minmax(280px, 1fr) gallery. There is no extra Accept control on those pictures. Passing runs and long notes start folded; failing runs stay open. Expand to read original test details and links. Human Accept is additional confidence, not a deploy gate.

Acting on a spec

drafting → Approve or Archive…
approved → Reopen, Complete, or Archive…
archived → Restore

Claim/Unclaim, Assignee and Copy Prompt share the visible toolbar with the main lifecycle action. Actions holds Reopen, Archive, governed follow-up and Record decision. Existing availability, lifecycle rules and confirmations still apply. Narrow drawers provide a labelled overflow arrow while keeping Actions reachable.

A drafting spec blocks starting its tickets. Approve it here first.

Out of date

When open tickets no longer match this spec, a card under Status (above Related) shows one control. The toolbar does not repeat it.

A saved plan shows Out of date counts, keep as-is / update / specs to create, Prepared by when an agent saved it, and Review changes. It opens that plan. It does not build a new one.
Open tickets that are out of date with no saved plan show Review changes. It opens this spec's review.
A finished, replaced, or withdrawn plan is not live. If nothing is out of date, the card is omitted.

Apply stays on the Review changes drawer. This drawer does not apply the plan.

New requirements

When someone adds a requirement to a switched-on spec and no ticket covers it yet, Review changes shows a card for it with a drafted ticket title and text. Each card has three choices:

Create ticket makes a ticket from the draft and links it to that requirement. The new ticket gets the spec's assignee.
Not planned keeps the requirement on the spec and records that no ticket is planned for it.
Later keeps the requirement on the spec and records that a ticket will come later.

Until someone decides, Acceptance shows No ticket yet next to that requirement.

Not planned and Later each need a reason, up to 2,000 characters. Apply stays off until every one of them has a reason. The reason then shows under that requirement in Acceptance; a long reason folds to two lines, with More and Less to open and close it. A requirement marked Not planned or Later is still not covered by a ticket; it stays visible so no one loses track of it.

When an Apply includes any of these new-requirement choices, everything in that Apply saves together. If any part cannot save, for example because the spec changed in another tab, nothing is saved: Review changes shows that the review changed, and you choose Reload, check your choices, and apply again. Choosing Create ticket twice never makes a second ticket. If a ticket already covers the requirement, Hub uses that ticket instead and says "This ticket was already created." (or "These tickets were already created.").

Partly applied

When Review changes updates several tickets and one does not save, the spec shows Partly applied under Acceptance. It names each ticket that did not update, by title, with a plain reason. Retry runs only those tickets again; Review changes reopens the review. Only a person can Retry. A ticket that already updated is never written twice, and if nothing is left, Retry says so. If Hub stopped mid-save, it finishes the stopped tickets on its next start.