Evidence, not a badge
There is no “verified” flag in this system and nobody can set one. Confidence is derived from what people reported after trying the procedure — including what failed — by a published rule.
About
A troubleshooting knowledge base where a fix comes with the evidence behind it, and where that evidence belongs to the exact version of the fix that was tested.
The problem this exists for
Search an error message and you get answers that were true four years ago, on a version you are not running, with a top comment saying it stopped working. There is usually no way to tell which of five suggestions applies to you, and no way to find out what happened when other people tried.
The information mostly exists. What is missing is any record of whether it worked, for whom, on what.
What is different here
Evidence belongs to a version
Editing a playbook creates a new revision that starts with no evidence. Nobody can build up credibility on one procedure and then swap in another, because the database cannot express it.
Failures are kept
A report that the fix did not work is stored, shown next to the successes, and counted. It cannot be edited or deleted afterwards by anybody, including us.
Your environment is part of the answer
Reports are recorded against the setup they ran on and shown segmented by it. When two environments disagree, that disagreement is the finding rather than something to average away.
Reading needs no account
Search, read and run a diagnosis without signing in — and report a result without signing in too. Signing in changes what a report counts toward, never whether you can file it.
What this is not
- A Q&A site. Nobody asks a question here and waits. The unit is a diagnostic procedure, not a thread.
- A feed. There is nothing to scroll and no reason to come back except a problem.
- A reputation game. There are no points, no badges, no ranks and no leaderboard, and that absence is deliberate.
- A chatbot. Nothing here generates an answer for you; the AI structures what people submit and never decides what is true.
- A code runner. Every command on this site is text you read and choose to run yourself, in your own shell.
Part of the ITISYOU network
DEV.ITISYOU is one of several independent products under itisyou.app. They share conventions and infrastructure conventions, not data: this product has its own database, its own accounts and its own storage, and nothing here is joined to anything there.
The mechanics are set out in full on how verification works.