Architecture System Map
Architecture pages are system maps with invariants: they name boundaries, components, flows, failure modes, and proof obligations so future implementation can preserve the system's shape.
Use this page when choosing which architecture article to read or update. Use the wiki/architecture/README.md router for the category writing standard. Use Filing Decision Tree when deciding whether a new page belongs in architecture/ at all.
Architecture Families
| Family |
Canonical pages |
Owns |
| Agent operating system |
Agent Operating System, Agent Company OS, Agent System |
Whole agent work stack, repo-local agent systems, skills/tools/memory/doctors loop |
| Harness layer |
Agent Harness Architecture, Claude Code Harness, Codex Harness (OpenAI), Cursor Harness, Hermes Harness (Nous Research), OpenClaw Harness, CoTCodec Harness Architecture |
Product/runtime wrappers around models, tools, memory, skills, rules, approvals, and workspaces |
| Runtime and control plane |
Agent Runtime Architecture, Agent Control Plane Architecture, Durable Agent Execution Architecture, Tool Execution Runtime Architecture, MCP Server Architecture |
One-run execution, fleet operation, tool invocation, durable state, governed capability exposure |
| Memory, context, retrieval |
Agent Memory System Architecture, Context Engine Architecture, RAG System Architecture, Vector Database and ANN Index Architecture, Sevenfold Hybrid Search, Knowledge System Architecture Comparison |
Context assembly, durable memory, ingestion/query split, hybrid retrieval, ANN storage, answerability |
| Agent safety and observability |
Agent Guardrails Architecture, MicroVM and Sandbox Isolation Architecture, Observability Architecture, Resilience Patterns (Circuit Breaker, Bulkhead, Retry), Idempotency and Exactly-Once Processing |
Unsafe input/action boundaries, sandbox isolation, traces, retries, idempotency, recovery |
| Dedalus and product systems |
Dedalus Machines - How They Work, Dedalus Filesystem & LSVD, Dedalus FS Engine, DCS Infrastructure: Gauntlet & Systems Push, API Backend, Website Frontend, Radar Registration Gate, Admin Dashboard Expansion, SEO/GEO/AEO/AX Implementation |
Dedalus/DCS infrastructure, product surfaces, app boundaries, storage and signup gates |
| Distributed systems primitives |
API Gateway Architecture, Load Balancing Architecture, Rate Limiting Architecture, Service Mesh and Service Discovery Architecture, Log-Based Streaming Architecture, Event Sourcing and CQRS, Consensus Protocols (Raft and Paxos), Replication and Consistency Models, Sharding and Partitioning Architecture, Saga Pattern and Distributed Transactions, Distributed Caching Architecture, Multi-Tenancy Architecture, Webhook Delivery Architecture |
Reusable system design patterns for services, data, coordination, delivery, scaling, and failure containment |
| AI/research/wiki infrastructure |
LLM Inference Serving Architecture, Streaming LLM Response Architecture, arXiv Indexer Pipeline, Research Infrastructure Overview, Kevin Wiki UI Architecture, Wiki Content Bundle Pipeline, X For You Algorithm (2026 Open Source), X Community Notes Scoring (Bridging Algorithm) |
Model serving, streaming UX, research/search infrastructure, wiki reader deployment, public algorithm architecture |
Merge Decisions
No existing architecture pages were merged in the 2026-07-01 pass. The reason is not "never merge architecture"; it is that the current pages mostly answer different boundary questions.
| Cluster |
Decision |
Reason |
| Harness pages |
Keep distinct, add Agent Harness Architecture |
Claude Code, Codex, Cursor, Hermes, OpenClaw, and CoTCodec have different state, tool, skill, and deployment contracts. The new family page owns the comparison. |
| Dedalus filesystem pages |
Keep Dedalus Filesystem & LSVD and Dedalus FS Engine separate |
LSVD owns the product/storage thesis; FS Engine owns the implementation design. |
| Dedalus app snapshots |
Keep as architecture snapshots |
API Backend, Website Frontend, Admin Dashboard Expansion, Radar Registration Gate, and SEO/GEO/AEO/AX Implementation each pin a different product/system boundary. |
| Distributed systems primitives |
Keep separate |
Each primitive is searched by name and has a compact independent invariant. |
| Retrieval/search pages |
Keep separate, cross-link by family |
RAG System Architecture, Vector Database and ANN Index Architecture, Sevenfold Hybrid Search, Knowledge System Architecture Comparison, and Kevin Wiki UI Architecture sit at different layers. |
Page Contract
An architecture article should answer five questions:
- What system boundary does this page own?
- What components are inside the boundary?
- What data/control flow crosses the boundary?
- What invariants prevent the known failure modes?
- What proof should an agent collect before claiming the architecture still holds?
If an article cannot answer those questions, fold it into a stronger page, move it to concepts/, or turn it into a ledger row.
Update Rule
When updating any architecture page:
- update its
updated: date
- add or preserve a one-line lead
- keep related architecture family links current
- preserve timeline evidence
- cite project/source pages when the architecture is project-specific
- regenerate
_index.md, backlinks, and qmd
- log structural changes in
wiki/log.md
Timeline
- 2026-07-01 | Created as the category-level system map for the Architecture rewrite. Added architecture families, merge decisions, and the page contract used to update all architecture articles. Source: User request, 2026-07-01