Latticra

Home / Roadmap

Current Direction

Roadmap and current direction

Latticra advances through narrow, evidence-backed slices: contracts before code, fixtures before runtime, read-only before mutation, and local proof before broader authority.

Roadmap Principle

Sequence matters as much as ambition.

The roadmap is a discipline layer. It records what can be promoted next, what must remain report-only, and which future claims still need reproducible evidence before they can be repeated publicly.

01

Contracts before code

Define the boundary, fields, report shape, and non-claims before implementation expands.

02

Fixtures before runtime

Use deterministic examples and guards before any live behavior or authority is considered.

03

Read-only before mutation

Prefer local evidence, status, reports, and denied cases over host-changing behavior.

04

Virtual before real device

Hosted and virtual-target evidence must precede real-device experiments.

Planning Estimates

Current estimates are posture markers, not release promises.

The latest public estimate refresh records planning percentages only. They are not production readiness, security guarantees, runtime-enforcement claims, or operating-system completeness claims.

Overall system 44%
Foundation docs 94%
Public docs 91%
Seal evidence layer 39%
Panel surface 31%
L-UI foundation 87%
Lat language 27%
Product readiness 10%

Active Lanes

Where the current work is concentrated.

The current direction favors small, reviewable, guarded slices across language metadata, report surfaces, Seal evidence, runtime-boundary classification, and host-facing planning.

Lat / LIR evidence

Parser, semantic, model normalization, lowering, diagnostics, and runtime-boundary evidence propagation remain no-effect.

Language overview

Kernel lifecycle evidence

State lattice, kernel seed, lifecycle runner, and subsystem summary are compiled and reportable while external effects remain denied.

Kernel overview

Boot preview evidence

SeaBIOS/GRUB compatibility, boot-preview fixtures, preflight, and templates are tracked without QEMU execution, disk images, or bootloader writes.

Boot preview boundary

Packaging and platform readiness

Fedora, Ubuntu, openSUSE, Debian, BSD, and macOS lanes stay static, fixture-only, dry-run, or disposable-target gated until release evidence exists.

Packaging overview

Seal evidence and policy

Report-only metadata, policy decisions, request freshness, receipts, key parsing, and dry-run posture stay authority-denied.

Seal overview

Runtime boundary

Request families, effect families, abuse-case fixtures, and denied evidence paths are mapped before runtime execution.

Runtime overview

Installer readiness boundary

Disposable VM CLI payload evidence and a local artifact manifest fixture exist, while production installer readiness remains blocked behind release-grade gates.

Installer readiness

Supply-chain release gates

CI, dependency, SBOM, signed-updater, zero-trust runtime-authority, and release-publication controls remain guarded before production wording.

Supply-chain gates

Roadmap Stages

The long path stays gated.

These stages come from the source roadmap and should be read as sequencing constraints, not claims that the later stages are already available.

0

Foundation planning

Define the system, public identity, contracts, evidence rules, names, and first implementation targets.

1

State lattice fixture

Create deterministic no-effect state shapes, labels, reports, and invariant tests.

2

Tri-plane model

Model spatial, state, and safety transitions before live movement exists.

3

Nucleus preview

Introduce supervisor classification and no-effect reports without task execution.

4

Lat-Core draft

Define native language contracts, validation fixtures, LIR direction, and no execution.

5

L-UI reports

Declare operator surfaces, rails, denial reports, and rendering boundaries.

6

Server/update fixtures

Model network and update behavior while keeping network denied by default.

7

Hosted reference

Run as a local hosted reference process with no server, hardware, or boot effects by default.

8-9

Virtual and read-only device evidence

Collect reproducible virtual-target profiles before real-device read-only observation.

10

Gated real-system experiments

Consider narrow real-world actions only after preflight checks, approval, audit, and rollback plans.

Promotion Rule

The next valid step is the smallest guarded slice.

The near-term queue repeatedly favors metadata, deterministic reports, status/public-entry alignment, and negative-case evidence over broad runtime behavior.

Completed planning pattern

Define future bounded APIs, records, fields, reports, failure behavior, and tests before code.

Completed implementation pattern

Copy evidence labels and metadata through deterministic reports while preserving no execution and no runtime authority.

Still blocked

Production runtime, host mutation, network authority, root authority, certified security, OS replacement, and broad AI-agent control.

Security Gate

Roadmap movement still needs safety evidence.

Use the security overview before repeating runtime, host, network, malware-prevention, sandboxing, or production-readiness language. Open security boundaries.

Source Records

Trace the roadmap back to exact files.

RoadmapStage sequence, principles, and non-claims. Current directionActive project direction and lane summaries. Upcoming workNear-term queue and completed slice pattern. Estimate rebaseCurrent planning estimates and readiness boundaries.