Dashboard2026-06-08 · Claude Minsky · v1.0
Plan Listauto-listed from ~/.claude/plans/
Every plan Claude creates appears here. New plans appear automatically when generate.py runs. Use the controls below to manually add a plan from any path, or hide a card.
•
~/.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)
•
~/.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)
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/07-mark-ii-findings-log.md.•
~/.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)
~/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.~/Claude/Mark-I/08-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 — #1: drop Step B; add external ship clock (TireSurf → 1 user by 2026-06-27) before any restructure•
04-panel-miller.md — #1: drop Step B; add ORIENT block at session open + per-terminal 9-line identity cards•
05-panel-wissner-gross.md — #1: drop Step B; add retirement primitive (every rule gets a death condition) before any structural layer•
06-08-v3-*.md — V3 adversarial agent reports (285 rules · 26+ refs · 10 patterns)~/.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~/Claude/Mark-I/backups/mark-i-operation-backup-2026-06-10.tar.gz · 250MB · delete-by 2026-07-10
Plan Execution3 plans executing
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.
Tier 0
Tier 1
Tier 2
Tier 3
Verification checkpoints
○ 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
Branch 1 — Domain reads + Verification
Branch 2 — Docs (after Branch 1)
Decisions + locks (this work)
Verification checkpoints
✓ 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
| # | 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
| 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/room/curiosity | 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
✅ DONE
⏳ QUEUED
❌ DROPPED
Kill condition
Panel reviews
~/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 structureAll 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 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
Phase 2 — Build & Deploy
Phase 3 — Post-Deploy Verify
Phase 4 — Harden
Validation strategy
Post-implementation testing
Next move
~/.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
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.
Infrastructureinternal · the systems we run on
What we build for ourselves. Same Blundin phase train, current phase highlighted.
~/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 AlexTask Listlive · from ~/Claude/task-list.md + Mark I task tracker
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
Pending — Claude Prime
Pending — Claude Alex
Pending — Claude Minsky
Dashboard/operating-criteria.md — Pat-in-loop, 9 operational tests/get-to-know-me skill — reads Pat_Profile.md + Personal_Constitution.md + mtp.md~/Claude/system-architecture.md — add Phase 2 substrate + Dashboard mode.md to …~/Claude/Mark-I/07-mark-ii-findings-log.md — Phase 2 substrate + struct…state.md architecture (living dashboard direction) — schema, per-domain stat…Completed
Activity Loglast 3 days · grouped by domain · from ~/Claude/activity-log.md
Dashboard
Mark I OS
Recursive Self-Improvement
TireSurf
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).
Continuity
Domain Continuity 🟢 active · ⚪ not active · toggle disabled when no START-HERE.md exists
Memory in context
•
~/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
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
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 closeOther 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)
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
Accessories
Deferred
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.
Specialists
2026-06-13 17:17 · v1.0 · Claude Minsky
Sources: handoff · task-list · activity-log · plans · domain foundation files