Immutable control plane · root materialization

Doğu One

The live interface below is resolved from the authoritative root binding, an exact-pinned HTTP manifest and reusable Surface IR primitives. Route and presentation changes are data changes.

LIVE · DATA-DEFINED

Active root contractruntime/dogu.one/bootstrap → active rootexplicit immutable binding · exact CID resolved at request time

HTTP root manifestruntime/dogu-one/http-root@7immutable content-addressed route manifest

Deployed kernelGeneric resolver + native targetproduction resolves deployed kernel

Resolution path

authority → manifest → target

Bootstrap bindingruntime/dogu.one/bootstrap

→

HTTP root manifesthost + path → immutable route target

→

Surface / native primitiverender, redirect, JSON or native protocol

01 · Surface

Manifest-rendered interface

This page itself is the proof: the root surface is rendered through Surface IR from immutable data, not a page-specific React implementation.

/runtime /runtime-health

02 · Protocol

MCP parallel cutover

Canonical /mcp stays on the temporary direct bypass while /runtime-mcp resolves through the root manifest to the exact same native MCP handler.

/mcp401 · AUTH OK

/runtime-mcp401 · SAME HASH

03 · Compatibility

Legacy fallback remains intact

Unmigrated paths fall through without owning business semantics. /login remains the current compatibility projection until it is represented by immutable data.

Open /login

Materialized review surfaces

The same data-first renderer is already driving real review interfaces with visual assets.

Channel conceptsWeb · Instagram · Facebook · LinkedIn · Newsletter mockups Image benchmarkFull outputs · crops · rounds · QA · economics