Updated 09-09-2026
Elite Outsiders ← Tools home

System Overview — 4 pillars + 5 HQs

last update 2026-09-09 · repos read back from git remotes and the Cloudflare API, not declared · for AL + Claude agents

This page is the visual cockpit of the AL ecosystem (EO + byForja + byCaliber + alexandrecorne.com). Use it to redirect an agent quickly to the right source of truth based on what they are touching.

1. The 4 knowledge pillars

The ecosystem rests on 3 governance pillars (Notion, Tools, Memory) plus 1 implementation pillar (Code). Each pillar has a different cost and usage profile.

📜 Notion

Governance
Doctrine, rules, decisions, processes. On-demand fetch. Zero permanent context cost.
  • Decision trees
  • 8 golden rules
  • Technical architecture
  • Sprint logs
  • Pending decisions
  • Bootstrap guides

🔧 Tools intranets

Governance
Live computed state plus short operational doctrine when live data lives alongside it.
  • /clients (D1 live)
  • /coredata analytics
  • /crons monitoring
  • /architecture (status)
  • /alsboard piloting
  • /backdata/* admin

🧠 Memory MD

Governance
Claude reflex. Loaded on EVERY session. Permanent context cost. ONLY recurring 1-3 line anti-patterns.
  • Reflex anti-patterns
  • Rotation rules (PostFast)
  • Pre-check reminders
  • ~/.claude/.../MEMORY.md
  • ~60 feedback_*.md files

💻 Code repos

Implementation
Ultimate truth. What actually runs in prod. Doctrine can drift, code cannot.
  • functions/ endpoints
  • migrations/ schemas
  • tests/ smoke + e2e
  • docs/ atomic runbooks
  • CLAUDE.md entry points

Authority hierarchy in case of drift

  1. Code wins. It is what actually runs in prod.
  2. If doctrine differs from code, either fix the code or update the doctrine.
  3. Never trust doctrine without verifying against code on critical paths.

2. Hierarchy of the 5 Claude Code HQs

1 universal HQ plus 4 vertical-specific HQs. The specifics inherit from the universal one and never contradict it.

📄 AL (Notion top-level, personal meta-piloting)
├── 🎬 EO Content System — doctrine (cross-vertical)
├── 🎯 AL Business Piloting — methodology (cross-vertical)
├── 🧠 Claude Code HQ — universal patterns ← PRIME SOURCE
│ 8 golden rules · smoke pipeline · brand canonical · magic link · PostFast · bootstrap guide · naming convention · cron pipeline · audit methodology
│
├── 🟦 Elite-Outsiders (vertical)
│ └── 🟦 EO HQ — specifics
│ trauma map · manifesto · EO content system · 24 sub-pages
│
├── 🟩 byForja (vertical)
│ └── 🟩 byForja HQ — specifics
│ craftsmanship · packages · Shopify · client Fred · brand assets
│
├── 🟫 byCaliber (vertical)
│ └── 🟫 byCaliber HQ — specifics
│ B2C coaching · 13h/1800€ offer · CTR-V2 contract · CM2C compliance · vocab restrictions
│
└── 🟧 alexandrecorne.com (vertical)
└── 🟧 AC HQ — specifics
personal brand · /alpersoroutines · cleanup-reports · sub-pages

Inheritance rule

  1. Universal HQ is the canonical source for cross-cutting patterns (smoke, brand, auth, naming, deploys, crons, audits).
  2. Each vertical HQ specifics holds only what is specific to that vertical (posture, vocabulary, brand assets, offer, contracts, content craft).
  3. To update a universal rule, edit Universal HQ once and the 4 verticals inherit automatically.
  4. To add a new vertical, clone the mini-HQ template and point it to Universal HQ.

3. Repos per vertical (15 repos on GitHub, verified 2026-09-09)

🟦 Elite-Outsiders

  • eliteoutsiders-site
  • eliteoutsiders-tools
  • eo-backup-worker
  • eo-highlights-system
  • eo-shortener: worker-shortener/ inside eliteoutsiders-tools
  • (eo-cron-purge: worker deleted 2026-08-28, folder has no git)

🟩 byForja

  • byforja-site
  • byforja-tools
  • byforja-backup-worker
  • byforja-cron-purge: repo kept, worker deleted 2026-08-28
  • byforja-500usd-site-offer: local git, no remote

🟫 byCaliber

  • bycaliber-site
  • bycaliber-tools
  • bycaliber-backup-worker
  • bycaliber-cron-purge: repo kept, worker deleted 2026-08-28

🟧 alexandrecorne.com

  • alexandrecorne-site
  • alexandrecorne-tools
  • ac-friday-live
  • (no backup-worker, the 2 crons live on ac-friday-live)

Cross-brand, on no vertical: mta-sts-policy (Worker on the 5 zones, folder without git). Every repo has a CLAUDE.md that points to Universal HQ plus its HQ specifics. Update Universal HQ once and the CLAUDE.md files stay valid.

4. Quick redirects — where to send an agent based on what they touch

You are about to... Pages to open
Add an API endpoint in any vertical Universal HQ §Decision tree + vertical HQ specifics §Architecture
Touch a secret or API key Universal HQ §Secrets persistence + §PostFast (if PostFast)
Touch the content system (carousels, shorts, quotes, newsletter) 🎬 EO Content System — doctrine (cross-vertical) + tools.<brand>.com/architecture (status)
Touch the Trauma Map (scoring, mythos, narratives) 🟦 EO HQ §sub-page Trauma Map Mythos + code public/trauma-map.html
Touch AL piloting (alsboard) 🎯 AL Business Piloting methodology + tools.eliteoutsiders.com/alsboard (live)
Duplicate a vertical or create a new one Universal HQ §Bootstrap guide + §Vertical-duplication bootstrap pattern (10 steps)
Run a full-page audit Universal HQ §Full-page audit methodology (4 subagents pattern, ~500k tokens)
Rotate PostFast / Kit / Resend / Brevo keys Universal HQ §PostFast + Memory feedback_postfast_key_rotation.md
Bug on a tools page, looking for doctrine vs live tools.<brand>.com/notion-vs-tools (source-of-truth split per vertical)
Ship a major fix and log it to Sprint logs Sprint logs of the vertical concerned (sub-page under HQ specifics)

5. Usage notes for AL

If an agent seems lost on "where to find X"
Point them at this page (tools.eliteoutsiders.com/system-overview). One read locates the pillar, the HQ, and the vertical concerned.
If an agent touches a universal pattern (auth, brand, deploy)
Always start with 🧠 Universal HQ. Otherwise they invent a pattern that drifts the 4 verticals.
If an agent touches something vertical-specific
Open the vertical HQ specifics plus the Notion top-level hub of the vertical (business doctrine). Keep Universal HQ open in parallel for cross-cutting coherence.
If a drift is detected between doctrine and code
Code wins by default (authority 1). Either fix the code or update the doctrine. Never leave the drift.
If we add a 5th vertical tomorrow
Clone the mini-HQ template, add the tools banner, the notion-vs-tools page, and the CLAUDE.md pointer. Universal HQ stays untouched. Pattern documented in §Bootstrap guide.
Recommended maintenance
Update Universal HQ when a cross-cutting pattern changes (auth, brand, deploy, crons). Update HQ specifics when there is a new ship in the vertical. Sprint logs: one entry per major ship.

Page created 2026-05-22 · translated to English 2026-05-23 · repos section verified 2026-09-09 · manual refresh when the structure evolves (new vertical, new pillar, HQ refactor).

For Claude

Audit of 2026-09-09, read back, not declared. Section 3 was rebuilt from git -C ~/Projects/<repo> remote -v and from GET /accounts/{id}/workers/scripts. The three purge workers and eo-url-audit-worker are gone from the account; their scripts sit in ~/Projects/_deleted-workers-backup-2026-08-28/.

What changed. 13 became 15 repos with a remote: eo-highlights-system and ac-friday-live gained one. The cron-purge lines are muted, not removed, because the GitHub repos still exist. Sections 1, 2, 4 and 5 are doctrine and were not touched.