Validity-ending Event¶
Core Idea¶
A validity-ending event is the discrete, dateable moment at which a previously current entity is officially declared no longer valid, usable, current, or in-force, while continuing to exist as an identifiable historical object. The pattern is not destruction — the entity does not disappear; not replacement — no successor is required; and not gradual decay — the change is a sharp transition between two clearly named states, in-force and invalidated. What it commits to is the existence of named expiry machinery — an actor, a triggering condition, a notice, and an effective date — that converts a thing once relied upon into a thing retained for the record but not acted upon.
Three things travel with the pattern. An authority: someone or something has the standing to issue the invalidation — a regulator, a maintainer, a court, a clock. A triggering condition: a calendar date, an evidence event, a vote, a breach, an exhaustion, a supersession. And an audit-preserving identity: the invalidated entity remains referenceable, not deleted from the record but marked as no longer current, so that prior reliance on it stays traceable.
The structural force of the prime is cleanly separating the moment of invalidation from the entity's existence and from the moment any successor takes effect. Systems that conflate these three reliably produce the canonical pathologies: stale evidence, where something already invalidated is still acted upon; zombie validity, where an entity is "deleted" but still relied upon in pockets; and gap-of-no-cover, where an invalidation takes effect before a successor is in place. By holding the invalidation moment apart from both existence and succession, the prime makes each of these failures a distinct, nameable condition rather than an undifferentiated muddle. The pattern is substrate-neutral: the same in-force-to-invalidated transition, with its authority, trigger, effective date, and post-invalidation regime, governs a revoked certificate, a recalled drug lot, a repealed statute, a retracted paper, and a senesced cell.
How would you explain it like I'm…
The Card That Stops Working
No Longer In Force
The In-Force-to-Invalidated Flip
Structural Signature¶
the in-force entity — the invalidating authority — the triggering condition — the effective-date semantics — the post-invalidation retention regime — the propagation channel — the invalidation-distinct-from-existence-and-succession invariant
A validity-ending event is present when these roles and relations hold:
- An in-force entity. A previously current, usable, relied-upon thing — a certificate, drug lot, statute, API version, paper, license, contract.
- An authority. Someone or something with standing to issue the invalidation — a regulator, maintainer, court, or clock.
- A triggering condition. What fires the invalidation — a calendar date, evidence event, vote, breach, exhaustion, or supersession.
- Effective-date semantics. When the invalidation takes effect — immediate, scheduled, conditional, or retroactive.
- A post-invalidation retention regime. The prime's distinctive commitment: the entity does not disappear but persists as an identifiable, referenceable historical object marked as no longer current — retain-and-mark, archive, or supersede — so prior reliance stays traceable.
- A propagation channel. How downstream consumers learn of and act on the invalidation, and what propagation latency is tolerable.
- The separation invariant. The load-bearing relation: the moment of invalidation is held apart from the entity's existence and from the moment any successor takes effect. Conflating these produces the canonical pathologies — stale evidence, zombie validity, gap-of-no-cover.
These six independent choices compose so that each conflation (invalidation = destruction, expiry = immediate effect, deprecation = removal) attaches a predictable, nameable failure.
What It Is Not¶
- Not
fading. Fading is gradual loss of relevance or attention with no dateable transition. A validity-ending event is discrete and dateable — a sharp before/after between in-force and invalidated, issued by an authority, not a slow erosion. - Not
versioning. Versioning is the full machinery of managing parallel states of an evolving artifact with successors. A validity-ending event needs no successor — a repealed statute or retracted paper has a validity-ending event with no versioning structure at all. - Not
supersession. Supersession requires a replacement that takes over. The validity-ending event holds invalidation apart from succession; many instances (a recall, a lapse) invalidate with nothing taking the entity's place. - Not
immutability. Immutability is a property of an object that cannot change. A validity-ending event changes the entity's status (in-force → invalidated) while preserving it for the record — the status flips even though the historical object is retained. - Not destruction or deletion. The prime's defining commitment is retain-and-mark: the entity persists as a referenceable historical object so prior reliance stays traceable. Deleting it breaks the audit trail and is the opposite of the pattern.
- Common misclassification. Treating invalidation as deletion, expiry as immediate effect, or deprecation as removal. Each conflation attaches a named pathology (broken traceability, gap-of-no-cover, zombie validity) — catch it by separating the six roles, especially the post-invalidation retention regime from existence.
Broad Use¶
The previously-in-force-entity-officially-invalidated pattern recurs across substrates that dress it in different vocabulary. In law and governance it is sunset clauses, repeal acts, vacaturs, license revocations, and treaty denunciations, each carrying an effective date, an issuing authority, and a record of what was in force when. In pharmaceuticals it is drug recalls, lot invalidations, and expiry dates — which do not destroy existing stock but invalidate it for use and trigger downstream return. In software and security it is API deprecations with announced sunset dates, certificate revocation, token expiration, and end-of-life declarations, where a revoked key continues to exist as bytes but is no longer trusted. In academic publishing it is paper retractions and withdrawn preprints, where the retracted work remains in the literature with a notice — the structural commitment is to mark, not erase. In records management it is record disposition, the structured transition of records out of active status. In finance it is option expiry, contract termination, and insurance lapse, where the expiry of an option is precisely a validity-ending event with an automatic clock-based trigger and a defined post-expiry treatment. And in biology it is cell senescence and enzyme inactivation, where the molecule persists in altered form but no longer plays its prior role. Across all of these the same object appears: a previously in-force entity, an authority empowered to invalidate, a triggering condition, an effective date, and a post-invalidation treatment that preserves the entity for the record while disallowing its prior operational use.
Clarity¶
Naming the validity-ending event separates four questions that domain-specific vocabulary tends to fuse: who has the authority to invalidate, what triggers the invalidation, when it takes effect, and what happens to the entity afterward. Many real failures live in the gaps between these. An API deprecation announced today but effective in twelve months requires clients to monitor the sunset date and migrate, with a structural risk of a wave of failures on the effective date. A drug recall issued today but acted on slowly leaves stale stock circulating. A statutory sunset that passes without renewal can produce a regulatory vacuum if no one tracked the date.
The clarifying force is that this single pattern absorbs a sprawl of domain-specific terms — expiry, revocation, recall, sunset, retraction, deprecation, withdrawal, repeal, retirement, vacatur, disposition, lapse — and exposes each as an instance carrying the same four design questions. It also distinguishes the validity-ending event from its near neighbors. It is not gradual decay, because the transition is discrete with a before-state operationally different from the after-state; a neglected rule fades from attention, a repealed rule has a validity-ending event. It is not the positive process of checking criteria; validity-ending is the negative discrete event that removes an entity from the in-force set. And it is not the full machinery of managing parallel states of an evolving artifact; a deprecation within such machinery is a validity-ending event, but standalone artifacts without successors — a retracted paper, a repealed statute without replacement — have validity-ending events with no versioning structure at all.
Manages Complexity¶
The prime compresses a class of lifecycle questions into a structured choice: what is the validity-ending machinery, who runs it, and what is the post-invalidation regime? This compression turns a tangle of domain-specific vocabulary into instances of a single substrate-independent pattern, each exposing the same four design questions, so a practitioner who has reasoned through one invalidation regime can reason through any other by re-asking the same four.
The pattern also surfaces a class of interaction failures that are invisible without the abstraction. A certificate revocation that fires before all clients have refreshed their revocation lists produces the same structural failure — action on stale validity — as a recalled drug still on shelves or a vacated regulation still being enforced by inattentive officials. Recognizing these as instances of one pattern makes the propagation-latency problem legible across domains: the gap between an invalidation's effective date and the moment all downstream consumers actually learn of and act on it is a single structural risk, not a set of unrelated operational mishaps. The deeper complexity gain is that the prime separates the six independent choices — in-force entity, authority, trigger, effective-date semantics, post-invalidation regime, and propagation channel — so that each can be designed and audited on its own, and so that the characteristic pathology of each conflation (invalidation equals destruction, expiry equals immediate effect, deprecation equals removal) becomes predictable rather than surprising.
Abstract Reasoning¶
Reasoning with the prime proceeds through a fixed sequence: identify the in-force entity; name the invalidation authority and its process; specify the triggering condition; choose the effective-date semantics — immediate, scheduled, conditional, or retroactive; define the post-invalidation regime — retain-and-mark, archive, destroy, or supersede; and design propagation, including how downstream consumers learn of and act on the invalidation and what propagation latency is tolerable.
The pattern's bite is that each of these choices is independent and has distinct failure modes. Conflating any two — treating invalidation as destruction, expiry as immediate effect, recall as silent withdrawal, deprecation as removal — produces a known class of operational pathology. This is what makes the prime a reasoning instrument rather than a checklist: it does not merely enumerate the choices, it asserts their independence and attaches a characteristic failure to each conflation, so that an analyst can predict from a system's design which pathology it is exposed to. A system that fixes the authority and trigger but leaves the effective-date semantics implicit is exposed to the gap-of-no-cover failure; a system that fixes everything but propagation is exposed to stale-validity action; a system that treats invalidation as deletion is exposed to broken traceability of prior reliance. The reasoning transfers because it is stated over the six roles, none of which mentions a particular substrate.
Knowledge Transfer¶
The role mappings make the transfer concrete. The in-force entity maps across certificate, drug lot, statute, API version, paper, license, key, and contract; the authority across certifying body, regulator, legislature, maintainer, journal, court, and issuer; the triggering condition across expiry date, vote, breach detection, sunset clause, retraction notice, and supersession; the effective date across revocation timestamp, repeal effective date, recall date, and deprecation sunset; and the post-invalidation regime across revocation-list entry, repealed-in-archive, retracted-with-notice, and deprecated-but-present. A security engineer reasoning about certificate-revocation latency is doing the same structural work as a regulatory lawyer reasoning about the gap between repeal and effective date, or a pharmacist reasoning about how fast a recall propagates to bedside medication carts.
What makes this more than analogy is that the structural roles are identical and only the substrate, authorities, and propagation channels differ. A reasoner who has internalized the prime in one domain reads a new domain by instantiating the same six roles, and carries with them both the design discipline — separate the moment of invalidation from existence and from succession — and the failure catalogue — stale evidence, zombie validity, gap-of-no-cover, and propagation latency. The prime's strongest single contribution is the post-invalidation retention requirement, which is what distinguishes it from halting, fading, and versioning: the entity persists for the record, remains referenceable, and continues to explain prior reliance. Because that requirement is substrate-neutral, the transfer reaches from administrative and legal substrates — where the authority role is natural — out to biology, where cell senescence and enzyme inactivation instantiate the same discrete in-force-to-invalidated transition even though the "authority" role is stretched, a programmed mechanism rather than an issuing actor. That reach across the administrative-to-biological boundary is the mark of a genuinely structural pattern, and it is what lets a practitioner who learned invalidation discipline in records management apply it, unchanged in skeleton, to security, finance, publishing, and the lifecycle of a cell.
Examples¶
Formal/abstract¶
X.509 certificate revocation is the cleanest worked instance, because it forces every one of the six roles to be designed explicitly and attaches a named pathology to each conflation. The in-force entity is a digital certificate binding a public key to an identity, currently trusted by relying parties. The authority is the issuing Certificate Authority (or a designated revocation authority) with standing to declare the certificate no longer valid. The triggering condition is a key compromise, a mis-issuance, or a subscriber request — an evidence event, not a clock. The effective-date semantics are immediate: revocation takes effect at the timestamp recorded, with no grace period. The post-invalidation retention regime is the prime's distinctive commitment, and it is exactly what revocation gets right — the certificate is not destroyed; it persists as a referenceable object whose serial number is added to a Certificate Revocation List or answered by an OCSP responder, so that a relying party can always determine that this specific certificate was valid until time T and revoked thereafter, keeping prior reliance traceable. The propagation channel is the CRL/OCSP distribution machinery, and the separation invariant is where the formal failure modes live. The gap between the revocation's effective date and the moment a relying party's cached CRL refreshes is propagation latency, and a relying party acting on a not-yet-refreshed list commits the stale-evidence pathology — trusting a key the authority has already invalidated. If a system instead deleted the certificate record rather than tombstoning it, it would commit the broken-traceability failure: a party that relied on the certificate before revocation could no longer prove the certificate had ever been valid. The design discipline the prime names — hold the moment of invalidation apart from the entity's existence (retain-and-mark, never delete) and from any successor's effective moment (re-issuance is a separate event) — is exactly the discipline a correct PKI implements.
Mapped back: Certificate revocation instantiates the in-force entity, the authority, the evidence trigger, immediate effective-date semantics, the retain-and-mark retention regime (CRL/OCSP entry rather than deletion), and the propagation channel — and OCSP-refresh latency producing trust in an already-revoked key is the stale-evidence pathology the separation invariant predicts.
Applied/industry¶
An academic journal retracting a published paper is the applied instance that most sharply exhibits the retain-and-mark commitment, and it diagnoses a real propagation problem. The in-force entity is a published, citable paper currently relied upon by the field. The authority is the journal's editorial board, with standing to issue a retraction; the triggering condition is an evidence event — discovered fabrication, an uncorrectable error, or plagiarism. The effective-date semantics are typically immediate on publication of the retraction notice. The post-invalidation retention regime is the structural heart of the case and is precisely not deletion: the retracted paper remains in the literature, with its DOI still resolving, but carries a prominent retraction notice marking it as no longer valid — the field's explicit choice to mark, not erase, so that the considerable body of prior work that cited it stays diagnosable and the reasons for retraction stay on the record. The propagation channel is the citation-and-indexing ecosystem, and the separation invariant exposes the field's characteristic failure: the gap between the retraction's effective date and the moment downstream consumers learn of it is large and poorly instrumented, so citations to the retracted work continue to accumulate for years — the stale-evidence pathology operating at the scale of a literature, where authors cite an invalidated result because the invalidation never propagated to them. The remedy the prime points to is propagation-channel investment: machine-readable retraction flags that citation managers and databases consume, so that the post-invalidation status travels as fast as the original publication did. The identical six-role skeleton governs a pharmaceutical drug-lot recall — the lot is the in-force entity, the regulator the authority, a contamination finding the trigger, the recall date the effective moment, retain-and-quarantine the retention regime, and the distribution-to-pharmacy network the propagation channel whose latency leaves recalled stock on shelves — so a security engineer reasoning about CRL latency, an editor reasoning about retraction propagation, and a pharmacist reasoning about recall reach are doing one structural job.
Mapped back: Retraction realises the six roles with the retain-and-mark regime as its defining feature — the paper persists and resolves, marked invalid, preserving prior-reliance traceability — and continued citation of retracted work is the stale-evidence-plus-propagation-latency pathology that the validity-ending event predicts wherever invalidation outruns its propagation channel.
Structural Tensions¶
T1 — Temporal: The Discrete-Event Idealisation Versus Gradual Loss of Validity. The prime insists on a sharp, dateable transition between in-force and invalidated, distinguishing itself from gradual decay. But many real losses of validity are gradual — a standard erodes in relevance, evidence accumulates against a result before any formal retraction, a drug's efficacy degrades continuously. The failure mode is forcing a crisp validity-ending event onto a slow erosion, so the entity is treated as fully valid until the stroke of an arbitrary effective date and fully invalid after, mis-modeling a continuum as a step. Diagnostic: ask whether the underlying validity actually changed discretely or whether the discrete event is an administrative stamp on a gradual process; where the latter, the in-force period contained latent invalidity the binary model hides.
T2 — Scopal: Partial Invalidation Breaks the Binary. The prime's in-force/invalidated dichotomy presumes the whole entity flips state, but invalidation is often partial — a statute repealed in part, a paper whose central finding is retracted while its methods stand, a drug recalled for one indication. The failure mode is treating a partially-invalidated entity as wholly dead or wholly live, either discarding still-valid content or relying on invalidated portions. Diagnostic: ask whether the validity-ending event scopes the whole entity or a part; where partial, the retention regime must mark which portions are invalidated, and the binary in-force flag is too coarse to carry the actual status.
T3 — Sign/Direction: Retroactive Effective Dates Invert Prior Reliance. The prime allows retroactive effective-date semantics, but retroactivity collides with the audit-preserving-identity commitment in a sharp way: declaring an entity invalid as of a past date means actions taken in good faith during the now-invalidated interval become retrospectively unwarranted. The failure mode is treating retroactive invalidation as clean while it silently invalidates a whole history of downstream reliance that was reasonable when made. Diagnostic: separate "invalid from now" from "invalid from a past date"; retroactive semantics require a distinct treatment of prior reliance (grandfathering, restitution) that immediate semantics do not, and conflating them mis-handles every action taken in the retroactive window.
T4 — Coupling: Invalidation and Succession Are Held Apart, but Often Must Co-Time. The prime's signature move is separating invalidation from succession, which prevents conflation. But the separation creates the gap-of-no-cover failure it names: where a successor is genuinely required (a security standard, a controlling regulation), invalidating before the successor is in force leaves a coverage hole. The tension is that the very separation the prime celebrates is what opens the gap. The failure mode is invalidating on schedule while the successor lags, per the clean separation, and leaving the system uncovered. Diagnostic: classify whether the entity is standalone (separation is safe) or coverage-critical (invalidation must be coupled to successor readiness); the separation invariant is a default, not a universal, and coverage-critical entities need invalidation gated on succession.
T5 — Measurement: Propagation Latency Is Rarely Instrumented. The prime names propagation latency as a structural risk, but the deeper tension is that most systems cannot measure how far an invalidation has propagated — there is no readout of which downstream consumers still act on the stale entity. The failure mode is declaring an invalidation effective and assuming compliance, while an unmeasured tail of consumers continues relying on it indefinitely (citations to retracted papers, unpatched revoked certificates). Diagnostic: ask whether the propagation channel returns acknowledgment or only broadcasts; an invalidation with no feedback on uptake has an unknown and possibly unbounded stale-reliance tail, and the effective date marks when invalidation began propagating, not when it completed.
T6 — Scopal: Authority Is Strained Where No Issuer Exists. The prime's authority role is natural in administrative substrates but stretched in biological ones (cell senescence, enzyme inactivation) where invalidation is a programmed mechanism with no issuing actor. The tension is that "declared no longer valid" smuggles in an agent that some instances lack, and forcing the authority role onto agentless processes mis-describes them. The failure mode is searching for an authority or a contestable decision where there is only a mechanism, or conversely importing mechanistic inevitability into administrative invalidations that are actually discretionary and appealable. Diagnostic: ask whether the invalidation is issued by an agent with standing (and therefore contestable, reversible, accountable) or triggered by a mechanism (inevitable, unappealable); the intervention space differs entirely, and the authority role means different things in each.
Structural–Framed Character¶
Validity-ending Event sits just on the structural side of the structural–framed spectrum, consistent with its mixed-structural grade — a 0.4 aggregate that puts it nearer the structural pole than the middle, but not at it. The skeleton is genuinely structural: a discrete in-force-to-invalidated transition with six separable roles — entity, authority, trigger, effective-date semantics, post-invalidation retention regime, propagation channel — and a separation invariant that holds invalidation apart from existence and from succession. What keeps it from a clean zero is the administrative tinge the "authority" and "declaration" roles carry.
One diagnostic reads clean structural and anchors the grade below the middle: evaluative weight is zero. A validity-ending event carries no inherent approval or disapproval — a revoked certificate, a recalled lot, a repealed statute, and a senesced cell are the same value-neutral status flip, with no normative load. The other four diagnostics sit at the midpoint, each contributing a mild framed tilt. Vocabulary-travel is mid: "expiry, revocation, recall, sunset, retraction" generalize cleanly, but the unifying language of "authority" and "official declaration" carries an administrative flavor that does not fully strip away. Institutional origin is mid: most canonical instances (law, pharma regulation, PKI, publishing) are administrative, and the "issuing authority" role is most natural there. Human-practice-boundedness is mid: the pattern reaches into biology — cell senescence, enzyme inactivation instantiate the discrete in-force-to-invalidated transition — but those cases stretch the authority role into a programmed mechanism rather than an issuing actor, as the prime's own T6 concedes, so the construct leans toward (without being confined to) human-administrative substrates. Import-versus-recognize is mid: invoking the prime recognizes a real discrete transition but also imports the authority-and-effective-date apparatus. The structural skeleton is real and reaches genuinely across the administrative-biological boundary — which is why the grade lands on the structural side — but the inherited administrative vocabulary holds it a notch in from the pole, exactly as a 0.4 mixed-structural reading records.
Substrate Independence¶
Validity-Ending Event is a highly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. Its domain breadth is broad: discrete invalidation events with an authority, a trigger, an effective date, and a defined post-state recur across law (sunset clauses, repeals, vacaturs, license revocations), pharmaceuticals (recalls, lot invalidations, expiry), software and security (API deprecations, certificate revocation, token expiration), academic publishing (retractions, withdrawn preprints), records management (record disposition), finance (option expiry, contract termination, insurance lapse), and biology (cell senescence, enzyme inactivation). Its structural abstraction is high: the signature — a previously in-force entity, an authority empowered to invalidate, a triggering condition, an effective date, and a post-invalidation treatment that preserves the entity for the record while disallowing prior use — is medium-neutral, with the biological instances (a molecule persisting in altered form but no longer playing its role) showing the pattern runs beyond administrative substrates. Transfer evidence is solid: the mark-don't-erase commitment and the effective-date discipline carry identically across law, software, publishing, and finance. What holds the composite a notch below five is a mild lean toward administrative and institutional substrates, where authorities and effective dates are most natural, even though the biological cases demonstrate genuine reach past that band.
- Composite substrate independence — 4 / 5
- Domain breadth — 4 / 5
- Structural abstraction — 4 / 5
- Transfer evidence — 4 / 5
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
-
Validity-ending Event is a kind of, typical State and State Transition
A discrete, dateable in-force -> invalidated status transition (with authority, trigger, effective-date, retention regime, propagation) — a specialization of state_and_state_transition where the prior state is RETAINED for the record, not destroyed.
Path to root: Validity-ending Event → State and State Transition
Neighborhood in Abstraction Space¶
Validity-ending Event sits in a sparse region of abstraction space (92nd percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.
Family — Identity, Authority & Trust Binding (11 primes)
Nearest neighbors
- Latent Realizable Capacity — 0.69
- Identity-Preserving Modification — 0.68
- Retired Term — 0.68
- Conservation Event — 0.67
- Threshold-Triggered Rule Activation — 0.67
Computed from structural-signature embeddings · 2026-06-14
Not to Be Confused With¶
The embedding-nearest confusion is with fading, and the two are near-opposites on the single dimension of discreteness. Fading is the gradual, often unannounced loss of an entity's relevance, force, or salience — a standard slowly becomes outdated, a norm quietly stops being enforced, a memory dims. There is no dateable moment, no issuing authority, and no sharp before/after; the entity slides from in-force toward irrelevant along a continuum. A validity-ending event is precisely the discrete, authority-issued, dateable transition that fading lacks: at the effective date the entity flips from in-force to invalidated in one step, and that step is on the record. The distinction is load-bearing because the two demand entirely different handling. A faded entity has no clean point at which prior reliance becomes unwarranted, so the question "was acting on it reasonable at time T?" has a fuzzy answer; a validity-ended entity has a bright line that makes that question crisp. The prime's own T1 marks exactly the danger zone — forcing a discrete validity-ending event onto what is really a gradual fade, stamping an arbitrary effective date on a continuous erosion and thereby mis-modeling latent invalidity in the in-force period as full validity. A practitioner who conflates them either treats a genuine fade as if it had a clean invalidation date (and over-trusts the entity until that arbitrary date) or treats a genuine validity-ending event as a fade (and never establishes the bright line that makes prior reliance auditable).
A second genuine confusion is with versioning, and here the distinction turns on whether a successor is required. Versioning is the full machinery of managing an evolving artifact through a sequence of states, where each version is typically superseded by a next, and the apparatus tracks parallel and historical states with their relationships. A validity-ending event, by contrast, needs no successor at all: a repealed statute with no replacement, a retracted paper, an expired option, a lapsed license each undergo a clean in-force-to-invalidated transition with nothing taking their place. The prime's signature move is precisely to separate invalidation from succession — to hold the moment an entity ceases to be in-force apart from the moment any replacement takes effect — which versioning, by bundling them, does not do. The distinction is consequential because it isolates the gap-of-no-cover failure (the prime's T4): where a successor genuinely is required, invalidating before it is in force opens a coverage hole, and only by treating invalidation and succession as independent events can that gap be seen and gated. A deprecation within a versioning scheme is a validity-ending event, but the prime insists the invalidation has its own authority, trigger, effective date, and retention regime regardless of whether a successor exists — so reasoning about it as "just the old version" misses the standalone cases entirely and hides the succession gap in the cases that have one.
A third confusion worth drawing is with supersession. Supersession is the specific relation in which a new entity replaces and displaces an old one — the new standard supersedes the old, the new edition supersedes the prior. It necessarily involves two entities and a takeover. A validity-ending event involves only one entity and its status change, and the prime deliberately decouples it from any replacement. The relationship is that supersession is one possible trigger for a validity-ending event (an entity may be invalidated because it was superseded), but the validity-ending event also fires from triggers that involve no successor whatsoever — exhaustion, breach, a clock, a retraction. Conflating them imports a replacement where none exists, leading an analyst to look for the "new version" of a retracted paper or a repealed law that simply has none, and to miss that the retention-and-mark regime (keep the invalidated entity referenceable) applies whether or not anything succeeds it.
For a practitioner these distinctions determine whether the failure catalogue even applies. Mistake a validity-ending event for fading and you lose the bright line that makes prior reliance auditable; mistake it for versioning and you bundle invalidation with a succession that may not exist, hiding the coverage gap; mistake it for supersession and you hunt for a replacement where the entity was simply invalidated. The prime earns its keep by isolating the discrete, authority-issued, successor-independent invalidation with its retain-and-mark commitment — the structure that keeps prior reliance traceable no matter what does or does not come next.
Solution Archetypes¶
No catalogued solution archetypes reference this prime yet.