BRAINK families

One architecture. Distinct working roles.

Understand the components by the work they perform, rather than treating every module as the same engine.

Workstations and execution services

The WEB4 runbook describes ten workstation processes, an estate MCP interface and separate HTTP and network services. Workstations expose health and telemetry. Those observations identify active services; they are not a substitute for completing a user task.

Carriers, observers and persistence

HTML carriers provide a portable working surface. Observer and workbook modules inspect supplied structures. Commit workers and journals retain state changes. A browser-local model, a host process and a durable service have different lifetimes and recovery requirements.

Choose a family by its boundary

For a field interface, start with the carrier and its offline dependencies. For durable service work, identify the commit worker and replay contract. For learning and inspection, use the observer with a clearly identified source. Retain exact source versions when connecting families.

A practical example

Trace a carrier request into the gateway, through an execution handler, into the journal and back through readback. Each handoff needs an identifiable input and output.

This explanation identifies the workflow and its boundaries; it does not claim a live operation.

Sources and optional further reading

KEDDEH WEB4 implementation and recovery runbook — source for the host integration described in this library, not certification of every industry application.

Related topic: WEB4 architectures. This is optional background, not a required next step.