Handbook

LMeta v5-alpha authoring

v5-alpha artifacts are source and compiler input, not a production runtime. Executable output is always AutomationFlow v4 JSON validated and run by FlowExecutor.

Updated

Native AutomationFlow v5 runtime remains held until an explicit RFC and parity evidence exist.

Authoring ladder (C0–C4)

Rung Artifact Maintainer action
C0 Human utterance Not stored in repo
C1 Taxonomy + recipe YAML Closed-world matchers
C2 Hand-authored AF v4 Rollback / parity baseline
C3 GoalSpec (*.goal.v5.json) Profile-bound goals
C4 IntentProgram router Static closed-world dispatch

Pipeline (lab / CI)

GoalSpec + profile.yaml
  → PlanIR → BoundPlan → AutomationFlow v4
  → validate_flow + parity tests → commit generated JSON

IntentProgram routers compile to the same static switch-router v4 shape as hand-generated dispatch flows (compile-router in lmeta-v5-lab).

Rules

  1. No live chat → compile — compilation runs in maintainer sessions and CI only.
  2. Closed profiles — capabilities, methods, and hooks come from the profile; GoalSpec must not embed SQL, paths, or hook names from user text.
  3. One LLM call on fast-path recipes unless an explicit policy documents otherwise.
  4. Pin hashes — CI --check scripts fail when generated v4 drifts without a deliberate refresh.

Laboratory package

Reference compiler and schemas live in workbench/lmeta-v5-lab (lmeta_v5_lab.compiler, router_compiler). Consumers set LMETA_V5_LAB_ROOT for router regeneration scripts.