You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: embed full system-architecture schematic in the README
Add an inline Mermaid architecture diagram (plane-level: clients, API, runtime
core, cross-cutting providers/governance/async/observability/telemetry, storage,
benchmark) in the style of the How-it-works diagram, with default-off components
dashed; add an Architecture nav link. The exhaustive per-module diagram + flag
table stays in docs/architecture-diagram.md.
5.**Pack & compact.** The packer assembles bounded context, retaining protected constraints under budget pressure.
74
75
6.**Replay everything.** Every retrieval is reconstructable from access/gate logs and a policy snapshot that distinguishes data drift from policy drift.
75
76
76
-
> 📐 The diagram above is the hot path. For the **complete system architecture** — every component across all planes (runtime, providers, governance, async, observability/telemetry, storage, benchmark, integrations), including the default-off ones and the flag that enables each — see [docs/architecture-diagram.md](docs/architecture-diagram.md).
77
+
## 🏗️ System architecture
78
+
79
+
The whole system at a glance — solid = default-on, **dashed = default-off / opt-in**, blue = data stores. Everything dashed is degrade-safe: turn it off (or leave the service/extra absent) and candidate scoring is byte-identical, benchmark stays 16/16. For the exhaustive per-module diagram + the `MEMTRACE_*` flag that enables each optional piece, see [docs/architecture-diagram.md](docs/architecture-diagram.md).
0 commit comments