Document metadata
Purpose
This sample shows how a TDS document keeps its purpose and state visible across formats. A file extension describes delivery; the document contract describes responsibility, version, provenance, and the conditions for publication.
Preflight record
- Metadata is present for the standard, version, type, output, project, language, typeface, glyph scope, geometry, and status.
- The output is self-contained and uses no third-party runtime asset.
- The sample remains non-canonical and does not present a checksum as approval.
- Official PDF release checks are not claimed as passed by this HTML sample.
Release boundary
A future official release would carry its reviewed version and reading order, pass the declared geometry and glyph checks, resolve required evidence findings, preserve its public provenance, and state its route and verification note. This sample does none of those things by implication.