Documentation and historical records
Current references
Use these documents for the 0.20.0 release:
| Topic | Reference |
|---|---|
| First build and application use | README, Building |
| Supported platform, inputs, and resource limits | Release scope |
| Public API and aliasing | Semantic contract, aliasing contract |
| Allocation and lifecycle classifications | Allocation evidence |
| PPFIF import limits | PPFIF resource contract |
| Mathematical source review | Branch review |
| Binary compatibility | ABI policy, 0.20 compatibility record |
| Executable validation procedure | Testing, Qualification |
| Release status and future work | Status, Roadmap |
| Interpretation of evidence | Claims and evidence |
Release notes record changes between versions.
PRODUCTION_CHANGESET_0.20.0.json records the production-source comparison
used for this release's audit.
Retained development evidence
Earlier reports preserve experiments, rejected approaches, validation snapshots, and measurements. Their version numbers identify the source they reviewed. They may contain superseded completion counts or future-work language; check the current references above before applying a claim to 0.20.0.
| Historical stage | Entry point |
|---|---|
| Deep numerical, lifecycle, and packaging audit | 0.19 deep audit |
| Arithmetic, fused-operation, and root allocation contracts | 0.18 contract |
| Transcendental and special-function allocation contracts | 0.17 contract |
| Certified-constant allocation and cache contracts | 0.16 contract |
| Text and interchange allocation contracts | 0.15 contract |
| Systematic aliasing validation | 0.14 validation |
| ABI epoch 1 establishment | 0.12 ABI validation |
| POSIX-thread ownership and cleanup | 0.11 validation |
| Earlier allocation and fuzz validation | 0.10.9 validation |
The corresponding versioned validation reports and production-change manifests remain beside these documents. This preserves traceability without making a historical report the current user entry point.
The history/ directory holds earlier entry points and reports, including
README_0.10.0_runtime_complete.md, RELEASE_NOTES_legacy_0.10.0.md,
REPOSITORY_BUILD_STATUS_0.18.md, and the earlier hardening report.
history/SHA256SUMS_0.10.0_runtime_complete.txt is a checksum manifest for its
original handoff; it is not expected to validate the current source tree.
The full source archive also retains development launchers, benchmark data,
root-level validation reports, and the historical PPFIF patch under
evidence/history/. These source-archive records are not all installed with
the library. The PPFIF repair is already integrated into the current source;
the retained patch is provenance, not an additional installation step.