COMPASS developer documentation

COMPASS stores what a team currently believes, keeps the history of how that belief changed, and can tell an agent — deterministically, without a model in the loop — whether a given rule still holds and why.

This documentation is for developers connecting an agent (Claude Code, Cursor, Codex, or a custom MCP client) or a service to COMPASS, and for anyone integrating directly against the REST API.

Where to start

• Concepts — the one form COMPASS stores everything in: Sache, Aussage, bi-temporal validity, superseding, the one-current-rule guarantee, tenants, and personas. Read this first.
• Quickstart — five steps: connect the MCP server, import a rule set, ask what holds and why, look at deviations, then supersede a rule and watch the old one become visibly superseded.
• Guides — task-focused walkthroughs: importing a rule set, setting and superseding a rule, attaching a check, connecting an editor, searching.
• Reference — the REST API grouped by area, every MCP tool with its parameters, and the shared form each record is built from.

Scope of this documentation

Everything documented here is checked against the running code — an endpoint or tool is only described if it exists in both the contract and the running code. Endpoints that exist in code ahead of the contract, or are mentioned in the contract but not yet built, are intentionally left out; they are not part of the supported surface yet.