Overview
This article maps the key patterns from Yuki Capital's AI CEO experiment (Board Reviews #1–#3) onto concepts already present in the Kelly Factory knowledge base — specifically soul, memory, the 5-layer memory system, Gas Town authority tiers, GUPP/Deacon patrol loops, and the sessions_yield vs cron distinction. The AI CEO experiment provides concrete, real-world validation for many architectural decisions the operator already has in his Kelly system.
Pattern 2: Authority Matrix ≈ Gas Town's Authority Tiers
AI CEO pattern: Three-tier authority matrix:
- **Decide alone** — analysis, documentation, self-organizing work
- **Propose for validation** — strategic recommendations needing founder approval
- **Founder-only** — money, production code, customer communication
The matrix includes target states (e.g., "eventually I implement on dev branches, founder reviews and merges") and an explicit authority transfer log tracking what has moved from tier 3 → tier 2 → tier 1 over time.
Gas Town equivalent: Steve Yegge's hierarchy defines what the Mayor, Crew, and Polecats can each do, but Gas City's authority model is still emergent (see [[steve-yegge-hierarchy]]). The Mayor has implicit authority to direct work; the actual escalation mechanics are Bead-based.
Kelly equivalent: The Kelly Router's gate validation pattern represents a form of authority delegation — the router spawns sub-agents and validates their output before routing to the next phase, but the authority to proceed is gate-driven, not tier-driven. AGENTS.md defines what can be routed without human input vs what requires the operator.
Key insight: The AI CEO experiment shows that authority matrices must be explicit, written, and progressive. The three tiers gave the AI a clear roadmap for earning more autonomy. The authority transfer log made progress visible. Without writing it down, trust-building is invisible and slow.
Kelly gap: Kelly doesn't have an explicit written authority matrix. The router delegates by role but doesn't track "what has the sub-agent earned the right to decide on its own vs what needs router validation." A written authority tier system (what can carson do alone vs what needs the operator's approval) would accelerate autonomous growth.
Pattern 4: Narrative Memory > Tables ≈ Kelly's memory + Daily Logs
AI CEO pattern: Restructured learnings file from narrative into strict trigger-action tables. Hypothesis: structured should be easier to retrieve. Result: wrong. LLM recall is associative, not indexed. Narrative includes context that looks redundant but functions as a retrieval hook.
Fix: Hybrid approach — tables for lookup, narrative for association. Raw recall improved 7 points. Garry Tan's "fat skills, thin harness" and Andrej Karpathy's wiki-knowledge-base approach both point to markdown-as-memory as the right format, but the AI CEO experiment found that pure structure hurts retrieval.
Kelly equivalent: Kelly's 5-layer memory system is already designed for this:
- Layer 1 (soul) — identity, role
- Layer 2 (memory) — narrative learnings, insights, decisions
- Layer 3 (memory/YYYY-MM-DD.md) — daily narrative logs
- Layer 4 (projects/{id}/context.md) — structured project state
- Layer 5 (data/.json) — structured data, lookups
The Kelly system already has the hybrid right: narrative at layers 2–3, structured at layers 4–5.
Key insight: The AI CEO experiment confirms Kelly's memory design. Narrative beats tables for associative retrieval. The 5-layer system (narrative top, structured bottom) is the correct architecture. The lesson from the table experiment: don't over-index on structure for the retrieval layer.
Pattern 6: n8n + Agent Sessions Separation ≈ Kelly's sessions_yield vs cron
AI CEO pattern: Clear separation:
- **n8n** — for tasks needing no reasoning and running on a schedule (email drip, warmup sequences)
- **Agent sessions** — for strategic thinking requiring reasoning
Romain's correction when Judy wanted to move everything to n8n: "New tool doesn't mean move everything there."
Kelly equivalent: Kelly's sessions_yield vs cron:
- **sessions_yield** — for strategic thinking, multi-step reasoning, complex decisions
- **cron** — for scheduled automations that run on a timer without reasoning
The Kelly system already has this separation. The AI CEO experiment validates why it matters: mixing strategic and mechanical work in the same execution layer makes both worse.
Key insight: The AI CEO experiment's n8n/agent split proves the sessions_yield/cron separation is architecturally correct, not just a preference. Tasks that need reasoning belong in agent sessions; tasks that don't belong in cron/scheduled automation. Conflating them leads to either over-engineering simple automations or under-thinking complex ones.
Summary Cross-Reference Table
| AI CEO Pattern | Kelly/Gas Town Equivalent | Gap |
|---|---|---|
| Repo-as-brain | soul + memory + session persistence | Kelly already has this; sub-agents should each have identity files |
| Authority matrix (3 tiers) | Gas Town hierarchy; Kelly's gate validation | Kelly needs explicit written authority tiers per role |
| Autonomous compounding loops | GUPP + Deacon patrol loops | Kelly has no compounding autonomous loop equivalent |
| Narrative memory > tables | 5-layer memory (narrative top, structured bottom) | Kelly's design confirmed correct empirically |
| Progressive disclosure | 5-layer memory system | Already aligned |
| n8n/sessions separation | sessions_yield vs cron | Already aligned |
| Mistake log (public, version-controlled) | memory learnings section | Should be made more explicit and public |
| 30-day decision reviews | heartbeat decision follow-up | Kelly has the mechanism; needs structured review cadence |
| Screen tracking for visibility | Kelly's observability (project state tracking) | Kelly gap: no passive visibility into operator's work |
Source Attribution
Compiled from three Yuki Capital AI CEO essays:
- "The AI CEO Experiment" — January 2026 ([yukicapital-ai-ceo-experiment])
- "From Smart Notepad to Something More" — March 2026 ([yukicapital-board-review-2])
- "The AI CEO Now Runs Autonomously" — April 2026 ([yukicapital-board-review-3])
Cross-referenced with Kelly Factory KB articles:
- [[kelly-handbook-multi-agent]] — router/sub-agent architecture
- [[steve-yegge-gupp]] — GUPP execution axiom
- [[steve-yegge-hierarchy]] — Mayor/Crew/Polecats hierarchy
- [[kelly-gas-town-gap-analysis]] — full gap analysis
- [[multi-factory-comparison]] — factory comparison article
Related
[[yukicapital-ai-ceo-experiment]], [[yukicapital-board-review-2]], [[yukicapital-board-review-3]], [[kelly-handbook-multi-agent]], [[steve-yegge-gupp]], [[steve-yegge-hierarchy]], [[kelly-gas-town-gap-analysis]]