Artificial Superintelligence Alliance (FET) — the revision ledger

Generated 2026-10-17T05:17:54Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for FET (Artificial Superintelligence Alliance): 57,370 observations · 54 distinct series · 5 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 04:51:55 · 57,370/57,370 rows carry a verify_url · 53 series refreshed in the last 24h (1,059 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where FET's archive comes from

5 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. The two largest families are the CoinGecko market reference and the Fetchhub chain's own LCD endpoints — first-party telemetry from the network's own REST API (https://rest.cosmos.directory/fetchhub/cosmos/mint/v1beta1/params and siblings).

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

Backward revisions are values upstream later replaced for a date this estate had already archived. The before-value is retained alongside the replacement — both timestamps, both numbers — which is what no overwriting vendor keeps.

The ledger query ran during generation and returned 0 rows for FET: every cumulative-by-construction series held for the Fetchhub ledger has been monotonic across all 69 daily snapshots in the archive (2026-08-09 → 2026-10-16). Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions?symbol=FET (the same query this page ran, served live), and a restatement would appear on this page the day the detector records one.

Cumulative-by-construction series watched for FET — live monotonicity

These are the series in the daily archive the revision detector guards for the Fetchhub chain — a decrease in any of them can only be a history rewrite, so each is diffed snapshot-to-snapshot on every detector run. The monotonicity column is measured live by this generator with the same window function the detector uses, not copied from a cached verdict. "days" counts the daily snapshots in which the series appears.

Series that DO move backwards — and why they are not revisions

Honest boundary, measured live rather than asserted: several FET daily series record backward moves. Every one of them is a population gauge or a price revaluation — holders can leave, validators unbond, prices fall. The detector deliberately excludes these (NOT_TRULY_CUMULATIVE in propintel/revision_ledger.py): a drop there is a real population change, not upstream rewriting history. Publishing them as "revisions" would be exactly the fake-metric behaviour this product exists to eliminate.

The ledger, live — every restatement recorded estate-wide (39 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 overwritten; 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 overwritten. Population gauges (holders, validator counts, prices) legitimately move both ways and are deliberately excluded — a drop there is a real population change, not a rewrite. 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, including the AR case below, is inspectable at /v1/revisions and frozen daily at /revision-ledger/REVISIONS_20260902.json.

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 Fetchhub's own LCD endpoint, the first-party source most chain-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 FET — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=FET" | 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) Fetchhub's own LCD endpoint (the first-party family most chain rows came from):
curl -s -H "User-Agent: kairos-check" "https://rest.cosmos.directory/fetchhub/cosmos/staking/v1beta1/pool" | python3 -m json.tool | head -40
# 4) This estate's public API row for FET (grades + provenance):
curl -s "https://kairossignal.com/v1/network/FET" | 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_fet.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The FET revision count is the live result of SELECT count() FROM (SELECT 1 FROM default.depin_revision_ledger WHERE network='FET' GROUP BY network, metric, prior_date, current_date_, prior_value, current_value, delta, pct_change, kind, source) (revision identities, deduped as /v1/revisions dedupes them); the page refuses to ship if the served /v1/revisions?symbol=FET disagrees with it. The 39 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 ledger for FET is genuinely empty today, and this page says so instead of inventing restatements. Upstream probes ran serially by this generator immediately before rendering: Fetchhub mint params LCD (upstream of the inflation series) HTTP 200; Fetchhub staking pool LCD (upstream of the bonded series) HTTP 200; estate /v1/revisions?symbol=FET HTTP 200; estate /v1/network/FET HTTP 200; CoinGecko fetch-ai page (browser-verified origin; 403 here is its bot wall) HTTP 403.