Intelligence.
In a different dimension.

One task. Relationships you can follow.

Take a request to update a record. Its position in a model, its address, its meaning and permission to change it concern the same object. To locate the right record, check authority and inspect the result, the responsibilities must connect through explicit interfaces. They are cooperating views of the work, not a fixed serial pipeline.

HOW IT WORKS

From a mapped relationship to a change you can check.

The dimension has technical substance. A vector describes quantities relative to a declared basis; a mapping connects one representation to another. For software, that relationship becomes useful when you can resolve the represented object, interpret the request, establish authority and inspect an actual operation. These are the architectural connections to examine together.

Vector and mapping models · represent the relationship

Keep the reference frame and transformation explicit. The vortex model exposes local and world position, velocity and basis. Its coordinate readback describes that model; connecting a represented point to application state needs a declared mapping and resolver. Read the vector guide or explore the coordinate model.

KEX · identify and address the state

The mapping needs an object to resolve to. KEX concerns state geometry, identity and addressing; KEX DNA supplies constraints. An address must retain its relationship to the intended object as state changes. The grid and stacked-book exploration separates projection layers so their relationship can be inspected.

IL-LLM · carry meaning through the relationship

The addressed object needs context. IL-LLM structures terms, definitions and relationships so traversal can distinguish, for example, a source document from its generated package. That meaning helps define the requested change without substituting a different object or operation.

BRAINK · govern the proposed change

The understood request and addressed state meet an authority boundary: which actor may perform which transition, with what scope and evidence? BRAINK governs that responsibility. Its execution path needs an actual bound handler and host for the requested operation.

Edge, transport and hardware · carry the relationship into equipment

The communication design extends KEX-addressed work across edge nodes, routers and customer hardware: identify the destination and state, carry the request through a defined channel, and retain the response against the same operation. Edge software keeps task context near the operator; the gateway and routing architecture defines the network boundary; TL / TL2 documents distinct wire implementations; their packet formats do not by themselves resolve KEX state or authorize a device. A target adapter must bind the permitted operation to the equipment’s actual interface.

The modular Ethernet BRAINK hardware design relates input, sensing and output modules through Network ToT and retains observed port responses in Memory ToT. Integration into machinery requires supported device profiles, electrical limits, timing, control authority and physical readback to be qualified for that target. These are documented engineering designs, with physical build and target qualification tracked separately.

Two specified applications, the same relationships. The hospital-bed control design includes a three-module arrangement, with each module designed to handle its own work or the whole bed environment. Input modules, load controllers and sensed responses remain connected through Network ToT and Memory ToT. The specified resilience goal is for a remaining controller to manage the loads through the wired system if two peers fail, retaining the relationship between control and memory. That is a design requirement, not a reported failover test. A requested operation and the observed equipment response retain their separate identities.

The vehicle-electrical retrofit design extends the architecture across a vehicle’s electrical systems to support a locally intelligent car. Switch and sensor modules, compatible load drivers and power distribution connect through local control and retained observations. The design keeps intelligence beside the equipment while preserving the route back to its addressed state and authority. These specified applications do not establish universal machine compatibility or a deployed, medically or automotive-qualified installation.

Application and runtime · execute and read back

The handler performs the permitted operation in its environment. Readback compares the observed state with the intended change. That observation can inform the next decision while preserving which object, meaning and authority the action concerned.

This is an explanation of how the responsibilities relate, not a report that the whole chain has executed. A rendered vector, an addressed object and a saved document each establish different, bounded observations.