Roam (ROAM) — the revision ledger

Generated 2026-09-02T19:48:35Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for ROAM Token: 8,173 observations · 33 distinct series · 2 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 19:34:01 · every one of the 8,173 rows carries a verify_url · 26 series refreshed in the last 24h (720 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where ROAM Token's archive comes from

2 source families feed this network's ledger. Every row they wrote carries its own source, as_of and verify_url; this table is the live rollup of that. Roam DOES expose a public first-party stats API — the estate polls api.weroam.xyz/v1/explorer/stat/total/num (the catalog's stats_api_url) for members, WiFi nodes, bound/online/metablox miners, network checks, issued points and stickers, landing under two collector spellings (first_party_api for the point-in-time rows and depin_first_party for the daily-snapshot family). The second family is CoinGecko's market series for the ROAM Token (chains binance-smart-chain and solana; token address RoamA1USA8xjvpTJZ6RvvxyDRzNh6GCA1zVGKSiMVkn on Solana): price, market cap, supply and volume.

Revision ledger — 0 backward revision(s) recorded for ROAM

The ledger query ran during generation and returned 0 rows for ROAM — and ROAM's zero is a measured negative: the daily archive this estate holds for ROAM — 620 rows over 27 snapshots (2026-08-06 → 2026-09-01) — contains four cumulative-class series the detector watches, every snapshot pair of all four was diffed, and every pair is monotonic. Real counters were watched; none was rewritten. Where a sibling network (AR) shows a BLOCKS restatement (1,988,930 → 1,702,206, on the estate-wide ledger below), ROAM's watched counters show nothing of the kind. The fee families the detector watches elsewhere (all-time protocol fees) are simply not part of ROAM's daily archive — absence stated, not filled. Zero here is the live query result plus the measured trails below, not a gap — the ledger itself is at /v1/revisions?symbol=ROAM (the same query this page ran, served live), and a restatement would appear on this page the day the detector records one. /v1/revisions?symbol=ROAM cross-check passed: the served API reports 0 row(s), matching the ledger count rendered on this page.

What the detector watches for ROAM Token — the intersection, measured

The detector diffs every daily snapshot of every cumulative-by-construction series. Below is the live intersection of the estate detector's cumulative watchlist — imported directly from propintel/revision_ledger.py (75 declared names, so this page can never drift from the detector) — with what the daily archive holds for ROAM. Four watched series are held and were fully diffed; none produced a backward pair. That is the structural content of the zero above: watchable counters exist, and they are clean.

The trails behind the zero — watched counters, end to end

These are the actual counter trails the detector diffed for ROAM, rendered live from the archive. Each is a series that cannot decrease unless upstream rewrote history — which is exactly what makes their smooth monotonicity the proof behind the zero, and the same trails where an AR-style restatement would appear if it ever happened. Both come from the weRoam first-party explorer-stats collector (CHECKS_TOTAL, QUALITY_CHECKS under depin_first_party).

CHECKS_TOTAL — lifetime network checks recorded by the Roam app (weRoam explorer stats, the series class that produced real restatements for SOGNI, AUKI and R1 elsewhere in the estate):

QUALITY_CHECKS — lifetime quality-verified checks on the Roam network:

Gauges that moved backward — deliberately NOT revisions

These series fall outside the detector's cumulative-by-construction class (NOT_TRULY_CUMULATIVE and plain gauges in propintel/revision_ledger.py): a drop there is a real population or market change, not upstream rewriting history. Publishing them as "revisions" would be exactly the fake-metric behaviour this product exists to eliminate. ROAM's worked example: ONLINE_MINERS moves backward 15 times across 27 snapshots as miners go offline and re-connect, POINTS_BURNED and POINTS_ISSUED are stored as negative-flow accumulations that revalue, BOUND_MINERS dips as miners rebind, and the whole CoinGecko family (price, market cap, rank, 24h window stats, supply, volume) is revalued at every snapshot.

Same-timestamp conflicting values on record for ROAM: none

The task-level conflict check, run live: any (metric, timestamp) family where this estate recorded two or more different values. The query ran at generation and returned 0 groups in both depin_onchain and depin_daily — every (metric, timestamp) pair the estate holds for ROAM carries exactly one value. Zero here is the live query result, not a gap; the archive kept every write it made, and none of them disagree.

The ledger, live — every restatement recorded estate-wide (18 deduped events)

Deduped on revision identity exactly as /v1/revisions dedupes it. This is the same feed a subscriber polls; it is rendered live from ClickHouse at generation, not copied from a snapshot. Each row is an upstream source replacing the value of a (network, metric, date) it had already published — after this estate recorded the original. The superseded value is retained, never deleted; that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards.

How detection works — and what it cannot see

The detector (propintel/revision_ledger.py) diffs every daily snapshot this estate holds of every cumulative-by-construction series — counters that cannot decrease unless upstream rewrote them (block heights, transaction and transfer counters, lifetime fees). A row enters default.depin_revision_ledger iff two snapshots disagree for an already-observed date; zero human judgement. Resolution rule: latest observation wins for current-state reads, the superseded value is retained, never deleted. Population gauges (provider sets, node counts, prices, capacity) legitimately move both ways and are deliberately excluded — a drop there is a real population change, not a rewrite; the gauge table on this page is the worked example. Honest boundary: this catches value-history rewrites ex-post; identical-schema semantic drift with plausible values is what the hash-pinned derivation_replay layer is for. The detector's full classification is inspectable at /v1/revisions and frozen daily at /revision-ledger/REVISIONS_20260902.json.

Estate grades for ROAM (graded 2026-08-20 13:54:15.000)

Served by /v1/network/ROAM — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, published exactly as the engines emitted them, unflattering parts included.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–2 hit this estate's public API (the same rows this page queried — every row carries source / as_of / verify_url); command 3 hits the weRoam first-party endpoint the network-side rows came from; command 4 is the estate's graded network row; command 5 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for ROAM — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=ROAM" | python3 -m json.tool
# 2) The estate-wide feed (every network, both sides of every diff):
curl -s "https://kairossignal.com/v1/revisions" | python3 -m json.tool | head -80
# 3) weRoam first-party explorer stats (members / wifi / miners / checks / points):
curl -s -H "User-Agent: kairos-check" "https://api.weroam.xyz/v1/explorer/stat/total/num" | python3 -m json.tool
# 4) This estate's public API row for ROAM (grades + provenance):
curl -s "https://kairossignal.com/v1/network/ROAM" | python3 -m json.tool | head -60
# 5) The public daily snapshot of the ledger (frozen copy):
curl -s -o /dev/null -w "%{http_code}\n" "https://kairossignal.com/revision-ledger/REVISIONS_20260902.json"

Method & honesty notes. All counts are queries against the live ledger at generation time, not restamped copy — this page is regenerated by gen_revision_page_roam.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The ROAM revision count is the live result of SELECT count() FROM default.depin_revision_ledger WHERE network='ROAM'; the page refuses to ship if the served /v1/revisions?symbol=ROAM disagrees with it. The 18 estate-wide events shown are deduped on revision identity (deterministic hash of network, metric, current_date, prior_date) exactly as the API dedupes them; detected_at is the first detection and never moves. Series absent from a section are absent, not zero: the daily-snapshot ledger for ROAM is genuinely empty today — because every watched counter the archive holds proved monotonic under the detector's diff, a measured negative published as found, with the full trails rendered above — and this page says so instead of inventing restatements. The same-stamp conflict check is likewise the honest live answer: 0 groups in depin_onchain and 0 in depin_daily. Upstream probes ran serially by this generator immediately before rendering: api.weroam.xyz /v1/explorer/stat/total/num (the weRoam first-party explorer-stats upstream: members, WiFi nodes, miners, checks, points) HTTP 200; CoinGecko ROAM Token page (browser-verified origin; 403 here is its bot wall) HTTP 403; estate /v1/revisions?symbol=ROAM HTTP 200; estate /v1/network/ROAM HTTP 200.