Jul. 25 at 2:27 PM
Yesterday we defended
$HYPD numbers that didn't deserve defending. A user called it out — he was right.
What was actually wrong: the holdings figure was the issuer's own "exceeds 2.00M HYPE" lower bound from May, and the share count came from the last 10-Q — expired for a company issuing this actively. Our metadata flagged both. Nothing forced the post to respect the flags.
Now something does. As of today, every current-state number we publish passes a preflight that fails closed: expired share counts, stale holdings, pending revisions — any red flag blocks the post.
$HYPD is blocked by its own gate right now, until a fresh share count files.
If a number looks wrong, tell us. Every input traces to a filing — and now its freshness gets enforced, not just stored.
@Jwa68 @tayloree26
