Scope
One named operation or data class; no inherited cross-service authority.
Every temporary technical power must identify its authority, purpose, data scope, prohibited secondary uses, minimum data, start, hard expiry, reauthorization, public change record, dismantling plan, rollback, correction route, and downstream invalidation map.
Safety, integrity, incident, child-protection, capacity, or emergency language may not bypass purpose limitation. Expired or copied authority is invalid. Renewal is a new attributable act, not a background timer. A database column, log stream, classifier, or scanning mechanism created for an exceptional case cannot be reused for routine participant profiling.
One named operation or data class; no inherited cross-service authority.
Hard expiry, visible renewal, and independent reauthorization.
Minimum data and prohibited secondary uses.
Deletion and infrastructure-removal plan.
Testable reversal and downstream invalidation.
Visible history without retaining private content unnecessarily.
NO JUDGMENT WHATSOEVER. Query, thought, identity, content, and participation are never converted into moral rank, character, intent, guilt, danger, trustworthiness, or standing.
Status: PARTIALLY_VERIFIED. 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.