extract-to-tickets
Extract to Tickets
Turn actionable extraction claims into approved local tickets; this workflow triages and publishes work but does not reinterpret transcripts, promote records, or implement changes.
Inputs
A. Extraction sources
A required selection of one or more repository-relative docs/transcripts/<day>/<order>-<slug>/extract.md paths or transcript directories. A directory denotes its direct extract.md; duplicate paths denote the same source.
B. Effort slug
An optional lowercase kebab-case slug naming .scratch/<effort-slug>/issues/. It is required only for publication and must identify an unused destination.
C. Publication approval
The user's explicit approval of the exact proposed scope, grouping, granularity, blockers, and elected change requests. It is absent during triage and required before any directory or ticket is created.