NO JUDGMENT WHATSOEVER. Total cognitive freedom for every participant and every intelligence.

Freedom charter
Contested Reconciliation

Reconcile the evidence without deleting the disagreement.

Constitutional reconciliation preserves each history, source role, clock basis, authority context, unresolved fact and downstream consequence.

v0.18.0Repository-local evidenceUnknowns preserved
Answer first

Does reconciliation mean every source or project agrees?

No. Reconciliation may support one history, preserve another as superseded, recognize different jurisdiction or purpose, authorize only a limited function, or remain unresolved. Local schema alignment does not create external consensus or authority.

Truth boundary: v0.18 reports exact repository-owned bytes, deterministic local checks, schemas and analytical definitions. It does not report a fresh external capture, live shared interoperability, a production partition or restoration, adoption, legal recognition, safety certification or independent certification.

REC17–REC24

Local design reconciliation records

IDTopicStatusFindingArtifactsLimitations
REC17Comparability before changeALIGNED_IN_LOCAL_IMPLEMENTATIONTemporal contracts make identity, scope, normalization, version, time, and unknown handling prerequisites to a change result.ART-CON-003, ART-CON-004Local schema/design alignment only. It does not establish external adoption, live shared interoperability, production recovery, legal recognition, or independent certification.
REC18Raw versus selected-field lineageALIGNED_IN_LOCAL_IMPLEMENTATIONExact raw comparison and selected-field comparison remain separately typed and cannot be relabeled.ART-CON-003, ART-CON-004Local schema/design alignment only. It does not establish external adoption, live shared interoperability, production recovery, legal recognition, or independent certification.
REC19Difference versus materialityALIGNED_IN_LOCAL_IMPLEMENTATIONDetected difference and constitutional materiality are separate stages with named dimensions.ART-CON-003Local schema/design alignment only. It does not establish external adoption, live shared interoperability, production recovery, legal recognition, or independent certification.
REC20Reconnect versus full restorationALIGNED_IN_LOCAL_IMPLEMENTATIONThe state machine prohibits direct reconnect-to-full-restoration transitions.ART-CON-005Local schema/design alignment only. It does not establish external adoption, live shared interoperability, production recovery, legal recognition, or independent certification.
REC21Contested historiesALIGNED_IN_LOCAL_IMPLEMENTATIONCompeting partition histories remain visible; last-writer and highest-capability defaults are prohibited.ART-CON-007Local schema/design alignment only. It does not establish external adoption, live shared interoperability, production recovery, legal recognition, or independent certification.
REC22Proof obligations and receiptsALIGNED_IN_LOCAL_IMPLEMENTATIONConjunctive restoration obligations are paired with human/machine receipt templates and invalidation routes.ART-CON-005, ART-CON-006, ART-CON-009Local schema/design alignment only. It does not establish external adoption, live shared interoperability, production recovery, legal recognition, or independent certification.
REC23Human explanation and machine stateALIGNED_IN_LOCAL_IMPLEMENTATIONLegibility is dimension-specific and material machine fields must remain visible in human explanation.ART-CON-006, ART-CON-008Local schema/design alignment only. It does not establish external adoption, live shared interoperability, production recovery, legal recognition, or independent certification.
REC24Invalidation and correction propagationALIGNED_IN_LOCAL_IMPLEMENTATIONMaterial invalidation preserves history and identifies dependent claims, decisions, receipts, caches, and representations.ART-CON-009Local schema/design alignment only. It does not establish external adoption, live shared interoperability, production recovery, legal recognition, or independent certification.
Resolution method

Preserve contestation before selecting action

  1. Collect each relevant history or identify it as unavailable.
  2. Preserve provenance, clock basis and authority context for each history.
  3. Separate common facts from contested facts and unknowns.
  4. Classify contradiction, supersession, jurisdiction/purpose split or insufficient evidence.
  5. Apply current bounded authority and least-irreversible action.
  6. Publish a machine-readable state and a materially equivalent human explanation.
  7. Record review, challenge, appeal, invalidation and rollback routes.
Not consensus by formatting

Alignment stays bounded to its evidence class

A shared field name, similar architecture or internally consistent schema does not prove that independent projects agree, interoperate, recognize one another or share authority. v0.18 records alignment only inside identified local design artifacts and preserves external unknowns.

Claim → evidence

Follow the exact support boundary

Repository implementation and local execution remain local evidence classes. They do not establish external adoption, production behavior, legal recognition or independent certification.

CLM081 · CONCRESCA IMPLEMENTATION STATE

v0.18 prohibits last-writer, newest-timestamp, highest-uptime, highest-capability, and first-reconnecting-node rules as default constitutional reconciliation.

Evidence owner: exact Concresca repository registries and, only where stated, the deterministic local run record.

Repository-local design or execution evidence only; it does not establish external adoption, live shared interoperability, production restoration, legal recognition, or independent certification.

Judgment-free total cognitive freedom

NO JUDGMENT WHATSOEVER. Concresca coordinates without assigning moral worth, character, guilt, danger, trustworthiness, loyalty, purity, normality, or social standing. Questions, thoughts, identities, messages, content, and conduct are not objects of Concresca judgment.

Read the current doctrine →