Spine plan · v2 panel-folded · for red-pen

The Held World

The spine that flips Eve from re-deriving her world to inhabiting it — six rungs, each gated by its own experiment. Reviewed by the three-legged panel you designed: your ambition adversary added the missing limb (the Carry), the frame adversary fixed the persistence instinct with the field’s own scars, and the failure red-team found the dark sibling machinery my draft had forgotten. All folded. Five calls are yours.

Panel-folded · awaiting your red-pen · experiments may start; no rung builds before it

What the panel did to v1 (your process, first run)

AMBITION (fable — your purchased seat): UNDER-REACHES. The ladder climbed to a perfect READ and stopped — the north star’s longest clause is the CARRY. Its flagship amendment is now rung R6: moves arrive executed to the edge of consent, and her own commitments become promise-slots watched by the same organ that catches false completes. Plus: silence becomes an event (the clock as the fourth source), she proposes new expectation shapes for your ratification, and gap-signatures cluster into aim-level cards — her first “sees aims you never named.”
FRAME (opus, external evidence, citations verified): RIGHT-FRAME-WITH-AMENDMENTS. The held-entity frame is convergent with the field’s frontier (temporal knowledge graphs over business + event data) — not an echo-chamber invention. But my persistence pick was the instinct the field spent fifteen years unlearning: update-a-record-in-place. v2 inverts it — the immutable event log is the truth; her held view is derived and routinely rebuildable, with a mechanical freshness invariant. Receipts prove provenance; currency proves freshness; only both close the stale-view false green.
FAILURE (opus, repo evidence): REVISE-FIRST, two blockers — both verified on disk. (1) “Event-driven” was false for two of three sources: email and Salesforce don’t push — only Stripe does. The rung is renamed the Reflex Arc: the poll stays the sensor; the reflex is what changes. (2) The sharpest catch of the night: a MORE rigorous expectation system already exists in her code — dark, orphaned, three days old — with typed promises (“a lapsed promise is DUE, never stale”) and an anti-circularity certificate. My v1 reinvented it without knowing. v2 adopts it as the substrate. The context loss you felt yesterday? The machinery caught mine, mechanically.

The story — what changes for you

Today Eve re-derives her world every fifteen minutes and holds nothing. The experiment showed what holding buys: CEO-ready cards and catches no fact states — the missing owner, the missing kickoff. The panel showed what the experiment couldn’t: a held world that only perceives is half an organism. So the spine runs perception AND carry: the entity becomes the unit of her mind; an immutable event log is the truth and her held view derives from it — rebuildable, never silently stale; typed expectations make absence and lapse visible; silence itself is an event; and every move arrives executed to the edge of consent, with her own commitments watched by the same organ that watches the world.

The ladder — experiments all start now; builds stay serial and gated

  1. R1 — Reach. Every conversation resolves to its person AND deal AND account AND thread — or becomes a named investigation target. Honestly re-scoped: five partial lanes to unify, dark doors to flip, one lane minting person-only links. Real experiment: a resolution-coverage probe on live cycles — the % that fully resolves, per link type. Blake’s thread must resolve live (today it does not).
  2. R2 — The entity view. Held state DERIVED from the event log: identity, people, trajectory with validity windows (supersession closes a window, never overwrites), leverage and decay inputs. Rebuild is routine, not recovery. Two invariants: the view has consumed its whole log (mechanical), and sampled lines still match the LIVE atoms (judged). Experiment: the ablation scaled to ten adversarially-drawn entities with distractors, plus a supersession case — when Blake replies, “reply owed” must close, not duplicate.
  3. R3 — Expectations (adopting the dark ledger). The 07-05 expectation-ledger becomes the substrate; kind-shapes become versioned DATA declaring each kind’s promises, cadences, roles — each slot naming whether absence is real evidence (missing owner) or maybe just un-ingested (missing lead-source; stays UNKNOWN, no gap). Gaps feed the investigation organ, which wakes HERE — and its experiment must exercise all three endings: one gap closed by a BUILT instrument, one honestly PRICED, and the forbidden fourth (silently judging around a hole) fails hard. R3b: she proposes new shapes from regularities she mines; your red-pen ratifies.
  4. R4 — The reflex arc. A detected change — polled email, polled stage, pushed payment, or a LAPSED CLOCK (“reply owed 4 days” is an event) — touches one entity, which re-judges NOW through a single-entity compose with an explicitly bounded neighbor-subgraph. The flip ledger rides the same router: arriving truth scores her past reads automatically. Mirror-Sisyphus dissolves. Experiment: replay Blake’s real email end-to-end — expected to surface the compose-severability gap, not rubber-stamp it.
  5. R5 — Rank as world-truth + your surface. Leverage × action-half-life computed on the entity, simply read by the board — who-lines, type-dots, cycle-through-everything, briefing-style unfold. Experiment runs THIS WEEK, no ledger needed: your full book ranked both ways; your five-minute reaction is the judge. R5b: gap-signature clustering → aim-level cards.
  6. R6 — The carry (the missing limb). Every move executed to the edge of consent: the outbound drafted in your voice, one tap from sent; a blast-radius line (who else is affected, who gets kept in the loop); her own commitments minted as promise-slots — “sent → reply owed → 3 days silent → re-poke” — so follow-through is owned by construction. Your #1 wound. Experiment: replay a real accepted move; kill if the draft needs rewriting or the slot never fires.

Your calls

1 · The Carry rung — in this arc?

The panel says it’s the point; it’s also the largest addition. My recommendation: yes — it’s the half that pays you.

2 · Entity center of gravity

The PRACTICE (people, deals, threads hang off it) — matching how you hold your book?

3 · Kind-shapes v1

Committed-customer · active-prospect · dormant-row · live-client — anything your gut adds (at-risk-client)?

4 · Event sources v1

Poll-reflex + Stripe + the clock. Gmail push / Salesforce CDC now or later? My recommendation: later — the clock buys more than push does.

5 · The interim

R2/R3 add work to the same 15-minute cycle that just recovered; until R4 lands, board honesty is carried by the Mirror as-is, explicitly. Accept, with the per-rung cycle-budget gate?

The fence — what this is NOT

No big-bang migration — every build dark, every flip walk-gated. No new judgment platforms. No Eve-local ontology where the shared engine or the 07-05 charter owns the ground. No rung builds before its experiment reports (the experiments themselves all start now, in parallel). The full shared world-engine with Fides stays fenced: the seam is code-level, the build is not in this arc.

Every rung: experiment → dark build → walk against the bar → flip. The ablation’s nine cards, the blind verdicts, and the three dossiers are standing fixtures. Nothing grades itself.