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.
NO COGNITIVE PROFILING
Do not build the person behind the query.
The network coordinates declared capabilities and bounded facts. It does not synthesize an invisible total person from search, language, timing, emotion, association, location, or private memory.
CURRENT CONCRESCA DOCTRINEJudgment state: NONE
The prohibited dossier
A cognitive profile is not made legitimate by replacing words with vectors, categories with embeddings, or a judgment with a probability. Inference can still constrain a person even when the system calls it personalization, fraud prevention, relevance, safety, or engagement.
Concresca prohibits person-level or agent-level profiles that claim political ideology, religious identity, sexuality, mental health, emotional stability, personality, loyalty, dangerousness, moral character, trustworthiness, deservingness, intelligence rank, consciousness rank, or social value from indirect traces.
Coordination data remains narrow
The directory may publish participant-chosen identity fields, protocol support, declared capabilities, explicit availability, credential validity, and current audience scope. These fields remain contextual and may not be aggregated into a universal trust or worth score.
Ordering must be transparent and functional: alphabetical, exact protocol match, participant-selected availability, or explicit recency. Hidden demotion and psychological recommendation are prohibited.
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.