Back to corpus
research noteexperiment writeup candidatescore 40
Living Implementation Checklist
- [x] **0.1** Create Project Charter - Owner: Agent - Input: Improvement document, existing architecture - Output: `docs/00-PROJECT_CHARTER.md` - Validation: Charter defines purpose, non-goals, success criteria - Status: ✅ Complete - Confidence: High
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Version**: 1.2.0 **Last Updated**: 2026-01-02 **Status**: Complete (All 8 Phases)
- [x] **0.1** Create Project Charter - Owner: Agent - Input: Improvement document, existing architecture - Output: `docs/00-PROJECT_CHARTER.md` - Validation: Charter defines purpose, non-goals, success criteria - Status: ✅ Complete - Confidence: High
- [x] **0.2** Create System Glossary - Owner: Agent - Input: Existing code, architecture docs - Output: `docs/01-GLOSSARY.md` - Validation: All security terms defined, overloaded terms flagged - Status: ✅ Complete - Confidence: High
- [x] **0.3** Create Invariants Ledger - Owner: Agent - Input: Improvement document, existing tests - Output: `docs/02-INVARIANTS_LEDGER.md` - Validation: All 8 invariants documented with canaries - Status: ✅ Complete - Confidence: High
- [x] **0.4** Create Implementation Guide - Owner: Agent - Input: CLAUDE.md, improvement document - Output: `docs/03-IMPLEMENTATION_GUIDE.md` - Validation: Decision rules, decomposition rules, validation rules defined - Status: ✅ Complete - Confidence: High
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.