Latticra

Home / Examples

Concrete No-Effect Path

Examples and local checks

A compact route from a checked-in L-UI fixture to parser reports, language pipeline checks, and the exact posture a reader should expect.

Tutorial Route

Start with one fixture, then widen carefully.

The current examples are local validation aids. They are useful because they show what the repository can prove now: parsing, metadata, reports, and denied authority.

01

Open the source

Read the accepted L-UI fixture for the Nucleus preview card.

View fixture
02

Parse in memory

The parser accepts caller-provided source bytes and returns a bounded summary.

Parser contract
03

Inspect report fields

Confirm card name, rail count, field count, effect, boundary, and no-effect flags.

Expected posture
04

Run the language guards

Use the Lat and L-UI scripts as regression checks, not as execution paths.

Command set

Fixture

NucleusPreview card.

The accepted L-UI fixture declares an operator-visible preview card with effect none and boundary preview_only. 

lui 0.1

card NucleusPreview {
  purpose "operator-visible Nucleus preview report"
  effect none
  boundary preview_only

  rail effects {
    field host bind state.host_effect
    field external bind state.external_effect
    field requested bind preview.requested_effect
  }
}

Expected Report

The successful example remains non-authoritative.

These are the headline values a reader should see represented by the parser contract for the accepted fixture.

card_name NucleusPreview
rail_count 9
field_count 23
effect none
boundary preview_only
no_effect 1
execution_allowed 0
mutation_allowed 0

Commands

Run examples as local checks.

These commands stay within the current evidence posture: local scripts, deterministic reports, and no production authority.

L-UI fixture path

sed -n '1,120p' examples/l-ui/nucleus-preview-card.lui
sh scripts/test-l-ui-parser.sh

Source spans and rendering

sh scripts/test-l-ui-parser-source-span.sh
sh scripts/test-l-ui-rendering.sh

Lat pipeline checks

sh scripts/test-lat-pipeline.sh
sh scripts/test-lat-to-lir-lowering.sh

Interpretation Rule

A passing example is evidence, not authority.

Treat each command as proof of a narrow invariant. A green script does not imply runtime execution, host mutation, network access, recovery authority, hardware behavior, or security certification.

Supported

Fixture parsing, deterministic summaries, no-effect flags, source-span metadata, and local regression checks.

Not supported

Rendering as a live UI, command execution, Nucleus task movement, network behavior, or host mutation.

Read next

Use the language overview and evidence page to connect examples back to contracts and claims.

Source Records

Trace the example back to the contract set.

Language overviewLat, LIR, and L-UI roles in one page. Seal overviewReport-only trust and dry-run boundaries. L-UI parserAccepted fixture, result fields, and error labels. L-UI renderingRendering boundary and non-claims. Lat pipelineParse, validate, lower, and report contract.