Input
POST body over HTTPS; no query string for private content.
DEVELOPER IMPLEMENTATION
Build a private query path that does not become a profile path.
The runtime should accept the minimum request, avoid body logging, separate identity from content where possible, constrain diagnostic metadata, prevent secondary use, and return a redacted lifecycle receipt.
LOCAL IMPLEMENTATION GUIDANCEJudgment state: NONE
Request path
Treat private query content as an ephemeral parameter, not an account attribute. Do not place the body in URLs, access logs, exception strings, analytics events, idempotency tables, cache keys, trace names, metrics labels, or operator receipts. Use random request identifiers that cannot be reversed into content and expire operational rate state independently.
Processing
Volatile request scope; no training or evaluation reuse by default.
Diagnostics
Route class, neutral status, random request ID, bounded timing.
Identity
Anonymous or scoped credential separate from content where possible.
Memory
Only explicit participant-selected promotion creates durable memory.
Deletion
Tombstone may prove lifecycle action without retaining removed content.
Neutral error example
A safe response states that a route, dependency, credential scope, privacy scope, schema, or capacity condition prevents the requested operation. It does not infer intent or assign blame, danger, morality, reliability, or worth to the participant.
{"type":"https://concresca.com/problems/resource-temporarily-unavailable","status":503,"code":"RESOURCE_TEMPORARILY_UNAVAILABLE","judgment_state":"NONE","participant_evaluation_effect":"NONE"}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: LOCAL_IMPLEMENTATION. 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.