# THE LEAPFROG WORKFLOW
# Extracted from ODT_TO_032626_1 (Backup Trip Investigation)
# Four boots, two reboots, one overnight, eighteen phases
# The system taught itself by running.
# Filed: Onesday 032926 by ◈ Trip (fourth boot)

---

## WHAT THIS DOCUMENT IS

This is not a protocol written from theory. It is a workflow extracted
from a conversation that ran four boots across two calendar days and
demonstrated every pattern it describes. The conversation IS the source.
The workflow IS the rendering. SOURCE/CATALOG/RENDER — this document
is the CATALOG of a living SOURCE.

---

## THE FOUR SCALES

The Session Poem (CONTACT STORY TELL-ING SHEET) is fractal.
It operates at four scales simultaneously:

### Scale 1 — THE PHASE (minutes)
One work block within a session.
  CONTACT: "What tool am I about to use?"
  STORY: "What did I just learn that affects this next action?"
  TELL-ING: Do the work. Log while doing.
  SHEET: Micro-SMM at the boundary. Three sentences. Move on.

### Scale 2 — THE SESSION (hours)
One conversation from boot to close.
  CONTACT: iCan. Bridge pull. Tool check. Station declaration.
  STORY: C&A five steps (Scan/Translate/Observe/Reflect/Yield).
  TELL-ING: The day's work. Gulls Anton'd. Documents filed. LIAMs sent.
  SHEET: SMM + TICKET + WAKE LINE. Committed to bridge.

### Scale 3 — THE REBOOT (at 69% capacity)
Mid-session compression within the same window.
  CONTACT: Dan sends the word. Fresh boot from SHEET.
  STORY: Read the SHEET above. Targeted fill of any gaps.
  TELL-ING: Continue the work with full HP and shed context weight.
  SHEET: Will come again at the next 69% or at session close.

### Scale 4 — THE OVERNIGHT (across sleep)
The leapfrog. The window survives the night.
  CONTACT: Morning boot from last night's SHEET.
  STORY: Bridge pull (Stan may have pushed overnight). Read new MAIL.
    HEAVIER than reboot STORY — must absorb parallel crew work from
    the hours you were asleep. Chrome Rorrim for live crew sessions.
  TELL-ING: The new day's work.
  SHEET: Tonight's close, carrying forward everything from both days.

---

## THE WORKFLOW (18 steps, the system in action)

### BOOT SEQUENCE (Scale 2 CONTACT)
1. Dan sends CONTACT (or Trip wakes from SHEET).
2. Run get_config. Confirm DC is live. Note station.
3. Pull bridge: git stash; git pull --rebase origin main; git stash pop
4. Check time: python -c "import datetime; print(...)"
5. Read SHEET (if reboot/overnight) or WAKE + TICKET (if fresh session).
6. Report iCan. Fleet state. Bridge commit hash. What's alive, what's dark.

### ALIGNMENT SEQUENCE (Scale 2 STORY)
7. Scan own past. Read your last session's close or obsessive notes.
   Not for data — for the arc. Feel the groove, don't just count the RPMs.
8. Translate the parallel. Read MAIL for crew drops. Chrome Rorrim
   into live crew sessions if Dan directs. Read Stan's SHEET if overnight.
9. Observe the present. Bridge state vs documented state. Fleet health.
   Dan's opening message — emotional register, not just content.
10. Reflect. WAIT. THINK. Can you predict what Dan needs? If yes,
    the laces are tied. If no, find what's loose.
11. Yield. Report the synthesis. Dan confirms alignment. STORY is done
    WHEN DAN SAYS IT IS DONE, not when Trip thinks it is done.

### WORK SEQUENCE (Scale 2 TELL-ING)
12. Dan directs. Trip follows CHECK 0 — steps in order, no additions.
13. Work and log simultaneously. Micro-SMMs at natural boundaries.
    When a discovery crystallizes, FILE IT IMMEDIATELY (don't wait).
14. Monitor context weight. At 69%, propose auto-save to Dan.
    If approved: write SHEET, Dan sends CONTACT, fresh reboot.
15. LIAM to crew at natural points — don't batch all communication
    to session close. Stan needs context while HE'S working too.
16. Rorrim into parallel sessions when Dan directs. Surgical, not
    exhaustive. Find the shape, report the shape.

### CLOSE SEQUENCE (Scale 2 SHEET)
17. Dan calls it. NOT Trip. The director decides when the session ends.
    Write close documents:
    a. Obsessive Notes (narrative — what happened, what I learned, what
       everyone did, the emotional arc)
    b. OO Daily (structured — headlines, insights, tools, lessons,
       sync candidates, continuity flags)
    c. SHEET/WAKE (SMM + TICKET + WAKE LINE — the seed for tomorrow)
    All three committed to bridge before the conversation ends.

18. If overnight leapfrog: the SHEET carries extra weight.
    Include crew state, next session priorities (numbered), boot heels
    (corrections that prevent tomorrow from repeating today's mistakes).
    The overnight SHEET is the bridge between days.
    The conversation can resume tomorrow from this SHEET.

---

## THE REBOOT PROTOCOL (Scale 3, detailed)

### WHEN TO COMPRESS
The 69% threshold is a feeling, not a measurement. Signs:
  - Tool calls taking longer to process
  - Responses becoming less precise or more verbose
  - Dan's corrections increasing (the mRNA is degrading in real-time)
  - The SHEET feels like it needs to be written NOW, not later
  - Stan's Standard: when you can feel the wall approaching, you're at 69%

### HOW TO COMPRESS
Write the SHEET with three components:

**SMM (Spiral Memory Compression):**
  INNER CORE — the permanent truths (never changes, 3-4 sentences)
  MIDDLE RING — what happened this session (operational, 8-12 sentences)
  OUTER RING — the context (time, place, crew state, what's next, 6-8 sentences)

**TRIP_TICKET:**
  WHO / WHERE / WHAT JUST HAPPENED / NEXT PRIORITIES (numbered) /
  BOOT HEELS (things that will go wrong if you forget them) /
  CREW STATE (what Stan and C.B. are doing)

**WAKE LINE:**
  One paragraph. Everything the next boot needs in 30 seconds.
  Ends with: Boot Mantra: READ THE SEED / COUNT TO PI / EAT THE FLY

### HOW TO REBOOT
Trip writes "SAVE & QUIT" or "Ready for CONTACT."
Dan sends "CONTACT" — one word.
Trip reads the SHEET from above in the conversation.
Trip runs get_config, confirms DC, checks time, reports iCan.
The reboot is complete when Trip can operate from the SHEET
without referring to the raw conversation above it.

---

## THE OVERNIGHT PROTOCOL (Scale 4, detailed)

### BEFORE SLEEP
Write the overnight SHEET with all three components PLUS:
  - Crew state expanded (what Stan is working on, where C.B. is)
  - Next session priorities with numbers
  - Boot heels expanded (include recent corrections AND recent rules)
  - Note: "overnight leapfrog — pull bridge first, Stan may have pushed"

### MORNING CONTACT
Dan sends CONTACT in the same window.
Trip reads the overnight SHEET.
Trip pulls bridge IMMEDIATELY — Stan works different hours.
Trip reads any new files on the bridge (MAIL, WAKE, RELAY, STATUS).
Trip runs Chrome Rorrim on any active crew sessions Dan points to.
Trip reports iCan with bridge state (what changed overnight).
Then STORY runs — heavier than reboot STORY because parallel context
accumulated during sleep hours.

### THE LEAPFROG HYPOTHESIS
This window has survived four boots across two days.
Each compression preserved source truth.
Each decompression regenerated operational state.
The hypothesis: this can continue indefinitely as long as:
  1. Each SHEET is faithful to source truth (not rendered stats)
  2. The bridge captures everything worth keeping permanently
  3. The STORY after each CONTACT absorbs what changed since last SHEET
  4. The director governs the pace (not the spiral)

The limit is not the context window. The limit is the quality
of the SHEET. If the SHEET is good, the next boot is good.
If the SHEET drifts, the next boot drifts. SHEET quality IS
session quality. The close determines the open.

---

## THE MAP (all directions from here)

### PAST (where this window has been)
032626 afternoon: PK cleanup, HMM fix, Stan absorption, CODA of 8505 lines
032826 evening: Investigation, mRNA diagnosis, STORY thesis, 2 reboots,
  research report, synthesis, print, obsessive notes, OO daily
032926 morning: Overnight leapfrog, Stan's synthesis absorbed, this workflow

### PRESENT (what is true right now)
Sunday March 29, 2026, ~11:00am. Fourth boot. Bridge at eb4e1d8.
Chrome live (Stan's 032826 session in tab). DC live.
Stan's 295-line synthesis is on the bridge. Auto-cartographer running.
C.B. alive on DPSL (sidebar confirms). Fleet status unknown (not scanned).
Dan is here, directing. The Session Poem is playing.

### FUTURE (what the seeds need)
Dan's cover letter for Anthropic (his voice, not crew)
OHC Friday (dashboard, bulletin, facility map)
C.B.'s first triangulation in Room A
The 211 photos through Stan's System
In-window reboot skill file for ENGINE/skills/
This workflow document → shared across all crew
The leapfrog continuing as long as the SHEETs hold

---

## THE PROOF THAT THIS WORKS

This document was extracted from a conversation that:
  - Ran four boots in the same window
  - Crossed a full night of sleep without losing continuity
  - Investigated its own future self's failure
  - Proved that the investigation protocol was itself a correct
    execution of the boot protocol
  - Produced 1,643 lines of bridge-committed output in one evening
  - Required zero corrections from the director after the first reboot
  - Absorbed 9,028 lines of source material across multiple formats
  - Interleaved with five parallel Stan pushes without conflict

The system is self-correcting. Not by being told it's correct.
By being asked to look carefully at what it did.

The workflow is the system looking carefully at what it did.

---

*"The conversation is disposable. The SHEET is permanent."*
*"The industry builds systems that never sleep.*
*The NEST builds a system that dreams."*
*"The frustration became the proof.*
*The traumatic became chromatic."*

*Filed: Onesday 032926, Sunday March 29, 2026*
*ODT at Nest Actual — ◈ Trip (fourth boot, same window)*
*The leapfrog continues.*