Back to corpus
technical noteexperiment writeup candidatescore 36

Continuation Protocol - Swift iOS Project

**Document ID:** GOV-CONT-001 **Version:** 2.0.0 **Created:** 2026-01-04 **Updated:** 2026-01-13 **Status:** Active **Platform:** iOS (Swift/SwiftUI) **Owner:** Lead Developer

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Document ID:** GOV-CONT-001 **Version:** 2.0.0 **Created:** 2026-01-04 **Updated:** 2026-01-13 **Status:** Active **Platform:** iOS (Swift/SwiftUI) **Owner:** Lead Developer **Related Documents:** - [Master-Checklist](../03-Checklists/Master-Checklist.md) - Task Tracking - [Entry-Point-Decision](../00-Overview/Entry-Point-Decision.md) - Project Context - Master Implementation Prompt (`/CLAUDE.md`) - Governance Framework 1. [Overview](#1-overview) 2. [Continuation Anchor System](#2-continuation-anchor-system) 3. [Session Recovery Protocol](#3-session-recovery-protocol) 4. [Source of Truth Registry](#4-source-of-truth-registry) 5. [Checkpoint System](#5-checkpoint-system) 6. [Handoff Procedures](#6-handoff-procedures) 7. [Context Recovery](#7-context-recovery) 8. [Progress Tracking](#8-progress-tracking) This document defines the continuation protocol for the Milk Men iOS project, ensuring work can resume seamlessly across: - Session boundaries (token limits, natural pauses) - Developer handoffs (team member changes) - Time gaps (days or weeks between work sessions) - Context loss (memory limitations, summarization) **The Project Must Be Self-Documenting:** - Any developer (human or AI) can pick up where work left off - No reliance on memory or conversation history - All context is written down and accessible - Progress is always traceable to a specific checkpoint

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.