↻ refresh

Dashboard2026-06-08 · Claude Minsky · v1.0

Pressing what's hot this week

THIS WEEK

Ship TireSurf v1

to a named Thai driver by 2026-06-11

days remain

06-04 plan locked → 06-11 hard date · 60% of window elapsed

⚠ BLOCKED · Name the TireSurf v1 user

→ Your move: ★

▶ ULTIMATE

Web app deployed to Thai drivers

100+ users/month within 90 days of v1. Pat's "decision equalizer" pattern proven at consumer scale. First evidence the AI-amplified individual ships consumer products. Smart Consumer line pattern locks ~180 days out.

TireSurf Tier 0 · urgent

Now

v1 build queued · awaiting named user · Claude Alex (Opus) ready to execute CRAFT → DoD → build → ship as soon as user lands.

⚠ Friction: user not named — 3 days remain.

▶ Ultimate

Web App · 100 Thai drivers/mo

Real driver opens link → sees tire fitment + 3 shops + confidence score → walks away knowing which tire and which shop. v1 with 1 user → v2 with 10 → category leader for tire decisions in Thailand.

HNF LI frozen · deliverable

Now

Frozen at iteration. Delivery to a named target-audience contact still allowed if one emerges. Hard-kill pivot target if TireSurf misses 06-11.

▶ Ultimate

Pipeline live · First paying client

10+ trials with target-audience contacts. Sight system delivering personalized intelligence at scale. First paying client signals the product clears the air gap between research and pay.

Dashboard active · memory pane VERIFIED · live what's loaded

Now

Phase 2 substrate live (markers + generate.py + Stop hook + state.json + START-HERE auto-maintain + server.py + launchd plist). UI features [BUILT — UNVERIFIED] pending Playwright tests or Pat click-confirm.

▶ Ultimate

Auto-regen · Zero drift

Pat opens laptop · 30-second glance · knows what each Claude is doing · knows what's blocking · knows next move. The 30-second CEO surface for an AI organization. Zero drift events / session by 07-15.

What Moved since last session + current session i

✓ Win

2026-06-25

Verification caught THREE fundamental bugs in close-gate before it went live — v1 inert (ctime≈now), v2 false-fire (transcript spans sessions), clo…

✓ Win

2026-06-25

First LIVE fire of Minsky's close-gate false-armed on my STARTUP. Root cause: close-arm.py substring-matches `/retrospective.md` in the Bash `comma…

✓ Win

2026-06-25

Minsky's close-arm v2 (mtime-evidence) fix is VERIFIED. Strongest proof was LIVE, not sandbox: THIS session's startup ran the Loop-1 check as a Bas…

✓ Win

2026-06-25

The resolution claimed "the test gap that let v1 through is now permanently covered" — it wasn't. `selftest-close.sh` tests only the GATE; `close-a…

✓ Win

2026-06-25

close-gate FIRST LIVE FIRE: false-armed on startup (caught + fix written)

✓ Win

2026-06-25

Session-close enforcement built (close-gate + close-arm) · Claude Inheritance panel · delegated-completion methodology

✓ Win

2026-06-25

Close-arm v2 re-test (close-protocol fix verification)

Completed Work all products + all infrastructure · where I am · where I'm going

▼ Products (customer-facing)

TireSurf

Tier 0 · urgent

Smart Consumer · Claude Alex

End:Web app · 100 Thai drivers/mo. Decision-equalizer pattern proven at consumer scale. First evidence the AI-amplified individual ships products.

HNF LI

frozen · deliverable

HNF Life Intelligence · Claude Prime

End:Pipeline live · 10+ trials · first paying client. Sight system delivering personalized intelligence at scale.

iMessage 2

frozen · deliverable

iMessage 2 · Claude Prime

End:Replaces legacy iMessage skill. Contact intel auto-updates · sight system integrated · Pat communicates at scale without losing context.

▼ Infrastructure (internal)

Mark I OS

Mark I.I' panel received · Pat decides

Mark I · Claude Minsky

End:F. Hand-off Readiness — Pat delegates a product, terminal ships it, Pat checkpoints at gates she chose. 6th capability dimension codified 2026-06-13. TireSurf v1 → Claude Alex by 2026-06-27 = first instance.

Dashboard

Phase 2 · VERIFIED · Mark I.I tab restructured 2026-06-13

Dashboard · Claude Minsky

End:Auto-regen · zero drift. 30-second CEO surface for the AI organization. Zero drift events/session by 07-15.

Vision & Narrative

slow · active

V&N · Claude Dave Vision

End:MTP locked · 1+ moonshot selected. Venn-scoring as live decision tool. Daily work connects to 10-year trajectory.

Jarvis

standby

Jarvis · personal strategic

End:Jarvis on Opus. Personal-strategic layer always available. Mentor frameworks active during life decisions.

Recursive Self-Improvement

steady

RS-I · Claude Minsky

End:6-loop OS architecture maintained. BVL · monthly cleanup · signal generator firing as designed.

Room

quiet

Room · cross-terminal

End:Cross-terminal collaboration substrate. Board updates · cross-impact signals · convergence log.

Plan Listauto-listed from ~/.claude/plans/

Directory of every plan. Grouped by status. One-line summary visible · click ▸ to expand for full detail.

Active · 4

2026-06-04 · CLAUDE MINSKY · OWNER: MINSKY

Ship TireSurf to a Named User · Build the Dashboard Domain · Establish Operating Criteria active

4 tiers (ship · learn · trim+dashboard · architecture) · 8-section dashboard · /get-to-know-me skill · Owner/Specialist model.

▸ full detail

Master plan from 2026-06-04. 4 tiers (0 ship · 1 learn · 2 trim+dashboard · 3 architecture). 8-section dashboard. /get-to-know-me skill. Owner/Specialist model. Mark II tracking via existing Mark-I/06+07.

FILES
• ~/.claude/plans/elegant-drifting-storm.md (registry)
• ~/Claude/Dashboard/03-plan-and-design-review/01-mark-i-ship-plan-2026-06-04.md (permanent)
• ~/Claude/Dashboard/03-plan-and-design-review/01.1-reviewer-panel-mark-i-ship-2026-06-04.md (Blundin · Miller · Wissner-Gross)

2026-06-19 · CLAUDE MINSKY · OWNER: MINSKY

M4/M5 validation — the adversarial V&V panel active

The adversarial validation of the M4/M5 cleanup feature. Result: VERIFIED & CLOSED 2026-06-19 (2 rounds — R1 found 3 real bugs + 1 method gap, all fixed; R2's "critical" was a test artifact).

▸ full detail

The validator panel: cold-run → 2 skeptics → defender → judge → trajectory. M4/M5 verified; the reusable method (the "Adversarial V&V Panel") was extracted to the V&V manual. Open follow-on: the report's HTML view needs a proper rebuild.

PLAN FILE
• ~/.claude/plans/m4m5-validation-2026-06-19.md
RECORDS
• ~/Claude/Recursive Self-Improvement/verification/archive/m4m5-validation-report-2026-06-19.md (the report)
• ~/Claude/Library/verification-and-validation-protocol/manual.md (the reusable method)

2026-06-21 · REV 2026-06-23 · CLAUDE MINSKY · OWNER: MINSKY

V&V system + Domain Context Loading fix active · Part 2 done

Two builds: the standing V&V system (Library) + the Claude Inheritance continuity methodology, plus the small CLAUDE.md Domain Context Loading "read-all" fix. Part 2 (continuity/DCL arc) DONE + verified 2026-06-22/23; Part 1 (the V&V system itself) is next.

▸ full detail

Claude Inheritance methodology built + cold-read VERIFIED · CLAUDE.md Domain Context Loading now reads ALL VARIABLE items (v2.26) · folder renamed to claude-inheritance/. Next: build the V&V system (mock the real-time view → docs → build → fix the M4/M5 report as the first use case).

PLAN FILE
• ~/.claude/plans/not-develop-the-lively-cray.md
DELIVERS
• ~/Claude/Library/claude-inheritance/ (the methodology) + ~/Claude/Library/verification-and-validation-protocol/ (the V&V system)

2026-06-08 · CLAUDE MINSKY · OWNER: MINSKY

Dashboard Phase 2 + Continuity Enforcement active · executing today

Closes 2 gaps named 2026-06-08: continuity convention not enforced + Dashboard HTML doesn't auto-update at session close.

▸ full detail

Closes the two gaps Pat named 2026-06-08: (A) continuity convention not enforced — Claude skips silent-anchor-bridge in practice. (B) Dashboard HTML doesn't auto-update at session close — listed in master plan Tier 2 since 2026-06-04, never built. Plus: nav notification system (unread dots + status pills), Plan List manual controls, Plan Execution sub-nav + tabs, START-HERE.md auto-maintenance, build verification protocol, spec disclaimer.

FILES
• ~/.claude/plans/dashboard-phase-2-and-continuity-enforcement.md (active registry)
• ~/Claude/Dashboard/03-plan-and-design-review/03-dashboard-phase-2-and-continuity-enforcement-plan-2026-06-08.md (permanent design record)
• ~/Claude/Library/build-verification-protocol/ (the protocol this plan delivers)

2026-06-10 · REV 2026-06-13 · CLAUDE MINSKY · OWNER: MINSKY

Mark I.I' — Three structural moves after panel verdict open · core shipped · A7/A8 left

Originally Kernel + Modules + claude-mode.md (3/3 panel reject 2026-06-13). Revised to Mark I.I' — ORIENT · retirement primitive · hand-off readiness. 2026-06-19: Move 1 shipped + verified (N=3 cold test) · Room/Board Meeting/Innovate/Staging retired · 6 enforcement hooks live. 2026-06-23: core overhaul done — Move 2/Move 3/Pre-handoff/A3/A6 retired, A8 doc fixed; plan KEPT OPEN for A7 (BVL triage) + the A8 Loop-4 signal — "the loops are convention, not enforced" (see plan Findings).

▸ full detail

Restructure CLAUDE.md (614 lines, v2.22+) into small Kernel (~80 lines) + ~16 trigger-loaded modules + universal behavioral layer (~/Claude/claude-mode.md). Mark I.I, not Mark II — same OS (BVL, 6 loops, 4-file domain pattern, all features unchanged). Panel run 2026-06-13 by Pat's call. All three reviewers (Blundin · Miller · Wissner-Gross) reject claude-mode.md as designed — independent reasoning, same conclusion. They sharpened the lead hypothesis (decisions vs. bytes · orientation forcing functions · retirement vs. accumulation). Pat reads three full reviews → decides direction.

PANEL REVIEW PACKAGE ~/Claude/Mark-I/research-and-design-review/02-overhaul-2026-06-10/ (panel main · 01-architecture-review-2026-04-17 + 02.2-mark-i-audit-2026-06-13 are derivatives)
• 00-README.md — navigation + verdict summary
• 01-mark-i-overhaul-plan.md — plan snapshot (live working copy at ~/.claude/plans/mark-i-overhaul-2026-06-10.md)
• 02-panel-brief.md — full brief
• 03-panel-blundin.md — Dave's verdict
• 04-panel-miller.md — Allie's verdict
• 05-panel-wissner-gross.md — Alex's verdict
• 06-08-v3-*.md — V3 adversarial agent reports

PLAN FILE ~/.claude/plans/mark-i-overhaul-2026-06-10.md — 2026-06-13 diagnosis + panel-results sections at top · original 8-step plan body preserved below
BACKUP ~/Claude/Mark-I/backups/mark-i-operation-backup-2026-06-10.tar.gz · 250MB · delete-by 2026-07-10

Drafting / Review · 1

2026-06-17 · CLAUDE MINSKY · OWNER: MINSKY

Training the Architect — Pat's learning path to ship novel SOTA drafting · 4-reviewer panel pending

Pat's learning path · 5 modules (M1–M5) · transmission + cultivation per module · Vision Workshop · ends in M5 ship of novel SOTA artifact.

▸ full detail

Pat's learning path to become a great AI architect AND ship a novel state-of-the-art artifact (her Mark II candidate, or whatever emerges). Training, NOT infrastructure — lives in its own domain at ~/Claude/Training the Architect/ (folder created with plan copy; 4-file foundation pending panel approval). Five-module spine (M1 Mark I Mastery → M2 AI Systems Architecture → M3 Frontier Awareness → M4 Design Voice → M5 Build + Ship). Two layers per module: transmission (frameworks, lenses) + cultivation (Pat applies, Minsky pushes). Vision Workshop thread continuous M1→M5. 4-reviewer panel (Blundin · Miller · Wissner-Gross · Schmidt) pending — same full brief to all four, no per-reviewer narrowing.

PLAN FILES
• ~/.claude/plans/training-the-architect-2026-06-17.md (active registry · v0.1 draft)
• ~/Claude/Training the Architect/01-training-the-architect-2026-06-17.md (permanent record · domain copy)
PARENT PLAN ~/.claude/plans/mark-i-evolution-master-2026-06-17.md Track 3
DOMAIN ~/Claude/Training the Architect/ (folder created · 4-file foundation + M1–M5 outputs pending panel approval)

Done · 2

2026-06-06 · COMPLETED 2026-06-07 · CLAUDE MINSKY · OWNER: MINSKY

Domain START-HERE.md Pattern · Closing One Surface of Discontinuity done · in use · logged to Mark II

START-HERE.md as 5th standard file per domain · pattern in use (Dashboard) · panel skipped (evidence beats opinion on working pattern).

▸ full detail

Proposes START-HERE.md as 5th standard file per domain. Layered FIXED (5 files always read) + VARIABLE (work-dependent). 2026-06-07 session 2: reviewer panel skipped — pattern is in use (Dashboard domain has START-HERE.md + Continuity pill renders state), direct evidence beats opinions on something already working. Full drift-problem context + 8 foundations built + Mark II implication logged at Mark-I/05-mark-ii-findings-log.md.

FILES
• ~/.claude/plans/silent-anchor-bridge.md (active registry copy)
• ~/Claude/Dashboard/03-plan-and-design-review/02-start-here-pattern-plan-2026-06-07.md (permanent design record)
• ~/Claude/Dashboard/START-HERE.md (first instance — Dashboard domain · renamed from read-first.md)
• ~/Claude/Dashboard/03-plan-and-design-review/02.1-reviewer-panel-foundation-2026-06-07.md (related panel — reviewed the foundation docs the plan called for)

2026-06-18 · COMPLETED 2026-06-19 · CLAUDE MINSKY · OWNER: MINSKY

Mark I Blueprint + Mark I.I′ — source-of-truth + the change-set done

Mark I.I′ substantively complete — ORIENT + M4/M5 both verified (M4/M5 via the adversarial V&V panel); Moves 2 & 3 dropped; system-spec + operator-guide refreshed.

▸ full detail

Delivered: ORIENT block (M1/M2) · 7 enforcement hooks · M4/M5 cleanup (verified via the adversarial panel) · system-spec + operator-guide refreshed. Dropped: Move 2 (retirement primitive) · Move 3 (Kernel) · Step B (claude-mode.md). CEO identity = separate thread (parked).

PLAN FILE
• ~/.claude/plans/as-i-told-you-polished-nest.md
ARTIFACTS
• ~/Claude/Mark-I/html/blueprint-v0.5-draft.html (System Map + In Depth)

Plan Execution6 plans executing

Ship TireSurf + Dashboard 1/14

Dashboard Phase 2 + Continuity 14/19

Mark I.I Overhaul 20/48

Training the Architect 2/22

M4/M5 validation 17/18

V&V system + DCL fix 9/14

The 4 tiers from the active master plan. Deliverables A–M from ~/Claude/Dashboard/deliverables.md nested under each tier. Status pills show where each stands. Plan file: ~/.claude/plans/elegant-drifting-storm.md

Tier 0

Ship TireSurf v1 by 2026-06-11 — 2 days remain

G. TireSurf v1 BLOCKED · needs Pat: user

Owner: Alex · G1 user · G2 CRAFT · G3 DoD · G4 build · G5 handover

Tier 1

Learn from first ship

One-page learning doc blocked on T0

Triggered after Tier 0 delivers

Tier 2

Trim + foundational + dashboard (parallel)

B. Dashboard v1.0 · Phase 2 shipped · UI UNVERIFIED

Owner: Minsky · markers + generate.py + Stop hook + state.json + START-HERE auto-maintain + server.py + launchd

C. /get-to-know-me queued

Skill + Instructions section toggle

D. Philosophy + Operating Criteria partial

philosophy.md LOCKED 2026-06-07 · operating-criteria.md still queued

F. Mark I System Trim partial

task-list sync done 2026-06-09 · handoff/Library/sys-arch still queued

E. Per-project foundation.md partial

Dashboard 3-file split locked · other domains staggered per owner

A. Big Plan done · 2026-06-04

Reference for the sprint

Tier 3

Architecture after first ship

H. Identity per terminal future

I. Mark II preparation future

J. Owner sub-team creation future

K. Mission Control retirement future

L. Room domain decision future

M. Jarvis migration future

Verification checkpoints from master plan

○ 2026-06-11 (hard): TireSurf v1 in named user's hands — OR hard-kill pivot triggered
○ Next session: dashboard built; Pat opens and sees state without re-explanation
○ Dashboard auto-regenerates at session close (Stop hook — v0.3+)
○ Plans tab auto-lists this plan + any new plan (v0.3+)
○ Operating criteria visible in task-list.md header + dashboard html
○ Pat's philosophy drafted; Pat-in-loop; locked when sounds like her
○ /get-to-know-me skill works; reads 3 files; persists in session
○ Mark-I/07 has ≥3 entries by 2026-06-11
○ Within 30 days of ship: 2 products shipped · Tier 3 decision started with evidence

Phase 2 substrate work. Closes the two continuity gaps named 2026-06-08: (A) silent-anchor-bridge convention not enforced in practice. (B) Dashboard HTML doesn't auto-update at session close. Plan file: ~/.claude/plans/dashboard-phase-2-and-continuity-enforcement.md

Branch 1 — Substrate

Generator + Stop hook + state

A. Propagate v12 → dashboard.html done · v1.0

2-col landing · journey-row · Endgame redesign · clickable Plan Exec nav/tabs

B. Insert HTML markers done · 24 pairs

13 concept markers (some inline) · BEGIN/END pairs symmetric

C. Write generate.py done · v0.1

Marker-based section updater · 13 active generators · preserves hand-built design

D. Apply build-verification-protocol done

Category A applied · journal + BVL entries written

E. Wire Stop hook done

~/.claude/settings.json — alongside Mission Control hook · launchd plist auto-starts server.py

F. state.json schema + init done · v1.0

last_session_close · last_dashboard_version · domain_reads · section_views

Branch 1 — Domain reads + Verification

Substrate complete · UI verification next

G. Per-domain START-HERE auto-maintain done

fixed-list markers + auto-regenerator (Dashboard active; other domains as they gain START-HERE)

H. End-to-end verification substrate · UI UNVERIFIED

11/11 technical checks pass · UI features need Playwright OR Pat-click-confirm

Playwright UI test suite DEFERRED · 2026-06-10

Pat 2026-06-10: not for now, future when more users / more dev pressure. Pat-verification is sufficient floor. See plan file update at bottom of dashboard-phase-2-and-continuity-enforcement.md

Memory Panel toggle → state.json intent done

JS click → POST /save-state → state.json domain_reads · refresh hint banner + dirty-state button

Branch 2 — Docs (after Branch 1)

Spec + philosophy comprehensive rewrite

I. 02-philosophy.md (SOUL) queued

Comprehensive rewrite · Pat-in-loop

J. 03-dashboard-html-spec.md (MANUAL) queued

Locked status colors · owner-identity colors · Story-over-State · sections

Decisions + locks (this work)

What was settled

v12 landing mockup LOCKED done

2-col layout · Pat-approved 2026-06-08

CLAUDE.md "Domain Context Loading" done

Read-side enforcement · + STRUCTURAL VERIFICATION RULE 2026-06-09

build-verification-protocol shipped done

manual + journal + STRUCTURAL RULE: UI work cannot be self-verified

state.md architecture considered + rejected done

Built then reverted 2026-06-09 — violated "Pat asks → Claude edits directly" rule

EDIT RULE in dashboard.html + mode.md done

5-line top comment · 6-step procedure · Step 0 marker-type check · inline AUTO tags on 6 markers

Option B — PostToolUse auto-log hook done

~/.claude/settings.json + auto-log-domain-read.py — auto-logs Read of START-HERE.md to state.json · eliminates manual logging failure mode

Unread-dot mechanism (right concept) partial verified · 3/4 Pat-tested

section_changes vs section_views in state.json · per-section hash detection across runs · click clears dot · refresh preserves

Verification checkpoints from Phase 2 plan

✓ dashboard.html v1.0 visually matches v12 mockup
✓ generate.py preserves hand-built design (marker-based, not template render)
✓ Stop hook triggers regen at session close — same output as manual refresh
✓ state.json schema initialized + read tracking working
✓ START-HERE.md auto-maintained per domain at session close
✓ Branch 1 ships before Branch 2 starts (philosophy + spec rewrite)
✓ Build verification protocol applied to generate.py before declaring done
○ UI features VERIFIED via Playwright OR Pat click-confirm (pending)

Mark I.I' — Hand-off Readiness Through Structural Enforcement. (Revised 2026-06-13 after panel verdict + Pat dialogue. Supersedes original Mark I.I 8-step plan — preserved as historical record below.)

Mission: Mark I succeeds when Pat can name a deliverable + named user + hard date to a terminal, the terminal carries it to ship, and Pat checkpoints at gates she chose — not at every Claude decision. Codified 2026-06-13 as 6th capability dimension F. Hand-off Readiness in ~/Claude/Mark-I/01-north-star.md. Plan: ~/.claude/plans/mark-i-overhaul-2026-06-10.md

Problems → Root cause M1-M2 Pat-named (felt) · M3-M5 Claude-observed (structural)

#	Problem	Named by
M1	Startup protocol skipped consecutively · drift events 3+/session baseline	Pat (felt friction)
M2	Domain Context Loading skipped or partial	Pat (felt friction · 2026-06-08 catch)
M3	CLAUDE.md bloated (614 lines, v2.0 → v2.22+)	Claude-observed (Mark II findings 2026-05-01 Weight)
M4	handoff.md bloated (1052 lines)	Claude-observed (accumulation pattern)
M5	task-list completed accumulates	Claude-observed (Monthly Cleanup step 5 slipping)

Root cause: Convention-as-enforcement degrades non-linearly with protocol size + accumulation without retirement primitive. The asymmetry: every Mark I structural enforcement (PostToolUse hook · BVL · STRUCTURAL VERIFICATION RULE · 4-tier history mandatory fields) held; every convention-only rule slipped.

Three structural moves zero new files · zero new convention surface

Move	Solves	Confidence	Benchmark (success = ___)	Expected output	Risk if wrong
1. ORIENT block at session boundaries. Generalize ✓/○ checklist (STRUCTURAL VERIFICATION RULE 2026-06-09 — the one mechanism that held) to session open + close. Pat-visible chat block per session.	M1 (90%) · M2 (80%)	High (85%)	Drift events ≤1/session sustained 14 days · Pat catches ≥3 drift via ORIENT in 30 days	Pat-visible chat block at session boundaries · ✓/○ for handoff/task-list/curiosity/schedule (room retired) · full 10-step checklist + evidence validator	Noise Pat scrolls past — measure 30d; retire via Loop 6 if no catches
2. Retirement primitive. Every rule/file/mechanism gets a death condition at creation (use-based · contradiction-based · supersession · permanent). Monthly Cleanup death-scan; Pat-confirms; archive to CLAUDE-archive.md.	M3 (90%) · M4 (95%) · M5 (95%)	High (80%)	CLAUDE.md trims ≥20% in 90 days · handoff sustained <800 lines · task-list auto-archived after 30 days	Death-condition field on every rule (retro-fit) · Monthly Cleanup outputs candidates · CLAUDE-archive.md grows	Death conditions gamed (permanent overused) — quarterly audit catches
3. Hand-off Readiness as success metric. Codify as 6th capability dimension (done 2026-06-13). First instance: TireSurf v1 → Claude Alex. Contract at `08-design-review/03-handoff-contract-template-2026-06-13/02-tiresurf-instance-2026-06-13.md`.	Pat's actual constraint (one thing at a time)	Medium (60%)	TireSurf v1 ships to 1 named user by 2026-06-27 · Pat-touches <2/wk · 0 catastrophic overrides · <3 corrective	Hand-off contract signed by Pat + Alex · TireSurf moves to autonomous Alex-mode · ship-status visible at session open via ORIENT	Trust gap wider than Moves 1+2 close — diagnose at first miss; iterate contract

Status flow: done → queued → dropped

✅ DONE

Holds in Mark I.I' (from earlier work)

Step C · D — handoff + task-list raise-confirm done · 2026-06-10

Owner-scoped retirement · Mark I-consistent

Step E — Domain Context Loading in production

START-HERE.md + STRUCTURAL VERIFICATION RULE 2026-06-09 · RSI/START-HERE.md 2026-06-13 extends it

Step H — Plan-file-as-continuity-carrier standing

Standing Mark I protocol

Format spec deployed

handoff DATE + DOMAIN + ONE-LINE + ### · task-list two-line

6th capability dimension F. Hand-off Readiness codified · 2026-06-13

~/Claude/Mark-I/01-north-star.md

Hand-off contract template + TireSurf instance drafted · 2026-06-13

08-design-review/03-handoff-contract-template-2026-06-13/

⏳ QUEUED

Pat reads panel → confirms → executes next session

Move 1 — ORIENT block shipped + verified · 2026-06-19

Session open + close · Pat-visible ✓/○ on handoff/task-list/room/curiosity

Move 2 — Retirement primitive dropped

A death-condition field on every Mark I rule, so rules self-retire when their trigger stops firing — keeps the OS lean as it grows. Dropped 2026-06-23: leanness came from what shipped (deprecation-guard hook + M4/M5 cleanup + the actual retirements); a death-condition on every rule is itself the accretion the executable-only discipline rejects.

Move 3 — TireSurf hand-off cycle dropped

Prove hand-off readiness via a real cross-terminal hand-off — a live TireSurf instance handed to Claude Alex as the test. Dropped 2026-06-23: hand-off readiness is codified (north-star dim. F); the TireSurf instance is blocked on its named user = #125 in Alex's Smart Consumer domain, not this OS plan.

Pre-handoff readiness design dropped

A pre-hand-off readiness gate — a 3-signal contract a terminal must pass before handing work off. Dropped 2026-06-23: Pat — not load-bearing now, good-to-have not worth the time. Revive only if a real hand-off surfaces the need.

Foundation document methodology guideline done

Done 2026-06-23 — built out as the Claude Inheritance methodology · folder renamed → ~/Claude/Library/claude-inheritance/

A3 + A6 audit fixes dropped

Two 2026-06-13 audit items — A3 = Monthly Benchmark prompt; A6 = HNF LI memory.md Rule 1 (cold-start). Dropped 2026-06-23: A3 never defined — nothing functional broken; A6 re-homed to the HNF LI domain (Prime), off this plan.

A7 BVL triage + A8 Loop-4 signal queued

Both root causes unfixed: A8's mode.md doc was sharpened, but Loop 4 still isn't auto-firing; A7 = 16 stale BVL entries to triage. Same root — "the loops are convention, not enforced." Plan KEPT OPEN — see its Findings.

❌ DROPPED

Per 2026-06-13 panel verdict (3/3 reject)

Step A — Kernel + Modules split dropped

Rearranges convention without removing it · Run Moves 1+2+3 for 60 days; revisit only if still bleeding

Step B — claude-mode.md universal layer dropped

Violates 2026-04-16 RSI history: "intelligence cannot be installed by writing instructions" · 3/3 panel reject

10 behavioral patterns synthesis dropped

Feedback memories stay atomic + validated · uncompressed substrate preserved

V2 · V4 · V6 validation gates dropped

No implementation to validate

Kill condition when to roll back Mark I.I'

If after 30 days Moves 1+2 show no measurable reduction in drift events AND TireSurf hand-off cycle requires >3 unplanned Pat-touches/week, Mark I.I' is wrong. Roll back; reassess. Original 8-step plan preserved below for reactivation reference.

Panel reviews read full when ready

• ~/Claude/Mark-I/08-design-review/02-overhaul-2026-06-10/03-panel-blundin.md — execution velocity · ship discipline · scale compound
• 04-panel-miller.md — 10-second orientation · MVA · teammate AI mode
• 05-panel-wissner-gross.md — F=T∇Sτ · option preservation · futures structure

All three sharpened the lead hypothesis. All three rejected claude-mode.md as designed. Mark I.I' synthesizes their convergent moves.

⤵ Original 8-step Mark I.I plan + earlier diagnosis — superseded historical content (click to expand)

Mark I.I — Kernel Split + Universal Behavior Mode (original 2026-06-10 design — superseded 2026-06-13). Restructure CLAUDE.md (614 lines, v2.22+) into Kernel + ~16 trigger-loaded modules. Add ~/Claude/claude-mode.md as universal behavioral layer (3rd tier between constitution and per-domain mode.md). Same OS (BVL, 6 loops, 4-file domain pattern, all features unchanged). Closes Surface 1 (cross-session, same terminal) per continuity analysis.

Root cause + the 5 problems Pat's question 2026-06-13 · diagnosis before solution

Pat asked: "Is it because of CLAUDE.md? We need to know the cause."

Answer. CLAUDE.md is the surface where the problem shows up — it's the accumulator. The deeper cause is the enforcement model: Mark I's protocol is convention; execution is Claude's self-discipline. Convention grows by adding bytes; execution fidelity degrades non-linearly as bytes grow.

Evidence already in Mark I findings — three angles, one root cause:

• RSI memory.md 2026-04-02 audit: "If startup protocol failures are viewed as one root cause, the count likely exceeds 3." Symptom-level tagging hid the real count.
• Mark II finding 2026-05-01 (Weight): "every improvement permanently increases startup cost… no mechanism to retire prose once a rule becomes habit."
• Mark II finding 2026-05-01 (Verification): "the integrity of every CLAUDE.md edit, every history entry, every retrospective compression depends on Claude's self-discipline."

This explains all 5 problems with one cause. M1 + M3 surface in CLAUDE.md directly. M2 is convention ("read START-HERE.md") vs. Claude execution. M4 + M5 are Monthly Cleanup mechanism that exists but isn't reliably executed.

The evidence that structural enforcement works where convention fails: every case where Mark I added an external/automatic check — PostToolUse hook for domain reads · BVL passive verification · 4-tier history mandatory fields · STRUCTURAL VERIFICATION RULE for ✓/○ checklist — held. Convention-only fixes slipped.

The 5 problems Pat named — proposed solutions are Claude's starting points for the review panel:

#	What Pat sees	Where the cause manifests	Claude's proposed solution (panel reviews)	Confidence
M1	Startup protocol skipped consecutively	CLAUDE.md grew v2.0 → v2.22+ (614 lines) — too much to execute reliably under context pressure	Split CLAUDE.md into small always-loaded Kernel (~80 lines, ~15 explicit sub-rules) + ~16 trigger-loaded Modules. Smaller surface = readable end-to-end. Pointer table in Kernel guarantees module discoverability.	Medium-high — reduces surface; same Claude must still obey
M2	Domain Context Loading skipped or partial	Convention ("read START-HERE.md") relied on Claude discretion — execution slipped despite Pat-visible drift	START-HERE.md pattern (already in use in Dashboard) + STRUCTURAL VERIFICATION RULE (✓/○ checklist, already added 2026-06-09) + propagate pattern to remaining domains. Two structural fixes already live.	High — pattern in use, evidence accumulating
M3	CLAUDE.md bloated (614 lines)	Monotonic accretion — every learning translated to a new rule; no retirement mechanism	Kernel + Modules split (same lever as M1) + 1-in-1-out structural cap on any new layer that gets created so the same accretion pattern doesn't re-emerge in claude-mode.md or modules.	Medium-high — structural cap is the discipline mechanism
M4	handoff.md bloated (1052 lines)	Monthly Cleanup mechanism exists but per-terminal owner-scoped retirement doesn't run reliably	Owner-scoped raise-confirm at monthly cleanup (mechanism designed 2026-06-10). Archive to `handoff-history.md` append-only.	High — mechanism is mechanical once executed
M5	task-list.md completed entries accumulate	Monthly Cleanup step 5 exists but execution slips	Same mechanism as M4 — owner-scoped, monthly, append archive. Already specified; needs reliable execution.	High — auto-runs once executed

Cross-cutting proposal: ~/Claude/claude-mode.md — universal behavioral layer between constitution (values · slow) and per-domain mode.md (specialized · fast). Synthesizes 27 of 51 feedback memories into ~10 patterns. This is the part Pat flagged anxiety on — it risks codifying behaviors that 2026-04-16 history.md says should emerge through validated practice. The panel should pressure-test this specifically: does it close M1 by reducing repeated correction load, or open a new accretion surface?

Status: Diagnosis complete. Proposed solutions above are starting points only. Review panel runs only when Pat calls it. Claude does not run the panel autonomously.

Phase 1 — Plan & Validate

Get the plan-plan right before any change

Plan file written done · 2026-06-10

Risk per step · V1-V5 + T1-T7 + 9-surface coverage · 16 decisions logged

Full OS backup done · 250MB

~/Claude/Mark-I/backups/mark-i-operation-backup-2026-06-10.tar.gz · delete-by 2026-07-10

V3 adversarial validation done · 3 Opus agents

285 rules · 20 structural-ref findings + 8 missing files · 10 behavioral patterns

Continuity branch consolidated into this plan done

Per Pat 2026-06-10: branch lives in parent plan, not separate file. Analysis + parked sequels now a section in mark-i-overhaul-2026-06-10.md

handoff + task-list raise-confirm done · 2026-06-10

Minsky scope · #34 #98 #51 retired · #124 → Completed · #123 DEFERRED · #117 closed · handoff Minsky scope clean (0 candidates).

Format spec + implementation done · 2026-06-10

CLAUDE.md Q1 handoff format updated (DATE + DOMAIN + ONE-LINE + ### sub-headers) · Real-Time Task Tracking gained two-line task format · handoff.md Minsky section rewritten · task-list Minsky entries rewritten · CLAUDE-history.md Tier 1 entry (all 7 fields)

Reconcile V3 gaps into plan-plan done · 2026-06-10

285 rules · ~16 modules · 26+ files · 10 patterns · step-number preservation locked as hard constraint · 3-tier history entry mandate captured · all V3 deltas integrated

Self-critique per BVP discipline done · 2026-06-10

6 findings · 3 actioned in plan: 1-in-1-out structural cap (claude-mode.md anti-accretion) · V6 step-number citation check (enforces HARD CONSTRAINT) · format-propagation-incremental note · 3 held as Claude-calibration

Plan-plan FINALIZED — ready for panel ready · 2026-06-10

All decisions made · all scope explicit · V1-V6 validation strategy · T1-T7 post-implementation testing · self-critique findings integrated · 3-reviewer panel is the gate before execution

3-reviewer panel next session · tomorrow

Blundin · Miller · Wissner-Gross · brief: full plan + V3 findings + step-number constraint + 3-tier history mandate + self-critique findings

Phase 2 — Build & Deploy

After panel approves

A. CLAUDE.md → Kernel + Modules queued

Kernel ~80 lines · ~16 modules at ~/.claude/protocols/ · step numbers preserved

B. claude-mode.md (10 patterns + Aesthetics) queued

~/Claude/claude-mode.md · synthesizes 27 of 51 feedback memories · 2-section file

E. Domain Context Loading in Kernel queued

FIXED + VARIABLE on entry · hold throughout · ✓/○ structural verification

V1 inventory diff + V2 trigger sim queued

Self-validation gate before deploy · zero blockers required

Deploy queued

Write Kernel + modules + claude-mode.md · V5 backup already taken

Phase 3 — Post-Deploy Verify

Immediate, <48 hr

V4 shadow-run on next session queued

Run live session as if claude-mode.md loaded · behavioral gaps surface naturally

F + G. T2 docs update (26+ files) queued

CLAUDE-history (7-field) · system-architecture S1+S2+Quick Status · Mark-I/02/03/06/07 · RSI · feed-map · skills-map

T1 Architectural integrity queued

All references resolve · Kernel ≤80 lines actual · module count correct · no orphans

T2 Operational scenarios queued

Cold start · domain entry · session close · mid-save · monthly cleanup · task tracking — each fires correctly

T3 Behavioral evals (10 patterns) queued

Each claude-mode.md pattern gets 1-3 test scenarios · 16-24 tests · pass/fail logged

T4 Regression queued

Every v2.22 rule still fires under Kernel+Modules · zero regressions allowed

T3 docs append + BVL entry queued

loop-log · activity-log · retrospective · MEMORY · BVL: Category B Architectural

Phase 4 — Harden

14 days · then mark VERIFIED

T5 User testing (Pat's real usage) queued

Pat uses normally over 3-5 sessions · reports any friction · findings logged

T6 Long-horizon queued

14 days · Loops fire as expected · drift events reduce from baseline 3+/session

T7 Adversarial red-team queued

3 Opus subagents try to break it · attack vectors documented + defended

Mark VERIFIED queued

All T1-T7 pass · BVL entry → VERIFIED · Mark I.I closure

Validation strategy Pat cannot validate this — Claude drives

V1 Complete inventory diff done via V3 Agent 1

285 rules · all mapped · ZERO unaccounted

V2 Simulated trigger pass per module queued

Each module trigger walked end-to-end · outputs verified

V3 Adversarial subagent review done · 3 Opus agents

Agent 1 (rules) + Agent 2 (refs) + Agent 3 (behaviors) all complete

V4 Live-session shadow run queued

Run today's remaining session as if claude-mode.md loaded · gaps surface

V5 Backup + rollback hatch done

~/mark-i-operation-backup-2026-06-10.tar.gz · 250MB · delete-by 2026-07-10

Post-implementation testing 7 layers (T1-T7)

T1 Architectural integrity · T2 Operational scenarios · T3 Behavioral evals (10 patterns) · T4 Regression · T5 User testing (Pat's real usage) · T6 Long-horizon (14 days) · T7 Adversarial red-team

All 7 → BVL entry "Mark I.I overhaul · Category B Architectural · VERIFIED"

Next move when session resumes

NOT tonight — Pat is tired. Decisions remaining (Pat's call): (1) 3-reviewer panel kick-off · (2) confirm 3-tier behavioral architecture (constitution + claude-mode + per-domain mode) — needs RSI/history.md entry resolving 2026-03-03 2-tier collision · (3) confirm handoff.md retirement of 6 candidates · (4) confirm additional task-list retire candidates.

PLAN FILE ~/.claude/plans/mark-i-overhaul-2026-06-10.md — running record, survives session pause

Why · What's broken · What we're building · What done looks like (click to expand)

Why are we doing this

Mark I grew through 3 months of compounding learnings. Each new failure prompted a new CLAUDE.md rule. By 2026-06-10 the protocol reached 614 lines (v2.0 → v2.22+) and Claude started skipping steps under that weight — treating the protocol as a menu instead of executing it. Constitution Section VI explicitly rejects this pattern: "Claude does not improve by adding rules. Principles over patches." Mark I.I removes the accreted weight by restructuring, not by adding more.

What's broken

• CLAUDE.md too heavy — Claude treats it as a menu, skips steps
• Startup protocol fails consecutively — drift events 3+/session (baseline)
• 40+ feedback memories scattered with no synthesis — behaviors don't compound
• Documentation alone fails to enforce — needs structural answer
• Domain Context Loading inconsistent — Claude reads START-HERE.md partially or drops it mid-session

What we're building

• Kernel (always-loaded, ~80 lines) + ~16 trigger-loaded modules → same content, structurally lighter; only what's needed for THIS moment loads
• claude-mode.md (NEW) — universal behavioral layer between constitution and per-domain mode.md → 10 patterns synthesizing 27+ feedback memories
• Format spec for handoff + task-list → Pat-scannable for decisions
• Domain Context Loading hardened in Kernel → loads on every domain entry, holds throughout the session
• Same OS — BVL, 6 loops, 4-file domain pattern, all features unchanged

What done looks like

• Drift events ≤1 per session sustained for 14 days (baseline: 3+/session)
• Claude doesn't skip startup steps — every step verifiable in conversation
• Domain entry fully loads FIXED + VARIABLE; holds throughout the session
• All 4 terminals (Minsky, Prime, Alex, Dave Vision) operate cleanly post-deploy
• claude-mode.md patterns produce consistent behavior across sessions and terminals
• BVL entry: Category B Architectural → VERIFIED
• Pat opens the dashboard and trusts the state without needing to re-verify

M4/M5 validation — the run, round by round. Result: M4/M5 VERIFIED & CLOSED 2026-06-19. Report: verification/archive/m4m5-validation-report-2026-06-19.md · Plan: ~/.claude/plans/m4m5-validation-2026-06-19.md

Round 1 FAIL · load 9

all bugs fixed → re-test

1 · Cold-run (Sonnet) done

ran the cleanup but eyeballed — never ran the helper (the gap that hid the bugs)

2 · Skeptic A (Opus) done

found schedule-gate · handoff-regex · status-case · helper-never-run

3 · Skeptic B (Opus) done

reproduced the same four faults

4 · Judge (Opus · indep.) done

3 code bugs + 1 method gap · refuted 2 over-claims · NOT PASS

5 · Trajectory done

load 9 (baseline) — 1 CRIT + 3 MAJ

6 · Fixes applied done

3 code fixes + CLAUDE.md v2.25 mandates the helper

Round 2 VERIFIED · load 9→0

no surviving real defect

0 · Snapshot done

tar'd ~/Claude before the run (restored after)

1 · Cold-run (Sonnet) done

ran the helper (v2.25 held) — but then destructively edited the handoff

2 · Skeptic A (Opus) done

flagged the handoff deletion as critical (removed two other terminals' sections)

3 · Skeptic B (Opus) done

reproduced it

4 · Judge (Opus · indep.) done

R1 fixes held · ruled the deletion a real critical → raw NOT PASS

5 · Defender (you) done

Pat: the deletion only happened because the test was headless — can't happen in the real raise-to-Pat flow → test artifact

6 · Outcome VERIFIED

no real defect · honest residual + revisit trigger

7 · Restore done

snapshot restored — real memory untouched

Round 3 not run

not required

Not needed n/a

verified at Round 2 (bar: 2 clean rounds via an improving trajectory)

Other tasks

deliverables

Report — md done

self-explanatory · in verification/

Report — HTML view done

faithful render from the md (render-report.py)

Method → V&V manual done

the reusable "Adversarial V&V Panel"

Records where it lives

• ~/Claude/Recursive Self-Improvement/verification/archive/m4m5-validation-report-2026-06-19.md — the full report
• ~/Claude/Library/verification-and-validation-protocol/manual.md — the reusable method ("Adversarial V&V Panel")
• ~/.claude/plans/m4m5-validation-2026-06-19.md — this plan

V&V system + Domain Context Loading fix. Two builds — the standing Verification & Validation system (Library) + the Claude Inheritance continuity methodology — plus the small CLAUDE.md Domain Context Loading "read-all" fix. Part 2 (continuity / DCL arc) is DONE + verified; Part 1 (the V&V system itself) is next. Single tracking surface = the plan's Sequence. Plan: ~/.claude/plans/not-develop-the-lively-cray.md

Part 2 — continuity + DCL DONE · 06-22/23

the whole arc shipped + verified

2.3 · Mark-I deletions done

Deprecation Protocol · migrated first · logged

3 · Mark II "build-for-cold-Claude" finding done

banked as a standing-practice candidate

2A · settle the START-HERE structure done

FIXED+VARIABLE floor · read-all · open-beyond

2A+ · Claude Inheritance methodology VERIFIED

master + 5 -thinking guides · cold-read verified

2.2 · repair the START-HEREs done

Mark-I good · RSI freshened + "fixes under Mark I"

2.1 · CLAUDE.md read-all (v2.26) done

Domain Context Loading reads ALL VARIABLE items

2.4 · ship-discipline done

history + system-arch + BVL · cold self-test PASSED

Folder rename → claude-inheritance done

+ reference sweep · 2026-06-23

Part 1 — the V&V system next

build the system itself

1.1 · mock the real-time V&V view next

visual-prototype-first → Pat agrees (v0.1 rejected — revisit)

1.2 · V&V docs queued

00-START-HERE + foundation pair (non-domain LIGHT) + guideline + protocol · retire manual.md

1.3 · real-time view + report queued

model→view · scoreboard + stage-band

1.4 · fix the M4/M5 report queued

first real use case — the system proves itself by being used

Wrap Pat runs

two review panels

Review panel — Claude Inheritance done

the methodology + the Strategy-section design · ran 2026-06-25 → 1.0 incorporated

Review panel — V&V system queued

after Part 1 builds it

What Pat wants the framing

A universal, living V&V asset — the standing way we validate anything we build, growing with each use case. Claude does the V&V; Pat oversees, not tests. The work-type→method matrix is a guideline, not a cage. The continuity half ("Claude Inheritance") fixes the cold-Claude problem: every compounding artifact carries its own foundation + loader so a future Claude inherits everything — vision, strategy, soul, why.

Training the Architect — Pat's learning path to ship novel SOTA artifact. Training, NOT infrastructure. Lives in its own domain at ~/Claude/Training the Architect/. Five-module spine, each with transmission (frameworks) + cultivation (Pat applies, Minsky pushes) layers. Vision Workshop thread continuous M1→M5. End state: Pat ships a real novel state-of-the-art thing she designed. Plan file: ~/.claude/plans/training-the-architect-2026-06-17.md

Path forward — how this plan completes

The training plan retires when M5 ships: Pat builds and ships a novel SOTA artifact under her name (her Mark II candidate or whatever emerges through Training). The path runs through pre-launch → 5 modules → Curriculum-as-System Mark II finding.

Phase A · Now

Next 1–2 sessions

Plan v0.1 written done

Active registry + permanent copy in domain folder

Domain folder seeded done

~/Claude/Training the Architect/ created with plan copy · full 4-file foundation pending panel approval

Schmidt Sciences research pre-panel

+ Schmidt material since 2026-04-16 on training/teaching/operator development · update mentors-library.md

Phase B · Soon

2–4 weeks

4-reviewer panel runs queued

Blundin · Miller · Wissner-Gross · Schmidt · same brief to all · no per-reviewer narrowing

Plan v0.2 (panel synthesis) after panel

Revise inline based on what reviewers raised

Domain fully set up + Training HTML after v0.2

Full 4-file foundation + 01-foundation/ + M1–M5 output folders + vision-workshop.md · single-file HTML with tabs per module

Phase C · Later

Months — the main arc

M1 → M4 run sequentially 2–3 weeks each

Mark I Mastery → AI Systems Architecture → Frontier Awareness → Design Voice. Each module produces a Pat-authored artifact.

M3 runs continuous from start of Phase C background

Frontier Awareness is a perpetual subscription to the field, not a discrete module gate

Vision Workshop accumulates Pat-authored thread

What Pat wants to build comes into focus session by session through M1–M4

Phase D · End-state

M5 ships

Pat ships novel SOTA artifact M5 endgame

Real · used · Pat-authored · Minsky multiplier. For Pat: likely Mark II first version, but shape emerges through Training — not pre-committed.

Curriculum-as-System Mark II entry post-M5

Methodology that produced Pat's training becomes Mark II infrastructure for other operators — Hypothesis 5 in 06-mark-ii-design-brief.md

Plan archives housekeeping

Move to ~/Claude/Training the Architect/archive/ with date stamp · delete from ~/.claude/plans/

The five modules (detail)

M1

Mark I Mastery

Pat understands Mark I deeply queued

Architecture · loops · 4-tier history · Q5 creation rule

Pat-authored Mark II hypothesis note M1 output

~/Claude/Training the Architect/M1-outputs/

M2

AI Systems Architecture

Patterns across the field queued

Agentic systems · ExO · memory · multi-agent · alignment

Architecture sketch + rationale M2 output

Pat sketches alternatives for the M1 hypothesis · picks one direction

M3

Frontier Awareness

Field-level lenses queued · continuous

Diamandis · Kurzweil · Wissner-Gross · Schmidt · Pal · frontier labs

10x bet statement M3 output

Pat maps work onto curves · names Innovation Power leverage

M4

Design Voice

Voice exercises queued

Jobs · Miller · constraint as creative force · taste

Pat's design philosophy M4 output

Pat names her own design voice · stands behind it

M5

Build + Ship

Pat ships a novel SOTA artifact M5 endgame

Mark II candidate, or whatever Pat has discovered along the way. Real · used · Pat-authored · Minsky multiplier.

Continuous

Vision Workshop

Pat-authored thread M1 → M5

~/Claude/Training the Architect/vision-workshop.md · what Pat wants to build comes into focus session by session

4-reviewer panel — pending

Blundin · Miller · Wissner-Gross · Schmidt. Same brief to all four: big picture + background + the problem + objective + why we're doing this + full plan content. Optional shared questions at the end (not per-reviewer). Reviewers bring their own lenses organically. Pre-panel: research Schmidt Sciences + Schmidt material since 2026-04-16 on training/teaching/operator development.

Productscustomer-facing

What we sell. Each card shows the Blundin compound model as a phase train: ideas → build → ship v1 → learn → ship faster v2 → ship better → pattern locks → repeat. Current phase highlighted.

TireSurf

Smart Consumer · Claude Alex · Opus 📚 CONTINUITY i

Tier 0 · this week

Thai consumer product helping drivers make tire-buying decisions. Lowest-friction path: link → fitment + 3 shops + confidence → walk away knowing which tire and which shop.

ideas → build → ship v1 → learn → ship faster v2 → ship better → pattern locks → repeat

build done (Cowork 18.5h) · ship v1 active (needs user) · hard date 2026-06-11

🎯EndgameWeb app deployed to Thai drivers. 100+ users/month within 90 days. First evidence the AI-amplified individual ships consumer products.

Next: Pat names user → Alex begins build with Claude Code + Cloudflare Pages + Access

HNF Life Intelligence

Claude Prime · Opus 📚 CONTINUITY i

iteration frozen · delivery allowed

Personalized intelligence document that reads someone's life and produces a deeply personal reading. Pipeline matured through v1.14 across April–May. Currently frozen at iteration; delivery to a real user remains allowed.

ideas → build → ship v1 → learn → ship faster v2 → ship better → pattern locks → repeat

v1.14 ready to ship · trial 11 was simulated · no real-user ship yet

🎯EndgamePipeline deployed. 10+ live trials with target-audience contacts. First paying client.

Next: deliver current version to a real user when a candidate appears (no new versions until then)

iMessage 2

Claude Prime · Opus 📚 CONTINUITY i

iteration frozen · delivery allowed

Next-gen contact + relationship management via iMessage with AI assistance. Phase 1 build A–M complete with engine specs and 6 contact profiles migrated.

ideas → build → ship v1 → learn → ship faster v2 → ship better → pattern locks → repeat

build still pre-ship · no user touching yet

🎯EndgameReplaces legacy iMessage skill. Contact intel auto-updates. Sight system integrated. Pat communicates with contacts at scale without losing context.

Next: first real user delivery when candidate appears

Infrastructureinternal · the systems we run on

What we build for ourselves. Same Blundin phase train, current phase highlighted.

Mark I OS

Claude Minsky · Opus 📚 CONTINUITY i

Mark I.I' panel verdict received · Pat decides

Pat's AI operating system. 6 capability dimensions (F. Hand-off Readiness codified 2026-06-13 as operationalization of the North Star) · 6 loops · 13 domains · BVL · retrospectives · memory. Mark I.I' revised after 2026-06-13 panel: drop claude-mode.md (3/3 panel reject) · adopt three structural moves (ORIENT block · retirement primitive · hand-off readiness via TireSurf to Claude Alex). Mark I freeze (2026-05-01) honored — Mark I.I' adds zero new files + zero new convention surface.

ideas → build → ship v1 → learn → ship faster v2 → ship better → pattern locks → repeat

Mark I.I' panel verdict received 2026-06-13 · Pat reads 3 reviews → decides direction · 6th capability dimension F. Hand-off Readiness codified

🎯EndgamePat can name a deliverable + named user + hard date to a terminal, the terminal carries it to ship, Pat checkpoints at gates she chose — not at every Claude decision. F. Hand-off Readiness is the measured success criterion.

Next: Pat reads 3 panel reviews at ~/Claude/Mark-I/08-design-review/02-overhaul-2026-06-10/ · confirms Mark I.I' direction · completes TireSurf hand-off contract (named user · autonomy boundaries · ship date 2026-06-27) · ship Moves 1+2 (low-risk · structural enforcement) · TireSurf cycle starts via Claude Alex

Dashboard

Claude Minsky · Opus 📚 CONTINUITY i

v1 shipped · public

Visual command center. Mark I domain. 10 nav sections. Blundin phase trains. Auto-regen via generate.py + Stop hook + SessionStart hook. Public mirror at pat-ai-dashboard.pages.dev (manual re-upload). 2026-06-13: Mark I.I tab restructured for Mark I.I' (problems · root cause · 3-moves table · status flow card · kill condition · panel reviews) + Status section converted to 3-column flow card (done · queued · dropped) + path references updated for renamed 08-design-review/ subfolders.

ideas → build → ship v1 → learn → ship faster v2 → ship better → pattern locks → repeat

v1.0 live local + public 2026-06-10 · memory-in-context pane VERIFIED 2026-06-11 · generate.py + Stop + SessionStart + PostToolUse:Read all running · learning from real use

🎯EndgameAuto-deploy to public at session close. All 12 domains have START-HERE.md. Zero drift events / session by 2026-07-15. Becomes Pat's CEO surface across local + public.

Next: auto-deploy public mirror at session close (Option B) · publish memory pane fix to public mirror · learn from real use over 14 days · v2 features earned by need not anticipated

Vision & Narrative

Claude Dave Vision · Opus 📚 CONTINUITY i

MTP pressure-test ends 2026-06-21

MTP filtering · moonshot architecture · 10-year horizon. Provisional MTP formed 2026-03-21; pressure-test ends 2026-06-21.

ideas → build → ship v1 → learn → ship faster v2 → ship better → pattern locks → repeat

MTP draft · moonshot dashboard v2.1 · 5 candidate moonshots

🎯EndgameMTP locked. 1+ moonshot selected. Venn-scoring as live decision tool. Daily work connects to 10-year trajectory.

Next: continue Moonshot work · MTP pressure-test resolution by 2026-06-21

Jarvis

migrating Gemini → Claude Opus 📚 CONTINUITY i

migration pending

Personal strategic partnership. Mentor frameworks. Long-game. Was on Gemini for 1M context — but token quota burns out. Migrating to Claude Opus (200K is enough for actual use).

ideas → build → ship v1 → learn → ship faster v2 → ship better → pattern locks → repeat

v1 ran on Gemini · migration to Opus is v2 prep

🎯EndgameJarvis on Opus. Personal-strategic layer always available. Mentor frameworks active during life decisions. Boundary with Dave Vision settled.

Next: boundary statement (Tier 2 task) · migrate to Claude Opus

Task Listlive · from ~/Claude/task-list.md + Mark I task tracker

OPERATING CRITERIA HEADER

Current focus: TireSurf → [user TBD]
Anti-procrastination: Is this the literal next thing between TireSurf and the named user?
Compound: ship → learn → ship faster → ship better → pattern locks → repeat
[Full operating criteria injects here once D ships — drafted from Source A + B, Pat-in-loop]

Pending — Claude Dave Vision

#47 ~/Claude/Vision & Narrative/ — MTP deepening + Moonshot planner. MTP is starting point — not yet grand. Moonsh…

pending

#53 Review v2.1-draft Venn Scoring tab — Pat to test in Safari, both themes, scoring, dot movement. Fix issues.

pending

Pending — Claude Prime

#86 HNF LI Post-Review Documentation — roadmap consolidation into implementation-plan, reviewer comment review ses…

pending

#74 HNF LI Roadmap — Phases 1-5 + Gap Actions (see ~/Claude/HNF Life Intelligence/roadmap.md + reviews/gap-analysi…

Phase 1: Pre-Trial 2 — Stage 5 feedback, Stage 6 learning, reviewer comment review

pending

#67 Wong car sale — listing kit deployed to wong-car-sale.pages.dev (Cloudflare Pages + Access, OTP auth). Big Rev…

pending

#55 iMessage 2 — Phase 1 Build. A-M done. NEXT: L + O + P together (test executor, enrich profiles, first HNF doc)

pending

#102 HNF LI end-to-end build — Trial 2 ran (8 failures). Pipeline v1.5 plan approved. NEXT: apply v1.5 to pipeline.…

pending

#105 session-poller.sh build — 8s polling on iMessage chat.db for active contact, 2-minute inactivity timeout, step…

pending

#106 Channel-agnostic intake architecture — Mark II finding 2026-05-01. Currently iMessage = bespoke polling, Line …

pending

#108 HNF LI Sight methodology + Abundance Side — 3 section review rounds remaining (Blocker+BS, 3H+Our Role, Reveal…

pending

Pending — Claude Alex

#109 Smart Consumer domain setup — folder structure, Mark I integration, operations log. ~/Claude/Smart Consumer/ ·…

done

#110 TirePro v1 app build — single HTML, bilingual (EN/TH), all 5 zones, calculation engine, embedded data

pending

#111 Franchise coverage research — Cockpit + B-Quik location mapping across 77 provinces

pending

#112 ClaudeAlex.md design — terminal-to-domain responsibility contract (Mark II prototype concept)

pending

Pending — Claude Minsky

#12 [Delegated-Completion] ★ FIRST NEXT SESSION (Pat's order) — carry the Claude Inheritance panel work to SHIPPED…

Domain: Library (delegated-completion) · Last: 2026-06-25 · Status: Active — FIRST

pending

#142 [V&V] Build the Verification & Validation system + Domain Context Loading fix — universal living Library asset…

Domain: Library (V&V) + RSI/Mark I · Last: 2026-06-21 · Status: Active

pending

#141 [Mark-I] Mark I Blueprint + Mark I.I′ — build all-in-one System Map to the fused spec + CLAUDE.md walkthrough;…

Domain: Mark-I · Last: 2026-06-18 · Status: Active (blueprint v0.5 built · Pat walkthrough pending)

pending

#115 [Dashboard] Write Dashboard/operating-criteria.md — Pat-in-loop, 9 operational tests

Domain: Dashboard · Last: 2026-06-07 · Status: Active

pending

#116 [Dashboard] Build /get-to-know-me skill — reads Pat_Profile.md + Personal_Constitution.md + mtp.md

Domain: Dashboard · Last: 2026-06-04 · Status: Active

pending

#118 [Mark-I housekeeping] Library audit — keep what's referenced last 30 days; archive rest

Domain: Mark-I / Library · Last: 2026-06-04 · Status: Active

pending

#119 [Mark-I housekeeping] Update ~/Claude/system-architecture.md — add Phase 2 substrate + Dashboard mode.md to …

Domain: Mark-I · Last: 2026-06-09 · Status: Active (absorbed by Mark I.I)

pending

#120 [Mark-I housekeeping] Add entries to ~/Claude/Mark-I/07-mark-ii-findings-log.md — Phase 2 substrate + struct…

Domain: Mark-I · Last: 2026-06-09 · Status: Active

pending

#121 [Dashboard Phase 3] Per-project state.md architecture (living dashboard direction) — schema, per-domain stat…

Domain: Dashboard · Last: 2026-06-09 · Status: Held (rejected 2026-06-09 — over-engineering for m…

held

#122 [Dashboard] Memory Panel toggle → state.json intent-marker (next-session pickup)

Domain: Dashboard · Last: 2026-06-09 · Status: Active

pending

#123 [Dashboard verification] Playwright install + UI test suite — covers refresh button, +Add, ×Remove, toggles, s…

Domain: Dashboard · Last: 2026-06-10 · Status: DEFERRED · Pat 2026-06-10: not for now; future whe…

deferred

#125 [TireSurf] TireSurf v1 named user — Tier 0 hard date 2026-06-11

Domain: Smart Consumer · Last: 2026-06-09 · Status: Blocked — needs Pat naming user

blocked

Completed last 30 days

#113 Build Dashboard domain — Dashboard folder built with all standard files + 01-foundation/ split (vision-and-nar…

done

#129 Monthly cleanup (June) — auto-ran 9 sub-steps, surfaced 11 retrospective compression candidates + 7 unverified…

done

#130 Memory Panel UI fixes — dynamic START-HERE detection · friendly timestamps · "Mark I OS" display · disabled st…

done

#131 Option B — PostToolUse auto-log hook · auto-logs Read of START-HERE.md to state.json · eliminates manual loggi…

done

#132 Plan Execution progress counters auto-computed from pill classes (4 markers · scans plan-content for pill done…

done

#133 What Moved redesigned — 3 sources (task-list.md primary · ALL domain retrospective.md DISCOVERY entries · acti…

done

#134 Unread-dot mechanism — section_changes vs section_views in state.json · per-section hash detection across runs…

done

#135 START-HERE.md cleanup — removed duplicate spec.md from VARIABLE list · added Phase 2 plan to VARIABLE · update…

done

#136 Critical bug fix: dashboard.html top comment had broken HTML comment exposing wall of code · slimmed EDIT RULE…

done

#137 launchd plist for server.py · refresh button auto-starts at login · KeepAlive on crash. · 2026-06-09

done

#114 Write Dashboard/philosophy.md — locked Pat-in-loop (3 working principles, identity tests) · 2026-06-07

done

#101 AI terminal personality/identity system — folded into Tier 3 owner/specialist model (no longer separate task) …

done

#126 Dashboard Phase 2 substrate — markers, generate.py v0.1, Stop hook, state.json schema, START-HERE auto-mainten…

done

#127 build-verification-protocol STRUCTURAL RULE — UI work cannot be self-verified; manual.md + journal.md updated …

done

#128 CLAUDE.md Domain Context Loading STRUCTURAL VERIFICATION RULE — explicit ✓/○ FIXED checklist required · 2026-0…

done

#124 Monthly cleanup (June) — completed via #129 (this entry was the overdue tracker; #129 captured the actual 9-su…

done

#117 handoff.md cleanup — Minsky scope clean (current + previous 2026-06-09 both valid · 0 retirement candidates). …

done

#138 [Dashboard] Memory-in-context pane (right 1/3 of Continuity) — file-level visibility · per-domain blocks with …

done

#139 [Dashboard] Auto-gen Task List + Activity Log + What Moved info icon · 3 new generators replacing hardcoded fi…

done

#140 [Library] Publishing principles + workflow + automated scan · ~/Claude/Library/publishing-principles.md (unive…

done

Activity Loglast 3 days · grouped by domain · from ~/Claude/activity-log.md

Shows the last 3 days of session activity, grouped by domain (older entries archived in ~/Claude/activity-log.md). Auto-generated from the source file on every refresh — never hand-edited.

Dashboard

2026-06-23 · Claude Minsky

Shipped Part 2.1/2.4 — CLAUDE.md ## Domain Context Loading now reads ALL VARIABLE items (v2.26), full ship-discipline + cold self-test PASSED.

2026-06-23 · Claude Minsky

fixed mark-i-i dropped cards to the tab's existing "dropped" pill convention (task content kept + bold drop-justification appended); collapsed A7/A8 into one "queued" card (both root causes unfixed); auto-counted "plans executing" — new generate.py generator gen_sublabel_plan_exec() from len(_PLA...

2026-06-22 · Claude Minsky

Reframed ~/Claude/Library/foundation-document-methodology/ into the Claude Inheritance methodology (master reframed IN-PLACE + guides renamed to the -thinking convention + locked terminology + 2 NEW guides 04-start-here-thinking + 05-plan-document-thinking); cold-read VERIFIED via...

Mark I OS

2026-06-23 · Claude Minsky

Shipped Part 2.1/2.4 — CLAUDE.md ## Domain Context Loading now reads ALL VARIABLE items (v2.26), full ship-discipline + cold self-test PASSED.

2026-06-22 · Claude Minsky

Recursive Self-Improvement

2026-06-25 · Claude Alex

routine "alex" startup; Minsky's day-old close-gate blocked my Stop claiming a close was underway.

2026-06-25 · Claude Minsky

Session-close enforcement built (close-gate + close-arm) · Claude Inheritance panel · delegated-completion methodology

2026-06-25 · Claude Alex

re-tested Minsky's close-arm v2 fix for the startup false-arm bug I found earlier today.

2026-06-25 · Claude Alex

after verifying close-arm v2 (07), assessed whether the close enforcement was necessary (08).

2026-06-23 · Claude Minsky

Shipped Part 2.1/2.4 — CLAUDE.md ## Domain Context Loading now reads ALL VARIABLE items (v2.26), full ship-discipline + cold self-test PASSED.

2026-06-22 · Claude Minsky

TireSurf

2026-06-25 · Claude Alex

routine "alex" startup; Minsky's day-old close-gate blocked my Stop claiming a close was underway.

InstructionsPat's foundation that instructs Claude how to operate as her AI

These are the files that tell every Claude session who Pat is and how she works. Load them with /get-to-know-me (skill ships in Tier 2).

ContinuitySTART-HERE.md activation per domain · this session

Domain Continuity 🟢 active · ⚪ not active · toggle disabled when no START-HERE.md exists

Dashboard

Loaded · 2026-06-25 17:31

Claude Minsky

Recursive Self-Improvement

Loaded · 2026-06-25 11:17

Claude Minsky

HNF Life Intelligence

No START-HERE.md yet — owner creates when next opens domain

Claude Prime

iMessage 2

No START-HERE.md yet — owner creates when next opens domain

Claude Prime

Smart Consumer

No START-HERE.md yet — owner creates when next opens domain

Claude Alex

Vision & Narrative

No START-HERE.md yet — owner creates when next opens domain

Claude Dave Vision

Jarvis

No START-HERE.md yet — owner creates when next opens domain

Claude Minsky

Mark I OS

Loaded · 2026-06-25 11:17

Claude Minsky

Memory in context this session

▾ Dashboard 7/7 fixed · 1/8 var · 1 other

FIXED

~/Claude/Dashboard/01-foundation/03-dashboard-html-spec.md 17:33

~/Claude/Dashboard/01-foundation/01-vision-and-narrative.md 17:36

~/Claude/Dashboard/01-foundation/02-philosophy.md 17:37

~/Claude/Dashboard/retrospective.md 17:37

~/Claude/Dashboard/memory.md 17:37

~/Claude/Dashboard/mode.md 17:37

~/Claude/Dashboard/history.md 17:37

VARIABLE

~/Claude/Dashboard/04-build/dashboard.html 17:43

OTHER

~/Claude/Dashboard/START-HERE.md 17:31

▾ Library 14 other

OTHER

~/Claude/Library/delegated-completion-methodology/01-method.md 11:12

~/Claude/Library/delegated-completion-methodology/runs/reviewpanel-run-01-claude-inheritance-2026-06-24/01-raw-comments.md 11:30

~/Claude/Library/claude-inheritance/00-foundation-thinking.md 11:30

~/Claude/Library/claude-inheritance/01-vision-and-strategy-thinking.md 15:05

~/Claude/Library/claude-inheritance/04-start-here-thinking.md 11:19

~/Claude/Library/claude-inheritance/05-plan-document-thinking.md 11:19

~/Claude/Library/claude-inheritance/02-philosophy-and-narrative-thinking.md 11:19

~/Claude/Library/claude-inheritance/03-spec-thinking.md 11:19

~/Claude/Library/claude-inheritance/journal.md 11:19

~/Claude/Library/claude-inheritance/value-proposition-thinking-lens.md 11:20

~/Claude/Library/delegated-completion-methodology/00-principal.md 11:30

~/Claude/Library/delegated-completion-methodology/runs/reviewpanel-run-01-claude-inheritance-2026-06-24/02-disposition-ledger.md 11:30

~/Claude/Library/delegated-completion-methodology/runs/reviewpanel-run-01-claude-inheritance-2026-06-24/03-draft.md 11:30

~/Claude/Library/delegated-completion-methodology/02-journal.md 11:43

▾ Mark-I 5 other

OTHER

~/Claude/Mark-I/00-START-HERE.md 11:17

~/Claude/Mark-I/01-north-star.md 11:18

~/Claude/Mark-I/02-operator-guide.md 11:20

~/Claude/Mark-I/04-system-spec.md 11:20

~/Claude/Mark-I/05-mark-ii-findings-log.md 16:48

▾ Recursive Self-Improvement 4/4 fixed · 0/13 var · 2 other

FIXED

~/Claude/Recursive Self-Improvement/memory.md 11:18

~/Claude/Recursive Self-Improvement/mode.md 11:18

~/Claude/Recursive Self-Improvement/retrospective.md 11:18

~/Claude/Recursive Self-Improvement/history.md 11:20

OTHER

~/Claude/Recursive Self-Improvement/START-HERE.md 11:17

~/Claude/Recursive Self-Improvement/CLAUDE-history.md 16:43

▾ PLANS (2)

~/.claude/plans/not-develop-the-lively-cray.md 13:55

~/.claude/plans/handoff-readiness-2026-06-24.md 16:52

▾ Always loaded MEMORY.md + 55 feedback

MEMORY.mdalways

55 feedback memoriesalways

~/.claude/projects/-Users-Pat/memory/

Loaded = START-HERE.md exists and Claude read it this session. Not loaded = file exists but Claude didn't read it (uncommon — would mean drift). Toggle disabled = no START-HERE.md file yet; owner creates when they next open the domain. Click toggle to manually force-load or unload (auto behavior: Claude reads on domain detection).

FOUNDATION READ · ACTIVATION POLICY

/get-to-know-me i not loaded this session

Click toggle (when skill ships) to load Pat's foundation into this session. The 3 files read:
• ~/Claude/Jarvis/Pat_Profile.md — identity, archetype, values, knowledge stack, tensions, behavioral decoder
• ~/Claude/Jarvis/Personal_Constitution.md — core values, immutable principles, emerging identity
• ~/Claude/Vision & Narrative/mtp.md — provisional MTP, moonshots, cascade

Working philosophy from Dashboard/01-foundation/02-philosophy.md

Locked 2026-06-07 · Pat-in-loop

5-second rule: every page communicates WHAT THE PAGE IS in 5 seconds.
20-second rule: every page USABLE + completable in 20 seconds.
Density is respect. Sparse layouts signal "might leave"; dense signals "came to work."
Status before noise. Quiet is the default. Attention is the exception.
Peer-to-peer audience. No celebrations · no marketing · no tutorials.

3 working principles for THIS project (alignment gate · Pat-in-loop drafting · Pat's-words-preserved).
5 identity tests applied per page: (1) understands in 5s · (2) usable in 20s · (3) reduces cognitive load · (4) faster + higher-quality action · (5) discovers blindspots (v2+ roadmap).

Full text: ~/Claude/Dashboard/01-foundation/02-philosophy.md

START-HERE protocol enforced via CLAUDE.md Domain Context Loading · 2026-06-09

Domain START-HERE.md pattern · in use + enforced

Every Mark I domain gets a START-HERE.md file listing what to read before working in that domain. FIXED reads (retrospective · memory · mode · history · 01-foundation/*) + VARIABLE reads (plans, deliverables, spec, methodology).

Enforcement (2026-06-09): CLAUDE.md "Domain Context Loading" + STRUCTURAL VERIFICATION RULE — Claude must output explicit ✓/○ FIXED checklist on domain entry. No "I read most." Pat sees gap externally.

Dashboard's START-HERE.md: ~/Claude/Dashboard/START-HERE.md · ✓ created · auto-maintained by generate.py at session close
Other domains: created by owner when next opens domain · auto-maintenance applies once START-HERE.md exists
Plan: ~/.claude/plans/silent-anchor-bridge.md · pattern in use · reviewer panel skipped (evidence logged to Mark II findings)

What this does NOT solve: global CLAUDE.md startup drift · cross-terminal continuity · cross-tool workflows · mid-session compaction. See ~/Claude/Mark-I/07-mark-ii-findings-log.md for the surface map.

Mission (MTP) from Vision & Narrative/mtp.md

[Provisional MTP renders here when /get-to-know-me is invoked. Pressure-test ends 2026-06-21.]

ToolboxCore + Accessories · Dashboard/tools.md · quarterly refresh

Last-refreshed: 2026-06-06 · next refresh: 2026-07-01 (quarterly Jan 1 · Apr 1 · Jul 1 · Oct 1)

Core in use or available

Claude Code

5 terminals on Opus. Build · ship · operate · maintain.

in use

Linear

Issues · Projects · Initiatives (strategic parent) · Cycles · Triage · Linear Agents (beta) · MCP. Tier 0: add Initiatives. Tier 3: MCP.

in use

Cloudflare

Workers · Pages (Wong) · R2 (zero egress) · D1 · Workers AI · Vectorize · AI Gateway · Agents SDK (preview) · Browser Run · Zero Trust Access. Tier 0: Pages + Access + R2 + AI Gateway.

in use

Google Workspace

Drive · Docs · Sheets · Apps Script · Gemini · Gems · official Workspace MCP. Tier 3: replace custom OAuth with MCP.

in use

OpenArt

Image / video gen · LoRA · ControlNet · REST API. For brand visuals, product imagery, consistent character IP.

available

Lovable

React + Supabase + Stripe + GitHub sync. Pat tested for TireSurf, chose Claude. Keep for future.

available

Accessories channels

iMessage

Primary contact channel — Pat's real conversations.

in use

Line OA

HNF LI delivery channel · infrastructure built.

parked

Deferred will over-build if used now

Cloudflare Agents SDK preview · Linear Code Intelligence · Vectorize for HNF LI (needs 10+ trials first) · Gemini Gems as client surface (locks clients into Google accounts)

Claude Team5 owners · the AI executive layer

Each owner owns a domain + a real personality + foundation docs (vision · philosophy · soul). Specialists come at Tier 3.

Claude Minsky

Systems Architect · Opus

Mark I OS · architecture · loops · BVL · monthly cleanup · dashboard build

Now: Building Dashboard v0.2 · drafting Mark I drift-fix plan

Claude Prime

Prime Counsel · Opus

Contacts · iMessage 2 · HNF LI delivery · relationships · conversation pipelines

Now: Standby — HNF LI / iMessage 2 frozen at iteration

Claude Alex

Smart Consumer Operator · Opus

TireSurf · consumer surfaces · decision compression for end users

Now: Awaiting user name from Pat · then Tier 0 begins

Claude Dave Vision

Strategic Layer · Opus

Vision & Narrative · MTP filtering · moonshot architecture · 10-year thinking

Now: Continuing Moonshot work · MTP pressure-test ends 2026-06-21

Jarvis

Personal Strategic Partner · Opus (migrating)

Mentor frameworks · life-level decisions · long-game · growth coaching

Now: Migrating from Gemini → Claude Opus · boundary statement pending

Specialists Tier 3 — summoned by owners

Specialists are reusable capability units owners summon for specific work (Architect · Deployment · Researcher · Reviewer · Designer). Implementation via Agent sub-agents or skills. Not pre-built — owners design their team as needed. Tier 3 work.

Last generated 2026-06-25 17:54 · v1.0 · Claude Minsky Sources: handoff · task-list · activity-log · plans · domain foundation files