jay
/
pi-remote-control
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
pi-remote-control/docs
History
jay 15772558dd docs: claim Phase 0 spike stream task 2026-05-15 03:40:50 +02:00
..
reference docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
PHASE-0-spike-stream.md docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
PHASE-1-sidecar.md docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
PHASE-2-ios-mvp.md docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
PHASE-3-ios-augmentation.md docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
README.md docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
SYNC.md docs: claim Phase 0 spike stream task 2026-05-15 03:40:50 +02:00

README.md

Implementation Docs

This folder drives the implementation work for the pi-remote iOS app and its sidecar. Background / spec / audit material lives in reference/.

File Purpose
PHASE-0-spike-stream.md Stream PoC — verify tmux + pipe-pane + WebSocket. ~1 day, single agent.
PHASE-1-sidecar.md Sidecar production-ready: all S-features, multi-agent parallel work.
PHASE-2-ios-mvp.md iOS app MVP — Groups A, B, C-01/02, D, E, F. Multi-agent parallel.
PHASE-3-ios-augmentation.md iOS feature polish — slash palette, voice, thumbnails, search, etc.
SYNC.md Live multi-agent coordination — claims, file ownership, contract changes.

Order of work

  1. Phase 0 first, single agent.
  2. Phase 1 starts after Phase 0 green-lights; multi-agent parallel.
  3. Phase 2 starts after Phase 1 is production-ready; multi-agent parallel.
  4. Phase 3 is continuous after Phase 2 MVP ships.

See SYNC.md for the current state.