System Map — Map of Content

This folder contains Mermaid visual maps of the OpenClaw platform — agent tiers, MCP server catalog, request lifecycle, port topology, governance gate networks, and OSIL data flows. Read when you need a visual reference for how components connect before proposing architecture changes. Currently holds 12 Tier 1 maps (Pass 1) with 67 total maps planned across 9 domains.

Stats

• Mermaid maps: 8 (6 tier1 + 5 osil + 1 test + 1 baseline)
• Planned: 67 maps (12 Tier 1 + 25 Tier 2 + 30 Tier 3)
• Last reviewed: 2026-05-03

Tier 1 — Must-have (live)

Core infrastructure maps. Read these first when debugging any system-wide issue.

• agents-tier-structure — Agent tier diagram: Strategic/Operations/Automation breakdown (44 agents; was 36)
• governance-gates-network — 22 cascade-failure gates (G-PLAN-INDEX through G-FAILED-SERVICE-MTTR) and their enforcement relationships
• mcp-server-catalog — 8 MCP servers with tool counts, status, and connection topology
• ports-topology — All 37 live services mapped to ports (15 user-systemd + 14 system-systemd + 8 PM2)
• request-lifecycle — Full request lifecycle: Internet → Tailscale Funnel → webhook handler → Supabase + agent dispatch → Portkey → LLM → response

OSIL Maps (Self-Improvement Layer)

Visual maps for the OpenClaw Self-Improvement Layer (OSIL) — 5 maps generated 2026-05-03.

• vm-osil-overview — OSIL high-level architecture overview (14-tier stack)
• vm-osil-dataflow — Data flow between OSIL components (GEPA, DSPy, Reflexion, Voyager, memory)
• vm-osil-decision-tree — Decision tree for OSIL optimizer selection
• vm-osil-stack — Technology stack breakdown by OSIL tier
• vm-osil-vendor-map — Vendor map: 12 OSIL candidates (DSPy, GEPA, TextGrad, Honcho, Mem0, Letta, etc.)

Auto-generated (Phase 2 of visual mapping plan — pending)

The following domain map categories are planned but not yet populated. They will appear here once the visual mapping plan Phase 2 executes.

• wiki/system-map/agents/ — Per-agent capability and integration maps (25 Tier 2 planned)
• wiki/system-map/data/ — Supabase schema maps, vector search topology
• wiki/system-map/integrations/ — Per-platform integration diagrams
• wiki/system-map/flows/ — Data flow maps for acquisitions, dispo, SMS pipelines
• wiki/system-map/governance/ — Governance gate enforcement maps
• wiki/system-map/historical/ — Historical architecture snapshots
• wiki/system-map/meta/ — Meta maps (plan dependency graphs, skill web)
• wiki/system-map/teams/ — Team ownership maps (30 Tier 3 planned)
• wiki/system-map/canvas/ — Obsidian canvas files for interactive exploration

Reference

• wikilink-baseline-2026-05-03 — WikiLink baseline audit (Pass 1): 308 wikilinks / 832 files / 93% orphan rate before optimization
• _mermaid-test — Mermaid rendering test (verify Obsidian Mermaid plugin working)

Related folders

• _index — Agent identity files (SOUL.md + summaries)
• _index — ARCHITECTURE.md, AGENT-REGISTRY.md, port-registry
• _index — Plans that reference visual maps
• _index — feedback_visual_map_required rule
• _index — Platform docs that inform these maps

See also

• _index (vault root)
• CLAUDE (operating instructions)
• ARCHITECTURE — Canonical architecture doc (prose form)
• openclaw-visual-mapping-2026-05-02 — Visual mapping plan (67-map initiative)
• feedback_visual_map_required — Visual map required for complex plans