WEB4 architectures
KEDDEH uses WEB4 as an architecture for connecting its preserved HTML environments with host services, named state and verifiable readbacks.
Follow the practical exampleThe documented gateway serves terminal, carrier and research interfaces. Its authenticated control path reaches the estate MCP, workstation services and commit workers. The user interface should show the returned state of those services, rather than translating browser animation into a success claim.
A browser tab can close while durable server state remains. Namespace generations, journals and stored snapshots identify what must survive. Recovery must reopen the stored state and verify its relationship to the source and previous generation.
Package the carrier, API contract, dependencies, configuration and recovery instructions together. Keep deployment identity distinct from a content pointer. A saved package, a launched process and a public HTTPS service are separate results that need separate records.
Open a carrier, request an operation, retain its result identity, close the tab and reopen it. Recovery should retrieve the same recorded result rather than reconstruct an unverified screen state.
This explanation identifies the workflow and its boundaries; it does not claim a live operation.
KEDDEH WEB4 implementation and recovery runbook — source for the host integration described in this library, not certification of every industry application.
Related topic: Edge nodes. This is optional background, not a required next step.