Skip to content

DocsReading HEY

This week

The weekly rollup: what shipped, who went quiet, who came back.

/this-week is HEY's rolling weekly rollup: what projects shipped in the last seven days, who became a verified builder, who came back to shipping, and where the two strict states stand. It is built on shipping, because shipping is what HEY records most of; the two strict states come last, as small blocks that say plainly when they are empty and why.

The window

The last seven days, ending when the page was rendered, printed on the page (for example "7 days to 4 Sep 2026"). A record is counted in exactly one window: the start is included, the end is not. There is no calendar week and no timezone rule to remember. The weekly report is different: it counts Monday to Monday (UTC), so the two cover different days.

The sections

What shipped. Every approved ship of a published project inside the window, grouped by project, newest first. Each card is the ordinary project card with that project's newest ship inside it, so it shows exactly what /ships shows for the same ship. The headline counts ships; the section counts projects. A project's "3 ships in this window" counts the whole window, not only what the card shows. The page shows a sample; the rest is on /ships.

New builders. Projects that became verified builders inside the window. This is when HEY finished checking the public evidence, not when the team started building. HEY verifies in passes, so a large number can mean HEY caught up on its own backlog rather than that many teams appeared; the page says so under the heading.

Back to shipping. Projects whose activity status moved from Quiet or Dormant to Shipping, Active or Resumed during the window, comparing HEY's first and last reading of each project inside the window. A project HEY read only once in the window cannot move, so the page says how many projects it could compare — "none moved" never hides "nothing was looked at".

Still Building · Under the Radar. The two strict states, as counts and names, read from the same stored result as the Radar, so the two pages never disagree. They are usually empty. That is the design, and the block says which condition is unmet rather than showing nothing. Neither is a buy signal. How each is decided is on /methodology.

When a section is empty

An empty section is a reading, not a fault: no approved ship in seven days, nobody cleared the evidence bar this week, no reading moved from quiet to shipping, or no project meets a strict state. The page can show all of them empty at once and still read honestly.

What it never says

No "alpha", "gem", "100x", "moon" or "undervalued". No price talk beyond a card's own market-cap context, and no sentence that connects building to price. Counts are counts, each printed beside the window it was counted over. Automated tests fail a release whose page breaks this.

As JSON

GET /api/this-week returns the same rollup, with the window (since, until, days and the label) and a disclaimer: counts of public, source-backed activity HEY recorded in the stated window — not a prediction, not a ranking by price, and not investment advice. It is cached for five minutes and answers 60 requests a minute per client without a key; the fields are in the public API. A feed of the same is at /feed/this-week.xml.