DEVELOPER DOCUMENTATION

CLI

Install the MANDATE customer CLI (mandate) via npm, bun, pnpm, or yarn.

Start in Observe on one route. Use the deployment URL and installed package version supplied for your workspace. Historical host examples and source capabilities do not establish a live service or published release.

Unpublished customer CLI

@mandate-security/cli 0.1.0 is source-only. Install the reviewed kit candidate;

global registry, Homebrew and signed binary installations are not available.

Internal mandatectl is a separate monorepo operator tool.

bash
npm install -g /absolute/path/to/mandate-integration-kit-v0.4.0/package-cli
mandate init --target . --mode observe --agent --write
mandate doctor

The guided candidate supports login/connect, route discovery, a reviewable

Next.js App Router setup plan and explicit apply, and grouped verify feedback.

Dashboard grant redemption is purpose bound to app/environment/site; current

runtime keys have only the required scoped permissions. Guided dashboard exposure

is flag gated. init, rollout, doctor, kit and version remain available.

No command establishes customer business success or silently enables enforcement.

Route capability declarations are static and bounded. Verify/Limit/Subject and

1–8 enrolled Reroute actions still require matching server/Gate and private-origin

configuration. CLI scanning never executes user callbacks or approves profiles.

doctor checks local connection/configuration without printing secret values.

Exit0 means success, 1 failed check, 2 invalid input. A dashboard one-time install

link writes private handoff files; it does not install the CLI binary. Keep the

link/credentials private and use the generated command exactly.

See Quickstart and SDK overview.