Laboratory › Developers › Use policy

Use policy

Short, because the surface is public and read-only. The constraints that matter are about representation, not access.

You may

• Fetch anything here, from anywhere, without asking or registering.
• Cache, mirror, archive and redistribute these documents, including the portable bundles — they were designed to survive this site.
• Build clients, indexes, readers and analyses on top of them.
• Quote and cite records, under the licences on the licences page.

You may not represent a record as stronger than it is

This is the only substantive restriction, and it is not about copyright:

• Do not present a DEMO_FIXTURE record as a scientific finding. They are marked in every payload.
• Do not present a superseded or withdrawn record as current. Both remain published precisely so the history is honest, and both say what they are.
• Do not present internal reproduction as independent replication.
• Do not present digest verification as scientific verification.
• Do not attach a confidence score, quality rating or ranking to a record and attribute it here. This laboratory publishes no such number and will not.
• Do not drop scope, limitations or falsifiers from a derived summary. A summary may omit detail; it may not change what the record asserts.

Attribution

Cite the version URL, not the current pointer. Every claim version page carries a ready plain and BibTeX citation including the digest, so a later reader can confirm they are looking at what you looked at.

Being a good client

Prefer the changes feed to polling records; fetch the manifest once rather than crawling to detect changes; identify your client in a User-Agent so unusual traffic can be understood rather than blocked. There is no rate limit today — this is a request, not a threat.