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.