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/protocols/. Create ~/Claude/claude-mode.md as 3rd-tier universal behavioral mode between constitution (values) and per-domain mode.md (specialized). Mark I.I, not Mark II — same OS: BVL, 6 loops, 4-file domain pattern, all features unchanged. Protocol restructure + behavior synthesis only. V3 adversarial validation complete (3 Opus agents): 285 rules inventoried, 26+ files for update, 10 behavioral patterns (Behaviors + Production Aesthetics). Plan-plan finalizing · 3-reviewer panel pending before execution.•
~/.claude/plans/mark-i-overhaul-2026-06-10.md (active plan · risk per step · V1-V5 + T1-T7)•
~/Claude/Mark-I/overhaul-2026-06-10/v3-agent-1-rule-inventory.md (285 rules)•
~/Claude/Mark-I/overhaul-2026-06-10/v3-agent-2-structural-references.md (20 findings · 8 missing files)•
~/Claude/Mark-I/overhaul-2026-06-10/v3-agent-3-behavioral-coverage.md (10 patterns)• Backup:
~/Claude/Mark-I/backups/mark-i-operation-backup-2026-06-10.tar.gz · 250MB · delete-by 2026-07-10Continuity Surfaces · Analysis + Parked Sequels — see "Branch — Continuity Surfaces" section in the plan file. Per Pat 2026-06-10: a plan branch lives in the parent plan, not as a separate file. Only Surface 1 needs solving (Mark I.I); Surfaces 2/3 parked as triggered candidates; 4 owned by Foundation Doc stream; 5/6/7/8/9 excluded.
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 — Kernel Split + Universal Behavior Mode. 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). Mark I.I, not Mark II — same OS (BVL, 6 loops, 4-file domain pattern, all features unchanged). Closes Surface 1 (cross-session, same terminal) per continuity analysis. Plan file: ~/.claude/plans/mark-i-overhaul-2026-06-10.md
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.
Task 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-11 16:32 · v1.0 · Claude Minsky
Sources: handoff · task-list · activity-log · plans · domain foundation files