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.
/ Amplio internal onboarding · use → to advance
/ 01 — Why a vault
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
/ 02 — The stack
Raw is immutable ground truth. Wiki is compiled, structured, interlinked. Schema is the rule book that governs both.
| Layer | What it holds | Home |
|---|---|---|
| L1 · Raw | Raw sources — articles, PDFs, transcripts, web clips. Immutable after capture. The ground truth every compiled note traces back to. | 00-Inbox/raw/ |
| L2 · Wiki | Wiki — atomic Galaxy notes: one idea, ≤300 words, ≥1 wikilink. Plus playbooks, templates, brand, skills. | 05-Galaxy/ · 03-Resources/ |
| L3 · Schema | Schema — the rules: routing, behaviour, priorities, commands. Every session reads this first. | CLAUDE.md · program.md |
/ 03 — Folder tree
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.
/ 04 — Routing
| Input | Destination | Rule |
|---|---|---|
| Unsorted thought | 00-Inbox/Brain-Dump.md | |
| Article / PDF / transcript | 00-Inbox/raw/ | Never edit after capture. |
| Work with a deadline | 01-Projects/Active/ | |
| Ongoing responsibility | 02-Areas/ | |
| Playbook / template / SOP | 03-Resources/ | |
| Atomic concept | 05-Galaxy/ | One idea per note. |
| Client work | 06-Clients/[name]/ | |
| Amplio's own work | 02-Areas/Amplio-Internal/ | Amplio is not a client. |
Amplio is never saved under 06-Clients/ — Amplio is not a client. Routing rule, non negotiable.
/ 05 — Hub graph
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.
Spine — session continuity. Read first, written last.
Concepts — atomic notes. The wiki proper.
Skills — Claude skills, callable on demand.
SOPs — playbooks and guides.
Clients — every client space, indexed.
Prospects — scored leads, stages, next actions.
Retired — notes retired from the active graph.
/ 06 — Client spaces
Every client space is scaffolded from the template under 06-Clients/[name]/.
Per client hub: status, contacts, signals, health. Always update it first.
Connected sources, schemas, metrics.
Closed loop log of advice given.
Dated notes, one per meeting.
Monthly + ad hoc deliverables.
Active today: 8 client spaces (direct + agency partner) — Certify Education · Odisei · Code & Wander · Birdie · The Lily Effect · Cropple · Instalat · Rapid Agency · end clients via the agency partner (Malone, Devenish, Alternative Energy, Capper Trading) live under Rapid Agency
/ 07 — Scheduled tasks
The old standalone task fleet is consolidated into four cron orchestrators — each phase inside them touches the vault for a different reason. Deck 13 is the full map.
Access sweep, update_ email routing, every dashboard regenerated and redeployed. Six fires a day, idempotent.
The heavy run: feedback sync, client data pull, vault-autoresearch (Phase I), learning sync, backup, hygiene, Monday exec briefing.
Prospect discovery to verified send, Attio sync, one consolidated summary email a day.
Day gated: Wednesday runs the Certify ads experiment, the 1st of the month ships the Certify monthly report.
Execution order and every phase map live in scheduled-tasks-reference.md; dashboards.md is the surface registry deploy-cycle reads.
Recurring manual work never stays manual — it gets folded into a cycle as a new phase, never a new orchestrator.
/ 08 — Autoresearch loop
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.
Context → compile raw → orphan fix → inbox routing → structural · learning · wrap. The standalone task is paused; its folder stays the instruction source.
The orphan script targets 0/0/0 every run. Learning lint confirms every active client has Health + Signals + tracker.
Galaxy notes, playbooks, templates, skills — the whole graph, linted daily. Counts as of 2026-06-29.
The score decides when the loop runs again.
/ 09 — Behaviour rules
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, with a data-context.md — API or manual.
#vault-queries answers ≤8 lines with sources, never writes. No revenue, entity IDs, contacts, scores, contracts or raw notes in Slack.
Prose for humans passes through humanize-writing before it ships, and never carries the hyphen character — em and en dashes only.
Artifacts ship on Workers + KV behind Access via deploy.sh. Dashboards default to the Mixpanel grammar.
No unverified absence claim leaves the vault. Newer guidance beats older. Diagnose the cause before the fix ships.
/ 10 — The vault dashboard
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.
Recurring revenue (MRR) · client health (score, band, lowest first) · recommendation loop (open vs actioned) · active projects (P0 / P1 / P2, overdue flagged) · pipeline top 20 (HIGH / MID / LOW).
Morning: open the dashboard before anything else. Health band < 70 → flag the client. Recommendations stuck → update_ email with the next action. Numbers look wrong → submit the feedback form.
Worker amplio-vault-dashboard at ops.ampliodata.io (fallback amplio-vault-dashboard.round-star-123d.workers.dev). KV namespace dd432f3c01cf42af871b5f8d18892a5b. Access: hello@, alana@, daragh@, jule@ via One Time PIN (24h session).
deploy-cycle Phase D redeploys it every 4 hours, six fires a day. On demand, from 01-Projects/Active/Internal/vault-dashboard/: python3 generate.py && ./deploy-check.sh && ./deploy.sh
forms.gle/Bcs52Zjd7qsyuJuv8 — one atomic signal per submission: Correction · Gap · Confusion · Contradiction · Example. Submissions flow back into vault lint + autoresearch.
The dashboard is read only. Writes flow only through update_ emails. Feedback on what the dashboard shows flows through the form. Nothing crosses the line.
/ Keep it alive
Claude reads it, writes to it, keeps it alive. Three habits make that true for every session.