Documentation

The canonical definition of BlackLake, Surface, Depth, the `blacklake` package, and the cloud control plane. Read this once and the four-question test answers itself.

One-minute decision guide: start with cloud for fastest time to value and shared team controls, or self-host when an air-gap or procurement constraint requires it.

Search-and-replace examples for moving from `@blacklake-systems/surface-cli`, `surface-sdk`, `depth-cli`, `depth-sdk`, and the standalone `blx` to the unified `blacklake` npm package.

Govern Claude Code, Codex, Cursor, and other MCP clients through BlackLake. The five-minute capture path for coding tools.

Wrap your code's LLM and tool calls with `govern()` — the right path for backend services and custom AI Actors.

`blx git push`, `blx terraform apply`, `blx gcloud run deploy`. Classify, govern, run, record. The shell-side capture path.

Write policies that enforce the rules you actually want — including cost-aware policies that deny before the spend.

Per-call cost across seven providers, budgets that deny at govern() time, cost-aware policies, baselines + anomaly detection, and v2 receipts that bind cost to the decision token.

AI Actors, tools, policies, evaluations, cost governance, budgets, v1+v2 receipts, baselines + anomalies — the model behind BlackLake.

Every method on the unified `blacklake` package — govern(), cost, budgets, decisions, agents, tools, bindings, policies, approvals.

Every HTTP endpoint with curl examples and error codes.

Run `npx blacklake run workflow.ts`, write your first workflow, and run it with crash recovery.

Steps, replay, LLM routing, cost tracking, governed tool calls.

Every workflow / step function and type in the unified `blacklake` package.