Technical design documents
Technical design documents explain a proposed subsystem before or during implementation. They may evolve as experiments reveal new constraints.
Documents
| ID | Title | Status |
|---|---|---|
| 0001 | On-demand MP4 packaging core | Accepted; verification pending |
| 0002 | Asset mapper interface | Accepted; implemented |
| 0003 | Production-grade HTTP API | Accepted; implemented |
| 0004 | Broader MP4 input support | Accepted; implemented |
| 0005 | Fragmented MP4 input | Accepted; implemented |
| 0006 | Trick play, subtitles, and adaptive renditions | Draft |
Workflow
- Copy template.md to the next zero-padded number.
- Keep the document in
Draftwhile major questions remain. - Record architectural choices as ADRs and link them from the design.
- Change the status to
Acceptedbefore implementation becomes the reference behavior. - Use
Supersededwhen a replacement design is accepted, and link both documents.