Back to corpus
research noteexperiment writeup candidatescore 24

Implementation Guide

| Decision Type | Signals Required | Example | |--------------|------------------|---------| | **Micro** (naming, formatting) | 1 signal | Variable names, comment style | | **Meso** (module API, struct fields) | 2 signals | Claim struct design, method signatures | | **Macro** (claim types, sigil assignments) | 3+ signals | Adding claim type 11, changing sigil |

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

| Decision Type | Signals Required | Example | |--------------|------------------|---------| | **Micro** (naming, formatting) | 1 signal | Variable names, comment style | | **Meso** (module API, struct fields) | 2 signals | Claim struct design, method signatures | | **Macro** (claim types, sigil assignments) | 3+ signals | Adding claim type 11, changing sigil | 1. **Charter wins**: If conflicting with implementation detail, charter governs 2. **Invariants win**: If violating invariant, implementation must change 3. **Glossary wins**: If term is ambiguous, glossary definition governs 4. **IR wins**: If N'Ko surface conflicts with IR structure, adjust surface A task is complete when: - [ ] Code compiles without warnings - [ ] Tests pass (`cargo test`) - [ ] Documentation matches implementation - [ ] Checklist item is marked complete with artifact reference A task is blocked when: - Missing dependency (another task must complete first) - Ambiguous requirement (needs clarification) - External service unavailable (Graph Kernel, DELL) - Resource constraint (memory, compute) The smallest unit of work: - Has a single, verifiable output (one file, one struct, one test) - Can be validated independently - Does not require context from unfinished sibling tasks - Can be rolled back without affecting other units

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.