This section contains the stable architecture of VDR-Suite.
Implementation progress belongs in development documents. Long-term decisions belong in ADRs. Planned dependency order belongs in the planning section.
- Target Platform Architecture
- Domain Dependency Map
- Implementation Dependency Map
- Architecture Audit Gap Matrix
The Target Platform Architecture is the canonical diagram set for the contract package accepted through ADR-0049. The dependency maps distinguish domain ownership from runtime implementation order.
A target diagram is not evidence of completed runtime behavior. Use Current Architecture State and Completed Phases for implementation truth.
The Core Platform Model is an earlier conceptual foundation. Where its older future wording differs from the accepted ADR-0038 through ADR-0049 package, the canonical Target Platform Architecture and active ADRs take precedence.
- Metadata Identity Foundation
- Suite Metadata Platform Schema v1
- ADR-0038: Suite Metadata Database and External Provider Strategy
- Recording Metadata Roadmap
The identity foundation defines the Phase 61.1 Suite-owned Entity, Assignment and Target identity boundary. Schema v1 defines the Phase 61.2 entity, target, provider, immutable evidence and assignment persistence contract. Runtime migration, repositories, resolver behavior and artwork storage remain later Phase 61 slices.
- VDR Backends
- VDR Domain Model
- RESTfulAPI Integration
- Suite Bridge Backend Agent Handshake
- Suite Bridge Local SVDRP Transport
- Suite Bridge Read-Only Observation Lifecycle
- Suite Bridge Embedded Agent Runtime
- External Project Analysis
- Recording Actions Architecture
- Recording Action Validation API
- Recording Action Execution API
- Recording Action Safety and Capability Model
- Recording Action Source Constraints
- Recording Action Real Backend Smoke Test Plan
- Recording Action Real HTTP Client Gap
- Snapshot Architecture
- Snapshot Access Architecture
- Partial Snapshot Refresh Architecture
- Snapshot Change Feed Architecture
Historical implementation notes are retained for reference. They do not override later accepted ADRs or the target diagram set.
See:
- stable architecture belongs here;
- target architecture and current implementation state remain explicitly separate;
- implementation progress belongs in development;
- dependency order belongs in planning;
- historical implementation notes remain historical;
- long-term decisions belong in ADRs;
- plugins, Agents, providers and frontends do not bypass the ownership boundaries in the target architecture.