Skip to content

Building A Ticket ​

The builder's page: how a ticket with its go is built, and when it counts as done. The path around it is in Work Workflow.

Why ​

The director can trust a ticket that is called done.

Building ​

  • Work comes from the plan only, and the plan holds only ready stories with a go and an agent. Every commit traces to a planned story's ticket and starts with its id (Commits). Something found mid-work that is not on the plan becomes a ticket first (Note Issues), apart from a fix that Don't Introduce Tech Debt makes in the same pass.
  • One ticket in flight per agent: the next in its story's order (Work Tracking).
  • Every word and number a change shows, configuration data included, is weighed along the ticket's entry points by what it means to the user at that moment (Walk The User's Journey). A text the user reads speaks the product's own words, never the workspace's internal terms.
  • A feature runs the feature workflow inside its ticket (Feature Workflow).
  • Per ticket, only what the change affects runs: the cases of every feature that uses what it touched, and the reels and captures that cross it. The whole touched suites run at the end of the story, and the full suites at the version's close.
  • Easy-to-change choices are made and written under Veto.
  • Only costly-to-undo choices wait, as a question in their ticket.

A Ticket Lands Right ​

  • A ticket leaves the codebase no worse: no new risk, debt or bad code, and no lower quality or value.
  • Whatever its own work needs to be right is done in it, taking the time it takes: a design risk mitigated by design belongs in the ticket, and so does a small, relevant fix.
  • The right solution is solved now, never pushed out as a follow-up. A follow-up ticket exists only when the work outgrows one ticket, which is a split, named under Veto when the build finds it.

Definition Of Done ​

A ticket is done only when every one of these holds. Until then it stays on the plan.

  • Every acceptance criterion is met and verified, and the spec covers each one.
  • The cases that touch the change, hygiene, types and the development build are green, each by its own exit code (Gate Commits On Exit Codes).
  • A bug's test reproduces the director's steps with real input and was seen failing before the fix (A Bug's Test Reproduces With Real Input).
  • A new hygiene check lands with its implementation, and its builder's report shows the run that failed before the change.
  • The Done part holds proof the director can open and verify (The Done Part, Review Every Capture Before Reporting).
  • Visual work meets its Visual Quality points and the project's visual checklist.
  • The docs are synced: the feature doc, the spec, and every reference to a changed name (Sync The Docs After Every Change).
  • No new tech debt: what the change made unused or duplicated is cleaned in the same commit.
  • The agent's own decisions stand under Veto (Flag Every Addition Of Your Own).
  • The change is squashed into one commit on the story's branch, its landing commit, which reaches main with the story's merge (Verify Staging Before Committing).
  • Captures and archive moves are never batched for later. The version's changelog lists the ticket by itself (Changelog Per Version).
  • A debt ticket is archived in its landing commit (Work Tracking).