mirror of https://github.com/zoriya/v10.git synced 2026-08-16 02:45:09 +00:00

Files

T

Christian PillsburyandClaude Opus 4.8 fb4b6b05fb docs(spf): reconcile live-stream-support to the reactor guard

seek-to-live-edge is now a reactor (inactive ↔ live): entry does the one-time
seek, effects runs the window-exit guard (window-update re-fire + a single
`play` listener — `play`, not `playing`, since a slid-past playhead is at an
unseekable position where `playing` never fires). The repositionPolicy seam
was removed once the guard became reload-driven (nothing consumed it); the
live-edge-only use-case defines its own reposition behavior when built.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-25 10:00:22 -07:00

README.md

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

File Naming

Use lowercase with hyphens:

queue-design.md
hook-naming.md
skin-theming.md