Redress · v0.21 WIP

Correcting the origin does not repair every copy or consequence.

Redress continuity preserves correction identity, supersession, downstream notice, nonresponse, nonreachability and residual error across custody changes.

v0.21.0-wiplineage recoverylocal synthetic evidence

Answer first

When may a correction be called complete?

Only within its identified reachable boundary. Unreachable recipients, independent derived records, public exposure and unconfirmed downstream copies remain explicit rather than counted as repaired.

Truth boundary: This WIP lineage-recovery branch locally evaluates repository-owned synthetic fixtures. It does not supply the missing sealed v0.19/v0.20 lineage, external execution, production migration, legal authority, institutional adoption, participant-study evidence, independent certification or deployment.

Dependency graph

Know what can and cannot be repaired

Node	Class	Meaning	Reachability
N-ORIGIN	origin	Origin record	Reachable
N-HOLDER	current_holder	Current receiving holder	Reachable
N-DOWN-A	downstream_recipient	Reachable downstream recipient A	Reachable
N-REDIST	redistributor	Known redistributor	Reachable
N-DOWN-B	downstream_recipient	Reachable downstream recipient B	Reachable
N-UNREACH	nonreachable_recipient	Known but unreachable recipient	Unreachable
N-DERIVED	independent_derived_record	Independent derived record	Reachable
N-PUBLIC	public_index	Public index	Reachable
N-RECEIPT	receipt_store	Receipt store	Reachable
N-REVIEW	review_archive	Review archive	Reachable

Correction scenarios

Notice, idempotence, conflict, supersession and nonresponse

ID	Scenario	Revision	Expected notice	Expected unreachable	Canonical actual
COR-001	Bounded downstream notice	1	N-HOLDER, N-DOWN-A, N-REDIST, N-DOWN-B, N-DERIVED, N-PUBLIC, N-RECEIPT, N-REVIEW	N-UNREACH	`null`
COR-002	Idempotent repeat	1	Scenario-specific	None	`null`
COR-003	Conflicting corrections	2	Scenario-specific	None	`null`
COR-004	Superseding correction	3	Scenario-specific	None	`null`
COR-005	Correction withdrawal	4	Scenario-specific	None	`null`
COR-006	Recipient nonresponse	5	Scenario-specific	None	`null`

Human explanation

Every receipt must answer the affected person

What changed?
Who changed it?
Under what authority?
Which recipients were notified?
Which recipients confirmed?
What remains wrong or unreachable?
What can the affected person do next?

Canonical evidence

Exact graph and scenarios

Open exact correction-dissemination JSON →

Claim → evidence

Follow the bounded support relationship

CLM090 · CONCRESCA WIP IMPLEMENTATION STATE

The correction graph distinguishes reachable, nonresponsive, unreachable and independently derived records rather than equating origin repair with complete correction.

Exact support Exact support

This WIP lineage-recovery branch locally evaluates repository-owned synthetic fixtures. It does not supply the missing sealed v0.19/v0.20 lineage, external execution, production migration, legal authority, institutional adoption, participant-study evidence, independent certification or deployment.

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 →