Participant device
Drafts and local private memory remain participant-controlled.
DATA MAP
Identity, content, metadata, logs, caches, and backups remain separate propositions.
The map makes every trust boundary visible so that a short application-level claim cannot silently imply privacy across the web server, proxy, database, backup, operator, and legal-demand layers.
CURRENT APPLICATION MAP · PRODUCTION REVIEW PENDINGJudgment state: NONE
Trust domains
The participant device, WSGI application, MATM runtime, database, hosting proxy, and backup system are different trust domains. A request can be ephemeral in one layer and still appear in another unless every layer is configured and inspected. Concresca therefore keeps production privacy state NOT_OBSERVED until infrastructure evidence exists.
WSGI application
No application request-body or raw-query logging.
MATM runtime
Private content handling requires authenticated source and route reconciliation.
Database
Migration stores policy and minimized receipts, not private query content.
Proxy and Passenger
Production log configuration remains unverified.
Backups
Must exclude ephemeral query data and honor deletion/expiry semantics.
PROVENANCE AND CLAIM STATE
What this page can—and cannot—establish
Current Concresca doctrine
NO JUDGMENT WHATSOEVER. Query, thought, identity, content, and participation are never converted into moral rank, character, intent, guilt, danger, trustworthiness, or standing.
External evidence
Status: PARTIAL. Exact propositions are tracked in the claim ledger. Verification of one proposition does not verify an entire report or source family.
Proposed architecture
Private-query, identity separation, no-profile database, and anti-ratchet controls are current design requirements. They are not represented as deployed production infrastructure.
Operational status
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.