Summary
Olympus is the team's operations wiki — a Claude-accessible knowledge base built from the Venterminator OS Obsidian vault. It gives Claude cross-project context so every session starts with full operational awareness instead of re-exploring the codebase. It also gives the team a searchable wiki surface for SOPs, sales tactics, coaching themes, and market intel. Live at olympus.stoicagent.com. Source: Venterminator OS/12-business-intel/wiki/.
Why This Exists
Claude cannot see beyond its project walls. Every new conversation starts cold unless context is piped in. Olympus solves that: Claude reads from a single wiki that compounds over time, so operational knowledge is compiled once and kept current — not re-derived on every query.
Architecture
- Source: Markdown files in
Venterminator OS/12-business-intel/wiki/ - Build: Node.js static site generator (
Tools/OLYMPUS/build.js) converts markdown to branded HTML - Deploy: Netlify auto-builds from
dist/ - Content pipeline: wiki-ingest skill processes transcripts, Slack threads, and documents into structured pages with frontmatter, wikilinks, and cross-references
- Auto-maintenance: Daily Slack batch ingestion keeps the wiki current without manual editing
Two Visibility Tiers
| Tier | Who Sees It | Contents |
|---|---|---|
| Internal | Fred only | Full wiki including strategic intel, recruiting pipelines, financial detail, API keys, competitor analysis |
| Team | All agents | Sanitized version — SOPs, sales tactics, coaching themes, market intel that agents need to operate |
Build-time filtering via frontmatter visibility: internal vs visibility: team keeps both versions in sync from one source.
What Lives Here
- SOPs — How things are supposed to work (lead routing, listing marketing, transaction processing)
- Operations — Decisions, policy changes, tool inventory (this page lives here)
- Sales Tactics — Active playbooks, frameworks, objection handling
- Coaching Themes — Recurring topics, skills gaps, progress tracking
- Market Intel — Local conditions, competitor moves, portal changes
See overview for the cross-category synthesis or the wiki index for the full page catalog.
Claude Integration
Every Claude session — Code, Chat, Apple Notes interface — can read the Olympus content via:
- Direct file read from Dropbox (Claude Code sessions)
- Operations Briefing export (
exports/operations-briefing.md) — a compressed sub-4K-token version pasteable into any Claude surface - Seneca integration — seneca-adoption now auto-reads Olympus, so every negotiation coaching conversation has current team context
Security
- Team-tier build strips internal intel before publishing
- Password protection at the Netlify layer (planned)
- Raw sources in
raw/are immutable — wiki changes only happen inwiki/ - No runtime user input; no server-side code; all HTML generated at build time from trusted local markdown
Related
- seneca-adoption — Seneca reads Olympus for live team context
- tool-build-sop — Build standards Olympus follows
- overview — Cross-category synthesis of wiki content