Agentic Workflow
The agentic workflow is how a change at ttoss goes from a signal to an effect observed in production. It is a state machine over a task graph, one engine runs it for every project while each project extends it, and it is built on Get Things Flowing (GTF) and Flow.
A State Machine
A task's state lives in Flow: its status, what holds it, and the changes it references. A tick reads that state, applies the transitions it calls for, writes the new state back, and stops. Nothing passes from one tick to the next except the graph, so a tick that dies loses nothing, any agent can run the next one, and whatever schedules the ticks sets the pace. That schedule is the project's routines: the tick, and beside it the Chase, the Health and the Audit.
The Delivery Process defines every state, the seven stages that move a task between them with one owner each, and the transitions a tick applies, what ages fastest first.
Two Queues
The work that waits in this machine waits on a person, in one of two queues: the decision queue, the choices work waits on before it can start, and the release queue, the work agents implemented that waits to reach the customer. While the release queue is full the tick starts no new work a person would have to move, and the Chase asks people only for what drains them. Where work waits says what each holds, and Principles why.
One Engine, Extended per Project
The Delivery Process is the same for every project. A project answers its extension points, its parameters, and never changes the engine; a point left empty takes its default. Why is One engine, extended for any project.
Built on GTF and Flow
GTF holds what is true of any work and this workflow what is true of software delivery; the ttoss skills carry it out, and precedence says what wins when two levels disagree. The skills read these pages from this repository's default branch, so a change here reaches every agent at its next run. Principles holds the workflow's own principles, each with the pillars it rests on and the rules that rest on it.
Adopting It
A repository adopts the workflow with the flow-setup skill: it installs the skills, defines the parameters with you from what the repository already says, proposes the Flow project and its standing decision, opens a pull request for your review and, once you integrate it, creates the project's routines. The flow skill runs the tick, the Chase and the Health; token-audit runs the Audit.