Latticra System Architecture

System Line

Declaration first, authority last.

The current architecture is best read as a sequence of gates. Each layer narrows ambiguity and records evidence. None of the current public pages should be read as a production-runtime or OS-completeness claim.

01

Lat

Contract declarations and source intent.

02

LIR

Bounded intermediate metadata and graph shape.

03

L-UI

Operator-visible parsing and report surfaces.

04

Nucleus

Task records and report-only classification.

05

Runtime Boundary

Disabled-by-default runtime posture checks.

06

Seal

Trust, request, policy, and tool-boundary evidence.

Core Boundaries

The architecture separates language, authority, and evidence.

Each layer has a specific job. The separation matters because it keeps future operational claims from sneaking into current no-effect records.

Declaration boundary

Lat and L-UI records describe system intent and operator-facing declarations before execution exists.

Language overview

Representation boundary

LIR records graph shape and metadata, but does not act as an execution engine.

LIR shape contract

Task boundary

Nucleus records task classification and prerequisites while remaining report-only.

Nucleus task contract

Kernel evidence boundary

State lattice, kernel seed, subsystem registry, and lifecycle reports remain compiled C evidence surfaces without external effects.

Kernel overview

Boot preview boundary

SeaBIOS/GRUB compatibility is fixture-only: preflight and templates exist while boot artifacts, QEMU logs, and bootable OS claims remain blocked.

Boot preview overview

Runtime boundary

Runtime Boundary records disabled-by-default classification before operational behavior.

Runtime overview

Trust boundary

Latticra Seal records request, policy, capability, signature, and tool-boundary metadata.

Seal overview

Host boundary

Panel, Console, Fedora, and macOS lanes stay local, guarded, and status-bound.

Workbench overview

Authority Posture

What the current architecture allows readers to infer.

Latticra's public records support evidence, metadata, reports, guards, and local validation. They do not support broad authority claims.

Supported now

Contracts, status records, no-effect implementation slices, deterministic local checks, public non-claims, and bounded report surfaces.

Guarded research lanes

Local installer, Fedora validation, macOS user-local packaging, host-embedding plans, and offline AI planning records.

Not inferred

Production enforcement, root authority, network authority, cryptographic key authority, certified security, OS replacement, or Fedora approval.

Move from the map to the exact record.

Use this page for orientation, then use the documentation map and status dashboard to reach the authoritative contracts and current posture records.

Status dashboardCurrent posture and planning estimates. RoadmapSequencing, estimates, and active lanes. Kernel and State LatticeCompiled C lifecycle reports, subsystem summaries, and denied external authority. Boot preview boundarySeaBIOS/GRUB fixture lane and evidence gates before any boot claim can promote. WorkbenchPanel, LC, and Nadia local surfaces. Latticra PanelGUI-first local workbench, guarded install flow, and user-local evidence boundary. Latticra ConsoleStage-0 command registry, host contracts, and no-effect operator-base planning. Language overviewLat, LIR, and L-UI boundaries. ExamplesConcrete no-effect local checks. Runtime boundaryDisabled-by-default runtime classification and Nucleus task reports. Seal overviewReport-only trust and policy boundaries. NadiaOffline AI planning contracts and Stage-40 non-runtime boundary. Security boundariesSafe testing, effect gates, and non-claims. Local validationInstall evidence, package guards, and disposable VM gates. Documentation mapGrouped links into the full record set. Foundation indexContracts, implementation notes, guards, and status files.

System architecture