A version-controlled Second Brain for the whole company — built on the Karpathy LLM-wiki pattern. Raw sources compile into a structured wiki, governed by a schema. Claude reads it, writes to it, keeps it alive.
Every change auditable. No "who edited this?" mysteries.
Concepts connect. The graph is the product — not the files.
Reads schema, executes commands, compiles raw into wiki, lints the whole.
The vault is the operating system. The behaviour rules are the kernel. Claude is the shell.
Three layers, each with a distinct job. Raw is immutable ground truth. Wiki is compiled, structured, interlinked. Schema is the rule-book that governs both.
00-Inbox/raw/
Articles, PDFs, transcripts, web clips. Immutable after capture. The ground truth every compiled note traces back to.
05-Galaxy/ · 03-Resources/
Atomic Galaxy notes — one idea, ≤300 words, ≥1 wikilink. Plus playbooks, templates, brand, skills.
CLAUDE.md · program.md
The rules. Routing, behaviour, priorities, commands. Every session reads this first.
Capture lands here. Raw sources in raw/ (immutable).
Time-bound work with a finish line.
Ongoing responsibilities — Ads, Analytics, Sales, Amplio-Internal.
Brand/ · Playbooks/ · Templates/ · Research/ · Skills/
Completed projects. Retired notes.
Zettelkasten — atomic concept notes, wikilinked, one idea each.
Per-client spaces + _Prospects/ pipeline.
Schema + session continuity at the root. Loaded every session.
Amplio is never saved under 06-Clients/. Amplio is not a client. Routing rule, non-negotiable.
Every note links to at least one hub. Hubs are the spine — indexes of indexes. That makes the wikilink graph navigable, not just a pile of files.
Session continuity. Read first, written last.
Atomic notes. The wiki proper.
Claude skills, callable on demand.
Playbooks and how-tos.
Every client space, indexed.
Scored leads, stages, next actions.
Notes retired from the active graph.
Active today: 7 client spaces (direct + agency partner) — Certify Education · Odisei · Code & Wander · Birdie · The Lily Effect · Cropple · Rapid Agency. End clients contracted via an agency partner (Malone, Devenish, Alternative Energy) live under Rapid Agency, not as separate Amplio clients.
Weekly exec readout.
Pulls yesterday + 28d trailing.
Confirms API access across clients.
Triages update_ emails.
7-phase compile · lint · enrich.
Partner-specific sync.
Client monthly report.
Signals · health · 1a→1d measurement.
Experiment-planning pass.
Keeps the portable fleet pack in sync.
The vault is live. Raw sources compile into Galaxy notes. Broken links and stale content get linted. Thin notes get enriched. A health score decides when to run again.
Search the vault before advising. Never recite from memory. Only cite the proof points in CLAUDE.md.
Clients link to Galaxy, Galaxy links back. Every session leaves it richer. Clarify ambiguous commands.
Every note has a Related section with ≥1 hub wikilink. Autoresearch hits 0/0/0 every run.
Amplio Updates emails rewrite overview, pipeline, index. Every triage decision logged for classifier training.
Recommendations tracked. Signals extracted. Contradictions downgrade pattern confidence.
Every active client scored. Every active client has a data-context.md — API or manual.
The Vault Dashboard never writes. No revenue, tax IDs, contacts, scores, contracts or raw notes leave the vault.
Emails, posts, proposals, reports — always pass through the humanize-writing skill before shipping.
Before the dashboard, "where are we with Odisei?" meant opening Obsidian, clicking through four folders, doing mental math. Now everyone reads the same snapshot without asking each other.
update_ email with next actionamplio-vault-dashboardops.ampliodata.io (fallback amplio-vault-dashboard.round-star-123d.workers.dev)dd432f3c01cf42af871b5f8d18892a5bhello@, alana@, daragh@, jule@ via One-Time PIN (24h session)daily-vault-dashboard-refresh · 08:15 + 17:15 local01-Projects/Active/Internal/vault-dashboard/python3 generate.py && ./deploy-check.sh && ./deploy.shforms.gle/Bcs52Zjd7qsyuJuv8 — one atomic signal per submissionThe boundary. Dashboard is read-only. Writes flow only through update_ emails. Feedback on what the dashboard shows flows through the form. Nothing crosses the line.