Skip to main content
Bijection is a governed operational workspace. It captures the systems you already run on at an immutable published basis, expresses that world as one model declared in code, and makes every change to it a planned, reviewable, recorded action. The platform is domain-neutral. A model directory — objects, links, functions, actions, connectors, dashboards, automations, and Workshops — is the complete production composition input. Swapping that directory yields a different operational product with no change to the platform itself.

​
Three product interfaces

eclipse

Requests Eclipse deployment lifecycle and authors signed product changes. No live-world or infrastructure credentials.

atelier

Governed human and agent operations over the same public HTTP API the web app uses. No direct database, storage, or connector authority.

axiom

Chat, Agent Runs, evaluation, and AI evidence. No Action execution or direct world authority.
The platform map is: Eclipse delivers. Atelier represents and governs the world. Axiom reasons over it. Only Atelier Actions change it. eclipse, atelier, and axiom are separate public CLI/SDK products. Mothership is deployment-internal and Panopticon is local-development-only.

​
The two contracts everything else follows from

Declared source datasets are captured and read only at an immutable published basis. There is no live, federated, or query-time source read. Freshness comes from capturing more often — never from reading around the basis. See Capture.
A plan is stateless and shows exactly what will change. Execution is the only thing that mutates, and it writes an append-only fact carrying the bounded decision evidence the action declared. See Actions.

​
Where to go next

Quickstart

Six steps from signing in to your first governed decision.

Architecture

What runs, what owns what, and where the boundaries are drawn.