USAGE_GUIDE.md

Locus64 Usage Guide

Use l64 as the primary command. On Windows release bundles, run l64.exe from the release directory. On Linux release bundles, run ./l64.

Verify Installation

l64 dump-runtime-roots
l64 clear-cache --scope all

If running from source on Windows:

cargo build --release -p l64 -p l64-cli -p l64-admin
.\target\release\l64.exe dump-runtime-roots

Campaign Certification

l64 certify-derived --campaign CPG_CHAIN_RULE
l64 certify-derived --campaign CPG_CHAIN_RULE_RECIPE
l64 certify-derived --campaign CPG_CHAIN_RULE_TRANSPORT
l64 certify-derived --campaign CPG_BAYES_BRACE
l64 certify-derived --campaign CPG_EXEC_INFER
l64 certify-derived --campaign CPG_PROB_JUDG
l64 certify-derived --campaign CPG_CERT_PROP
l64 certify-derived --campaign CPG_CH_NORM
l64 certify-derived --campaign CPG_CH_INH

Use observe-run after certification:

l64 observe-run --report REPORT_THS_CHAIN_RULE_CPG_CHAIN_RULE

Bundle Certification

l64 certify-bundle --file samples/chain_rule_bundle.dna --conflict-policy exact-match
l64 certify-bundle --file samples/chain_rule_integrated_bundle.dna --conflict-policy exact-match
l64 certify-bundle --file samples/imported_claim_bundle.dna --conflict-policy exact-match
l64 certify-bundle --file samples/imported_claim_stress_gap_bundle.dna --conflict-policy exact-match

RNA/DNA Commands

l64 normalize-rna sample.gene.rna
l64 compile-rna sample.gene.rna --out sample.gene.dna --artifact-class gene --persist-lineage
l64 sequence-dna sample.gene.dna
l64 inspect-dna sample.gene.dna
l64 verify-roundtrip sample.gene.rna --artifact-class gene
l64 export-genome-release --rna sample.gene.rna --out sample-release --artifact-class gene

The lower chain is ledgered as:

Tokenization -> RnaNormalization -> StructuralResolution -> CanonicalNormalization

DNA emission validates header truth, structural opcode law, and symbol-table non-authority before writing the artifact.

compile-rna accepts source RNA only. It rejects inspection reports, receipts, generated views, closure maps, claim pages, stress maps, replay records, and JSON report/projection text.

sequence-dna emits canonical reconstructable RNA suitable for recompilation. inspect-dna emits JSON inspection output and is not source. verify-roundtrip checks the fixed-point path:

RNA -> DNA -> canonical RNA -> DNA

export-genome-release creates a derived release directory with:

genome/
spine/
claims/
frontier/
replay/
views/

Generated manifest, claim pages, dependency spines, closure maps, closure frontiers, stress maps, lineage records, replay records, views, and receipts are projection/record artifacts and are rejected by compile-rna. Generated source RNA and canonical RNA are the only release text artifacts intended to re-enter compile-rna; generated non-source artifacts use role-specific .projection, .record, or receipt filenames rather than .locus authority hints.

Export, Import, Validate

l64 export-validation-dna-bundle --id REPORT_THS_CHAIN_RULE_CPG_CHAIN_RULE --out chain-rule.validation.dna
l64 import-bundle chain-rule.validation.dna
l64 export-report-dna --report-id REPORT_THS_CHAIN_RULE_CPG_CHAIN_RULE --out chain-rule.dna
l64 import-report-dna chain-rule.dna

Lock and Replay

l64 lock-bundle samples/chain_rule_integrated_bundle.dna --optimizer-policy conservative --conflict-policy exact-match
l64 replay-with-lock <LOCK_ID> --parallel-obligations --max-obligation-workers 3

Research Host

l64 research-import --kind task samples/research/task_operational_truth.json
l64 research-import --kind signature samples/research/signature_operational_truth.json
l64 research-route --task-id TASK_OPERATIONAL_TRUTH_HARDENING --signature-id SIG_OPERATIONAL_TRUTH_HARDENING
l64 research-derive-from-report --report-id REPORT_THS_CHAIN_RULE_CPG_CHAIN_RULE --persist
l64 research-promotion-readiness REPORT_THS_CHAIN_RULE_CPG_CHAIN_RULE
l64 research-status

research-derive-from-report creates warm-host projection records unless a later replay-specific path promotes them. A report verdict such as Integrated or Certified is preserved as an assumption on the derived claim packet; it is not automatically evidence authority for the research object.

For exact syntax and record shapes, see LOCUS64_LANGUAGE_SPEC.md.

For semantic claim governance, branch tracking, derivation lineage, and cosmology-style workflows, see SEMANTIC_USAGE_GUIDE.md.

Policy Authority

Evaluator behavior comes from named, scoped policy objects rather than ambient defaults or report prose. Equivalent policy sets resolve deterministically even if registry ordering changes.

Use policy objects in bundle text when you need scoped evaluator behavior:

policy-object {"id":"MOP_LOCAL_EVAL","kind":"Evaluator","scope":{"Theorem":"THS_LOCAL"},"extends":null,"optimizer":null,"evaluator":{"evidence_preference":"RecomputeIfSupported","allow_approximation":false,"unsupported_mode":"StrictFail","require_symbolic_fidelity_route":false,"prefer_comp_replay":true},"replay_cache":null,"report":null,"scheduler":null,"canonicalizer_mode":null,"merge_policy":null,"notes":["strict local evaluator"]}

Coverage and Tower

l64 dispatch-coverage --report-id REPORT_THS_CHAIN_RULE_CPG_CHAIN_RULE
l64 derive-frontier --report-id REPORT_THS_CHAIN_RULE_CPG_CHAIN_RULE
l64 tower-step --report-id REPORT_THS_CHAIN_RULE_CPG_CHAIN_RULE
l64 derive-distress --report-id REPORT_THS_CHAIN_RULE_CPG_CHAIN_RULE

Reuse is lawful only when canonical identity or declared transport-equivalence, closure-valid lineage, replay legality, and residual-obligation accounting all pass.

Torture Harness

powershell -ExecutionPolicy Bypass -File .\scripts\torture-test.ps1

Useful smaller smoke pass:

powershell -ExecutionPolicy Bypass -File .\scripts\torture-test.ps1 -OuterRounds 1 -InnerNamespaces 1

Artifacts land in release\torture by default.

Cache Isolation

Set MF_CACHE_NAMESPACE to isolate runs:

$env:MF_CACHE_NAMESPACE='demo'
l64 clear-cache --scope all

Release users can delete .l64-cache safely when no run needs cached reports or research artifacts.