Source Basis

The binder is built from public source metadata, official public material where it is available, tooling documentation, and clearly marked synthetic artifacts. Its purpose is to teach inspection and evidentiary boundaries, not to reproduce standards.

Source Ladder

1. Canonical standards metadata establishes names, document numbers, and scope.
2. Official public specifications and standards-owner material support claims at the level their publication permits.
3. Public kernel and tooling documentation supports runnable examples and capture syntax.
4. Vendor notes and public explainers provide teaching cross-checks, not normative authority.
5. Open-source implementations can reveal interoperability assumptions, but do not establish conformance.
6. Synthetic artifacts provide deterministic examples without redistributing captured operational data.

Citation Specificity

Each final-copy page identifies the role of its sources. Document-level metadata does not support section-level claims. A public explainer does not become a standard merely because it is readable. Tool behavior is evidence about that tool, not universal protocol behavior.

Legal Handling

The repository does not include paywalled standards text, unofficial mirrors, proprietary tables, private captures, scraped login-gated material, or cached external documents without explicit redistribution rights. Protocol numbers and titles may be named as bibliographic metadata.

Implementation Impact

Runtime claims require concrete code and tests. Documentation-only pages remain explicitly docs-only or draft. Source notes bound what an example establishes and what remains dependent on a standard, device profile, database, schedule, or capture provenance.