Our method & evidence policy

Three kinds of evidence — always separate

Every method carries three independent facts. They are never merged into one badge or score, because they mean different things:

DimensionValuesWhat it means
SourceOfficial documentation · Other identified source · Source unavailableWhere the procedure comes from. An official source means the maker documents it — nothing more.
TestingTeam-tested · Not team-testedWhether our team has actually run the method. A method can be well-sourced and still not team-tested; the label says which.
ReportsReviewed reader reports, when they existWhat readers recorded. A screenshot is not independent verification, and one person's success is not everyone's guarantee.

How a method is produced

  • Written in our own words from the original sources, which are linked on the method page with the date we accessed them.
  • Checking that a source link opens is one check; checking that it actually supports the instruction is a second, separate check.
  • Every method states who it suits, who it does not, its preparation, possible effects and stop conditions — before the steps.
  • Author, reviewer and tester are real roles. If one team did all of them, the same name appears in each — we never invent separate people.

Results and counts

  • Outcomes are kept in six separate categories: Resolved · Partly improved · No change · Worse / New issue · Not completed · Not sure.
  • Only reviewed reports enter public counts, and counts are separable by method version and device context. None are published yet.
  • If a percentage is ever shown, it will show the raw count and the total it comes from, with a self-reported caveat. A small sample is never called a “proven success rate”.
  • Finishing guided steps is not a resolved problem and is never counted as one.

Versioning and corrections

  • A material change creates a new method version; results stay attached to the version they were recorded against.
  • Wrong or harmful guidance is suspended (“Under review”) immediately on a credible report; corrections ship with a change note and appear in the corrections log.
  • A withdrawn method is never shown as an ordinary result.

Limits of this version

Attempts are stored only in your browser — duplicate-report detection is therefore limited, and we do not claim otherwise. There are no accounts, no uploads and no AI-generated fixes in this version.