xdv-draft

Non-Normative Archive (Historical Drafts)

Status: Archived / Non-Normative
Canonical specification source: ../xdv-spec
Scope: historical draft material retained for traceability only.

Archive Policy

1. xdv-draft is not authoritative for XDV requirements.
2. Normative requirements, status tags, and pass/fail criteria are defined in xdv-spec only.
3. New technical work, requirement edits, and architecture changes must be authored in xdv-spec.
4. Changes in xdv-draft are limited to archival metadata, cross-links, and historical notes.

Canonical Sources

• ../xdv-spec/README.md
• ../xdv-spec/Corpus.md
• ../xdv-spec/NORMATIVE_FREEZE.md
• ../xdv-spec/requirements/xdv_requirement_index.csv
• ../xdv-spec/requirements/xdv_requirement_pass_fail.md

Section Cross-Linking to Canonical IDs

The full crosswalk is in SECTION_CROSSWALK.md.

Summary map:

• Domain model and doctrine: XDV-001..005
• Kernel architecture and core subsystems: XDV-010..015
• Hybrid execution semantics: XDV-020..024
• Security/integrity controls: XDV-030..034
• Networking/distributed/cloud: XDV-040..043
• DPL integration and verification: XDV-050..053
• Hardware provider interfaces and boot architecture: XDV-060..062
• Telemetry/replay/diagnostics: XDV-070..072
• Reference implementation and conformance: XDV-080..084

Drift Control

To prevent drift between draft text and normative spec:

• Do not add or modify requirement semantics in this directory.
• Treat every technical statement here as historical context only.
• If a mismatch is found, xdv-spec is the source of truth.
• Open/update items in xdv-spec first; optionally add a historical note here after the canonical update.

Legacy Documents in this Archive

• xdv-white_paper.md
• xdvfs-White-Paper.md
• DESIGN_PRINCIPLES.md
• XDV-OS-Implementation-Plan.md
• XDV-OS-Implementation-Plan-DPL.md
• XDV-OS-Implementation-Plan-v3.md
• XDV-OS-Implementation-Plan-v4.md

Each legacy file contains an archive redirect banner to xdv-spec.