The documentation is organized by audience:
| Document | Audience and authority |
|---|---|
| README | Users choosing and integrating an API |
| Package documentation | Exact exported behavior and lifetime contracts |
| Architecture | Maintainers reviewing package boundaries and execution design |
| Benchmarking | Contributors running coverage suites or regression gates |
| Benchmark snapshot | Users reviewing absolute comparison results and their fairness contract |
| Contributing | Required development and review workflow |
| Migration | Users moving from the former module or database layout |
| Security | Supported revisions, private reporting, and deployment controls |
| Provenance | External source, algorithm, corpus, and license ledger |
| Unsafe inventory | Generated unsafe scopes, invariants, tests, and benchmarks |
maintenance-baseline.json is an intentionally immutable historical
measurement captured at the commit recorded inside the file. It is not a
description of the current tree. Current source counts, API shape, fuzz targets,
and benchmark results must be measured from the checked-out revision.