orchestrate
orchestrate
Work through a Ticket Store's ready Tickets, or pursue an explicitly assigned outcome through
useful investigation and delivery. A queue invocation stays a finite queue assignment; standing
delegation and --autonomous do not turn it into project operation. A Ticket is a self-sufficient
work packet in the project's store; an effort is a named group of Tickets with one
destination and one front item (the effort's front file: the tracking item's body, or the
effort's README in a file store). Each run is one run-ticket attempt on one Ticket, in its
own session. This skill plans, launches, lands, and keeps the person informed, in check-ins:
at each one it re-reads the store, gives one finished run its landing turn (its merge onto
the target branch), gathers debt, and fills free run slots. Its durable state stays in the store: Tickets, the effort item, git, and designated
evidence sources, so a new orchestrator, or a second one, rebuilds the same picture. A
signpost is a Revisit when line — a condition in the world and where it is read — on a
deferred Ticket, or after a title in the North Star's list of strategy choices in force.