Architecture

Architecture

This is the trunk architecture view for R1.

Audience

and registry work

Core System Planes

R1 currently has five architectural planes that matter together:

1. Mission execution: planning, execution, verification, review

2. Governance and evidence: ledger, WAL, receipts, honesty, cost

3. Deterministic skills: compile, manufacture, register, select, run

4. Distribution and runtime extension: packs, registries, MCP-backed

runtime functions

5. Anti-truncation enforcement: regex catalog, scope-completion gate,

supervisor rules, agentloop wiring, post-commit git hook, and

r1 antitrunc verify CLI / MCP tool — a layered, machine-

mechanical defense against LLM self-reduction. Each layer is

independently effective so the model cannot side-step one and

pass.

Execution Core

The execution core still centers on the orchestrator packages:

That is the original runtime thesis: one strong implementer, explicit

verification, and adversarial review instead of loose multi-agent

consensus.

Evidence Core

The evidence plane gives R1 its governance posture:

This is why new runtime features keep adding audit and metrics hooks

instead of only new prompts.

Deterministic Skill Plane

The deterministic skill lane now spans more than compilation:

The important architectural shift on April 30 is that pack distribution

is now a real subsystem, not just a future direction.

Anti-Truncation Plane

The anti-truncation plane addresses a documented LLM behaviour: under

long-running multi-task work the model self-reduces scope to fit

imagined token / time / Anthropic load-balance budgets. The plane is

seven layers, each independently effective:

internal/mcp/r1_server.go

The gate composes BEFORE any other end-turn hook, so a model that

says "skip the gate this once" is ignored at the host process layer.

Operator override (--no-antitrunc-enforce) is real but has no

LLM-visible toggle. Full details: ANTI-TRUNCATION.md.

Runtime Extension Plane

cmd/r1-mcp/backends.go is now a practical bridge between the core

runtime and deterministic helpers:

These let deterministic workflows observe and prove more about their own

execution.

Status

Done

In Progress

Scoped

Scoping

Potential-On Horizon

assets

Pages in this directory