Protocols in Force
Not a document — a living registry. It records every protocol the methodology currently runs, and it has grown by accretion since its first entry, across eight instars of the system. It carries no version number; it grows by the day. Here are its real epochs, and where it stands now.
Some of what's in force here began as a single prompt to Claude. Sweet Prompts keeps the origin prompts.
Every protocol here serves the seven drives above them. The Creed is published in full — the drives and the Seven Questions that test them.
Protocols in Force
The registry, as a funnel — not a dump
Protocols — a funnel, not a dump
Tier A — the whole registry
The methodology runs on about 154 protocols in force. Everything below is a subset of that registry — a taste of a much larger set.
Tier B — some of the names
A sample of protocol names, each with a one-line sense of it. Just the names here — how each one works is held back at this tier.
- The Chronicle — A git-log/work-log report over a span of sessions
- Projection Lint — The Ink-Law/Tromp-Test discipline checker
- The Field Model — The room-scale lens for good collective work
- The Source Ladder — CX's five-rung trust spine: R0 byte-truth · R1 derived · R2 the Dig · R3 genome · R4 external, plus the KP rung
- The Pack — Work-line context-pack memoization over CX
- The Consult — A gated, read-only domain-literacy check
- The Conn — The grammar of how steering moves between the operator and the board across a line of work
- Self-Review Protocol — Mandatory four-file review cycle with Convergence Gate
- Process Audit Protocol — Mandatory sampling at EOD, rotating question bank, improvement register
- Walk Home Protocol — Closing ritual for exploratory sessions
- Prompt Amplification Protocol — Decompressing operator prompts into full production instructions
- Let's Go — Single-trigger session startup
- The Lay — The five-facet description of a Trust Object
- RCR (Round · Collision · Resolution) — Structured board deliberation. v4.1: Scope Fence amendment (RCR12)
- Three Passes (3P) — Three-round iteration cycle (Build → Repair → Reframe)
- Low Gear — Reduced-speed production mode for precision work. Maintenance-class reframe pending
- The Sounding — Operator-invoked byte-truth position readout on one Work Line
- The Chunk — Decomposes parallelizable work into balanced Work Order bundles
- Sitrep — Mid-session state snapshots for cross-tab coordination
- The Kiln — KP Revision Protocol
- The Sweep — Systematic filing verification. v1.3: Reverse Pass amendment
- The Last Call — Autonomous session lifecycle management
- Super RCR — Three-round deliberation (perception → dialogue → integration)
- The Bench — Experiment Design Protocol
- The Dock — File-level workflow control for multi-file deliverables
- The Shuttle — Structured command language with Express Pidgin v3
- The Dig — Corpus extraction and journal composition
- The DDE (Design Derivative Engine) — General-case derivative engine. Three-tier (Glance/Quick Draw/Full Forge). Six Gates. Channel-coupling analysis. The Braid
- Acid Bath — Cross-domain extraction and reform. v1-A1: Block Principle convergence
- The Jury — Human judge validation protocol. Three verdict tiers
- The Run — Experiment execution protocol
- The Shrug — Operator-delegated method selection
- The Survey — Cascade bridge protocol
- The Cascade — Protocol composition. v1.1-A1: Block Principle convergence
- The Slice — Image examination at resolutions above native downsampling
- Resurface — Structured resurfacing of buried work items
- The Resonance — Audio-to-waveform detection and registration pipeline
- The Dare — Adversarial challenge protocol
- The Fishbowl — Demonstration protocol. Demo stack
- The Mirror — Board reflection protocol. Demo stack
- Memory System Protocol — Five-layer Cambium architecture. **Records** as atomic unit (renamed from "memory mesh," A3 29.1254)
- The Burn — Intentional context utilization (invoked) + the Default Close Discipline (default close trigger: budget-triggered not task-triggered, §13, S02.0820). Spore branch origin
- The Keel — Stigmergic improvement protocol. Spore branch origin
- Character Development Protocol — Structured character creation and evolution. Spore branch origin
- The Portage Protocol — Lateral synchronization between concurrent project instances. File manifest (add/replace/delete), sync prompt, operator checklist. Not a handoff (forward in time) or Settle (internal reconciliation)
- The Rigging — Cross-Tool Integration Audit Protocol
- The Core Sample — Grain extraction pipeline
- The Customs House — The R4 external-context security gate
Tier C — a few, in full
The last step of the funnel: a small, chosen set of protocols shown in their entirety. Those selections are being finalized — the full texts land here next.