tv-anarchy/fleet
Natalie a86e68c525 feat(apps): add fleet engine mesh core integration
Co-Authored-By: Lilith Autocommit <noreply@atlilith.com>
2026-06-09 21:23:36 -07:00
..
README.md feat(apps): add fleet engine mesh core integration 2026-06-09 21:23:36 -07:00

fleet/ — fleet manager + self-healing torrent mesh

Design spec: ../.project/history/20260608_fleet-manager-mesh-design.md

Status: the single-fleet core (stage 1 + stage 3) is implemented in the governor../governor/src/fleet/ — not here:

  • registry ingest (~/.config/tv-anarchy/fleet.json array form authoritative, devices.json fallback)
  • deterministic duty assignment (broadcast / f2f_relay / public_swarm_face) with the spec invariants
  • custody floor-check (custodians_of, rolling baton, re-pin planning)
  • zombie reaper (healthy | stalled | dead; mesh-first recovery planning)
  • peer-source model with both private-tracker policy gates + peers_for

CLI: portable-net-tv fleet status|duties|custody|reaper [--apply]|peers <q> (see ../docs/operations.md). Tests: bun test in ../governor.

This directory remains the placeholder for the parts that are still design-only and/or blocked on infrastructure outside this repo:

  • re-pin actuation (cross-host torrent copies) and automated re-search
  • the fleet WireGuard fabric (plane 1 — blocked on the 10.9.0.4 question)
  • a broadcast host serving peers_for to other devices
  • friend-mesh / F2F relay (stage 4), private-tracker sources (stage 5), Discord planes, multi-identity

Build order and the up-to-date status table live in ../docs/roadmap.md.