Approved private-beta setup

Installation starts after private-beta approval.

Public account creation and Profile login are closed. This page is the setup reference for selected private-beta teams after Imladri issues their workspace and credentials.

1

Receive private access

Selected teams receive an approved workspace, scoped credentials, and an onboarding contact before they run the product path.

2

Install the CLI

After approval, install the CLI and SDK in the customer repo. The command creates local config only; it does not print or store provider secrets.

3

Publish policy

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

4

Run proof

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

5

Verify and share

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

StepCommand
Approved package installnpm install @imladri/cli @imladri/sdk
Invited workspace setupnpx imladri onboard --worker-url https://<approved-worker> --email <approved-email> --password <issued-password> --scan-path . --proof-format json --proof-output imladri-proof.json
Manual proof runnpx imladri proof run --allowed-action ticket.summarize --blocked-action credential.export --stack "OpenClaw"
JSON exportnpx imladri proof export --format json --redaction auditor --output imladri-proof.json
Local verifynpx imladri proof verify --input imladri-proof.json
Browser verifyhttps://imladri.com/verify-proof
SurfaceResponsibility
Terminal/APIWraps the action where it actually runs, uploads runtime evidence, scans the repo, certifies adapters, and exports proof artifacts.
ProfileShows the active agent, policy, SDK key state, monitored decisions, proof readiness, public shares, DB sandbox state, and provider training status.
AdminReads back customer, workspace, agent, route, activity, key, and proof state without exposing raw SDK keys.