Register
SV
thebigredbutton.org →

Methodology

This page describes how entries enter the register. It is written so the register can be cited. Placeholder wording until the owner voice pass.

1. Selection

An instrument is listed when it creates, proposes, or clarifies a legal obligation related to kill-switch, stop, safe-state, human oversight for interruption, or loss-of-control controls for AI or AI-enabled systems. Advisory material without a legal instrument may be listed as guidance when it is issued by a public authority.

2. Two-source rule

Every production entry cites at least two sources with distinct publishers. The rule is enforced in continuous integration. Placeholder rows are marked and excluded from production checks.

3. Counts

Published: 7. Tracked but not published: 1. Candidates awaiting review (not yet in the collection): 0. Absence is recorded, not hidden.

4. Shared statutory text

Where two instruments share text, the register treats them as one drafting and not as independent corroboration. Cross-links and a byte-identity build check enforce that.

3. Verification cadence

Each production entry carries a lastVerified ISO date. The build fails if any production entry is older than 180 days, and the failure lists those entries.

6. Languages

Interface chrome is available in multiple locales. Instrument text is maintained in English; English is authoritative. Non-English pages may carry machine-translated UI and are not human-reviewed for instrument substance. The JSON export is English-only.

4. Corrections

Send corrections to [email protected]. There is no submissions form in v1.

5. Privacy and indexing

No cookie analytics. If measurement is added later, it will be privacy-preserving and described here. robots.txt allows indexing of all public pages. Machine-readable export: /api/instruments.json.

6. What this is not

This site is a register, not advocacy. Argument and position live at thebigredbutton.org.