3D Vector Clock Ledger — Allen H Builds LLC

James Allen Heifner · Causal Telemetry Engine

Vector Clock Ledger

3D Federated Cluster & Regional Visualizer

How to Read This Simulation:
• Axes ($X, Y, Z$): Map logical clocks for US, EU, and Edge fleets.
• Fossil Records: Dimmed nodes are retained earlier states.
• Action: Hover or tap to inspect supplied vectors and event annotations; clicking or tapping an active node advances its vector once.

✦ MODEL: Clock Knowledge & Explicit Messages [EXPAND]

1. Local clock demonstrations
Existing examples increment local counters and optionally join their clock knowledge. Divergence is not a detected network partition.

2. Explicit message models

New synthetic scenarios use local, send and receive events on three logical processes. Receives merge a sent vector, then increment the receiver. An independent graph check uses process order and matched message edges, never screen position or replay index.

3. Scope of a vector join

Join Clock Knowledge computes componentwise maxima. This is neither a consensus protocol nor an application-payload merge. Displayed demo latency is synthetic. Imported vectors are supplied data; only the explicit message-model format is checked against its causal graph.

Local actions

Divergent

0ms

Synthetic latency

NOMINAL

State Health

Regional Cluster Inspector [Select Node]

Click a 3D node to inspect illustrative regional roles; these are static labels, not running agents.

Cluster Payload Controls

Cluster A:

Cluster B:

Cluster C:

Import Trace File (.JSON / .CSV)

> System Initialized. Regional Clusters Active.

Cluster Logical Clocks:
Cluster A (US)	[0, 0, 0]
Cluster B (EU)	[0, 0, 0]
Cluster C (Edge)	[0, 0, 0]

Enterprise Licensing & Acquisition

Vector Clock Ledger

2. Explicit message models

3. Scope of a vector join