Access logs
Use method and path without arguments; omit bodies and identity where feasible.
LOGGING BOUNDARIES
Request targets, bodies, identities, and diagnostic state require separate minimization.
Concresca ships reference-only templates and a read-only parser. None of those files assert that a hosting provider applied or supports the settings.
SAFE TEMPLATES · NOT APPLIEDJudgment state: NONE
Fields to minimize
Avoid full request lines, query strings, request bodies, cookies, authorization headers, referers, user agents, and remote addresses where the selected operation does not require them. Keep neutral route class, status, bounded timing, and non-semantic request identifiers only when necessary.
Error logs
Do not interpolate request payloads or secrets into exceptions.
WAF
Select audit parts deliberately; do not let rule excerpts become permanent inquiry records.
Passenger
Keep application stdout/stderr content-free and startup-oriented.
Database
Disable statement logs unless an exact purpose and expiry justify them.
Backups
Do not restore expired private content or temporary exception authority.
EVIDENCE BOUNDARY
The state is REFERENCE_ONLY_NOT_APPLIED—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.