Mandatory Controls Are Not a Confidence Score
A high aggregate score cannot compensate for a missing authority, an unmet legal condition, stale evidence or a prohibited action. Mandatory controls remain gates.
Not every requirement can be averaged. A system may have abundant evidence and a convincing mathematical signal, yet still lack the authority to act. It may have an excellent score while the governing rule requires a document, approval or independent professional signoff that is absent.
A revised runtime assurance paper shows how weighted risk scores can admit cases that a conjunction of compulsory gates would block or route to review. The paper tests synthetic cases, so it does not establish a general incident rate. It does establish a fundamental design point: a score and a mandatory control are not interchangeable.
God Code guides. Gates decide.
ANUNNAKI Mathematics and God Code can calculate consequence, dependency, horizon, confidence and Necessary Work. They expose implications a professional may not have seen from one document alone. They do not erase a missing legal condition, authority boundary, freshness check or prohibited act.
Anunnaki.Live therefore records mandatory requirements as named gates. The evidence route shows whether each gate was completed. The action time gate checks whether it remains current. ABOS may prepare, reserve, escalate or refuse work, but it may not use an aggregate score to turn a prohibited action into an allowed action.
The record remains understandable
The Replay tells a professional which condition stopped the work, what evidence would address it and whether a human decision is required. It does not hide the limitation behind confidence language.
Source: Trust Is Not a Score. Read the complete Replay upgrade here.