Docket
A delivery docket is the slip that travels with a shipment and proves what was delivered. Here, every spec gets one docket: a list of what counts as done, registered before the first code, filled with evidence, written by the team and read by you. What it is for: Long, autonomous implementation runs. You think with the model until the WHAT is agreed, write it down as a spec, then hand it over: one session runs for hours, spawns its own agents, verifies its own work and ends with one message. docket exists so that such a run can be trusted without watching it: the run checks its own work against commands written down before the first code, the docket shows what was done with evidence you can check, and hooks hold only the rules that have no exception (your project rules and the gate before delivered). It is not a chat assistant for quick edits. The modes before the run are short; the run itself is long.
More from members
All projectsSee what other members are building and what each project is looking for.
Comments · 0