# DOT releases

Public release notes use `docs/releases/<version>.md` and are also used as the
reviewed GitHub release body.

- `0.0.1.md` — published immutable baseline: initial DOT source,
  documentation, publication, and release contract.
- `0.0.2.md` — two-lane Agent and four-stage Research consolidation,
  tagged-archive ingestion, structured release lifecycle, migration audit, and
  compatibility routes.
- `0.0.3.md` — on-demand Summary contract, executive-brief request
  and completion records, PDF quality controls, and publication routes.
- `0.0.4.md` — repository-wide Release contract, adaptive release notes,
  sequential publication safeguards, and immutable manual-test handoff.
- `0.0.5.md` — evidence-completing Summary behavior, required Fact matrix,
  bounded official-source gap filling, and versioned completion controls.
- `0.0.6.md` — configured shared browser tabs, worker ownership, resumable
  queues, blocker monitoring, and recovery controls.
- `0.0.7.md` — continuous project progress, evidence-based `#LAZY` recovery,
  verified persistent files, purpose-based Agent storage, Research archives,
  and three-format dataset views.

Tags use bare semantic versions. Published tags are immutable; corrections use
a later version. Compatible corrections and clarifications accumulate in the
current patch series; the next minor series is reserved for a separately
approved contract-maturity milestone. Editorial-only changes are batched
rather than released alone.