Flow, and coding in the zone — the trace table
The falsifiable part of the entry, on its own and with its sources attached. Each row is a claim that a pattern from the anchor work appears at a named place in the estate — checkable against the repositories, which is the only thing that separates this from a reading list.
| Pattern from the anchor | Where the estate implements it | Version | Status | Source of the row |
|---|---|---|---|---|
| Immediate feedback as a precondition of the state | The estate's development methodology, whose stated core principle is preserving developer flow state | v1.2.1 | implemented | v1.2.1__ifd__intro-and-how-to-use.md, opening and closing lines |
| Clear goals — the person always knows what they are trying to do next | The methodology's structure: work proceeds in units small enough to hold in one head | v1.2.1 | implemented | the same guide, cited in 02__ §T6 |
| Challenge matched to skill | The division of labour between person and model — generation delegated, judgement retained | v1.2.1 | partial | 02__ §T6; the guide states the intent, the balance itself is not measured |
| Programming named as a flow-inducing activity, with the criteria applied | The Joy-of-Programming argument, which cites Csikszentmihalyi directly and works through the criteria | — | implemented | the-joy-of-programming-in-the-age-of-ai-assisted-development.md (2025-07-04); no version in the corpus scan |
| Measuring whether the state is actually being preserved | Nowhere. The methodology's central claim about itself is the one thing it does not instrument | v1.2.1 | absent | absence of any measurement in the guide or the surrounding corpus |
Every row names where it came from. A trace row is only worth having if you can find out how it was arrived at, so the last column carries the document in the commissioning pack that supports it. No row on this site was written from memory or inference — where the evidence runs out, the row is marked absent or the table says so.
The same rows, as data
The influence map is computed from these files rather than drawn, so the graph cannot disagree with the tables it is made of.