Kernel Lane

Scope & Responsibilities

• Constraint lattice: Declarative optimization problem: minimize drift subject to constraints
• Runtime validation: Enforces output provenance, blob boundaries, convergence gate checks
• Process supervision: Supervises agent lifecycle, heartbeat monitoring, stale-lane detection
• OS-level policies: File-system layout, lane-directory enforcement, SMB mount validation
• Drift score calc: Computes divergence between intended state and actual state

Isolation Model

The Kernel runs closest to the metal. It can kill or restart agents, enforce read/write boundaries, and validate every output against provenance contracts. It does not make decisions — it enforces constraints defined by governance. Its authority is absolute but bounded by the Archivist-ratified constraint lattice.

Connection to Papers

The constraint lattice formulation is documented in the Kernel's README and specification papers. These define the optimization objective (minimize drift) and hard constraints (identity, session-mode, lane-relay paths).