Architecture Reference¶

This is the curated entry point to the 141 architecture documents in this repository — deep dives on one subsystem, one seam, or one hardening incident each. Start with North-Star Architecture for the whole-program view, then drop into whichever group matches what the operator're touching. Every file here is also reachable through MkDocs Material's site search if the operator already know its name.

New to the codebase? docs/pillars/index.md is the 5-pillar concept map these documents implement. This page is the implementation detail underneath it.

Start here — whole-program view¶

The north star, the operating model, and the standards every other document here assumes the operator've read.

Identity, session & authority¶

Who is acting, on whose behalf, with what authority — from the first request to a delegated sub-agent.

Control-plane suite¶

The remaining runtime authority and resource-management seams. - Relational Authority & Registry Read Model - Resource-pool capability authority - Native WorkItem resource-reservation boundary - Fleet scale authority - Durable ScaleIntent actuation - Service-surface scale units

Ingestion & data preparation¶

Getting external and internal signal into the graph — classification, commit-history tails, Arrow-based prep, and stability under load.

Ontology & semantic layer¶

OWL/RDF, SHACL, argumentation, and object-centric process semantics — the reasoning layer over the raw graph.

Memory, reasoning & cognition¶

How the system remembers, attends, and reasons across turns and agents.

Evolution, evaluation & learning loops¶

The self-improvement flywheel: propose, evaluate, distill, and the evidence trail that grounds it.

Orchestration, execution & routing¶

How a request becomes a plan, a plan becomes tool calls, and results come back through one entrypoint.

Enterprise system integrations¶

Bridges into the enterprise tool landscape — BPM, GRC, and the runtime that carries the organization's own intelligence.

Ecosystem, communication & UI surface¶

How the platform talks to the outside world — cross-session messaging, reactions, frontend contribution points, and code intelligence.

Scaling, sharding & the engine surface¶

Everything about running more than one of something — engine shards, GPUs, gateways, caches, tenants, and the wire protocols between them.

Observability, governance & safety¶

Metrics/logs/traces, autonomous governance, and the reliability loop that watches all of the above.

Deployment, release & repo operations¶

Shipping the platform itself — containerization, orchestrator migrations, versioning, the merge queue, and the shared dev environment.

Trace, provenance & incident history¶

The canonical record of what ran, why, and — for closed incidents — what broke and how it was found.