Guides & technical docs

Don't trust the docs

Verify before you read

The fastest way to calibrate how much of this documentation to believe is to break the integrity claim yourself, offline, in about a minute. Export a store, verify the bundle with no network, flip one byte, and watch the verifier refuse it:

corecruxctl context export --data-dir <dir> --out ./bundle
corecruxctl context verify ./bundle --json   # ok=true, offline
bash scripts/demo-receipt-tamper.sh          # flips a byte, asserts the catch

Every guide below assumes that footing: claims link to source, commands are copy-paste runnable, and anything gated by tier says so explicitly.

evidencetamper script·release verification·security policy

Build on the daemon

Crux Daemon developer guide

Thirteen chapters on extending corecruxd: packs, tools, sandboxed modules, connectors, and the signed rail you ship them on. Every claim carries a file:line reference into the Crux repository, and where a surface is declared but has no runtime, it says so.

1. 00Developer guideIndex and entry points for building on the Crux Daemon: who each chapter is for, the three principles the whole extension surface follows, and three copy-paste quickstarts.
2. 01ArchitectureWhat you build against: one binary with HTTP, MCP and gRPC listeners, the data-dir layout, the auth modes and scopes, and the error shape every route returns.
3. 02Integration packsThe crux.integration.v1 manifest field by field, all nine entry kinds, and the single validate() gate that every install path runs.
4. 03Capabilities and grantsThe 14 declarable capabilities, the two grant models that share vocabulary but no storage, and the operator posture that decides what installed code may actually do.
5. 04Signing and trustEd25519 signing end to end: the signature envelope, the operator keyring, trust tiers, the curator-signed community index, and the development bypasses.
6. 05External toolsThe HTTPS extension path: the wire contract for your own service and the full enforcement pipeline the daemon runs on the way out and back.
7. 06WASM extensionsRunning sandboxed code inside the daemon process: the wasmtime sandbox, the host ABI, hash pinning re-verified on every dispatch, and the fuel, memory and wall-clock limits.
8. 07Connectors and syncPush-based work: the shared scheduler, the status facts a job writes, the vault watcher, and the GitHub and OpenAI connectors that ship today.
9. 08Studio packs and workspacesShipping dashboards other people install: the crux.studio.v1 payload, canonical JSON, build and verify, the underlying fact schemas, and the curator-signed template library.
10. 09Registry and publishingBoth distribution rails end to end, from authoring and signing through curation, sync and install, plus the full corecruxctl command reference.
11. 10MCP surfaceHow an installed, granted extension tool reaches an agent tool list beside the built-in tools, and what happens when the passport is missing.
12. 11Security modelA plain statement of the extension trust boundaries and which controls are enforced, which are advisory, and which are declared but not yet wired.
13. 12TroubleshootingReal error strings quoted from the code that emits them, what each one means, and the silent-failure modes that produce no error at all.

Technical guides

Defensibility & legal FAQ

Security & legal policy