Back to corpus
research noteexperiment writeup candidatescore 18

Implementation Checklist

1. Phase 0: Project Control Layer 1.1 Step: Perform Artifact Intake Pass 1.1.1 Substep: Document Intake Findings [ip] Artifact: INTAKE_REPORT.md [ip].1 Description: Create intake report with discovery, classification, gap analysis, and confidence assessment. [ip].2 Owner: Agent [ip].3 Input dependencies: README.md, existing scripts. [ip].4 Output artifacts: INTAKE_REPORT.md [ip].5 Validation condition: File exists and includes sections 1-4 and change history. [ip].6 Status: Complete [ip].7 Confidence: Medium 1.2 St

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

1. Phase 0: Project Control Layer 1.1 Step: Perform Artifact Intake Pass 1.1.1 Substep: Document Intake Findings [ip] Artifact: INTAKE_REPORT.md [ip].1 Description: Create intake report with discovery, classification, gap analysis, and confidence assessment. [ip].2 Owner: Agent [ip].3 Input dependencies: README.md, existing scripts. [ip].4 Output artifacts: INTAKE_REPORT.md [ip].5 Validation condition: File exists and includes sections 1-4 and change history. [ip].6 Status: Complete [ip].7 Confidence: Medium 1.2 Step: Create Canonical Documentation Set 1.2.1 Substep: Create Project Charter [ip] Artifact: PROJECT_CHARTER.md [ip].1 Description: Create Project Charter with purpose, non-goals, success criteria, direction constraints, commitment level, traceability, and change history. [ip].2 Owner: Agent [ip].3 Input dependencies: README.md [ip].4 Output artifacts: PROJECT_CHARTER.md [ip].5 Validation condition: File exists with required sections and traceability notes. [ip].6 Status: Complete [ip].7 Confidence: Medium 1.2.2 Substep: Create System Glossary [ip] Artifact: SYSTEM_GLOSSARY.md [ip].1 Description: Define core terms with what it is, what it is not, layer, and stability. [ip].2 Owner: Agent [ip].3 Input dependencies: README.md, existing scripts. [ip].4 Output artifacts: SYSTEM_GLOSSARY.md [ip].5 Validation condition: File exists with required definition fields and change history. [ip].6 Status: Complete [ip].7 Confidence: Medium 1.2.3 Substep: Create Assumptions and Invariants Ledger [ip] Artifact: ASSUMPTIONS_INVARIANTS.md [ip].1 Description: Document assumptions and invariants with break conditions and detection. [ip].2 Owner: Agent [ip].3 Input dependencies: README.md [ip].4 Output artifacts: ASSUMPTIONS_INVARIANTS.md [ip].5 Validation condition: File exists with assumptions, invariants, and change history. [ip].6 Status: Complete [ip].7 Confidence: Medium 1.3 Step: Create Implementation Guide 1.3.1 Substep: Define Implementation and Validation Rules [ip] Artifact: IMPLEMENTATION_GUIDE.md [ip].1 Description: Define decision, decomposition, validation, and traceability rules with change history. [ip].2 Owner: Agent [ip].3 Input dependencies: Constitution instructions [ip].4 Output artifacts: IMPLEMENTATION_GUIDE.md [ip].5 Validation condition: File exists with required rule sections. [ip].6 Status: Complete [ip].7 Confidence: Medium 1.4 Step: Create Living Implementation Checklist 1.4.1 Substep: Initialize Checklist [ip] Artifact: IMPLEMENTATION_CHECKLIST.md [ip].1 Description: Create checklist with Phase -> Step -> Substep -> Artifact hierarchy and required fields. [ip].2 Owner: Agent [ip].3 Input dependencies: Phase Zero requirements [ip].4 Output artifacts: IMPLEMENTATION_CHECKLIST.md [ip].5 Validation condition: File exists with required

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.