Skip to main content

15-minute quickstart

This quickstart runs the implemented single-tenant treasury-transfer pilot on loopback with sandbox execution and synthetic assets. It produces a complete authorization and evidence workflow for controlled validation.

Source access

The public protocol repository provides the cryptographic core. Approved design partners and security reviewers receive the complete commercial-pilot source bundle and deployment components.

Prerequisites​

  • Rust 1.88.0 or the toolchain pinned by the supplied source bundle;
  • Node.js 20 or newer;
  • cargo, npm, curl, and a Unix-like shell; and
  • an isolated development machine with no real keys or assets.

1. Build the pilot binaries​

From the commercial-pilot source root:

cargo build --all-features --bins
npm ci

2. Create private pilot state​

deploy/pilot/pilot-control.sh init examples/product-v0.1/policy.json

Initialization creates role credentials, a sandbox signing seed, policy, state, logs, and backup directories under .luvion-pilot/. These files are private and must never be committed.

3. Validate and start​

deploy/pilot/pilot-control.sh doctor
deploy/pilot/pilot-control.sh start
deploy/pilot/pilot-control.sh health

The API listens only on 127.0.0.1:8787. A correct local profile reports a non-production environment, an authorization backend, and sandbox execution.

4. Run the acceptance workflow​

npm run demo:pilot

The script exercises three scenarios:

  1. a policy-scoped transfer through separated approvals, authorization, sandbox execution, and evidence export;
  2. a destination outside the allowlist that must fail closed; and
  3. an emergency rejection that ends with a terminal evidence bundle.

The report is written under .luvion-pilot/demo-reports/<run-id>/ and contains no bearer credentials or private signing material.

5. Inspect and stop​

find .luvion-pilot/demo-reports -maxdepth 2 -type f -print
deploy/pilot/pilot-control.sh stop
deploy/pilot/pilot-control.sh doctor

Read Request lifecycle for the state transitions and Protocol objects for the fields bound into authorization and evidence.

Validated scope​

This workflow proves that the controlled pilot can bind a request to one policy, enforce separated roles, issue a signer-backed authorization, reject selected invalid paths, execute through an idempotent sandbox adapter, and export deterministic evidence.

The production progression adds independently operated signer hosts, hardware-backed keys, a named partner adapter, external security review, and production operations acceptance.