mirror of
https://github.com/zoriya/v10.git
synced 2026-08-16 02:45:09 +00:00
Christian PillsburyandClaude Opus 4.8
7cde2ea28d
Convert anchor-live-tracks from N per-track buffer pins to a single shared (media-time <-> PDT) anchor applied to every selected track — video, audio, and now text. A two-state reactor (unanchored -> anchored) positions from the manifest estimate until a selected A/V track has SourceBuffer ground truth, then establishes the shared anchor once (first track to buffer wins) and positions each track onto it by PDT, leaving it to the parser's carry-forward thereafter. The resolveBufferedAnchor seam now takes the standard (track, deps) setup arguments instead of closing over engine scope; the HLS engine's implementation lives in its own generic module (resolve-buffered-anchor) so a future audio-only-live engine can reuse it. anchorLiveTracks is now a makeAnchorLiveTracks<Context>() factory mirroring makeShareSignals. Realizes internal/decisions/live-presentation-anchor.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Design Docs
Decisions you own — documented for posterity.
What Belongs Here
Design Docs are decisions you own. Write one when:
- Making architectural decisions in your area
- Choosing between implementation approaches
- Introducing design patterns others will follow
- Documenting internal APIs or component specs
When to Use RFC Instead
Use an RFC (rfc/) when:
- Changes public API surface
- Affects product direction
- Affects user-facing developer experience
- Significant changes to core architecture
- Hard to reverse once shipped
Rule of thumb: If you need someone else's approval, it's an RFC. If you're documenting your own decision, it's a Design Doc.
Format
---
status: decided
date: 2025-01-27
---
# Title
## Decision
What you decided. Be direct.
## Context
Why this came up. What problem triggered the decision.
## Alternatives Considered
- **Option A** — Why not chosen
- **Option B** — Why not chosen
## Rationale
Why this choice wins. Keep concise.
Status Values
| Status | Meaning |
|---|---|
draft |
Thinking through it, not final |
decided |
Decision made, documented |
implemented |
Built and shipped — kept for rationale |
superseded |
Replaced by another design doc |
Archive
archive/ contains design docs for fully implemented features where the "what" is now captured by the code itself. These docs are preserved for reference but are no longer actively maintained. Docs with high "why" value (decisions, rationale, alternatives) stay in the main directory with status: implemented.
File Naming
Use lowercase with hyphens:
queue-design.md
hook-naming.md
skin-theming.md