Test the platform

One ID for everything

platform

Everything below uses one account: your compass-platform ID. Sign-in pages live at id.compass-platform.dev (your account belongs to its platform realm), and every service and connector on this page authenticates against it.

Sessions are per app: signing in to one service does not sign you in to the others. Each app sends you to the same sign-in page once, then keeps its own session — so an occasional extra sign-in prompt is expected, not a fault.

CheckOpen any service below while signed out — you are redirected to a sign-in page on id.compass-platform.dev.

See your world on the System Map

public

Open map.compass-platform.dev and sign in. The System Map is a living picture of the entities that carry your system, in two views: the dossier (the entities and what is written about them) and the journal (what happened, in order).

CheckAfter a fresh sign-in, a chip with your name appears in the app — that is the map recognising you.

Connect the map to your assistant

public

The System Map speaks MCP — the open protocol AI assistants use to reach tools. In claude.ai, open Settings → Connectors → Add custom connector and fill in:

Name

System Map

URL

https://map.compass-platform.dev/mcp

When you add it, a sign-in window on id.compass-platform.dev opens — approve it. The connector asks for exactly two permissions: system-map:read and system-map:write.

Using the System Map connector, read the current system map and give me the three most load-bearing entities with their constitutional notes.

CheckThe reply names entities from your map — the same ones you saw in the dossier view — not invented ones.

Let your assistant prepare a decision

business

The Decisions service keeps significant choices out in the open: each decision has a briefing, options, and a recommendation — and a clear record of who ruled, and when. Add it as a second connector, the same way as before:

Name

Decisions

URL

https://decisions.compass-platform.dev/mcp

Approve the sign-in window (the consent screen identifies the app as decisions-connector). The permissions are decision:open, decision:inspect, decision:read, and decision:await — revising or withdrawing a decision rides on decision:open.

The rule that matters: an assistant can open, inspect, read, revise, withdraw, and await decisions — it can never rule one. Ruling is reserved for you, in person, in the Factory studio (next step).

Two things worth knowing about every decision:

• Its id reads workspace/project/decisionKey — for example ai-experiments/recursive-system-map/D18.
• The moment a decision is opened it also appears in the public ticket ledger on the Forge (git.compass-platform.dev, project compass-platform/tickets) as an issue labeled awaiting-GO — a paper trail nobody can quietly edit.

Using the Decisions connector, list open decisions and show me ai-experiments/recursive-system-map/D18 — briefing, options, and the marked recommendation.

CheckThe assistant returns the decision's briefing, its options, and which option carries the recommendation mark — and the same decision is visible as an awaiting-GO issue in compass-platform/tickets.

Rule it yourself, in the Factory

business

Now close the loop. Open the Factory studio at platform.compass-platform.dev/factory and sign in. Find the decision your assistant just showed you, read the briefing with your own eyes, and make the ruling.

This is the platform's division of labour in one gesture: the assistant did the reading and the preparation; the judgment stayed with you.

CheckAfter you rule, watch the matching issue in compass-platform/tickets: its label changes away from awaiting-GO.

For developers: the same connectors in Claude Code

platform

Both connectors work anywhere MCP does. In Claude Code, add them from the terminal — the sign-in opens in your browser:

claude mcp add --transport http system-map https://map.compass-platform.dev/mcp
claude mcp add --transport http decisions https://decisions.compass-platform.dev/mcp

Developers working inside the platform codebase additionally get a set of Claude Code plugins for operating and extending the platform itself; their source lives in the platform repository under packages/platform-plugins. That is platform-developer territory and not covered here.

CheckAfter claude mcp add and the browser sign-in, the connector's tools appear in Claude Code.

The Forge: your code on the platform

platform

The platform runs its own Git service at git.compass-platform.dev — sign in with your compass-platform ID. This is also where the ticket ledger from the decision steps lives.

One deliberate difference from other Git hosts: SSH is disabled. Pushes go over HTTPS, authenticated with an access token you generate in your Forge account settings.

CheckYou can sign in to the Forge with the same ID as everywhere else, and a push over HTTPS with an access token succeeds — while an SSH remote does not connect.