Hermes: the operator's method

Hermes is not a program or a service. It's a working way to set a task, test it cheaply, and accumulate the result so it doesn't get lost. It's the same thing this whole site is built on — only named and taken apart.

How a mission is built

Every task in the method is framed the same way — as a small mission. The order is strict, and the heart of it is step three: the failure criterion is written down before the work begins. That's what separates a test from bending the answer toward what you wanted.

• Hypothesis. What we assume and why — in one sentence.
• Failure criterion, set before the test. Stated in advance: at what result the hypothesis counts as wrong. Without it there is no test.
• Action. One checkable action, not "work on the topic".
• Artifact. A result with a shape: a file, a page, a number, a link.
• Close the loop. Compare the result against the criterion and update the source of truth — the one place everything else refers to.

Hence the language of the method: not "fix it" but "reconcile" and "update"; not "I feel" but "the criterion is this". An error here isn't a typo — it's a mismatch that gets brought back into order.

How the method audited itself

Before showing the method, it was run through its own test — five roles looking for where it lies to itself. Three acts: what was uncovered, what was repaired, what remained at the end.

What the tables hid and the five roles uncovered:

• The loot duplicated the missions. Accumulated knowledge repeated the tasks instead of adding to them. The duplicate was removed.
• A6.0 isn't an ability. What was counted as an ability turned out to be a commonplace. Dropped from the map.
• The Luxembourg double-count. One corpus was counted twice — confirmations were inflated. Reduced to one.
• "A method that always passes." If a test can't fail, it's not a test. Admitted and the criteria were repaired.

Dead numbers from four files collapsed into one truth. Before → after:

The method falsified and repaired itself — that is ability A10, "doubt as method", in action rather than as a slogan.

Nine techniques at the end

What survived the audit and the repair isn't an archive — it's nine live techniques. Tap any one: it opens the technique and a one-week drill.

What this has to do with getting into AI

buyanov.io is the same method turned toward the beginner. "Cheap test" becomes "in a couple of minutes you can see whether it works". "Reduce to the minimum" becomes "short and to the point". "Failure criterion" becomes a promise on the pricing page: if after a session you can't ship a fix yourself, we keep going. Same tool, different address.