The working loop
Seven steps forward, three paths back, shown on one small feature.
The method
The aigile framework in plain language, one page per element, with worked examples.
A short summary of the method before the details: humans decide what to build and why. Work moves in small slices through a short loop. Everything the team learns flows back into a small set of living documents that agents read at the start of every session. Humans check the running software themselves at defined points. How much the agents do on their own is a setting that gets adjusted on evidence over time.
Each page in this section covers one element and shows it on a running example: a small team building order software for business customers, and one feature of it, a month-end reconciliation view. The same example runs through the papers and the practitioner guide, so the material connects. The pages build on each other, so reading them in order works best the first time.
Slicing the work
How features become slices, why the shape matters, and a catalog of ways to split.
The artifact layers
Three kinds of documents with three different rules, with an example of each.
The constitution
A short set of binding rules, slow to change on purpose, with a worked amendment.
Deviation and drift
What to do when specs and code disagree, during the work and after it, with examples.
The validation architecture
Why judging the goal stays with humans, and how their attention is placed, with a worked demo.
The authority matrix
One setting per checking layer, moved on evidence, with a worked graduation.