The v1.5.3 Native lispex binary evaluates source and exposes versioned lowering, receipt, namespaced Vouch issuance, authentication, verifier re-execution, a local decision gate, structural inspection, and Bridge checks with separate contracts.
Current guarantees
lispex [FILE|-]evaluates source;receiptrecords the native execution envelope;lowerandeval-graphoperate on the checked subset.- The namespaced workflow is
lispex vouch issue,lispex vouch verify,lispex vouch verify --reexecute,lispex vouch gate --require-decision, andlispex vouch inspect; npm also provideslispex vouch replay. There is no flatgatealias. - A successful
--reexecutereport hasauthentication.statusset toauthenticated,reexecution.statusset toexecution-agreed, fixedobservation_scopecsk.vouch-complete-transcript/v0, andcomparison.current_vs_signedset toagree. vouch gaterequires all raw context paths plus--require-decision approve|deny|review|invalid-inputand--report-out. Itscsk.native-gate-report/v0separates authentication, re-execution, and gate status and records the fixed basiscsk.current-native-agreement/v0.- File and stdin identities are recorded explicitly where an artifact contract requires them.
Command boundaries
| Command | Reads | Writes / does not establish |
|---|---|---|
| lispex [FILE|-] | Lispex source bytes | canonical result/stdout and diagnostics; no receipt |
| lispex receipt FILE | source bytes | native execution receipt; not a Vouch differential receipt |
| lispex diff-receipt --input I RULE | checked-profile rule and datum | csk.differential-receipt/v0; not authenticity |
| lispex verify RECEIPT | receipt JSON and optional source | consistency verdict; does not re-run policy |
| lispex issue-native ... | checked-profile rule, pinned input, profile, and local PKCS#8 key handle | atomic payload, DSSE envelope, and issue report; native release binary only |
| lispex verify-native ... | DSSE envelope, consumer trust policy, source, input, profile, and expected engine context | authentication report for exact checked context; no identity, time, deployment, or policy-correctness proof |
| lispex verify-bridge REPORT | Bridge report and bound artifacts | Bridge consistency verdict; no external-engine execution |
Boundaries
- For
vouch gate, exit 0 means a live grant matched the required decision; 10 means authentication succeeded but no grant was minted; 1 means authentication rejection; 2 means usage error; and 3 means I/O, execution, or report-publication failure. A report is diagnostic output and cannot be reused as gate input.