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.
ANTI-RATCHET DESIGN
Temporary means temporary.
Exceptional controls do not inherit permanence, new purposes, wider audiences, or person-level meaning merely because the infrastructure already exists.
CURRENT CONCRESCA DOCTRINEJudgment state: NONE
Eight constraints against function creep
The v0.35 anti-ratchet contract makes expansion visible and nonautomatic. Each control has an exact purpose, exact data class, exact audience, exact owner, exact expiry, exact secondary-use prohibition, exact correction route, and exact rollback sequence.
| Control | Required property | Prohibited drift |
|---|---|---|
| Defined purpose | One bounded operation and measurable technical objective | Vague safety, integrity, or trust mission |
| Minimum data | Only fields needed for the current transaction | General query, reading, or conversation history |
| Hard expiry | Automatic stop at a fixed time | Self-renewal or indefinite emergency |
| Reauthorization | New attributable decision for new scope | Silent reuse because infrastructure exists |
| Context firewall | No cross-room or cross-service meaning | Technical event becomes character or access judgment |
| Public change ledger | Versioned purpose, scope, retention, and owner | Secret definitions or hidden model updates |
| Deletion and rollback | Tested exit before activation | Irreversible accumulation |
| No judgment | Technical state only | Unsafe, bad, suspicious, dangerous, or unworthy participant label |
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.