Skip to content

the audit's remaining majors, and the minors that were about truth - #3024

Merged
Flotapponnier merged 1 commit into
devfrom
fix/audit-majors-minors
Oct 17, 2026
Merged

Flotapponnier merged 1 commit into
devfrom
fix/audit-majors-minors

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

the audit's remaining majors, and the minors that were about truth

A bench that ranks nobody was telling machines it had never run.
perp-max-leverage-terms shows four venues and a timestamp from this
morning, while /api/stat, /api/citable and llms.txt all said "Awaiting first
run". headlineParts read "nobody is ranked" as "nothing ran", and on a board
that ranks nobody by design that never corrects itself. It now says what is
true: how many venues were measured, and that none is ranked here.

Two sibling perp benches contradicted each other. perp-active-markets
rendered "Hyperliquid at 178 is crypto only" while perp-asset-breadth's own
title says Hyperliquid lists 156 non-crypto markets. Both are right about
different universes: the core book is crypto, the HIP-3 deployer markets are
not. The sentence now says which one it describes and points at the bench
that counts the other.

The same page called market count "the fastest proxy for breadth". "Fastest"
is the measured claim of a latency page; spending it on an unmeasured one is
the rule this repository keeps. It is "simplest" now, in both places.

And it pointed the reader at a findings text that ships only behind
/api/bench//variant, which sends x-robots-tag: noindex: a winner named
on evidence no page renders. The clause is gone, replaced by the fact it was
reaching for, that raw count can outrank breadth of asset class.

Figures typed into prose go stale in silence, so rpc-free-tier's "a
factor of eight: 3.3M requests against 392k" and perp-asset-breadth's "the
other 175 coins" are now claims that cannot rot.

Five titles ran 61 to 64 characters with the brand suffix, and the hub's
ran 64. Dropping one word keeps the entity, the two cohorts and the metric.
The hub's description also named four keyed providers where the chain pages
list six, and the snippet cut landed inside that list, shipping "...plus
Alchemy, Chainstack." It now names all six and fits.

/hyperliquid/traders invited indexing on an empty page. It is new, has
no snapshot, sits in no sitemap and is linked from nowhere, and its static
metadata carried no robots rule. It switches to generateMetadata so the rule
follows the data: noindex while the page says "Awaiting the first run",
indexable once a snapshot exists, follow throughout.

And the hub linked neither new family. /rpc is the page that ranks for
the head term and it pointed at neither rpc-free-tier, which answers "free
RPC plan", nor any block-push race. Both join the pills.

Not in this change, and deliberately: the six WebSocket pages are still
near-identical (Jaccard 0.98 on the first 300 words) and still have no
inbound link from the chain pages. That is differentiation work with a real
editorial cost, not a correctness fix.

Gates: 253 specs valid, tsc clean, eslint 0 errors, 597 tests.

**A bench that ranks nobody was telling machines it had never run.**
perp-max-leverage-terms shows four venues and a timestamp from this
morning, while /api/stat, /api/citable and llms.txt all said "Awaiting first
run". headlineParts read "nobody is ranked" as "nothing ran", and on a board
that ranks nobody by design that never corrects itself. It now says what is
true: how many venues were measured, and that none is ranked here.

**Two sibling perp benches contradicted each other.** perp-active-markets
rendered "Hyperliquid at 178 is crypto only" while perp-asset-breadth's own
title says Hyperliquid lists 156 non-crypto markets. Both are right about
different universes: the core book is crypto, the HIP-3 deployer markets are
not. The sentence now says which one it describes and points at the bench
that counts the other.

The same page called market count "the fastest proxy for breadth". "Fastest"
is the measured claim of a latency page; spending it on an unmeasured one is
the rule this repository keeps. It is "simplest" now, in both places.

And it pointed the reader at a findings text that ships only behind
/api/bench/<slug>/variant, which sends x-robots-tag: noindex: a winner named
on evidence no page renders. The clause is gone, replaced by the fact it was
reaching for, that raw count can outrank breadth of asset class.

**Figures typed into prose go stale in silence**, so rpc-free-tier's "a
factor of eight: 3.3M requests against 392k" and perp-asset-breadth's "the
other 175 coins" are now claims that cannot rot.

**Five titles ran 61 to 64 characters** with the brand suffix, and the hub's
ran 64. Dropping one word keeps the entity, the two cohorts and the metric.
The hub's description also named four keyed providers where the chain pages
list six, and the snippet cut landed inside that list, shipping "...plus
Alchemy, Chainstack." It now names all six and fits.

**/hyperliquid/traders invited indexing on an empty page.** It is new, has
no snapshot, sits in no sitemap and is linked from nowhere, and its static
metadata carried no robots rule. It switches to generateMetadata so the rule
follows the data: noindex while the page says "Awaiting the first run",
indexable once a snapshot exists, follow throughout.

**And the hub linked neither new family.** /rpc is the page that ranks for
the head term and it pointed at neither rpc-free-tier, which answers "free
RPC plan", nor any block-push race. Both join the pills.

Not in this change, and deliberately: the six WebSocket pages are still
near-identical (Jaccard 0.98 on the first 300 words) and still have no
inbound link from the chain pages. That is differentiation work with a real
editorial cost, not a correctness fix.

Gates: 253 specs valid, tsc clean, eslint 0 errors, 597 tests.
@Flotapponnier
Flotapponnier merged commit 2341cb3 into dev Oct 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant