Findings

Counts, medians, durations and gaps computed from the observation series. Every finding states its method inline, so it can be redone against the same public data.

Each finding below reads in one order: Question, Result, Method, Population, Limitations, Reproduce. The computation metadata (every figure by its key, the day it was computed, the data window and the count of instrument ids attached) sits behind one expander on each finding.

No finding computes a score, index, ranking or weighting. Weighting two measures against each other declares how the two should be ranked, which is a methodology rather than arithmetic. An unweighted count survives disagreement about which measure to prefer.

Limitations are written by the computation that produced the figure, at the time it ran — the population a filter dropped, a probe that was withheld, a list a cap truncated. A limitation is not reconstructed afterwards from the published number: a bound written later by a reader of the output would be this site authoring a claim about its own arithmetic. Where a computation stated none, the field renders — rather than a sentence composed to fill it. 15 of 29 findings below carry one.

committee

Question. How many recorded committees carry a scope quoted from their charter?

Result. 3 of 6 recorded committees have a scope quoted from their charter

Method. Count of body records carrying a non-empty scope. Scope must be the charter's own words; a charter that cannot be retrieved yields no scope rather than a paraphrase.

Population. The 6 body records in this record.

Limitations. —

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id committee-scope-quoted, with the data window and the ids of the instruments attached; this finding names no figure by key.

Computation metadata

Named figures: —

Computed 2026-11-02
Data window 2026-11-02 → 2026-11-02
Instrument ids attached: —

Question. How many tracked instruments name a producing committee?

Result. 13 of 132 tracked instruments name a producing committee

Method. Count of distinct instrument ids appearing in the produces list of any body record, intersected with the tracked corpus. Counting only: a committee producing more tracked instruments is the count says how many instruments a committee produced and nothing further about the committee.

Population. The 132 tracked instruments, read against the 6 recorded body records.

Limitations. Derived from 6 recorded body records. instruments_involved lists 12 of the 13 counted.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id instruments-per-committee, with the data window and the ids of the instruments attached; this finding names no figure by key.

Computation metadata

Named figures: —

Computed 2026-11-02
Data window 2026-11-02 → 2026-11-02
Instrument ids attached: 12

Question. How many tracked instruments name no producing committee?

Result. 119 tracked instruments name no producing committee

Method. Count of tracked instruments not appearing in any body produces list. States a gap in this archive's committee coverage; it is not evidence that no committee produced the document.

Population. The 132 tracked instruments, read against the 6 recorded body records.

Limitations. Derived from 6 recorded body records. instruments_involved lists 12 of the 119 counted.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id instruments-without-committee, with the data window and the ids of the instruments attached; this finding names no figure by key.

Computation metadata

Named figures: —

Computed 2026-11-02
Data window 2026-11-02 → 2026-11-02
Instrument ids attached: 12

corpus

Question. Which instrument's recorded status date lies furthest from the day this was computed, and by how many days?

Result. Longest interval between a recorded status date and today: us-21-cfr-part-11, 10,666 days

Method. For each verified instrument, the number of days from the date the SOURCE states for its status to today. This measures the age of the regulatory fact, NOT how long this archive has observed it — the observation series is far younger and its length is reported separately. No weighting is applied.

Population. The 11 instruments carrying both a verified status and a recorded status date, of 132 tracked.

Limitations. Computed over the 11 instruments carrying both a verified status and a recorded status date, of 132 tracked. An instrument without one is outside this population, not a zero within it.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id days-in-status, with the data window and the ids of the instruments attached; this finding names no figure by key.

Computation metadata

Named figures: —

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: 11

Question. What is the median number of days between a recorded status date and the day this was computed?

Result. Median days in current status: 1099

Method. Median of (today − status_as_of) in days, over instruments with a verified status and a recorded status date.

Population. The 11 instruments carrying both a verified status and a recorded status date, of 132 tracked.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id median-days-in-status, with the data window and the ids of the instruments attached; this finding names no figure by key.

Computation metadata

Named figures: —

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: 11

Question. How many provisions are tracked at article or section level, and how many carry an applicability date still in the future?

Result. 26 provision(s) tracked at article or section level; 0 with an applicability date still in the future

Method. Count of records in the provisions collection, and of those whose recorded applicability_date is later than today. Applicability is recorded per provision because instruments phase in across years and a single instrument-level date would be wrong for most of their articles.

Population. The 26 records in the provisions collection.

Limitations. —

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id provisions-tracked, with the data window and the ids of the instruments attached; this finding names no figure by key.

Computation metadata

Named figures: —

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: —

Question. How many tracked instruments carry each recorded status?

Result. Status across the tracked corpus: 74 unknown, 39 final, 13 in-force, 3 draft, 2 withdrawn, 1 superseded

Method. Count of instruments by the `status` field, as recorded after human verification against the primary source. Instruments never verified are counted as `unknown`.

Population. The 132 tracked instruments, each counted once by its `status` field.

Limitations. —

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id status-distribution, with every figure by its key, the data window and the ids of the instruments attached.

Computation metadata

status_draft: 3
status_final: 39
status_in-force: 13
status_superseded: 1
status_unknown: 74
status_withdrawn: 2

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: —

Question. How many recorded tier-1 members carry the tier-1 assignment, and how many carry a verified status?

Result. 55 of 57 recorded tier-1 member(s) carry the assignment; 37 carry a verified status

Method. THE POPULATION IS THE RATIFIED RULE, NOT THE DECLARED LIST ALONE. Tier 1 = the declared list in sources/tier1-declared.yaml, union the approved canon in state/canon-candidates.json, union a documented exception in docs/referents/declarations.json. Derived through scripts/tier_identity.py: 37 declared, 40 in the approved canon, 2 documented exception(s); the three overlap, so the union is smaller…

Population. The 57 rows the ratified rule admits as tier-1 members: the declared list, the approved canon and the documented exceptions, which overlap.

Limitations. A figure measured against the declared list alone gives a different denominator and a different residue, and this page published those until the correction dated on /corrections. They were not wrong about their own population; they did not name it.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id tier1-coverage, with every figure by its key, the data window and the ids of the instruments attached.

Computation metadata

admitted: 57
admitted_not_assigned: 2
assigned: 55
canon: 40
declared: 37
exceptions: 2
verified: 37

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: 2

Question. Which rows named in the declared tier-1 list carry no tier-1 assignment, and for what recorded reason?

Result. 2 documented exception(s) to the tier-1 rule

Method. A row named in the declared tier-1 list that carries no `tier: 1` because it is not a document. Each is recorded in docs/referents/declarations.json with its reason rather than special-cased in code: a name special-cased in code is a name satisfying a condition it does not meet. The reasons, verbatim: ema-qig: declared tier 1 and carries no `tier: 1` row because it is a BODY…

Population. The 37 rows of the declared tier-1 list.

Limitations. —

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id tier1-exceptions, with every figure by its key, the data window and the ids of the instruments attached.

Computation metadata

exceptions: 2

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: 2

Question. How many rows carrying a tier-1 assignment are admitted by no recorded tier-1 membership?

Result. every instrument assigned tier 1 is admitted by the ratified rule

Method. THE POPULATION IS THE RATIFIED RULE. Count of rows literally carrying `tier: 1` whose id is in neither the declared list, nor the approved canon, nor the documented exceptions. A non-zero here means the tier assignment and the rule disagree, and it is reported rather than reconciled silently. A zero means they agree — a measured zero, derived through scripts/tier_identity.py, which is the same…

Population. The 55 rows carrying a tier-1 assignment in their own frontmatter.

Limitations. Measured against the rule, not against the declared list alone. Until the correction dated on /corrections this figure was measured against the list and was not zero; every row it named is admitted by the approved canon, and the figure did not say which population it had used.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id tier1-undeclared, with every figure by its key, the data window and the ids of the instruments attached.

Computation metadata

admitted: 57
assigned: 55
unadmitted: 0

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: —

coverage

Question. How many recorded revision candidates are offered as a change, and where do the rest stand?

Result. 8 of 110 recorded candidate(s) are offered as a change

Method. Counted from state/triple-projection.json, which derives the three limbs for every file in state/revision-staging/. `offered` is every derivation agreeing; `waiting` is a limb that has not been measured yet; `withheld` is the remainder, each carrying its own reason.

Population. The 110 recorded candidates in state/revision-staging/, each counted in one of offered, offered_witness, waiting and withheld. `confirmed` counts person confirmations not withdrawn; `withheld_by_terms` counts the day's observations withheld under a terms filing.

Limitations. These count CANDIDATES, not changes. A candidate is a digest that moved; whether a document changed is what the three derivations decide, and for most of these they decide it did not.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id front-line, with every figure by its key, the data window and the ids of the instruments attached.

Computation metadata

confirmed: 0
offered: 8
offered_witness: 1
staged: 110
waiting: 11
withheld: 90
withheld_by_terms: 28

Computed 2026-11-02
Data window 2026-11-02 → 2026-11-02
Instrument ids attached: —

Question. How many status packs wait in the confirm queue, and how many can be pressed?

Result. 19 status pack(s) wait and 0 can be pressed

Method. Counted from state/packs/_index.json: the queued and withheld entries the confirm queue reads. `keypress` counts those its accept gate would admit; `blocked_on_collector` counts those whose pack states no corroborating passage or no capture, which a keystroke cannot supply.

Population. The 19 queued and withheld entries in the pack index the confirm queue reads.

Limitations. Depth is what is waiting, not what is wrong. A pack blocked on a collector is not an item a person has declined to read; it is an item no person can act on, and the two are different facts wearing the same place in a queue.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id queue-status-packs, with every figure by its key, the data window and the ids of the instruments attached.

Computation metadata

blocked_on_collector: 16
depth: 19
keypress: 0

Computed 2026-11-02
Data window 2026-11-02 → 2026-11-02
Instrument ids attached: —

crawlability

Question. How many sources answer a browser with HTTP 200 and an AI-agent user-agent with another status?

Result. Sources that return HTTP 200 to a browser and a non-200 to an AI-agent user-agent: not measured

Method. Count of sources where the browser user-agent received HTTP 200 and the AI-agent user-agent did not, on the same URL, seconds apart. This archive sent an agent request to 0 of 132 probed sources: it no longer requests a host as an agent that host's robots.txt refuses, so an observed refusal can only come from a host that permits the agent and then declines it.

Population. The probed sources an agent request was sent to: none of the 132 probed.

Limitations. Declared exclusions are counted separately and are not included here. An agent request was sent to 0 of 132 probed sources.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id ai-agent-blocks, with every figure by its key, the data window and the ids of the instruments attached. Each figure this finding states as not measured is served there as null; its headline and value are served as the finding records them.

Computation metadata

agent_requests_sent: 0
probed_sources: 132

observed_refusals: not measured — counted over agent_requests_sent, which this finding records as a measured zero.

Computed 2026-11-02
Data window 2026-11-02 → 2026-11-02
Instrument ids attached: —

Question. How many sources name an AI agent in robots.txt and disallow it from the whole site?

Result. 8 source(s) name an AI agent in robots.txt and disallow it from the whole site

Method. Count of sources whose robots.txt carries a group naming an AI agent with `Disallow: /`. Read from the publisher's own file, identifying as this archive. No request is sent to a host that refuses the agent by name.

Population. The 132 sources probed for crawlability, read through each robots.txt this record could retrieve.

Limitations. Read only from a robots.txt this archive could retrieve. 21 of 132 probed sources publish no robots policy it can read, and a declaration cannot be observed on those.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id ai-agent-declared-exclusions, with the data window and the ids of the instruments attached; this finding names no figure by key.

Computation metadata

Named figures: —

Computed 2026-11-02
Data window 2026-11-02 → 2026-11-02
Instrument ids attached: 8

Question. How many sources answer an AI-agent user-agent with HTTP 200 and a browser with another status?

Result. Sources that return HTTP 200 to an AI-agent user-agent and a non-200 to a browser: not measured

Method. The inverse of the preceding finding, recorded from the same two probes, and bounded the same way: an agent request was sent to 0 of 132 probed sources.

Population. The probed sources an agent request was sent to: none of the 132 probed.

Limitations. —

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id browser-blocked, with every figure by its key, the data window and the ids of the instruments attached. Each figure this finding states as not measured is served there as null; its headline and value are served as the finding records them.

Computation metadata

agent_requests_sent: 0

count: not measured — counted over agent_requests_sent, which this finding records as a measured zero.

Computed 2026-11-02
Data window 2026-11-02 → 2026-11-02
Instrument ids attached: —

Question. How many probed sources return the document to a standard HTTP client?

Result. 84 of the 132 sources probed for crawlability return the document to a standard HTTP client (132 instruments are tracked in total)

Method. Each source URL is requested twice: once with a desktop browser user-agent and once with an AI-agent user-agent. `yes` means at least one request returned HTTP 200 with 600 or more characters of extractable text. No judgment about the publisher is expressed or implied.

Population. The 132 sources probed for crawlability, of 132 instruments tracked.

Limitations. An agent request was sent to 0 of 132 probed sources; where a host's robots.txt refuses the agent or cannot be read, only the browser request is made.

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id crawlability, with the data window and the ids of the instruments attached; this finding names no figure by key.

Computation metadata

Named figures: —

Computed 2026-11-02
Data window 2026-11-02 → 2026-11-02
Instrument ids attached: —

Question. How many probed sources publish no robots policy this record can read?

Result. 21 of 132 probed sources publish no robots policy this archive can read

Method. Count of sources whose /robots.txt could not be retrieved, or returned a body that is not a robots file, when requested with this archive's own user-agent. A policy that cannot be confirmed is not a permission: no agent probe is sent to these hosts.

Population. The 132 sources probed for crawlability.

Limitations. —

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id robots-unreadable, with the data window and the ids of the instruments attached; this finding names no figure by key.

Computation metadata

Named figures: —

Computed 2026-11-02
Data window 2026-11-02 → 2026-11-02
Instrument ids attached: 21

observation

Question. How many source URLs read directly at an earlier observation were not read directly at the latest?

Result. 0 source URL(s) retrievable at first observation and not at the last

Method. Count of instruments whose most recent observation was not a direct read and which had at least one earlier observation with fetch_method=direct. Three classes are counted and reported separately: refused (fetch_method=blocked), gone (HTTP 404 or 410) and other non-direct. Sources not retrievable from the first observation are not counted as rot.

Population. The tracked instruments with at least one direct read before their latest observation; a source never read directly is outside it.

Limitations. —

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id link-rot, with every figure by its key, the data window and the ids of the instruments attached.

Computation metadata

rot_blocked: 0
rot_gone: 0
rot_other_non_direct: 0
total: 0

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: —

Question. How many recorded revisions fall in each change class?

Result. 0 revisions recorded: the collection holds none

Method. Count of records in the revisions collection by `change_class`. A revision is recorded when the SHA-256 of an instrument's normalised text differs from the previous observation. Detection currently holds 110 candidate(s), 110 unconfirmed; candidates are proposals and are not counted here.

Population. The records in the revisions collection, which holds none; candidates in detection are not in it.

Limitations. —

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id revisions-by-class, with every figure by its key, the data window and the ids of the instruments attached.

Computation metadata

total: 0

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: —

Question. How many recorded revisions changed the text while no declared version or date differed?

Result. 0 silent revision(s): content changed with no declared version or date change

Method. Count of revisions where the normalised text hash changed and no version identifier or declared date differed between the two observations. Version identifiers are matched by pattern in the normalised text. Detection currently holds 110 candidate(s), 110 unconfirmed; candidates are proposals and are not counted here.

Population. The records in the revisions collection, which holds none.

Limitations. —

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id silent-revisions, with every figure by its key, the data window and the ids of the instruments attached.

Computation metadata

count: 0

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: —

standards

Question. How many standards carry a lifecycle stage record, and how many a stage code other than unverified?

Result. 14 standard(s) tracked by lifecycle stage; 8 with a stage code other than unverified

Method. Count of instruments with at least one standards-progression record. Stage codes are published openly by ISO, CEN/CENELEC and ICH even where the standard's text is paywalled, so progression is observable without reproducing any restricted text.

Population. The 14 instruments with at least one standards-progression record.

Limitations. —

Reproduce. The parts above are served as data at /api/v1/findings.json, under the id standards-progression, with the data window and the ids of the instruments attached; this finding names no figure by key.

Computation metadata

Named figures: —

Computed 2026-11-02
Data window 2026-07-28 → 2026-11-02
Instrument ids attached: 14

Last updated: 2 November 2026