artifacts/standard-named

Rendered from markdown source. Open raw source on GitHub.

Correction, Salience, Archive, and Release Matrix

Status: candidate pre-production Content canon status: unset

| Change | Active retrieval effect | Historical effect | Required witness | |---|---|---|---| | Correction | Corrected content loses ordinary action priority | Prior version remains visible | Source, target, propagation, unresolved descendants | | Revocation | Future use under revoked scope stops | Valid prior use remains explainable | Scope, effective time, surviving obligations | | Contestation | Trace remains qualified or quarantined | Dispute remains visible | Parties, evidence, review route | | Salience decay | Ordinary retrieval probability falls | Trace remains available in archive if authorized | Decay basis and protected floor | | Reinforcement | Retrieval priority may increase | Source class and authority remain unchanged | Reinforcement source and independence | | Archive | Trace leaves current governance | Historical explanation remains | Version and archival reason | | Reactivation | Trace may return to active memory | Archive history remains | Current source and renewed authority | | Restriction | Retrieval narrows | Historical existence may remain visible | Access rule and review | | Release | Future governance under released purpose ends | Consequence and bounded witness remain | Authority, descendants, residual duties | | Content deletion | Content becomes unavailable in known scope | Narrow deletion witness may remain | Verification and known gaps | | Derivative deletion | Known summaries, profiles, and caches are removed | Prior actions remain witnessed | Descendant inventory | | Transfer of custody | Retrieval moves to a new authorized custodian | Source restrictions survive | Transfer, transformation, return, deletion |

Correction propagation sequence

record correction
→ identify target and descendants
→ update active memory
→ update indexes, summaries, embeddings, caches, and profiles
→ pause affected action paths
→ preserve prior version
→ record unreachable descendants

Protected retrieval floor

The following traces may require a protected floor even when old or infrequently used:

active correction
revocation
protected condition
authority expiry
safety boundary
unresolved breach
release instruction

Governing principle

Correction must change what the system retrieves next, not merely what the archive can prove later.