PRD Index
Product Requirements Documents for OceanCanvas. One per customer-facing experience. Derived from OC-02 (Project Concept), anchored to OC_PA (Product Architecture).
What gets a PRD
A PRD is for work where the user-value argument needs to be made — not for every feature, and not for plumbing. Pipeline ingestion, data processing, rendering mechanics, file format schemas: those are RFCs and ADRs anchored to OC-04 (concept) and OC_TA.md (settled contracts).
The bar: if the "Why this is a PRD" sentence in the header is hard to write, the work belongs elsewhere.
Product Architecture
All PRDs anchor to a shared reference document that holds audiences, promises, and principles.
| Doc | Purpose |
|---|---|
| OC_PA.md | Audiences, promises, principles, PRD map. Every PRD links into this. |
PRDs
| PRD | Title | Status | Primary audiences |
|---|---|---|---|
| PRD-001 | Recipe (the authored work) | Draft v0.1 | artist, climate-communicator |
| PRD-002 | Dashboard | Draft v0.1 | scientist-adjacent, curious-person |
| PRD-003 | Recipe Editor | Draft v0.1 | artist |
| PRD-004 | Gallery | Draft v0.2 | curious-person, climate-communicator |
| PRD-005 | Video Editor | Draft v0.3 | climate-communicator, artist |
| PRD-006 | The piece (audio-video as one designed work) | Accepted · May 2026 | artist, climate-communicator, curious-person |
Numbering
Fresh 1–6. PRD-001 through PRD-005 cover the four customer-facing surfaces and the recipe primitive itself. PRD-006 argues for the next iteration of the Video Editor surface — a single authored curve shaping image and sound as one piece. Pipeline, processing, rendering, audio, and overlay mechanics are not PRDs; they live as RFCs and ADRs.
Template
New PRDs: copy PRD_TEMPLATE.md. Read the "Notes on writing PRDs in this format" section at the bottom before starting.