Your system now holds context and learns weekly. Two jobs remain, forever: keep it lean, and make it grow. Fifteen minutes every Sunday covers the first. Modules 4 and 5 are the second.
MAINTAIN · WHY
From 30 Files to 3,000
Mine grew from ~30 files to 3,123 in three months. You cannot load it all, and you should not.
Growth is not the problem. Silent rot is: stale indexes, duplicate files, loose ends left in chat.
📎 Count: one builder's live vault, Jul 2026, archive excluded.
MAINTAIN · SAME PROTOCOL, NEW FOLDER
One Index Per Folder
The CONTEXT protocol from last deck, now on projects/: exactly one index, everything listed, one line each. Unlisted = invisible.
Same rule, every folder, forever. A trigger word checks any folder against its index.
📎 The 3-layer canon from last deck, enforced. Index sizes: small folder = 10 lines, my network folder = 2.4k tokens.
MAINTAIN · THE ROUTINE
Fifteen Minutes Every Sunday
Four moves, AI-prepared, you judge: review the week · approve the focus update · archive what finished · check the size budgets.
Mine arrives inside the Sunday email from last deck. Three replies from the phone, ~12 minutes.
📎 Weekly-review skill: materials/library · budgets: ~1,000 chars per life area, ~14 KB focus total · overflow → dated logs, never deleted.
MAINTAIN · DAILY
Close Every Session
Chat is where decisions go to die. Before ending a work session, the AI answers two questions: does any index need updating? does the focus file need updating?
Mine is a trigger word. Clean exit or a numbered list.
📎 My trigger: one word at session end. Cost: ~30 seconds when clean.
AUDIT 1 OF 2 · THE MACHINERY
The System Audit
Monthly, the AI audits its own machinery: what loads and what it costs · skills used and unused · every tool tested live · security holes · honest comparison with the field.
Run a full audit of my second brain. Work in parallel agents if you can.
1 MAP — What is this system? Which files load automatically at session
start? Measure each in tokens. Lean or bloated, current or stale, and
do any two contradict each other?
2 SKILLS — List every skill/trigger. Which were unused for 30+ days?
Compared to what people publicly build today, name up to 3 I lack.
3 TOOLS — List every connected tool: MCP servers, APIs, scheduled jobs,
channels. TEST each one live. Flag broken jobs, dead keys, silent
channels, tools connected but never used.
4 SECURITY — Where are the holes? What can connect from outside? Which
credentials sit in plain text? Which tools can write or send
externally without my approval? What would you tighten first?
5 COMPARE — Against the current state of the art, where am I behind?
Report the five sections, then TOP 5 FIXES ordered by impact.
Read-only: change NOTHING in this run.
📎 Run it on the strongest model at maximum thinking, parallel agents on. Mine took ~30 min on ChatGPT and ~50 min on Claude Code. Full skill: library/system-audit.md
AUDIT 2 OF 2 · THE WRITING
The Content Audit
The librarian pass: every folder has one honest index · constitution measured against its own token budget · all 5 layers present, nothing leaked between them · focus file matches reality.
Audit the CONTENT of my second brain, not the machinery.
1 INDEXES — Walk every folder holding more than a handful of files.
Each must have exactly one index file. Flag folders with none,
folders with two, and orphan files listed in no index.
2 CONSTITUTION — Measure every always-loaded file in tokens. Compare
against the budget written in the constitution itself. Flag stale
dates, ended projects, statements a newer file contradicts.
3 FIVE LAYERS — Constitution, memory, skills, tools, focus: each
present, findable, current? Flag content leaked into a wrong layer.
4 FOCUS — Does the focus file match reality? Dead dates, finished
projects still listed, new work it never mentions?
Report per folder, one line each: OK or the finding.
End with one list: MERGE / ARCHIVE / REWRITE, one line per item.
Propose only. Change NOTHING yet.
📎 Same rule: strongest model, maximum thinking, 30 to 50 minutes. Full skill: library/content-audit.md
GROW · WHAT COMES NEXT
The Growth Ladder
Four rungs. Each one stands on everything below it, and each adds cost that must pay for itself in time or revenue.
The next five slides show the top rung in practice: machines built on a second brain that people pay for.
Client calls live in the brain, analyzed. From them: a one-page brief in the client’s own words. An app builder ships the site from that brief.
I shipped my agency’s site this way, bilingual, in days.
📎 Pipeline: call analysis (M4 skill) → brief → app builder (Lovable or similar) → live site. Own build, Jul 2026.
GROW · EXAMPLE 2 OF 5
An SEO Content Machine
The brain holds the client’s voice file, offer, and keyword list. A weekly job drafts posts in that voice against those keywords.
You review once, it publishes. Ten drafts, one sitting.
📎 Common agency build: voice + keywords in memory layer, scheduled drafting job, human approval gate before publish.
GROW · EXAMPLE 3 OF 5
A Personal Data Dashboard
My training dashboard: watch data lands every night, a job rebuilds one web page, my AI reads the same numbers I see.
Same pattern sells as client work: any data feed → a living page.
📎 Own build: nightly sync from a sports watch API → static page on free hosting → the brain reads it for the weekly review.
GROW · EXAMPLE 4 OF 5
This Course Site Itself
Every deck, template and skill file on this site is written, checked and deployed by my second brain, agents in parallel, me approving.
You are looking at the proof right now.
📎 loai.wisdomblend.com: vault → parallel agents (research, build, verify) → git → deploy. Human gate before every publish.
GROW · EXAMPLE 5 OF 5
Your Own Product
A game. A micro-SaaS. An MCP server other people install. The brain holds the design doc, user feedback, and roadmap; agents build against it.
The second brain is the co-founder that never forgets.
📎 Pattern across indie builders 2025-26: solo founders shipping games and SaaS with agent teams; the design doc in the brain is the single source of truth.
CLOSING
Next: Module 4
Maintenance: 15 minutes on Sunday, sessions closed clean, two audit prompts a month. Growth: Module 4 starts with the tool list and the first skills you build yourself.