How the record works

This site and the repository it is built from are a running document with a permanent DOI. It is revised as the field develops, discussed in regular meetings, and versioned for citation. The live site always shows the current state; dated snapshots are available under Releases.

The practices run from the most general (decisions that hold across resources and institutions) to the most specific (per-use-case mechanics).

How practices are recorded

Each practice has a page with the same structure: the statement, what it means for each audience, why it matters, what it looks like in practice, and its sources. Practices link back to library entries, which quote the source passages.

How practices are gated

The record keeps a small number of high-impact practices. A new one gets its own page only if it passes all of these:

1. Scope. It changes how science is planned, performed, evaluated, communicated, or governed (the mission test).
2. Generality. It applies across audiences or many resources, not to a single service.
3. Not a sub-case. If it is a narrower version of an existing practice, it becomes a supporting note on that page.
4. Backed. It is supported by a published document or observation.
5. Distinct action. A reader could do something differently because of it.

Status legend

Status	Meaning
draft	Proposed, under discussion.
reviewed	Accepted by the editor group.
endorsed	Formally backed by at least one named organisation or task force.

Review date

Each practice page shows a "Last reviewed" date. It is the date an editor last went through the whole page and confirmed it stands, not the date of the last edit. Editors set it when a challenge or a review of that page is resolved, or after a deliberate re-read. Adding a source or an example does not move it. The full edit history is in the repository.