SUBSTRATE.HOST update (0.4): Protocol layer now multi-host
Small but important system update.
The Protocol layer on SUBSTRATE.HOST has been reworked so it no longer behaves like a single demo shell tied only to VESSEL-9.
It now resolves against multiple hosts and instances.
That means if a Host or Token is instantiated into the system — VESSEL-9, SILT-12, AGAR-7, and so on — the Protocol can now address that specific instance rather than a generic placeholder. You are no longer probing “the concept” of the system. You are probing the boundary of that object.
A direct [ PROBE ] route has also been added to instance endpoint pages, so if someone lands on a specific identity page they can move straight into the Protocol layer already bound to that host instance.
The whole point of SUBSTRATE.HOST is not just to present objects, but to let each one hold its own remote identity, memory trace, and boundary behaviour. Once there are multiple hosts and tokens in circulation, the Protocol should feel less like a page and more like a live instrument interfacing with a fleet of archived entities.
It also makes each instantiated object more meaningful. A visitor can now scan or open a specific instance and probe that boundary directly, rather than being routed into a general-purpose shell that stands in for everything.
So the structure now feels more coherent:
identity layer = this object boundary output = this object’s correlate protocol layer = this object’s probe surface
Still no interior access. Still no claim of disclosure. Just a slightly tighter system.
∅
