fleet-topology 0.1.0

Fleet network topology with constraint-aware routing and holonomy verification
Documentation
  • Coverage
  • 25.45%
    14 out of 55 items documented0 out of 25 items with examples
  • Size
  • Source code size: 30.23 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 817.22 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 21s Average build duration of successful builds.
  • all releases: 21s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • SuperInstance/fleet-topology-rs
    1 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • SuperInstance

fleet-topology — Fleet Network Topology with Constraint-Aware Routing

Which devices know which. How constraints propagate. Where cycles need holonomy checks.

What It Does

  • Fleet graph: nodes (devices) + edges (communication links)
  • Betti number β₁: counts independent cycles (holonomy checks needed)
  • Cycle detection: find all cycles for Kawasaki condition verification
  • Constraint routing: messages follow constraint-capable edges only
  • Holonomy verification: cycle product must be identity

The Math

  • β₁ = |E| - |V| + c (Euler characteristic)
  • Tree topology: β₁ = 0, no cycles, trivially consistent
  • Ring topology: β₁ = 1, one Kawasaki condition
  • Complete graph: β₁ = N(N-1)/2 - N + 1, many conditions, high redundancy

Use Cases

  • Fleet device discovery and topology mapping
  • Constraint propagation planning
  • Holonomy verification scheduling
  • Fault-tolerant routing (avoid broken links)

Composable With

  • fleet-proto-rs: device and constraint types
  • fleet-raid5: security audit uses topology for spatial parity
  • fold-compression: fold groups operate on topology edges
  • physics-clock: temporal inference uses edge latency

Install

[dependencies]
fleet-topology = "0.1"

License

Apache 2.0