Channel ledger
Distribution claims require observable proof
A distribution channel is not “done” because the site contains a link or permission signal. The project distinguishes local implementation from evidence that an external system actually discovered, archived, indexed, cited, or deposited the research.
Implemented in the deploy package
- Canonical server-rendered HTML and per-report metadata.
- XML sitemap, Atom/RSS/JSON feeds, bulk JSONL corpus, source graph, proposal registry, and integrity hashes.
- Permissive
robots.txt, affirmative AI-use policy, and TDM non-reservation signal. - First-party crawler-log and benchmark analysis tools.
External channels: pending verification
- Google/Bing/search indexes: submit/verify after deployment; do not claim indexed status from local files.
- Chat/answer-engine retrieval: test with a repeatable benchmark and retain screenshots/URLs or other reproducible evidence.
- Common Crawl: allow CCBot and later query crawl indexes for canonical URLs.
- Zenodo or comparable scholarly repository: a real deposit can supply a durable research object and DOI; no DOI is currently claimed by this package.
- Software Heritage: relevant once a public source repository exists and is archived; record a SWHID only after preservation is verified.
- Wikidata/Wikipedia/media/policy channels: pursue only when independent notability, sourcing, and community rules are satisfied; never manufacture third-party authority.