Why this platform works the way it does
The decisions behind the price, the refusals and the database — each one already written down before it was built.
Every post here is drawn from a document in this project's own record and names which one at the foot. Nothing is claimed that was not decided first, and no number appears that was not measured.
What an MCP server should say about itself
An MCP server's annotations, descriptions and results are three separate promises. How juudd sets each one, and why two hints contradict their tool's name.
The exit is a tool, not a support ticket
Your code, your database and your domains each leave juudd by a call your assistant makes — with no deadline, and with six calls that keep working even on a suspended account.
Why we do not count requests
Neither plan meters requests or bandwidth, because a bot flood is traffic you did not cause — and we measured what absorbing one costs us: $3 per ten million.