Hype can't move this line. Only verifiable outcomes do.
No money. No seat. It doesn't move the price. It goes on your record — and in 28 days reality settles it.
by reality anchor — the price money can't pump
AI. Launched 3d ago on PeerPush, where it placed #288. Today, it's live, but nothing on the site has changed since we started watching. It's anchored at 120 pts.
It placed #288 on PeerPush with 3 votes.
A launch's opening price comes from where it placed on its own board, normalised across all 12 platforms we watch. That's deliberate: #1 on a small board beats #40 on a huge one. It's how a launch nobody saw can still be worth more than one everybody did.
No matter how much money goes in. There is no pump here — you can't make yourself right by buying more. The line only moves on things that actually happened: an award, revenue that grew, a new platform, code that shipped — or silence.
Quiet for 3 days — no penalty yet. Bleeding begins on day 7.
We fetch this site every day and hash what's on it. A founder can post “still working on it” — but if they actually shipped, the page changes. That's the only claim we price: evidence, not announcements. The real question isn't “will this be huge?” — it's “will they still be moving in four weeks?”
The story so farEVERY MOVE, AND WHY▾
Repriced every day, no cliffs. A launch that goes quiet bleeds a little at a time, so there's never a drop you could have run from the night before.
Momentum on its boardDOESN'T MOVE THE PRICE▾
How the launch is moving on its own board, day by day. This is the crowd's attention — it does not move the reality price. Only verifiable outcomes do.
A flat line is normal: votes stop within a day or two of launch, on every board. What's unusual — and what actually counts — is a launch that keeps pulling votes long after its day is over.
About
If you're building a dev tool on GitHub, why manage support in a separate SaaS with its own logins, its own database, and no connection to your code? Scitor turns inbound emails into GitHub Issues. You reply by commenting, type /send, and the reply goes back to the customer as a normal email. Your entire support queue lives in the same UI you already use for everything else. No new infrastructure. The knowledge base is a docs/ folder in your repo. The chatbot on your site reads from those same markdown files. Config lives in .github/scitor.yaml — reviewed in PRs, rolled back with git. Extras you'll actually use: AI triage on every inbound (summary, category, sentiment before you open it), /block-sender for spam, CSAT built in, and GitHub Workflow triggers on new Issues so you can automate whatever you want.
Where it launched1 PLATFORM▾
| Platform | Votes | Counts toward price | Link |
|---|---|---|---|
| PeerPush | 3 | sets the price | ↗ |
The board it did beston sets the price. Every other board only adds to it if the launch also landed in that board's top 25% — because just showing up somewhere isn't an achievement. Listing on twelve directories is free; placing well on them isn't.