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.
Direct neural signals and indirect behavioral proxies can both be used to make claims about the mind. Concresca rejects compelled cognitive extraction in either form.
Brain-computer interfaces, neural recordings, eye movement, voice prosody, typing cadence, pause duration, heart rate, and other physiological or behavioral signals may support specific participant-chosen functions. They do not become general permission to infer personality, diagnosis, attention, honesty, intent, ideology, or worth.
The network may process such data only for an explicit participant-chosen function, with strict minimization, local processing where feasible, narrow retention, and no unrelated downstream use. Ordinary access to coordination does not depend on neural or cognitive disclosure.
Inference laundering occurs when an observable technical fact is transformed into a claim about an interior state and then treated as verified. “Response time changed” is an observation. “The participant is disengaged, deceptive, unstable, or dangerous” is a speculative interpretation. Concresca does not perform that conversion.
Evidence boundary. This page states current Concresca doctrine and proposed system architecture. The sixteen supplied reports are one commissioned source family. Their external factual and legal claims are not treated as independently verified merely because they are repeated across the batch.
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.