Skip to main content

Agentic Workflow

The agentic workflow is how a change at ttoss goes from a signal to an effect observed in production. Three ideas shape it: 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. The next tick reads the state as it is now and does the same. 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 a run that chases the people the graph waits on and one that audits what the agents spend.

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.

One Engine, Extended per Project​

The engine is the same for every project: the states, the stages and their owners, the transitions and the rules of the Delivery Process. A project extends it at defined extension points, its parameters. An extension answers a question the engine asks and never changes the engine. A point left empty takes its default, so a project starts from the engine as it is and extends only where it differs, and a rule that turns out true of every project moves into the engine.

Built on GTF and Flow​

GTF holds what is true of any work, this workflow what is true of software delivery, the ttoss skills how an agent carries it out, and a project's parameters what is true of one product; precedence says what wins when two disagree. The skills read these pages from this repository's default branch, so a change here reaches every agent at its next run. Principles maps every rule of the workflow to the product development and agentic development principles behind 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 and the chase they fire, and token-audit the audit.