ticket-up

ticket-up

ticket-up is the single Ticket-authoring boundary. It shapes prose, applies the convention, deduplicates, and renders the result through the project's configured venue.

Read references/TICKET_CONVENTION.md before emitting. It defines the unit, kinds, anatomy, lifecycle, and priority every venue must preserve.

Resolve the input and Ticket units

Accept any of these inputs:

• a finished Manifest;
• a direct work request that should enter the store;
• one or more questions that need separate management;
• findings discovered while running a source Ticket, with that source identified.

Without explicit input, use a recent Manifest only when the conversation already establishes it as the intended source; otherwise ask what should become a Ticket.

One Ticket represents one independently schedulable lifecycle. Bundle work that shares one outcome and would be assigned, prioritized, and closed together. Split only where separate ownership, priority, blocking, or closure has real value. Do not turn every Deliverable, question, or minor finding into a Ticket.

Whether to split is one question; where the cut falls is another, and the second is answered the same way whatever the input was. Every Shaped Ticket a split produces is a slice someone can exercise end-to-end on its own — run, read, or otherwise judged in the situation it is for, not merely inspected as present. A Ticket cut along an implementation layer ("the schema", "the endpoints", "the screen") has nothing to run, so its definition of done falls back to checking that something exists and whoever picks it up cannot tell whether the work helped. Re-cut work that arrives framed in layers instead of passing the layers through; renaming a layer does not re-cut it. A Question Ticket is outside this — an investigation has no slice to run, and its done is the answer recorded.

Manifest input defaults to one Shaped Ticket for the whole Manifest. Its Deliverables remain an internal execution and verification structure. Split into one Ticket per Deliverable only when the caller explicitly asks for delegation or parallel pickup. Existing Deliverable boundaries are the smallest allowed split: if one is too large, or is a layer rather than something exercisable end to end, amend the Manifest rather than shipping a unit that cannot be judged end to end.