How partner packs encode a methodology

The three rule types

A hard rule gates: fail it and the entry is vetoed, with the failure named in the rule flags. A confluence weighs: it moves the pack score without deciding on its own. A manual confirm asks you.

The manual type exists because some parts of a published methodology are genuinely judgements — whether a session narrative holds, whether a catalyst is real, whether a signal bar is clean. A machine check for those would be a guess wearing the costume of a measurement, and would be indistinguishable from the real checks sitting beside it.

Machine coverage is published

Each pack declares what share of its rules can actually be checked mechanically. That figure is published rather than hidden, because it is the honest measure of how much of a methodology the product has really encoded.

When public teaching contradicts itself

Published methodologies are often taught with varying detail across sources. Where readings conflict, the pack encodes the tighter documented reading and records which one it took.

A looser reading would admit more setups and make the pack look more useful while representing the methodology less faithfully — which is the wrong trade for a feature whose entire value is fidelity to somebody else's rules.

Packs under review

A pack that has not completed review says so on its own surface rather than shipping silently at full confidence.

Frequently asked

What does a manual confirm checkbox on a pack do?

It holds the grade conditional on your judgement. Subjective concepts — a session narrative, a catalyst, signal-bar quality — are kept as manual confirms rather than faked as machine checks that would look identical to the real ones.

How much of a methodology does a pack actually encode?

Each pack publishes its machine coverage: the share of its rules that can be checked mechanically. The remainder are manual confirms, which is why the figure is disclosed rather than left for a user to discover.