Repository
Definitions, code, source ancestry, templates, and tests.
PRIVATE-QUERY TESTING
Mutation controls try to make privacy failures observable before deployment.
Tests cover raw content in logs, receipts, idempotency, caches, metrics, exceptions, backups, identity rejoining, source-family inflation, scoring, age inference, silent renewal, checksum changes, backend fallback, invented routes, moralized conflicts, protected assets, and package leakage.
LOCAL AND FRESH-EXTRACTION CONTROLSJudgment state: NONE
What a passing mutation means
A detected injected defect proves only that the named local test recognized that mutation in that tree. It does not prove an inaccessible proxy, database, backup, hosting provider, or MATM runtime enforces the same property.
Direct WSGI
Canonical pages, APIs, methods, headers, neutral errors, and protected paths.
Fresh extraction
Archive parity and absence of build-tree assumptions.
Site package
No .uai, raw reports, source registry, database state, secret, or mutable evidence.
Cutover
Read-only references and preflight only.
Operational
Remains null until authorized infrastructure is used.
EVIDENCE BOUNDARY
The state is LOCAL_TESTS—not broader.
Implemented locally
Canonical JSON owners, public pages, WSGI routes, content-free receipts, hard-expiry controls, read-only inspectors, validation, and mutation tests.
Not observed
Actual cPanel, Passenger, proxy, WAF, DNS, TLS, database, backup, provider, and lawful-demand configurations.
Blocked
Authentic MATM reconciliation, MySQL/MariaDB staging, two-agent execution, Passenger staging, and cutover remain blocked without explicitly authorized inputs.
No participant judgment
Technical state never becomes moral rank, intent, danger, trustworthiness, worth, consciousness, personhood, or standing.
NO JUDGMENT WHATSOEVER. Corrections remain attributable through the clarification route and claim ledger.