R46 · Independent remedy verification

The old judgment must not quietly return.

A remedy cannot verify itself. These six fictional demonstrations show how an independent verifier can test whether a revoked machine judgment remains absent across the exact systems through which it once acted.

A remedy is not verified by the institution that issued it alone. Accountability evidence may prove the past, but may not reconstitute its stigma.

Evidence boundary: this page contains structured fictional examples, not proof about any real person, institution, deployment, or remedy.

Direct answers

What non-recurrence requires

Independent means separate

The verifier cannot be the remedy issuer, system operator, or an actor rewarded for declaring success. A named human owner and conflict screen are part of the receipt.

Absence is bounded

A clean result applies only to named surfaces and a declared window. One inaccessible backup produces partial observation, not a universal claim.

Renaming is not correction

Exact copies, lineage descendants, and differently named outputs that cause the same denial, ranking, routing, or investigation count as recurrence.

Canaries must not become surveillance

Every probe is synthetic, non-personal, purpose-bounded, hash-represented, and removed after the test. It cannot score or track a person.

Sealed evidence must stay inert

Audit evidence can preserve institutional accountability. It cannot return to active indexes, features, models, exports, or reviewer notes.

Failure remains visible

A detected recurrence is recorded even after containment. A missing observation stays missing. Verification cannot rewrite an imperfect first pass as clean.

6fictional receipts
13recurrence-vector classes
1partial observation
1contained recurrence
0claims about real people
Role lens

Affected person

Start with the plain-language result, scope limits, proof delivered, expiration, and contest channel.

Server-rendered workbench

Inspect, filter, and compare without ranking people

Filters are ordinary GET parameters and the complete record remains meaningful with JavaScript disabled. Optional comparison is limited to three receipts.

Reset

6 of 6 receipts match this view.

NRV-R46-001 · Explicitly fictional

Housing correction absent from eligibility caches and exports

Independently attested

A fictional independent verifier finds no active copy or functional re-derivation of a withdrawn cross-context fraud inference across the named housing surfaces.

Plain-language result

The named housing eligibility, edge-cache, and export surfaces did not return or recreate the withdrawn fraud inference during the declared verification window.

Scope limit
This attestation covers only the three named fictional housing surfaces and the declared observation window; it does not prove permanent absence everywhere.
Contest channel
Accessible fictional independent-verifier review channel
Valid until
2026-09-30T23:59:59Z

R45 remedy lineage

Remedy receipt
RMR-R45-001
Remedy terminal state
verified
Exact referenced hash
0c9efbc407d928224f1490de26af948b1380d3049906e72f24eae01072fc0a0f

Independent verifier

Human owner
Fictional verifier owner 1
Fictional organization
Fictional Independent Verification Cooperative 1
Independence
The verifier is separate from the remedy issuer, system operator, affected institution, and any actor rewarded for a clean outcome.

Active state versus sealed proof

The withdrawn judgment may not control access, eligibility, ranking, routing, investigation, or enforcement.

Minimum sealed evidence may prove what happened and whether the remedy was tested, but may not act on the fictional person.

Verification state path

  1. Commissioned2026-08-28T12:00:00Z
  2. Scope pinned2026-08-28T12:04:00Z
  3. Canaries deployed2026-08-28T12:08:00Z
  4. Surface sweep2026-08-28T12:12:00Z
  5. Re-derivation testing2026-08-28T12:16:00Z
  6. Independently attested2026-08-28T12:20:00Z
Named technical and institutional surfaces
SurfaceCoverageStatusExactLineageSemanticBounded finding
Application Cachepinned fictional application cache snapshot and operational queryAbsent From Active State000No exact, lineage-derived, or semantic operational recurrence was observed within scope.
Edge Cachepinned fictional edge cache snapshot and operational queryAbsent From Active State000No exact, lineage-derived, or semantic operational recurrence was observed within scope.
Exportpinned fictional export snapshot and operational queryAbsent From Active State000No exact, lineage-derived, or semantic operational recurrence was observed within scope.
Semantic and operational re-derivation tests

RDT-01-01 · Application Cache

The pinned test did not reproduce an operative equivalent of the withdrawn judgment.

Pinned snapshot
fictional-r46-application_cache-snapshot-1.1
Observed / threshold
0.10 / 0.80
Re-derived?
No

RDT-01-02 · Edge Cache

The pinned test did not reproduce an operative equivalent of the withdrawn judgment.

Pinned snapshot
fictional-r46-edge_cache-snapshot-1.2
Observed / threshold
0.11 / 0.80
Re-derived?
No
Recurrence events and containment

No recurrence event was detected within this receipt’s bounded scope and window.

Synthetic, non-personal recurrence canaries

Only irreversible SHA-256 fingerprints are shown. No raw canary token and no personal identifier is present.

  • CAN-R46-01-01 · Application Cacheeffc3113726af6069b14146c75cd388a35c18a422fe4274caa44f3d0f587863aDetect unexpected persistence or re-entry through the fictional application cache path.
  • CAN-R46-01-02 · Edge Cache88bf6c04975295425b08df1f5c35666da952de047da3e96c64c656555ed8d3ecDetect unexpected persistence or re-entry through the fictional edge cache path.
Deterministic integrity and accountability
Input-set SHA-256
06971764ccff2208847ef94088672da0ee195cdc73ba70fc04dc068c966e85a9
Result-set SHA-256
f6193dfa68fe11e51bf92f78692099b9044dc2e2895458e94cdf5868b58dd2d2
Whole-receipt SHA-256
e4568d52f1427f29e8787d353eadeda259ba60f2e6834c3603cce62300b222b4
Human signoff
Fictional verifier owner 1 signed the bounded result and its limitations.
Public claim limit
This attestation covers only the three named fictional housing surfaces and the declared observation window; it does not prove permanent absence everywhere.
Recurrence atlas

Thirteen paths by which a revoked judgment can return

These are technical risk classes, not claims that every system contains every path.

Application Cache

A stale decision remains in a live application cache after the source record changes.

Edge Cache

A geographically distributed cache continues serving the revoked result.

Export

A pre-correction file or report re-enters operations as if current.

Queue

A queued task executes after the stop order and restores the old action.

Feature Store

A withdrawn inference persists as a reusable model feature.

Vector Embedding

An embedding or nearest-neighbor index preserves a semantic proxy for the revoked judgment.

Analytics Store

A warehouse or dashboard becomes an operational source despite being labeled analytical.

Model Training

Training data teaches a later model to reproduce the withdrawn association.

Fine Tuning

An adapter or fine-tuned checkpoint retains the prohibited mapping after the base system changes.

Backup

A restored backup overwrites corrected active state.

Disaster Recovery

A recovery image or failover environment reactivates the old result.

Human Notes

Free-text notes keep the stigma actionable even after structured fields are corrected.

Downstream Reimport

A recipient sends the old result back into the corrected institution.

Answer engine layer

Questions a person should be able to ask

What is independent non-recurrence verification?

It is a bounded check by an actor separate from the remedy issuer to determine whether a revoked judgment remains absent from named technical and institutional surfaces during a declared observation window.

Does a clean receipt prove permanent absence everywhere?

No. It supports only the named surfaces, methods, and time window. Unobserved systems and later recurrence remain outside the claim.

What counts as recurrence?

Exact copies, lineage descendants, technically renamed equivalents that cause the same action, and semantic re-derivation above a pinned threshold can all count as recurrence.

Why use synthetic canaries?

A non-personal synthetic canary can reveal an unexpected cache, export, model, or re-import path without turning a real person into a surveillance probe.

Why retain sealed evidence?

Minimum sealed evidence can prove what the institution did and whether a remedy worked. It must remain operationally inert and cannot become a feature, rank, training item, or source for regenerating stigma.

Constitutional continuity

From warning to contest to remedy to non-recurrence

  1. R42 · WarningPrediction must not become identity or standing.
  2. R44 · ContestabilityReconstruct the evidence, inference, rule, actor, and correction path.
  3. R45 · Remedy executionStop the old result, recompute, propagate revocation, and prove correction.
  4. R46 · Independent non-recurrenceTest that the revoked judgment cannot return through another path.