Back to corpus
research noteexperiment writeup candidatescore 18

Implementation Guide

| Decision Type | Examples | Required Signals | Allowed to Proceed? | |---------------|----------|------------------|---------------------| | **Micro** | Naming, formatting, local refactors | 1 signal | ✅ Yes | | **Meso** | Module design, API shape, integration | 2 signals | ⚠️ After convergence | | **Macro** | Architecture, schema, cross-system | 3+ signals | ❌ Only after full convergence |

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Version**: 1.0.0 **Last Updated**: 2026-01-02 **Authority**: Master Implementation Constitution (CLAUDE.md) | Decision Type | Examples | Required Signals | Allowed to Proceed? | |---------------|----------|------------------|---------------------| | **Micro** | Naming, formatting, local refactors | 1 signal | ✅ Yes | | **Meso** | Module design, API shape, integration | 2 signals | ⚠️ After convergence | | **Macro** | Architecture, schema, cross-system | 3+ signals | ❌ Only after full convergence | **Signals** include: - Explicit requirement in improvement document - Existing code pattern (precedent) - Test failure or production incident - User clarification **Example**: - "Add `AdmissibleEvidenceBundle` type" — Macro decision - Signal 1: Improvement doc explicitly recommends it - Signal 2: Current code lacks type-level safety (audit finding) - Signal 3: Promotion pipeline could accept unverified evidence (security gap) - **Decision**: Proceed with implementation ✅ When signals disagree: 1. **Document the conflict** in this guide 2. **Ask user for clarification** via `AskUserQuestion` 3. **Do not proceed** on assumptions 4. **If micro-level**: Choose the most conservative option (easiest to reverse)

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.