A roadmap board that can't fake its own votes
Most "public roadmaps" are decoration. A voting widget sits next to a list someone maintains in a spreadsheet, the two rarely talk to each other, and the votes exist mostly to make you feel heard while the team does whatever it was already going to do.
We didn't want to ship that. So /roadmap is now backed by
mechanics that actually constrain what happens next:
- Voting is signed, not vibes. Every vote is tied to your account - you get exactly one per item, and casting it again toggles it off. No stuffing the box with five browser tabs.
- Suggestions are a real pipeline, not a suggestion box. Anyone signed in can submit one (capped at five open at a time, so nobody floods the board), edit or withdraw it while it's pending, and search the backlog before adding a duplicate.
- Promotion doesn't erase the paper trail. When we promote a suggestion to a real roadmap item, it keeps every vote it already earned. We even had to fix a bug where deleting your account would cascade-delete an item you'd already gotten promoted to the board - so we changed that. Your suggestions and their votes now outlive your account, on purpose, not by accident.
The honest tradeoff: we only show the net score in public, not the raw up/down split. Full transparency there is still an internal view for now, mostly because a raw breakdown makes brigading a more visible strategy, not less. That might change.
Full mechanics - statuses, the promotion flow, what's public vs hidden - are in the roadmap docs.
One MCP Call, 24K Characters: Why Tool Results Keep Blowing Up Your Context Window
A single MCP tool call putting 24,568 characters into someone's context isn't a fluke - it's the default outcome of how most MCP servers respond. Here's why, and what actually fixes it.
We shipped llms.txt - here's exactly what's in it, and what isn't
Most llms.txt files are a markdown file nobody validates. Ours is generated from live content - and we're telling you the one thing it doesn't cover yet.