The Method
The concepts, stated once and defined by what a machine can check. The papers (base, derivatives, Compendium) carry the arguments; these pages carry the working definitions.
| Page | What it answers |
|---|---|
| The rubric | Seven properties that make a project derivable, and the failure named for each |
| Spec completeness | When is a specification complete enough for a stateless reader |
| Quality gates | The non-LLM checks that make the discipline enforceable |
| The evidence | What the experiments established, with the bounds on each claim |
| The course | GS Core: theory intercut with five hands-on labs |
| The Andon Method | A proposed method built on the same thesis: the machine builds, a gate stops the line, the human judges. Team process not yet defined |
| Twelve working principles | How a practitioner works under the method, in twelve lines; two carry evidence caveats |
| Lifecycle and debt | Three definitions: no new debt per change, criteria coverage, and what the method covers across the lifecycle (with what is not yet covered) |
Looking for the practice (how to do it on a real project)? See the workflow recipes.
Using this in a company? Governance, assurance and due diligence built on this method live at pragmaworks.dev.