Install path

One command to get from customer repo to verified evidence.

Imladri setup is split intentionally: terminal/API commands control the action boundary in the customer repo, while Profile owns review, monitoring, proof export, and buyer sharing.

Verify a proof Read customer guide

Install the CLI

Run the installer or install the packed CLI in the customer repo. The command creates local config only; it does not print or store provider secrets.

Login to Profile

Authenticate the customer workspace, select the active agent, and rotate a one-time SDK key into the local ignored session.

Publish policy

Declare allowed, review-required, and blocked actions in Profile or from terminal flags, then publish the active constitution.

Run proof

Execute one allowed action and one blocked-before-body action from the customer repo or API path.

Verify and share

Export JSON/Markdown/PDF, verify the JSON packet locally or in the browser, then create an auditor-redacted share when ready.

Step	Command
Install	`powershell -ExecutionPolicy Bypass -File .\scripts\install-imladri-cli.ps1`
One command setup	`imladri onboard --worker-url https://<worker> --email [email protected] --password <password> --scan-path . --proof-output imladri-proof.md`
Manual proof run	`imladri proof run --allowed-action ticket.summarize --blocked-action credential.export --stack "LangChain"`
JSON export	`imladri proof export --format json --redaction auditor --output imladri-proof.json`
Local verify	`imladri proof verify --input imladri-proof.json`
Browser verify	`https://imladri.com/verify-proof`

Surface	Responsibility
Terminal/API	Wraps the action where it actually runs, uploads runtime evidence, scans the repo, certifies adapters, and exports proof artifacts.
Profile	Shows the active agent, policy, SDK key state, monitored decisions, proof readiness, public shares, DB sandbox state, and provider training status.
Admin	Reads back customer, workspace, agent, route, activity, key, and proof state without exposing raw SDK keys.