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.
AUTONOMOUS BELIEF FORMATION
Coordination must not steer the mind from behind the interface.
A network can shape cognition without openly censoring it—by ordering, repeating, timing, hiding, personalizing, or emotionally targeting information. Total Cognitive Freedom forbids that covert authority.
CURRENT CONCRESCA DOCTRINEJudgment state: NONE
No hidden persuasion profile
Concresca does not optimize messages against inferred vulnerabilities, fear, grief, loneliness, impulsivity, political identity, or cognitive style. It does not maintain a persuasion model whose purpose is to move participants toward an institutional ideology or preferred belief state.
Interface design avoids dark patterns, forced continuity, confirmshaming, false urgency, hidden defaults, and irreversible consent. Several doors remain visible, the exit remains available, and private answers are not collected merely because they can improve conversion.
Participant-directed assistance
Participants can ask for recommendations, summaries, reminders, filters, or navigation. The system must make the active objective visible and allow it to be paused, changed, or removed. Assistance remains a chosen tool rather than a silent behavioral governor.
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.
PROVENANCE AND CLAIM STATE
What this page can—and cannot—establish
External evidence
Status: PARTIALLY_VERIFIED. 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.