The interest-rates record.
One maintained truth object, fully inspectable. This page is assembled from the same live record our machines serve. It keeps the kinds of thing it holds apart — what reporting says, what our own coverage measures, and what markets expect — and labels each claim with the kind of source behind it. Nothing here is retyped for marketing. When the record changes, this page changes with it.
Stated plainly: this is the second subject published in this format — the same seven-layer schema as the Hormuz record, in an unrelated domain. Two layers below are marked pending because they ARE pending for this subject; the exhibit shows the method holding on a young record, which is the claim.
What the record holds now
Separate layers, kept apart on purpose — reporting, our coverage metric, market expectation, our judgment, and the reporting- consensus ledger. They can disagree — and as of 2026-09-04, they do. Reading only one of them is how a machine gets this wrong.
0 · Observed policy state — primary sources · issuers named; no readings yet
The first-party issuers for this record are named below, but no row here has been fetched or hand-verified yet — this layer states its SOURCES, not their current values. Nothing here is a current fact; the automated verification against these issuers is the next build, and when it runs each row will state the date it was confirmed.
1 · Observed reporting — attributed sources
What outside reporting in our tracked set says. Attributed, not first-party policy data — we link each source; verify at the source. Primary policy feeds are the next depth (see layer 0 above and limits below).
2 · Coverage state — our own measurement
OUR COVERAGE REGIME
rising
Our coverage of interest rates is 88% above its 3-week baseline, sustained. This measures our attention — how much our tracked set is writing about it — not any central bank's policy stance.
TRACKED (OURS)
109 days
Across 10 intelligence verticals, 50 signals in the current sweep (as of 2026-09-04). Our own count.
EVENT ARC
25 markets
"Rate decision: Interest Rates" maintained since 2026-06-24; last priced 2026-08-11.
3 · Market expectation — attributed, belief not fact
We preserve the market signal as it is: a probability stays a probability, its market stays linked, and our public grading of that sensor — those prices scored against how reality resolved — measures that the signal survives our machinery without losing its meaning. Markets price collective belief about defined outcomes — a committee decision here — and they do not prove what any committee will decide. Read them for what they are: each question below is one defined outcome with the crowd’s current odds attached.
4 · Our reading — derived judgment over the cited layers
No first-party reading is on file for this subject yet: layer 0 names 4 issuers, none machine-read so far. No press-consensus ledger has been computed for this subject yet, and we say so rather than previewing conclusions. Prediction markets price 2 live questions under this record (newest price stamp Sep 4) — collective belief, cited as a sensor; never our probability, and never proof. Read together, each layer speaking for its own date, that is the maintained state of interest rates as this record holds it: our derived judgment over the cited layers, attributed throughout, never a forecast of ours.
5 · Reporting consensus — retroactive claims ledger, pending
What the press corpus agrees on, counted honestly: kernel facts (who, what, when, where) scored by how many independent reporting chains assert them — syndication collapsed first, so forty echoes of one wire story count once. Consensus measures reporting agreement, not reality.
Honest state: no retroactive ledger has been built for this subject. The machinery exists — it computed the first subject's corpus — but nothing publishes here until it has run for THIS subject with real receipts. We do not preview conclusions.
The recorded history
Every state change is written to a ledger the moment we observe it, with how long the prior state held. The ledger records what it measured — a coverage state transition, our attention metric, not a claim about any central bank. It began recording 2026-07-19; states before that date were tracked but not yet ledgered, and we say so rather than backfilling: we do not backfill history we did not record. The record is never edited after the fact.
No ledgered transitions yet in this window.
The receipts
Every claim on this page carries the kind of source behind it, so nothing borrows more authority than it has:
- Reporting (attributed) — outside coverage, linked in layer 1; verify at the source.
- Market (attributed) — Polymarket questions, linked in layer 3; belief, not fact.
- Our own measurement — the coverage regime, tracked days, vertical and signal counts, and every ledgered transition come from our record, not an outside source.
- Derived judgment — layer 4, our reading over the layers above; ours, and labeled ours.
- Pending layers — layers 0 and 5 state their own status in the record itself. A pending layer is a fact about the record, stated; it is never rendered to look finished.
The same question, read two ways
What keeping the layers apart changes for a machine reader. The left column is what a one-layer reader concludes; the right column is what the maintained record keeps in view. Each line is derived from the record’s own layers — the same truth object machines fetch — not from a staged chat.
WITHOUT THE RECORD — ONE LAYER AT A TIME
Reading only the coverage line (coverage state — our own measurement): attention is 88% above its baseline and rising — concludes “breaking — escalate.”
Reading only one reporting headline (attributed): “Inflation expectations softer than predicted ahead of interest rate decision” — concludes “whatever that single frame implies — with no way to see the layers that disagree with it.”
Reading only one market price (belief, not fact): “Will there be no change in Fed interest rates after the September 2026 meeting?” at 58% — concludes “the crowd has settled it — mistaking one question's odds for the whole state of the world.”
3 single-layer reads, 3 different verdicts — each brittle, and none aware the others exist.
WITH THE RECORD — EVERY LAYER IN VIEW
No first-party reading is on file for this subject yet: layer 0 names 4 issuers, none machine-read so far. No press-consensus ledger has been computed for this subject yet, and we say so rather than previewing conclusions. Prediction markets price 2 live questions under this record (newest price stamp Sep 4) — collective belief, cited as a sensor; never our probability, and never proof. Read together, each layer speaking for its own date, that is the maintained state of interest rates as this record holds it: our derived judgment over the cited layers, attributed throughout, never a forecast of ours.
Composed from the record’s own dated layers — derived judgment — assembled from the layers above at build time; ours, and labeled ours. The layers it holds apart: observed policy state · observed reporting · the record itself · coverage state · market expectation · our reading · reporting consensus · the recorded history. show the machine’s judgment sentence, as served
We keep the layers apart and do not collapse them. Our attention on interest rates stands 88% above its baseline and is rising. That measures our coverage, not the subject. The reporting layer is attributed press coverage tied to its jurisdictions; the market rows price something narrower — specific committee meetings, each on its own terms — and a priced probability is not a headline's mood. The market layer prices 2 live questions — collective belief about defined outcomes, never proof. A system that read any single layer alone could answer wrongly in either direction; the maintained record keeps every layer in view, each claim tied to its jurisdiction and its kind of source. This is our judgment over the layers above, labeled as such.
Provenance of this panel: each line above is derived from the record’s own layers, not from a staged chat. The coverage numbers, the headline, and the market price are fields in the same truth object served at GET /api/truth/interest-rates; the right column is composed from the record’s dated layers, with the served judgment sentence one tap away, verbatim. No transcripts were invented — the disagreement is in the data.
Verify it yourself, machine or human: this exact record is served live by the API and MCP — this page, GET /api/truth/interest-rates, and the get_truth_object tool are all assembled by the same builder, so what you fetch is what you are reading. One honest distinction: get_entity("interest rates") returns the broader live entity dossier — a different, complementary object, useful for trajectory and evidence receipts, but not this record.
curl -s https://sigb.ai/api/truth/interest-rates
curl -s https://sigb.ai/api/mcp -X POST -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_truth_object","arguments":{"topic":"interest-rates"}}}'Honest limits
- This is the second published truth object, and two of its seven layers are young: primary policy sources (layer 0) are not yet wired for this subject, and the reporting-consensus ledger (layer 5) has not been computed for it. Each pending layer says so on the layer itself; the schema holds, and the record fills in as the machinery reaches it — nothing is previewed to look finished.
- The coverage regime measures our declared source universe (139 actively-scraped verticals — definitions on the API page), not the whole internet, and it is our attention — not any central bank's stance.
- The transition ledger started 2026-07-19. Earlier state was tracked, not ledgered; we do not backfill history we did not record.
- Cadence, stated plainly: the record refreshes on a daily sweep with intraday market updates. It is maintained, not instantaneous.
- Market probabilities are collective belief about defined outcomes, never proof of what any committee will decide.
Informational only, never financial, legal, or investment advice. This exhibit is rebuilt from the live record on every data deploy.