VDR-Suite

Project Overview

• German: Projektübersicht
• English: Project Overview

Quick Links

• Project Status Dashboard
• Current Project Status
• Developer Documentation
• Developer Onboarding
• Architecture Map
• Roadmap
• Architecture
• ADR

---

Current Release State

Backend Foundation        ████████████ 100%
Snapshot Runtime          ████████████ 100%
Read API                  ████████████ 100%
Change Feed               ████████████ 100%
Backend Registry          ████████████ 100%
Backend-Aware Snapshots   ████████████ 100%
Multi-Backend Routing     ████████████ 100%
Multi-Backend Polling     ████████████ 100%
Multi-Backend Read API    ████████████ 100%
CI Foundation             ████████████ 100%
Live Transport            ████████████ 100%
Selective Event Queries   ████████████ 100%
Heavy Domain Policy       ████████████ 100%

Latest Completed Implementation Phase: Phase 24.5 - Live RESTfulAPI EPG Verification

Current Implementation Focus: Phase 25.0 - EPG REST API Boundary

Roadmap Progress: see Roadmap

---

VDR-Suite modernizes the Video Disk Recorder ecosystem with a backend service layer, daemon-owned state, snapshot architecture, REST APIs, backend registry foundations and future frontend integrations.

VDR remains the primary backend domain and source of truth.

VDR-Suite complements VDR. It does not replace it.

---

Architecture Highlight

ADR-0021 defines a core runtime rule:

Prefer selective backend queries
before full-domain transfers.

The performance target is backend workload comparable to established VDR frontends such as live when equivalent user-visible information is requested.

---

Start Here

New to VDR-Suite?

Read these documents first:

1. Project Status Dashboard
2. Project Overview
3. Documentation Index
4. Developer Documentation
5. Developer Onboarding
6. Architecture Map
7. VDR-Suite Vision
8. Current Project Status
9. Roadmap
10. Architecture Index
11. ADR Index
12. ADR-0021 Selective Backend Query Strategy

---

Documentation Navigation Rule

The README is the repository entry point.

Every documentation page should provide navigation back to:

• README
• Documentation Index
• Project Overview
• the local section index when applicable

This prevents documentation dead ends and keeps the documentation usable from GitHub, editors and local checkouts.

---

Current Architecture State

✓ Snapshot Architecture
✓ Snapshot Cache
✓ Snapshot Access Layer
✓ Snapshot Read APIs
✓ Snapshot Change Feed
✓ Runtime Diagnostics
✓ VDR Health API
✓ VDR Snapshot Summary API
✓ VDR Capability API
✓ Capability Resolver Foundation
✓ Backend Registry Foundation
✓ Backend Registry API
✓ Backend-Aware Snapshot Access
✓ Backend-Aware VDR Controller Methods
✓ Multi-Snapshot Cache Foundation
✓ Backend-Aware Snapshot Builder
✓ Backend-Aware Polling Service
✓ Backend Polling Coordinator
✓ Backend Runtime Context
✓ Daemon Runtime Context Collection
✓ Registry-driven Backend Runtime Context Creation
✓ Backend-aware Snapshot Change Feed
✓ Multi-Backend Snapshot Read Foundation
✓ Multi-Backend Snapshot Summary Serialization
✓ Multi-Backend Snapshots REST Endpoint
✓ Multi-Backend Snapshots REST Route Test
✓ GitHub Actions CI
✓ Selective Event Query Contract
✓ Heavy Domain Refresh Policy

Current architecture focus:

Phase 25.0 - EPG REST API Boundary
Use heavy-domain policy for refresh decisions
Keep Events / EPG out of automatic full refresh paths
Preserve backend-neutral adapter boundaries