Signals

This page holds publisher-originated signals: one record of one item a source’s own publication feed listed, carrying the address the source listed it at, the day the source dated it, the class the source stated, and a digest of the listing entry’s own text. Nothing here is a signal this record originated.

This is a separate store from the observation series and neither reads the other. The observation series records what this site has fetched and hashed; a signal records what a source’s listing listed. No figure on this page is derived from an observation, and no signal is one. The Observatory reports whether each source has been read; this page reports what the store holds.

What the store holds

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: state/signals/ holds no file for any source. Every zero in the tables that follow records what this archive has not kept, not what a source did not publish.

• astm — 1 attempt(s) on the pacing ledger, 0 of them a fetch, the last on 2026-09-13; no run has been authorised to write the store, so nothing is kept for it
• ec — 2 attempt(s) on the pacing ledger, 1 of them a fetch, the last on 2026-09-13; no run has been authorised to write the store, so nothing is kept for it
• ecfr — 6 attempt(s) on the pacing ledger, 3 of them a fetch, the last on 2026-09-20; no run has been authorised to write the store, so nothing is kept for it
• ema — 2 attempt(s) on the pacing ledger, 1 of them a fetch, the last on 2026-09-13; no run has been authorised to write the store, so nothing is kept for it
• eurlex — 2 attempt(s) on the pacing ledger, 1 of them a fetch, the last on 2026-09-13; no run has been authorised to write the store, so nothing is kept for it
• fda — 2 attempt(s) on the pacing ledger, 1 of them a fetch, the last on 2026-09-13; no run has been authorised to write the store, so nothing is kept for it
• federalregister — 2 attempt(s) on the pacing ledger, 1 of them a fetch, the last on 2026-09-20; no run has been authorised to write the store, so nothing is kept for it
• http — no attempt is on the record; nothing has asked this source yet
• isoiec — 1 attempt(s) on the pacing ledger, 0 of them a fetch, the last on 2026-09-13; no run has been authorised to write the store, so nothing is kept for it
• nist — 2 attempt(s) on the pacing ledger, 1 of them a fetch, the last on 2026-09-13; no run has been authorised to write the store, so nothing is kept for it
• pics — 1 attempt(s) on the pacing ledger, 0 of them a fetch, the last on 2026-09-13; no run has been authorised to write the store, so nothing is kept for it

The object, field by field

The fields are the ones the order names. Each says what it is read from and what it is not read from, because on this page the second half is the part that decides whether a value is a source’s fact or this record’s.

class

One of 12, read from the source’s own category values and from nothing else. A source’s whole stated token has to name the class after case and separators are folded; a fragment, a plural and a synonym do not. Nothing is read from a title, an address, or the section a listing sits in.

date

The day the source itself dated the entry, kept in the source’s own offset and never converted. An unreadable timestamp renders as an absence, never as the day this record read it.

authority

The host the listing was served from — answered where a request landed somewhere, asked where none did. No author, editor, contributor or creator element is read into any field: a syndication format defines two of those as the email addresses of people, this record names no natural person, and a host cannot be one.

source URL

The address the source declared for the entry inside its own listing. It was never requested, so no field here claims it was retrieved, and every record states which of the two it is.

attached source ids

The tracked entries that every address the source declared for one item names, matched on the whole address and on no looser form. A title that resembles a tracked entry’s title is this record reading two strings, so no such match is offered.

distance from source

4 values, derived from which surface a record came from. An entry a body lists on its own host and an entry it lists on another official host are different structural facts; neither is a statement about the entry’s content. Value 0 is the primary document itself and this store never writes it, because no adapter fetches an item.

By class

All 12 classes are listed, in the order they were filed, including those the store holds nothing for. Ordering by count would rank the classes against one another, and a class with no member keeps its place and its address: a page built only where membership exists disappears the day the membership does.

Every count above is drawn from the same population: the 0 record(s) this reader could read.

What a class reading can be, other than a class

A null in the class column is not one fact. These are the states a reading lands in, over the same population as the table above.

• No reading has been taken, because the store holds no record. This is an empty list rather than a set of zeros, so that it cannot be read as 0 records having been examined.

By distance from source

All 4 values are listed, including those nothing holds. Distance is a structural fact about which surface a record came from and says nothing about what any entry contains.

Drawn from the same 0 record(s). Value 0 is in the scale and this store never writes it: every record here is an entry in a listing, no adapter fetches the item behind one, and a 0 would say this record holds bytes it never requested.

By authority

The host each listing was served from, alphabetically. Ordering by count would rank the sources against one another, which is a claim this record does not make.

No record carries an authority, because the store holds no record at all. This page states which zero that is at the top.

Records

The store holds no record. This page states which zero that is at the top of this page and per source above; it is not one fact.

What this page counts, and what it does not

• The population is the files under state/signals/: one .jsonl and one .meta.json per source. 11 source(s) are listed whether or not a file exists for them, because a declared source with no file is the never-attempted state and a directory scan cannot see it. That figure is derived from the adapters themselves — every scripts/signals_*.py that declares a source key — and not from a list kept beside them: a list is a fact about the list, and this one said two while the corpus declared 11.
• Every count is derived from the .jsonl, which is the store. The .meta.json is the collector’s account of its own last run and is read for one question: whether a read has ever succeeded. It is not read for whether a read was attempted: it is written only by a run authorised to write, so its absence records that none was. The attempt fact comes from state/signals-pacing.jsonl, which records one row per gate decision, and this page holds 21 of 21 such row(s).
• 0 source(s) are excluded from every count here because their file holds lines this reader could not parse. An unmeasured result is not a negative result.
• No count is a judgment. A figure here says how many records the store holds and nothing about what any of them concerns. This record reports what sources published, and when what they published changed.
• A title is the source’s own text and is held under the 14-word ceiling read from scripts/quote_cap.py. A longer one is withheld with its reason and never trimmed: a truncated quote is a misquote.
• No signal reaches the instrument registry. A signal never becomes an observation, no observation gained a field for this work, and an address match names a tracked entry without changing anything the entry records.

Last updated: 25 September 2026