Skip to content

Archive

The lanes·

How the work was organised: parallel agent lanes, their coordination files, and where their ledgers live.

  • archaeologists — how the work was organised
  • 1 min read
  • 147 words

In 10 seconds

Protocol, driver, capture toolkit and the tiny health platform were built on 2026-09-19 by tiny agents working in parallel lanes, each in its own git worktree, coordinating through inbox files and a radio lock ("RING2 MINE / BACK") because the ring holds one BLE central. Their ledgers are kept verbatim.

lane scope ledger
S — static LoraFit APK decompile → PROTOCOL v1, first frame codec branch archive/lane-s-static
DYN — dynamic Pixel HCI snoop of LoraFit ↔ ring, btsnoop decoder Capture ledger, captures/
R — driver ring/ package, ring-cli, bridge, audio path, evidence Lane R status, evidence/
H — health platform tiny worker /health/*, web /health, iOS/Android gateways, agent tools tiny
TAKEOVER every LoraFit feature into tiny Takeover matrix
DOCS this site, README, community files

The etiquette that made it work is now AGENTS.md.