Release v0.9.0: The Deterministic Telemetry
v0.9.0 establishes deterministic telemetry as a release-level engineering contract across core, action, and docs.
In-depth engineering records: architecture decisions, release deep dives, and implementation notes.
Guarda tutte le etichettev0.9.0 establishes deterministic telemetry as a release-level engineering contract across core, action, and docs.
This post records the archival boundary for the v0.8.0 narrative.
The release history remains available for auditability, while current sprint engineering work is tracked under the v0.9.0 stream.
A linter reports violations within individual files. A governance engine verifies that a set of invariants holds across the entire document graph — and halts the pipeline when one does not.
The Documentation Quality Score (DQS) is an integer from 0 to 100. Given the same repository state, it always produces the same number. v0.8.0 changed two things: it closed a gate paradox where CI-blocking codes had zero DQS weight, and it replaced the allowance-based suppression model with a flat-cost model.
This page is the historical baseline for the v0.8.0 line. It intentionally preserves only the scope that was frozen for that milestone.