307417b392
Phase 0 found that tmux pipe-pane is unreliable across alternate-screen transitions. Before Phase 1 commits to a streaming primitive, a short follow-up spike evaluates tmux control mode (`tmux -CC`) as an alternative to pipe-pane + watchdog. Verdict drives T-1.1 design. |
||
|---|---|---|
| .. | ||
| reference | ||
| PHASE-0-spike-stream.md | ||
| PHASE-0.5-spike-tmux-control-mode.md | ||
| PHASE-1-sidecar.md | ||
| PHASE-2-ios-mvp.md | ||
| PHASE-3-ios-augmentation.md | ||
| README.md | ||
| SYNC.md | ||
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. Done, see reference/PHASE-0-report.md. |
PHASE-0.5-spike-tmux-control-mode.md |
Follow-up spike: tmux control mode (-CC) vs pipe-pane + watchdog. Decides Phase 1 streaming path. ~2h, single agent. |
PHASE-1-sidecar.md |
Sidecar production-ready: all S-features, multi-agent parallel work. Blocked on Phase 0.5. |
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
- Phase 0 first, single agent.
- Phase 1 starts after Phase 0 green-lights; multi-agent parallel.
- Phase 2 starts after Phase 1 is production-ready; multi-agent parallel.
- Phase 3 is continuous after Phase 2 MVP ships.
See SYNC.md for the current state.