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>
Decisions
ADR-style records of single tactical decisions.
What Belongs Here
A decision doc captures one specific choice: what was decided, why, and what was ruled out. Keep them short and focused — usually one page.
Write one when:
- You picked one approach over another and want the reasoning on record.
- A decision depends on or supersedes an earlier one (link across docs).
- You want future contributors to understand why the code is the way it is.
Decisions vs Design Docs
Use a design doc (internal/design/) when you're specifying architecture, a feature, or a subsystem — forward-looking, often longer, status ranges from draft → decided → implemented → superseded.
Use a decision doc here when you're recording a single trade-off within that work — short, always status: decided.
A design doc often spawns several decision docs as implementation choices get made.
Format
---
status: decided
date: 2026-01-27
---
# Title
## Decision
What you decided. Be direct.
## Context
Why this came up. What problem triggered the decision. Link related decisions.
## Alternatives Considered
- **Option A** — Why not chosen
- **Option B** — Why not chosen
## Rationale
Why this choice wins. Keep concise.
File Naming
Lowercase with hyphens, name after the subject of the decision:
captions.md
gestures-as-components.md
provider-attach.md
See Also
- Design Docs — Architecture specs and feature designs
- RFCs — Proposals needing buy-in
- Plans — Implementation notes
- CLAUDE.md — How these relate