We can think of the multiplexed instance tree as a queuing system. The links between the workflow nodes (async functions leading from one to the next) are like (possibly conditional) links in a promise chain. In a holon, all the workflow nodes connect each other into such a chain and there can also be other parallel event-triggered chains.

All these nodes occupy the same closure (local namespace) together so they can collaborate on and progress shared and persistent state and workload. This is identical to a JS stateful closure pattern where control passes between different async functions that all operate on the same shared closure together collaborating on state and progressing work.

Note that call and return parameters are not used in this pattern. The condition:action nature forms naturally since in a closure of siblings collaborating on state and work, they will assess conditions based on that local state that lead to activity being performed on it.

These private closures are not just JS, but are merged together with other forms of agency that are also local siblings such as LLMs and humans – a sort of cross-discipline distributed object. Even foreign agents can be participants in such a workflow pattern, this is the so-called “social computation” pattern.

It’s the same thing with a “cross-discipline” pattern involving multiple forms of agency, it’s multiple versions of the instance maintained in different instance-trees maintained by different tech-stacks and focused on different aspects. But the group of them form a common background content structure so the collective aspect is known.

I think in terms of an async environment (stateful closure pattern), we think of a closure as having a workflow aspect that can be represented in JS as a conditional promise chain such as by using async() as a function execution queuing mechanism.

Other execution or agentic systems can participate in local closures such as LLM or shell. They represent the same instance closure structure as well and all the various representations are synchronised. In any of these contexts, the siblings of all disciplines are seen as local, and their actions spontaneous and asynchronous.

Any kind of agent in any holon scope in whatever language/tech context can interact as a local universal sibling-agent-holon with the others regardless of their differences in implementation, physical location, scale or speed etc.

But this can be very useful solely as JS even before we figure out connecting other agency or remote holons in. The UI is a cross between workflow and brain.com / mindmap representing the self-organisation of the holon.

Different views onto the context can serve different purposes (the views are themselves siblings maintaining specific-lang “reports” of the context).

To summarise the quadrants in this context: the self-organisation structure (BL) is the mind-map, the allocation of our own attention and forms of resource. This can have workflow with live condition-triggers throughout it. BR is the interface sessions of interaction and activity stream. TL is the ontology, the full institutional aspect of all our classes of interest. TR is the schedule of value exchange, and our profile as a market participant.