VDR-Suite is a VDR-centred, domain-first platform for modern Web, mobile, desktop and TV clients. VDR remains the native runtime authority; VDR-Suite owns backend scope, policy, orchestration, persistent read models and client-facing contracts.
- Current State — sole repository authority for volatile operational status
- New Chat Handoff — mandatory entry point for a new VDR-Suite chat
- Strict Roadmap — binding forward execution order and phase gates
- Phase Map — compact phase-number map
- Current Project Status — stable narrative context
- Target Platform Architecture
- Architecture Decision Records
- Completed History
- Agent Workflow Rules
The stable platform boundary is:
clients
-> VDR-Suite Control Plane / public Suite contracts
-> Backend Agent
-> explicitly owned local provider
-> VDR native runtime
VDR remains authoritative for native VDR state and execution. VDR-Suite owns durable Suite identity, authorization, policy, orchestration, reconciliation and client-facing semantics. Private provider details such as RESTfulAPI, SVDRP, Streamdev or SuiteBridge do not become public client contracts merely because they are reachable.
The current numbered platform sequence is defined only by the Strict Roadmap. In particular, Phase 65 Streaming follows completion of the reliable Phase-64 Timer orchestration engine; a broad polished Timer UI is separately gated on account/backend access management and is not a prerequisite for Streaming.
Do not copy exact branch heads, active PR numbers or CI checkpoints from this README. Those facts change quickly and belong only in Current State, with live GitHub state re-read before any action.
A chat discussion is not a binding VDR-Suite project decision until the decision is represented in the repository through the appropriate ADR, roadmap, current-state or workflow contract. Repository documents and exact accepted runtime evidence take precedence over conversational memory.