NEXUS CEREBRI / Developer Surface
One Rust authority, multiple thin transports.
The synchronous core facade backs REST and the provisional Node process bridge. Public web pages consume generated fixtures, not live runtime calls.
The API exposes planning, validation and temporal diagnostics under /v1. Execution is intentionally absent from the REST surface.
Native bindings, worker isolation and provider adapters are future transport/application choices, not planner semantics.
A transport boundary lists validate, plan and temporal REST routes and explicitly shows that execute is absent, followed by a directional adapter-to-core-to-domain flow.
POST /v1/validate
POST /v1/plan
POST /v1/temporal
// intentionally absent:
POST /v1/executeTransport delegates. Domain truth does not move outward.
Text alternative
A transport boundary lists validate, plan and temporal REST routes and explicitly shows that execute is absent, followed by a directional adapter-to-core-to-domain flow.