E1 — Clip capture: bytes on the ring

[liversedge]

The single largest gap in the product, and the one everything visual sits behind.

Why this clusters

Connecting the ring, configuring the encoder honestly, assembling a clip on trigger and writing the sidecar are one mechanism seen at four depths. Splitting them across epics would let a half-connected ring look finished.

Capability levels

Level	Capability	Release
E1.1	Frames reach the ring	v1
E1.2	A clip you can extract	v1
E1.3	A clip that is self-describing	v1
E1.4	Bitrate hardened	v1

Each level is independently shippable. They are tracked as sub-issues of this one.

Dependencies

A physical device. E-M2 gates E1.4 only — E1.1–E1.3 proceed on a provisional bitrate, and must not harden one.

Requirements covered

REQ-BUF-1, REQ-BUF-3, REQ-CAP-3, REQ-CLIP-1, REQ-ENC-1, REQ-ENC-2, REQ-ENC-3, REQ-FPS-2, REQ-FPS-3, REQ-META-1, REQ-OPT-1..4 (hardware verification), REQ-SHOT-2, REQ-STANDALONE-3

---

_{Scope: delivery-scope.md · Requirements: traceability.md · PRD: capture-companion-requirements.md · Conformance: ppcp-conformance.md}