Forge

One command port. Four surfaces, generated from it. Documentation that cannot disagree with the code.

Start where you are

API: your first call	Read something, change something, read it back. Five minutes, no credential for the first half.
CLI: forge login	The whole registry from a terminal.
MCP: connect an agent	The registry as agent tools, behind the kernel’s own scope check.
SDK: npm install	Three methods, every name typed.
Development environments	A shop and an admin on your machine in minutes, as many benches as you need, reachable from any network — then staging, then production.

The idea, in one paragraph

Every mutation in Forge goes through a single command port — no admin back door, no direct table write, no second path. Because there is exactly one place where change happens, the API, the CLI, the MCP server and the SDK are not four implementations of the same thing: they are four projections of one registry, generated from it. So is the reference on this site.

A command that exists is reachable from all four on the day it lands, and a reference page cannot describe an endpoint that is not there. Not by discipline — by construction.

Then the shape

• The kernel & the single port — one transaction, one truth, and what follows from refusing a second write path.
• Apps & extension — the four places your customisation lives, none of them inside the kernel.
• Identity & scopes — why the audit trail names a key rather than “someone”.
• Deploy & the fleet — a version you pin, on infrastructure you own.