Early-stage evidence-bound systems architecture
Latticra
A contract-first architecture for making requests, capabilities, policy boundaries, runtime posture, and evidence records explicit before authority is granted.
- Status
- Early-stage foundation
- Runtime posture
- No-effect by default
- Status record
- May 27, 2026 CDT
Choose a Path
Start with the question you have.
Latticra's public record set is dense by design. These routes keep the first click purposeful: current posture, safe local review, system shape, security boundaries, validation evidence, or the source map.
Orientation
Built around claims that can be inspected.
Latticra treats architecture as an evidence trail. The repository separates contracts, metadata, reports, guard scripts, implementation slices, and non-claims so readers can see what exists now and what still requires proof.
What Latticra is
- An evidence-bound systems substrate for Linux-era and AI-era computing.
- A public engineering record for explicit authority, request, capability, and runtime boundaries.
- A collection of no-effect C, constrained C++, Rust installer, shell guard, and documentation lanes.
What Latticra does not claim
- No production runtime, hardened sandbox, certified security boundary, or operating-system replacement.
- No unrestricted command execution, network authority, root installer, Fedora approval, or Ubuntu archive readiness.
- No active AI-agent execution control or production cryptographic key authority.
First Source Records
Jump from public summary copy to exact repository evidence.
If you need to verify homepage wording quickly, start with the current status record, the non-claims boundary, and the foundation or documentation authority records that govern the public mirrors.
Architecture
Named layers, conservative posture.
The current system emphasizes declaration, classification, metadata, and deterministic reports before operational behavior. Each lane has a role and a boundary.
Contract language direction
Parsing, validation, diagnostics, and metadata lowering for system declarations.
Bounded representation
Graph-shape and metadata reporting without LIR execution.
Operator-visible surface
Declaration and report rendering foundations before terminal-control behavior.
Task-boundary records
Coordination and task classification under report-only, denied-by-default posture.
Before operational behavior
Disabled-by-default classification and report surfaces before runtime authority.
Trust and tool boundaries
Request freshness, signed-request, policy-decision, capability-gate, and dry-run metadata.
Local workbench
User-local installer and evidence review path with no root and no network authority by default.
Validation lane
Ubuntu build/local deb and Fedora disposable VM/local RPM evidence paths, not distribution readiness.
Evidence Path
Promotion requires more than intent.
Latticra uses a staged evidence model: define the boundary, produce deterministic records, keep effects denied, then promote only when tests and status records support the claim.
-
01
Contract
Name the capability, prerequisites, limits, and explicit non-claims.
-
02
Metadata
Represent the request, policy, capability, and report fields in bounded structures.
-
03
Guard
Run deterministic scripts and tests that preserve no-effect behavior.
-
04
Status
Record the exact posture so public entry points do not overstate readiness.
Latticra Seal
Report-only tool-boundary planning for AI-era automation.
Latticra Seal records what would be denied, why it would be denied, and which evidence supports the decision. Unknown tools, unsigned requests, stale requests, replayed requests, invalid schemas, and missing authority remain blocked cases.
Start Locally
Read the status first, then run no-effect checks.
The repository is designed to be inspected from the public records outward. The commands below mirror the current no-effect posture rather than promising operational authority.
Read the public posture
sed -n '1,220p' STATUS.md
sed -n '1,260p' docs/status/CURRENT_STATUS.md
Run broad safety guards
make quality
make seal
Inspect the no-effect CLI
mkdir -p build
cc -std=c99 -Wall -Wextra -pedantic src/latticra_cli.c -o build/latticra
./build/latticra --status
Resources
The important records, grouped for fast entry.
These links are the best first paths through the repository: general orientation, current status, foundation contracts, subsystem documentation, and safety policy.
Concept overview
Start here when you need the public explanation before opening source records.
Documentation operating rules
Use these records to check wording, freshness, traceability, status mirrors, and claim boundaries.
Reader routes
Guided HTML pages for onboarding, current posture, architecture, examples, and roadmap context.
Workbench, validation, and release boundaries
Local workflow, installer, packaging, and validation pages that stay dry-run or evidence-only until promotion gates pass.
Source records and books
Repository records, status files, foundation indexes, and generated reference materials behind the public pages.
Security and assurance gates
Baseline pages for security policy, supply chain, cryptography, access, logging, recovery, change control, exposure, data, incidents, and vulnerability review.