Process states
The model is a loop, not a waterfall.
Projects can occupy multiple states at once, skip states that do not match their pressure, or revisit a state when new evidence appears.
Evidence-backed process model
Build fast where the idea is uncertain. Become rigorous where the system must tell the truth.
Process states
Projects can occupy multiple states at once, skip states that do not match their pressure, or revisit a state when new evidence appears.
Timeline and corpus
The same operating pattern appears in public apps, local tools, games, publication systems, and meta-process products. The timing changes with project pressure.
Pattern strength
Frequency is not treated as a universal checklist. It shows which process moves repeat and where caveats matter.
Pressure to artifact
The practical question is not which phase comes next. It is which pressure is real now, and what smallest artifact can carry it.
Evidence map
The evidence matrix shows where each state is strongly supported, partial, absent, or intentionally not applicable.
Research trail
Summary files give the fast read. Per-project dossiers, timelines, and evidence indexes provide the rich specifics.