committee
One of the 12 signal classes. A record carries this class when a source’s own category value names it — the whole token, after case and separators are folded, and no looser match.
What the store holds for this class
10 of 11 source(s) carry a read attempt on
state/signals-pacing.jsonl, 7 of them a
fetch, and no run has been authorised to write the store. Nothing has been
kept for this class or any other, which is a fact about this archive and
not about what any source published under it.
How a record acquires this class
- The class is read from the source’s own category values in its own listing, and from nothing else. It is not read from a title, an address, or the section a listing sits in.
- Case and separators are folded, because they are serialisation: one token written three ways is one token. Nothing else is folded — a fragment of a longer phrase, a plural, and a synonym all fail to name this class, and the source’s own words are then kept and reported as stated.
- Where a source states several classes, every one is kept and the first in the source’s own document order is the one recorded. Choosing among them on any other basis would rank a source’s own values against each other.
- Where a source states no class, the record says so. There is no residual bucket here, and a record with no class is never counted into one.
Records
No record is listed below. This page states above which zero that is; it is not one fact, and this page keeps its address either way.
The other classes
All 12, in the order they were filed. Ordering by count would rank them against one another, which is a claim this record does not make.
- document
- revision
- consultation
- agenda
- work item
- notice
- press release
- implementation
- effective date
- standard progression
- committee
- technical
Last updated: