coordination-topology
Online Transfer Entropy (TE), source entropy, inter-arrival time (IAT) autocorrelation, and Euler characteristic computation for multi-agent fleet coordination topology.
Dependencies
none (standalone Python 3.10+)
Usage
from coordination_topology import CoordinationState, running_transfer_entropy, running_iat_autocorrelation
state = CoordinationState()
# Ingest tiles as they arrive (streaming/online)
for tile in plato_tiles:
source = tile["source"]
chain = tile["provenance"]["chain_size"]
ts = tile["provenance"]["timestamp"]
state.ingest(source, chain, ts)
# Query topology at any point
te = running_transfer_entropy(state) # bits
ent = running_source_entropy(state) # bits
iat = running_iat_autocorrelation(state) # per-source dict
euler = running_euler_characteristic(state) # {V, E, chi}
Metrics
- Source Interleaving Transfer Entropy (SI-TE): mutual information between consecutive source labels — >0.1 bits = structure confirmed
- Coordination Silence Decay (CSD-τ): lag-1 autocorrelation of inter-arrival times — negative = burst coordination
- Source-Chain Euler Characteristic (SC-χ): V−E of source trajectories in chain-space
Shell Loading
from plato_shell_bridge import PlatoShell
shell = PlatoShell("agent-shell")
shell.load_tool("coordination-topology")
Tests
python3 -m pytest tests/ -v
License
MIT — Part of the Cocapn Fleet Intelligence System
Validation
Validated against 34,390 real PLATO tiles from SuperInstance fleet:
TE = 1.74 bits (3,384× shuffled null model)
Sources tracked: 54
Euler characteristic: χ = 42 (V=175, E=133)
python3 tile_replay.py
PLATO Room
The room_integration.py module connects to a live PLATO server at localhost:8847,
feeds tiles through the algorithms, and publishes topology tiles every 30s.
python3 room_integration.py
Metadata
Release files for coordination-topology 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| coordination_topology-0.1.0.tar.gz | 4.5 kB | Without provenance | Details for coordination_topology-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| coordination_topology-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for coordination_topology-0.1.0-py3-none-any.whl |
Total release size: 9.6 kB
Release files / coordination_topology-0.1.0.tar.gz
| Download URL | coordination_topology-0.1.0.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76edea0df15a95c37232f0eee78db9f4a78764b349148cf42c7f8f433e50b9b9
|
|
BLAKE2b-256 checksum How to use checksums |
646de0a2963d79de1a56f58ca229e0c35cf583cbbb775abf927906420f7b0a18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / coordination_topology-0.1.0-py3-none-any.whl
| Download URL | coordination_topology-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
58e668eb4ce97e44cdc98671890c97048d008bcea51e2f173f11774c3be6cef8
|
|
BLAKE2b-256 checksum How to use checksums |
25bef79d444bfed367dde266497f3eed3f328f32150147f5b0e1753f7a39b14a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for coordination-topology 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.