Repository navigation
docs(architecture): Chimera system-architecture diagram (SVG + 18×24 PDF) - #421
Merged
Merged
Conversation
A comprehensive "Chimera — System Architecture" reference in the Leonardo diagram grammar: 12 tiers x 6 components, a cross-cutting-concerns rail, the closed drift/trust/escalation feedback loop, and source-of-truth + governance callouts. Grounded in a 12-agent CodeGraph map of the repo — boxes name the primary module and real symbols, with thresholds, CHIMERA_* flags, and ADR numbers. Corrects a few stale README framings against code truth (9-phase cycle with COMMIT stub; invocation-driven, no daemon; per-cycle/rolling-hour/per-task caps; 26 widgets; ~90 flags). - docs/architecture.svg — 2004x2678 source - docs/architecture.pdf — 18x24 in (ARCH C), vector, print-ready
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a comprehensive Chimera — System Architecture diagram to
docs/, in the same visual grammar as the Leonardo architecture diagram.What's included
docs/architecture.svg— 2004×2678 source (theme-neutral parchment palette, tier bands + component boxes, cross-cutting rail, feedback-loop gutter).docs/architecture.pdf— 18×24 in (ARCH C), single-page, fully vector (embedded fonts) — prints crisp at 11×17 fit-to-page or scaled up to ARCH D/E.Coverage
12 tiers × 6 components (72 boxes) following the cycle's data flow: loop & 9-phase cycle · task shaping/entropy sub-tasking · ACT parallel dispatch & guards · inference/tier-ladder/escalation-learning · three cost caps · verification (critic/witness/scope/repo-verify) · memory/KFM/Kuzu/FTS5 · engines/drift/T0–T5 trust/adaptation · self-PR & foreign-PR pipeline · skills/positioning/prompts · A2A federation/MCP server · observability/runtime/config.
Right rail: invocation & cadence · models & external services · governance + three cost caps + guards · security baseline (ADR 0175/0178) · trust & drift thresholds · operator/mutation/CLI loop · scenarios & drills · tests & CI gates · ★ key feedback loops · ★ source of truth.
Provenance & accuracy
Grounded in a 12-agent CodeGraph map of the repo — every box names its primary module and real symbols, with thresholds,
CHIMERA_*flags, and ADR numbers. The mapping corrected a few stale README framings against code truth: the cycle is 9 phases (COMMIT is a stub), it is invocation-driven (no in-process daemon), cost caps are per-cycle / rolling-hour / per-task (no daily reset), 26 dashboard widgets, and ~90 flags in the registry.Docs-only; no code changes.