2.0 KiB
2.0 KiB
Built-in Ticket intake and orchestration routing umbrella is complete.
This umbrella was split into four implementation-sized child tickets, all of which are now closed:
-
ticket-local-files-backend- Added the low-level
ticketcrate, typed Ticket domain/backend, andLocalTicketBackendover currentwork-items/files.
- Added the low-level
-
ticket-built-in-feature-tools- Added built-in Ticket tools through typed backend authority and the Pod feature contribution path.
- Kept Ticket tool behavior in
crates/ticketand Pod as a thin feature adapter.
-
ticket-intake-workflow- Added
.yoi/workflow/ticket-intake-workflow.mdfor clarifying user requests and materializing agreed Tickets after user approval.
- Added
-
ticket-orchestrator-routing- Added
.yoi/workflow/ticket-orchestrator-routing.mdfor classifying Tickets into requirements sync, preflight, spike, implementation, review, blocked/action-required, close-ready, defer/pending, or no-op paths.
- Added
Terminology decision:
Ticketis the durable orchestration record concept.Taskremains session-local progress tracking.Assignmentis concrete Pod delegation.IntentPacketis the implementation/review contract derived from a Ticket.work-items/remains the current LocalTicketBackend storage path for now.
Scope preserved:
- The storage directory was not renamed.
tickets.shremains compatible and in use.- Ticket authority is separate from delegated filesystem write scope.
- Intake does not schedule implementation.
- Orchestrator routing does not introduce an unattended scheduler/lease/queue system.
- TUI spawned-Pod panel work was deprioritized and is not part of this path.
Validation:
- Child tickets were independently reviewed and validated.
- Final child workflow validation passed
git diff --checkand./tickets.sh doctor. ./tickets.sh doctorpasses for the umbrella close.
Historical note:
Older thread entries and artifacts may contain superseded WorkItem or old system-name wording as historical context. The current terminology and implementation use Ticket.