jay
/
pi-remote-control
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: mark Phase 0 complete in SYNC.md 

- Phase 0 status: done (GREEN LIGHT)
- Phase 1 status: ready to start
- Remove active claim for T-0.*
- Add history entry
- Full report available in feat/spike-stream branch
This commit is contained in:
jay 2026-05-15 03:51:14 +02:00
parent 15772558dd
commit d97bd4aeef
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/SYNC.md
View File

@ -36,8 +36,8 @@ The point: no central scheduler is required. A short structured edit on
| Phase | Status | Notes |
|---|---|---|
| Phase 0 — Spike Stream | not started | First task. See `PHASE-0-spike-stream.md`. |
| Phase 1 — Sidecar | blocked on Phase 0 | Can begin only after Phase 0 verdict is green. |
| Phase 0 — Spike Stream | done | ✅ GREEN LIGHT. See `reference/PHASE-0-report.md`. pipe-pane reliability issue noted. |
| Phase 1 — Sidecar | ready to start | Recommend node-pty over pipe-pane based on Phase 0 findings. |
| Phase 2 — iOS MVP | blocked on Phase 1 | Sidecar must be reachable and stable. |
| Phase 3 — iOS Augmentation | blocked on Phase 2 | Continuous after MVP ships. |
@ -50,7 +50,7 @@ Update the **Status** column when a phase transitions. Allowed states:
| Task | Branch | Owner | Claimed at | ETA | Notes |
|---|---|---|---|---|---|
| T-0.* | feat/spike-stream | @worker-phase0 | 2026-05-15 | +1d | Phase 0 Spike Stream PoC |
| _(none)_ | | | | | |
Example of a filled row:
```
@ -150,9 +150,6 @@ Append-only log of completed work and notable events. One line each.
yyyy-mm-dd @handle T-x.y what was done
```
Example:
```
2026-05-15 @jay init docs reorganised; phase plans + SYNC created
2026-05-15 @worker-phase0 T-0.* Phase 0 spike complete. tmux+pipe-pane PoC validated. GREEN LIGHT for Phase 1. Report: reference/PHASE-0-report.md. Branch: feat/spike-stream (kept for reference, not merged).
```
(populated as work happens)