Liria

Documentation

Three readers,
three paths.

The docs are single-sourced in the repository and curated here by consumer. The tiers are explicit on purpose: ground-truth references are prominent, narrative chapters carry their caveats, and aspirational chapters are labeled rather than hidden. A docs claim you cannot check is testimony, not documentation.

01

Human developer

Build and run your first agent

The verified track: install, write an agent, replay it — then the references that match the parser as it ships.

  1. 01 Getting started (install → first agent → replay → trust)
  2. 02 Language reference
  3. 03 Modules quickstart
  4. 04 Testing
  5. 05 Development workflow
  6. 06 Style guide
02

Agent · machine consumer

Learn the grammar from ground truth

Machine-checkable sources only. Do not learn syntax from narrative chapters — learn it from the reference, the opcode table, and examples that pass liria-cli check.

  1. 01 Language reference (grammar truth)
  2. 02 Opcodes
  3. 03 Syntax reference
  4. 04 Cheatsheet
  5. 05 Verified examples (pass liria-cli check)
  6. 06 Specs (IR, hashing, interchange)
03

Auditor · verifier

Verify without trusting the operator

The replay tutorial, the trust model, the constitution the runtime enforces, and the decision record — everything a third party needs to check the chain.

  1. 01 Deterministic replay tutorial
  2. 02 Trust model
  3. 03 Constitution
  4. 04 Critical-infra guardrails
  5. 05 ADR index (architecture decisions)
  6. 06 Release docs + conformance conformance: docs/conformance · gate: gate.sh
  7. 07 Security guide status caveat

Narrative chapters verify against the language reference

Useful orientation, written ahead of the parser in places. When a sample here disagrees with language_reference.md, the reference wins.

Aspirational chapters syntax does not parse in v0.1

Design-direction documents carrying NOT-IMPLEMENTED banners in the repo. Listed here because hiding them would be dishonest; do not learn syntax from them.