PLATE · Ⅱ Living Connectome Digital artifact · NFT
№ 4 ARI Living Connectome

№ 4

Software architecture made inspectable — with permanent provenance.

№ 4 is the ARI Living Connectome drawn as an interactive object: modules, classes, functions, and methods recovered from the running stack; edges recovered as real dependencies; the commit record attached so the work can be audited. The chamber below is a live slice of that graph. Launch the full viewer when you want every construct in view.

Living connectome

Modules · classes · functions · methods · edges recovered from the running ARI stack

Every node is a real symbol in the codebase. Every edge is a recovered dependency. The graph is the architecture made visible — not a metaphor for it. Launch the full viewer to navigate all 6,712 constructs and read provenance at the commit stamped above.

· LIVING CONNECTOME · loading…
click + drag to orbit · scroll to zoom · construct field preview
Best experienced in a full window. Audio plays inside the viewer.
Launch full viewer
Constructs
—
Edges
—
Modules
—
Provenance
· —
§ 01 · The subject is the system

An interactive 3D artifact of a running architecture

Most digital art represents something. № 4 is something: a navigable rendering of the call graph, module boundaries, and runtime topology of the ARI software stack. Every node corresponds to a function or module that actually exists in the codebase; every edge corresponds to an actual reference relationship recovered from static analysis.

The chamber previews the construct subgraph; the full viewer is the same code the NFT owner runs locally — there is no separate marketing build of the graph. Provenance is anchored to a specific commit hash, displayed at the top of the chamber and stamped into the token metadata.

§ 02 · What you are looking at

Nodes · Edges · Modules

What the chamber renders maps one-to-one to what the ARI system contains. The viewer is not a stylized metaphor for an architecture — it is the architecture, drawn. Every shape on screen names a real entity in the running code.

Node
Every node is a real symbol in the codebase — a class, a method, a helper, a function, an internal API surface, a support process. The connectome's node count is the system's symbol count, not a sampled or curated subset.
Edge
Every edge is a real reference between two nodes — a call, an import, a subscription, a message hop, a data dependency. Recovered directly from static analysis of the actual source tree, then validated against runtime traces.
Module
Every cluster is a real package boundary. Membership is determined by the codebase, not by the renderer. When the repository reorganizes, the clusters reorganize with it on the next build.

There is nothing decorative in the scene. Removing a symbol from the codebase removes it from the connectome. Adding one adds it.

§ 03 · Live behavior

The scene reflects operational state in real time

The same connectome you orbit visually carries the live state of the running system. As traffic moves through ARI you see the actual flow of data through the graph: nodes pulse when their function is executing, edges illuminate when their relationship is active, and the topology itself shifts the moment the system shifts.

Failure
A service degrades. The surrounding region dims, the failing node telegraphs upstream, and callers visibly stall. The blast radius is legible at a glance instead of buried in a dashboard.
Scale
Autoscaling fans in additional method instances. The cluster they belong to physically expands in the scene, and the traffic-bearing edges thicken to reflect the new throughput.
Heal
Recovery paths fire, retries succeed, and the region's color phase returns to its resting band. Healing is shown as it happens, not summarized after the fact.
Emergence
When a new pattern stabilizes — a cycle, a feedback loop, a recurring path the architects did not explicitly design — the connectome marks it and keeps marking it for as long as the pattern holds.

The owner of the NFT is not looking at an animation of a system. They are looking at the system.

§ 04 · What the buyer owns

The artifact, the provenance, and the right to run it

The on-chain token records the commit hash, the graph fingerprint, and the canonical render parameters. The off-chain bundle includes the viewer, the graph data, and the audio. The owner can run the scene anywhere, share a link to a hosted instance, or display it through any browser-capable surface.

§ 05 · Why it sits in the BÄRŌ DYNAMICS portfolio

Beneficial intelligence is also legible intelligence

BÄRŌ DYNAMICS builds systems that work outside the demo environment, which means their operators need to see what they own. № 4 is the most extreme version of that principle: an entire intelligent system rendered as something a person can look at, walk around, and tell the truth about.