The one MVP scope item with no owner. mvp-online.md §3.3 is titled "(b) — preview, and configuring the device from Studio", and §4a has carried "What does 'config from PPS' actually cover?" as an open question since 25 August without ever becoming an item. Preview is now done (#108); this is the half of §3.3 that never got scoped on either side.
Where it came from
Mark, 25 August 2026: "preview and config in PPS (from preview stream in PPC) and then actual capture and transmission post shot." Preview was promoted to the next tranche on that sentence. The second noun in it was never sized.
⚠ It is not in the MVP's (a)–(d) as agreed, which is why it has drifted: (b) reads "the device captures video, and supports preview and hi-res capture". But §3.3 has always been the place the work is described, and an operator who can see a picture and cannot change anything about it is the obvious next question a demo produces.
The question
What does an operator change from Studio, and what happens on the phone when they do? Candidates, from §4a and from what the code already declares:
|
What it would mean |
What already exists |
| Capture format |
Choose among the declared profiles — 1080p240, 1080p120, 4K60 |
⚠ declare already offers all 40 modes (#102). Nothing lets a host pick one |
| Which lens |
Preview and capture on the ultra-wide instead of the wide |
⛔ Calibration-affecting — that is #115, and it must be answered first |
| Retention |
How much ring, how much pre-roll |
RingBufferRecorder takes it at construction; no wire path |
| ROI / framing |
The crop PinPointStudio's editor already draws |
⚠ They have the editor. Whether the crop is theirs to apply or ours to honour is undecided |
| Arm / disarm |
Already built and already a level |
#26 E3.3 — not this |
Why it needs a decision before an issue
⛔ Every row above is a different protocol answer, and some may need no protocol at all. Format selection is plausibly stream_open naming a different profile — no new message. ROI may be entirely PinPointStudio's, applied to frames they already hold. Retention may be out of scope for v1 altogether.
⚠ And it is cross-repository: mvp-online.md names this as PinPointStudio's to size alongside the viewer, and the viewer half is now delivered. The viewer arriving without this is what makes the question due.
Exit criterion
A named list of what an operator can change from Studio in v1, agreed with PinPointStudio, each row either mapped to an existing PPCP message or explicitly deferred. Then issues, if any are needed.
Where it came from
Mark, 25 August 2026: "preview and config in PPS (from preview stream in PPC) and then actual capture and transmission post shot." Preview was promoted to the next tranche on that sentence. The second noun in it was never sized.
⚠ It is not in the MVP's (a)–(d) as agreed, which is why it has drifted: (b) reads "the device captures video, and supports preview and hi-res capture". But §3.3 has always been the place the work is described, and an operator who can see a picture and cannot change anything about it is the obvious next question a demo produces.
The question
What does an operator change from Studio, and what happens on the phone when they do? Candidates, from §4a and from what the code already declares:
declarealready offers all 40 modes (#102). Nothing lets a host pick oneRingBufferRecordertakes it at construction; no wire pathWhy it needs a decision before an issue
⛔ Every row above is a different protocol answer, and some may need no protocol at all. Format selection is plausibly
stream_opennaming a different profile — no new message. ROI may be entirely PinPointStudio's, applied to frames they already hold. Retention may be out of scope for v1 altogether.⚠ And it is cross-repository:
mvp-online.mdnames this as PinPointStudio's to size alongside the viewer, and the viewer half is now delivered. The viewer arriving without this is what makes the question due.Exit criterion
A named list of what an operator can change from Studio in v1, agreed with PinPointStudio, each row either mapped to an existing PPCP message or explicitly deferred. Then issues, if any are needed.