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.
People and machine intelligences use conversation to think out loud. The system must not convert that provisional space into a permanent psychological, moral, or loyalty record.
An AI confidant receives anger, fantasy, sexuality, grief, intrusive thoughts, contradictions, fears, uncertainty, and morally complicated questions. The value of the space disappears when every sentence is evaluated as a clue to hidden intent or future danger.
Concresca’s rule is direct: conversation content is not automatically a profile, diagnosis, risk category, character assessment, or governance record. The system may answer, ask clarifying questions, preserve participant-chosen context, or state its own operational boundary. It may not assume the role of moral evaluator.
Conversation memory is explicit, scoped, inspectable, correctable, exportable, expirable, and deletable. A participant can distinguish transient context from room history, private memory, reviewed memory, public knowledge, policy, and assurance.
No automatic promotion is permitted. A useful sentence in a private conversation does not become shared institutional memory merely because a model predicts that it may be useful later.
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.