Architecture

Architecture

The repo's ARCHITECTURE.md is the canonical long-form architecture. This page is the short map. For the phase clock see Phase-Clock; for flags see Configuration-Flags.

Three product pillars

1. Cognitive Substrate — context manager, A-MEM, skill router, RLVR telemetry/reflection, dynamic-tool sandbox. Default fragment 262 BPE.
2. Multi-Agent Intelligence — Supervisor + worker roles; peripheral monitor → alert → task; fairness; self-heal ticks.
3. Peripheral Abstraction Layer (PAL) — mock/MQTT/Serial/BLE/Zigbee/ROS2/ Matter foundations; pairing; device-capability profile; power/forecast/anomaly; cluster leases (Phases 25–40).

The overlay / UIA inspect surface is a coordinate grid, not a fourth pillar and not a perception runtime.

Four engineering fabrics (conceptual, not four new src/ trees)

Fabric	Phases	What it is	What it is not
Agent	existing src/main/agents	roles, handoff, contracts, PAL tasks	not relocated
Inference	41–45	OpenAI-compatible providers, /route, budget, telemetry, TaskContract, escalation	not a "model OS"
Execution	46–47	in-process fabric + declared-independence scheduler	not a worker pool
Transport	48–51	interface + bench + loopback lab + advisory policy table	not HTTP/3, not production QUIC, not a cutover

Transport neutrality

• Worker semantics are not coupled to TCP / HTTP/2 / HTTP/3 / QUIC. Provider APIs remain HTTPS / OpenAI-compatible.
• Transport grants no authority. A handle's invoke() only calls the injected function; it cannot skip budget, routing, escalation, confirm rails, or PAL.
• Agents never open transport streams.
• Reserved kinds (http2/http3/quic/ipc) fail closed with unsupported-transport. The QUIC worker lab is a loopback stand-in, not a production QUIC/HTTP-3 stack.