Public Records

Documentation map

A reader-first route through Latticra’s current claims, contracts, architecture lanes, subsystem records, and local validation paths.

How to Read

Start with status, then follow the boundary.

Latticra documentation is intentionally evidence-heavy. The best reading order is current status, foundation rules, subsystem contracts, implementation records, then guard scripts and local validation lanes.

01

Start Here

02

Evidence and Claim Boundaries

03

Architecture Foundation

07

Panel, Nadia, and Local Workflows

  • Workbench OverviewReader-facing guide to Panel, LC, Nadia, and user-local authority boundaries.
  • Latticra Panel OverviewGuided GUI workbench, dry-run-first install flow, receipts, updater, and user-local evidence.
  • Latticra Console OverviewStage-0 LC identity, command registry, Panel profiles, host contracts, and receipt planning.
  • Nadia OverviewReader-facing guide to offline AI contracts, Stage-40 metadata, and non-runtime boundaries.
  • Installer READMELocal Panel and installer workflow orientation.
  • LC FoundationConsole foundation and profile presets.
  • Nadia Offline AINo-effect offline AI foundation and boundaries.
  • Nadia Stage-40Prompt-evaluation result release receipt review disposition release receipt review contract before runtime, inference, or release-receipt-review recording.
  • macOS User-Local App BundleUser-local bundle contract and limits.
08

Security, Packaging, and Roadmap

Reading Rule

Trust the narrowest current claim.

If a contract, implementation note, and status record disagree, treat the narrower status posture as authoritative until the broader claim has reproducible evidence and public-entry alignment.