Snapshot of the three tracked domains. Full detail on the Nodes tab; what changed and when on Version History.
Every tracked node, grouped by domain. version_added marks which dashboard version first surfaced it.
One entry per check that produced a real change. INIT first build · PATCH a node updated · MINOR a node added or structural change · NOOP checks (nothing changed) are logged to the refresh log only, not here, to keep this list signal-only.
A complete file-based agentic operating system, from a Karpathy-pattern seed to an externally-benchmarked, multi-machine fleet. Click a phase to see its milestones.
Plain markdown on local disk, governed by a two-level router. Everything reads from a three-file session start, routes down to content, and syncs off-machine.
claude-system-architecture.md (SYS02, Jun 13) still describes the deprecated checkpoint system and a 9-task fleet. This dashboard reflects the current state; SYS02 should be refreshed.Copying files reproduces the library. Adopting these fifteen findings reproduces the system. Ordered by leverage; gold = highest.
Two paths. Clone Dean's exact KB for a same-operator machine, or fresh-build the architecture for a separate persona with its own data.
2026-06-29 external benchmark, 33 sources, 7 parallel research agents. Parity-to-ahead of the published frontier on the core stack; ahead of the entire creator market.
What the system saved, what it costs to run, and what a comparably-skilled engineer would spend to build it from scratch. No raw billing telemetry exists — credit figures are a transparent model (frequency × model tier × token cost), labeled measured / modeled / estimated, now anchored to periodic real Settings > Usage readings starting 2026-07-10.
~440 man-hours (280–660) = 2.2 FTE = ~$23.5K wages avoided in 5 weeks. Top roles: Software Dev + Knowledge Manager — not admin. (OP13)
The recurring operation displaces ~$150K–$250K/yr in labor once one-time build spikes are stripped.
Same output ordered from agencies: $70K–$236K (mid ~$150K). The Gravitas platform drives the high end.
Comparable-skill solo engineer to reproduce the apparatus: ~460 hrs (300–630) × $100–175/h = ~$60K ($30K–$110K), 3–6 months. Actual: ~150 operator-hrs + ~$300 tooling → ~3× compression, >95% cash saving.
Settings>Usage read 26% weekly / Fable 0%. Turn-weighted attribution: ONE browser-automation session (character factory, 350 turns) ≈ 48% of that week's usage alone — 9× past its 40-call checkpoint threshold, none fired. Formula k≈0.0118%/weighted-turn calibrated from this reading — provisional, not a cardinal rule. Full detail: CL07 claude-session-load.md; trend: outputs/usage-capacity-ledger.md.
The census above first shipped historical turn counts marked "not measured, too costly" — untested, and wrong; 3 real read_transcript pulls came back cheap. Found: at least one session_id spans multiple day-resets (session_id ≠ work-unit). Fix rolled forward into planning: weekly-review-friday Step 4C computes a weekly capacity budget/headroom; daily-briefing's Monday run surfaces it (no re-computation). Full diff for Jim: outputs/jim-update-audit-2026-07-10.md.
~25 long Sonnet runs/week (curiosity, kaisen, youtube, claude-opt). #1 recurring sink.
browser_batch embeds base64 images — ~10× a text-tool flow. #1 per-session burn.
~7× token multiplier. Powerful fan-out, priciest per unit of work.
~22K tokens across 4 core files × ~20 daily runs = a fixed daily floor. (Halved by CLAUDE 512→265.)
Highest per token, low frequency (Gravitas strategy, decisions, contradiction resolution).
Haiku mechanical tasks, disabled one-time reminders (zero cost), routed pointer-memory, short briefings.
Text-tools over screenshots (~10×) · JIT routing (~4.7K tok/session) · CLAUDE 512→265 (~½ read cost) · spent-output pruning · Advisor (11%) · suppress-explanations (30–50%) · no vector DB · task condensation · lane system (kills re-read waste).
Done 2026-07-01: nightly research consolidated (4→1) · frequency-tuned (YouTube + Claude-opt → M/W/F) · JIT loading rule. Remaining: Haiku-first (interactive / API only — no model param on tasks) · n8n/API migration (tabled) · skill-chains (already CL03 standard).
The live two-panel map: Panel A the operating architecture as a labeled concept map, Panel B the FULL KB content graph — every tracked .md file in the KB, not just registered wiki articles — grouped by topic, Canvas-rendered for scale. Regenerated 2026-07-17 (Dean-requested deep audit: the prior graph only covered ~242 registered wiki articles and was silently missing the entire CL/Claude-Optimization domain; rebuilt to cover the full KB per Dean's directive). If the frame is blank, open system-concept-map.html directly (it sits beside this file in outputs/).
Content graph (FULL KB, 2026-07-17): 1,524 files · 4,903 links · 155 hubs · 510 isolated (no detected cross-refs — mostly changelog-lane archives and raw source dumps) · 33 topic clusters. Architecture map: 31 nodes / 7 subsystems. Source builders: outputs/build_full_kb_graph.py + outputs/build_system_concept_map.py.