Back to corpus
technical noteexperiment writeup candidatescore 30

cc-anticipation: Continuation Protocol

This document defines the protocol for continuing work on cc-anticipation across sessions, ensuring consistent context restoration and preventing drift from canonical specifications.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Document Version**: 0.1.0 **Created**: 2025-12-26 **Parent**: [PROJECT_CHARTER.md](./PROJECT_CHARTER.md) This document defines the protocol for continuing work on cc-anticipation across sessions, ensuring consistent context restoration and preventing drift from canonical specifications. ### 1.1 Context Documents (Always Read) 1. **[PROJECT_CHARTER.md](./PROJECT_CHARTER.md)** - Mission, scope, interfaces 2. **[CHECKLIST.md](./CHECKLIST.md)** - Current status, next actions 3. **[INVARIANTS.md](./INVARIANTS.md)** - Non-negotiable properties ### 1.2 Reference Documents (Read as Needed) 4. **[GLOSSARY.md](./GLOSSARY.md)** - Terminology definitions 5. **[IMPLEMENTATION_GUIDE.md](./IMPLEMENTATION_GUIDE.md)** - Code structure, patterns 6. **[Anchor.md](../../../../docs/Anchor.md)** - Canonical specification ### 1.3 Integration Context (Read for Integration Work) 7. **[cc-core-rs/src/lib.rs](../../cc-core-rs/src/lib.rs)** - Available primitives 8. **[rag_plusplus types](../../rag_plusplus/)** - HNSW, OutcomeStats

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.