Back to corpus
research noteexperiment writeup candidatescore 32
Governance Framework
**Anticipation Over Prediction** — Don't predict outcomes; detect when futures become constrained enough that action is warranted.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
--- name: governance-framework description: Documentation-driven project governance using the Master Implementation Prompt. Use when starting a new project, initializing governance scaffolding, or resuming work on governed projects. Triggers on project setup, phase zero, governance init, master plan, or implementation checklist requests. ---
**Anticipation Over Prediction** — Don't predict outcomes; detect when futures become constrained enough that action is warranted.
| Signals | Action | |---------|--------| | 1 signal | Observation only | | 2 signals | Provisional commitment | | 3+ signals | Actionable commitment | | Disagreeing signals | Pause, investigate |
| Type | Scope | Signals Required | |------|-------|------------------| | **Micro** | Naming, formatting | 1 | | **Meso** | Module design, API | 2 | | **Macro** | Architecture, schema | 3+ |
Or manually create `.governance/` with: 1. `PROJECT_CHARTER.md` — Purpose, non-goals, success criteria 2. `GLOSSARY.md` — Unambiguous term definitions 3. `INVARIANTS.md` — Assumptions + inviolable rules 4. `IMPLEMENTATION_GUIDE.md` — Decision rules, file structure 5. `CHECKLIST.md` — Living task tracker
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.