Native CLI Commands

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; receipt records the native execution envelope; lower and eval-graph operate on the checked subset.
  • The namespaced workflow is lispex vouch issue, lispex vouch verify, lispex vouch verify --reexecute, lispex vouch gate --require-decision, and lispex vouch inspect; npm also provides lispex vouch replay. There is no flat gate alias.
  • A successful --reexecute report has authentication.status set to authenticated, reexecution.status set to execution-agreed, fixed observation_scope csk.vouch-complete-transcript/v0, and comparison.current_vs_signed set to agree.
  • vouch gate requires all raw context paths plus --require-decision approve|deny|review|invalid-input and --report-out. Its csk.native-gate-report/v0 separates authentication, re-execution, and gate status and records the fixed basis csk.current-native-agreement/v0.
  • File and stdin identities are recorded explicitly where an artifact contract requires them.

Command boundaries

CommandReadsWrites / does not establish
lispex [FILE|-]Lispex source bytescanonical result/stdout and diagnostics; no receipt
lispex receipt FILEsource bytesnative execution receipt; not a Vouch differential receipt
lispex diff-receipt --input I RULEchecked-profile rule and datumcsk.differential-receipt/v0; not authenticity
lispex verify RECEIPTreceipt JSON and optional sourceconsistency verdict; does not re-run policy
lispex issue-native ...checked-profile rule, pinned input, profile, and local PKCS#8 key handleatomic payload, DSSE envelope, and issue report; native release binary only
lispex verify-native ...DSSE envelope, consumer trust policy, source, input, profile, and expected engine contextauthentication report for exact checked context; no identity, time, deployment, or policy-correctness proof
lispex verify-bridge REPORTBridge report and bound artifactsBridge 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.