Getting Started with Latticra

First Rule

Read before running.

Latticra is an early-stage systems architecture repository. The first pass should confirm status, boundaries, and non-claims before touching local validation commands.

01

Read current posture

Start with the dashboard, root status, and detailed current-status record.

Open status dashboard

02

Understand layers

Review how Lat, LIR, L-UI, Nucleus, Runtime Boundary, and Seal relate.

Open architecture guide

03

Run no-effect checks

Use local commands only as inspection and regression checks.

Open examples

04

Pick a record lane

Use the documentation map to continue into the exact contracts.

Open documentation map

Safety Expectations

Keep the first pass narrow.

These boundaries make the first-run path useful without overstating what the project currently provides.

No root authority

Do not treat the first pass as a root installer, host mutation path, or privileged setup flow.

No production runtime

Current commands expose status, reports, and guards. They do not enable production enforcement.

No network authority

The public posture emphasizes local records and bounded checks, not network execution authority.

No certification claim

Status records and planning estimates are not security guarantees, approvals, or readiness claims.

Local Commands

Inspect, then confirm no-effect posture.

These examples keep the first pass non-privileged. Run them from the repository root after cloning; review prerequisite records separately before choosing any host setup path.

Review prerequisite records

sed -n '1,80p' docs/QUICK_START_CHEATSHEET.md
sed -n '256,270p' docs/UBUNTU_READINESS_PLAN.md

Read status

sed -n '1,220p' STATUS.md
sed -n '1,260p' docs/status/CURRENT_STATUS.md

Build the no-effect CLI

mkdir -p build
cc -std=c99 -Wall -Wextra -pedantic src/latticra_cli.c -o build/latticra
./build/latticra --status

Run broad guards

make quality
make seal

Expected Posture

The first successful read should still be no-effect.

A local status surface should reinforce disabled runtime behavior, denied authority, and no host or network mutation.

mode=no-effect
runtime_behavior=disabled
host_mutation=0
network=0
effect_authority=denied

Reading Paths

Choose the next lane by intent.

Latticra has a dense record set. Pick a route based on the question you are trying to answer.

Project identityEvidence rules, real-system boundary, and non-claims. RoadmapSequencing, estimates, active lanes, and guarded promotion rules. Kernel and State LatticeCompiled C kernel reports, lifecycle summary, subsystem posture, and no external effects. Boot preview boundarySeaBIOS/GRUB compatibility, fixture manifest, preflight, QEMU templates, and blocked boot claims. Runtime boundaryDefault-deny runtime posture, Nucleus reports, and policy matrix metadata. Local workbenchPanel, LC, Nadia, and user-local authority boundaries. Latticra PanelGuided GUI workbench, dry-run-first installer flow, receipts, and user-local evidence. Latticra ConsoleStage-0 operator base, command registry, host contracts, and no-effect authority floor. NadiaOffline AI contract lane, metadata commands, and blocked runtime authority. Local validationPanel install evidence, package guards, disposable VM gates, and dry-run contracts. Installer readinessDisposable VM payload evidence, artifact manifest fixture, production gates, and blocked release claims. Packaging readinessPlatform package-shape records, source fixture gates, notice blockers, and publication non-claims. Security boundariesSafe testing, effect gates, and non-claims. Supply-chain gatesCI, dependency, SBOM, updater, runtime-authority, and release non-claims. Signed-updater delivery gateClosed update-delivery gate, local-checkout updater policy, and blocked signed apply authority. Incident response boundaryReporting routes, evidence preservation, response gates, and incident-response non-claims. Vulnerability management gateKEV/NVD review, exception records, release blockers, and product-security non-claims. Cryptographic assuranceFIPS/CMVP claim gates, key lifecycle, randomness, and no production crypto authority. Identity and access managementICAM gates, privileged access, MFA planning, account lifecycle, and no hosted identity services. Security logging and monitoringEvent-source inventory, audit events, redaction, retention, triage, and no SIEM or telemetry claims. Backup and recovery resilienceRestore testing, recovery prioritization, rollback planning, RTO/RPO, and no recovery-service claims. Secure configuration and change managementConfiguration inventory, baselines, checklists, approved changes, rollback planning, drift detection, and no hardening claims. Network exposure and remote accessNetwork inventory, internet exposure, ingress/egress policy, remote access, RMM, DNS/TLS lifecycle, and no network-service claims. Data classification and protectionData inventory, sensitive-data flows, PII review, minimization, retention, disposal, redaction, and no customer-data claims. Evidence modelPromotion levels, claim boundaries, and exact source records. System structureLayered architecture, authority boundaries, and evidence flow. Language laneLat, LIR, L-UI, no-effect reports, and source records. ExamplesRunnable local checks and expected report fields. Tool-boundary reviewLatticra Seal status, policy, reports, and boundaries.

Getting started