Runtime
No raw query, prompt, or request-body logging in application code.
The suite executes positive controls and mutations covering raw-body logging, identity linkage, profiles, scores, secondary use, database schema, receipts, anti-ratchet controls, minor privacy, protected assets, and WIP packaging.
A detected mutation proves that the current local test recognized the injected defect. It does not prove that an uninspected hosting proxy, Passenger configuration, MySQL service, backup process, third-party processor, or deployed MATM instance enforces the same property.
No raw query, prompt, or request-body logging in application code.
No query-content or cognitive-profile tables or columns.
No private content bodies or participant evaluation effects.
Authority, purpose, hard expiry, rollback, deletion, and correction.
No hidden contradictory metadata, scores, or moralized labels.
No raw reports, secrets, private .uai memory, or final aliases.
NO JUDGMENT WHATSOEVER. Query, thought, identity, content, and participation are never converted into moral rank, character, intent, guilt, danger, trustworthiness, or standing.
Status: LOCAL_TESTS. Exact propositions are tracked in the claim ledger. Verification of one proposition does not verify an entire report or source family.
Private-query, identity separation, no-profile database, and anti-ratchet controls are current design requirements. They are not represented as deployed production infrastructure.
Local repository, browser, WSGI, and fixture evidence remains separate from MySQL, Passenger, public traffic, outside participation, Eviulon ratification, Patefacere adoption, or Evulgare certification.
Correction route. Challenge a claim through the claim ledger or the public clarification and correction route. One commissioned report family is never counted as independent corroboration.