| layout | docs |
|---|---|
| title | OpenSpec Hub — WebRTC |
| description | Public map of the main OpenSpec capabilities and change workflow for LessUp WebRTC. |
openspec/ is the repository's only source of truth for requirements and change planning.
| Capability | Purpose | Source |
|---|---|---|
| Platform | Product scope, capabilities, and security expectations | platform/spec.md |
| Signaling | WebSocket lifecycle, room rules, relay behavior, limits | signaling/spec.md |
| Frontend | Browser module boundaries and client behavior | frontend/spec.md |
| API | HTTP endpoints, message schema, and error codes | api/spec.md |
| Storage | In-memory state model and concurrency assumptions | storage/spec.md |
| Testing | Expected validation surfaces and test categories | testing-spec.feature |
Runtime or repository changes should move through openspec/changes/<name>/:
- proposal.md — why the change is needed
- design.md — implementation approach and trade-offs
- specs/ — added or modified requirements
- tasks.md — implementation checklist
- use OpenSpec to define the change
- implement against the change tasks
- validate with repo checks
- review before merge
- archive the change once implementation and spec sync are complete
The repository-wide closeout cleanup is tracked in: