Type: Node / Governed Displacement
Working Definition: Supersession is the governed displacement of one rule, commitment, status, interpretation, authority, or institutional artifact by another — a complete replacement in which the prior instrument ceases to govern going forward, its authority transferred to the superseding instrument, with the prior instrument archived rather than erased.
Function in the Grammar: Supersession is total governed change. Where amendment modifies part of an existing instrument while preserving its continuity, supersession displaces it entirely: the old instrument no longer governs, and a new instrument takes its place. This difference matters for the accountability chain. An amended rule is the same rule with changed text; its history is the prior versions. A superseded rule is a prior instrument with a known cessation date; the superseding rule is a new instrument with its own history. Supersession is the mechanism for fundamental institutional change that exceeds what amendment can accomplish — replacing a constitution, retiring a commitment that has been entirely overtaken by events, or displacing one governing framework with another.
The anti-silent-overriding rule applies with particular force to supersession: a later institutional artifact must not implicitly nullify a prior one without an explicit supersession relation. Silent overriding — where a new rule governs as if the prior rule did not exist, without formally acknowledging that the prior rule has been displaced — is a form of institutional amnesia that makes the accountability chain unreadable. The institution's ledger must show that the old instrument was superseded, when, by what, under what authority, and why.
Formal Grammar Representation
Supersession(s, prior: T, new: T′, institution: I) iff
s is produced through I's recognized procedure for supersession
s specifies: Prior(T), Superseding(T′), EffectiveDate, AuthoritySource, Reason
s is authorized: the agent(s) producing s hold authority to supersede T
T ceases to govern going forward from EffectiveDate
T is archived: T remains in Ledger(I) with status: superseded_by(T′)
T′ becomes the governing instrument from EffectiveDate
Anti-silent-overriding:
For all cases where T′ would implicitly displace T:
s must include an explicit SupersedesLink(s, T) in the ledger
Acting under T′ without recording s is an institutional violation
The ledger must show the displacement chain, not merely the current state
Anti-retroactivity (same as Amendment):
Acts performed under T before EffectiveDate retain their validity from that moment
T′ does not govern acts performed before its effective date
Exception: retroactive supersession is valid only if explicitly authorized
and no party's vested rights under T are prejudiced without consent
Supersession(s) is complete iff
T is archived with status: superseded_by(T′, at: EffectiveDate)
T′ is enacted and in force
All dependent instruments have been reviewed for compatibility with T′
A consolidation event confirms the transition in the ledger
Semantic Constraints
The formal expression Supersession(s, T, T′, I) is well-formed when s specifies the prior and superseding instruments, the effective date, the authority, and the reason, and when T is archived rather than erased. Whether s functions as legitimate supersession — whether the institution genuinely treats T′ as governing going forward, whether the history of T is preserved and traceable, whether dependent instruments were reviewed and updated — requires institutional discipline the form cannot ensure. The most common failure mode is treating supersession as if it were erasure: the new instrument governs, the old is forgotten, and no one can reconstruct the transition.
Formal Pattern
Supersession(s, prior: T, new: T′, institution: I)
SUPERSEDES(T′, T, at: EffectiveDate, via: s)
ARCHIVES(I, T, status: superseded_by(T′))
ENACTS(I, T′, from: EffectiveDate)
PRESERVES(s, Validity_of: Acts(α) performed under T before EffectiveDate)
REQUIRES(s, DependencyReview: instruments depending on T)
RECORDS(I, s, Ledger(L), predecessor: T)
Core Relations
| Relation | Notes |
|---|---|
| Amendment contrasts | Amendment modifies part of T, which survives in amended form (T_amended). Supersession displaces T entirely; T ceases to govern and T′ is a new instrument. The distinction matters for continuity: amendment preserves a single lineage; supersession creates two — one ending, one beginning. |
| Constitution governs | Supersession of a constitution requires the constitution's own procedure for supersession, if one exists — or a recognized founding procedure if the constitution is being replaced by a new one. Supersession without procedure is a coup, not a governed transition. |
| Ledger records | Every supersession must create an explicit link in the ledger: this instrument was superseded by this instrument, at this date, under this authority. A ledger that shows only T′ without showing T's cessation has hidden the transition. |
| Continuity requires | The accountability chain must remain traceable through supersession events. Acts performed before the supersession are governed by the prior instrument; acts after by the superseding one. The ledger must make this reconstruction possible. |
| Authority enables | Supersession requires authority to displace — usually a higher authority threshold than amendment, since the change is more complete. The authority must be traceable to the institution's constitution or to a recognized founding procedure. |
| Commitment affects | Supersession may affect active commitments created under the prior instrument. Supersession does not automatically discharge existing commitments; those require explicit treatment — fulfillment, waiver, or formal supersession of the commitment itself. |
| Dependency review requires | When T is superseded, all instruments that depended on T must be reviewed. Bridge rules that cited T, commitments that referenced T, recognitions granted under T — each must be assessed for compatibility with T′. Omitting this review creates governance gaps. |
Typical Questions
- Has this instrument been superseded, and if so, by what and when?
- Does the ledger show an explicit supersession link, or was the displacement silent?
- What happened to acts and commitments created under the superseded instrument?
- Have dependent instruments been reviewed for compatibility with the superseding one?
- Was the supersession produced through the institution's recognized procedure?
- Is the prior instrument archived, or has it been erased?
Examples
| Domain | Prior instrument | Superseding instrument | What the transition requires |
|---|---|---|---|
| Constitutional law | A national constitution | A new constitution adopted after a constitutional convention | Explicit article specifying transition; continuity provisions for prior acts; archiving |
| Corporate governance | Original bylaws | Completely revised and restated bylaws | Board/shareholder adoption; notice to all parties; treatment of prior commitments |
| Science / publishing | An old editorial policy | A new editorial policy that governs the same matters in a different framework | Announcement; treatment of submissions already under review; archiving prior policy |
| Contract law | A master service agreement | A new master service agreement between the same parties | Explicit supersession clause; treatment of prior work; acknowledgment of transition |
| Digital governance | A bridge rule | A new bridge rule governing the same action type | Suspension of prior rule; dependency review; effective date; ledger record |
| Employment law | An employment handbook | A new handbook replacing prior policies | Notice; transition provisions; treatment of prior commitments to employees |
| Ordinary life | An agreement between partners | A new agreement that replaces the old entirely | Explicit acknowledgment of the prior agreement and its replacement |
Distinctions
Supersession ≠ Amendment. Amendment modifies part of an existing instrument; the instrument survives in amended form with the same identity. Supersession displaces the instrument entirely; the prior instrument ceases to govern. A constitution that has been amended five times is one constitution with five amendments in its history. A constitution that has been superseded is a prior instrument, archived, with a successor that is a different instrument.
Supersession ≠ Repeal. Repeal removes an instrument without replacing it — the prior rule simply no longer applies, and the gap is left unfilled. Supersession displaces one instrument with another, so the domain remains governed. Repeal creates a vacancy; supersession creates a transition. Many repeal-and-replace operations are properly understood as supersession.
Supersession ≠ Revision. Revision is an informal or editorial change — updating language, correcting errors, improving clarity — that does not alter the substantive governance. Revision does not require the supersession procedure because it does not displace the instrument. Treating a substantive supersession as a "revision" to avoid the procedure is institutional bad faith.
Supersession ≠ Waiver. Waiver releases a specific obligation in a specific instance without changing the underlying instrument. Supersession displaces the instrument entirely for future cases. A series of waivers does not constitute supersession; the instrument remains in force unless formally superseded.
Supersession ≠ Breach. Breach is unauthorized non-compliance. Supersession is authorized displacement. An actor who ignores an instrument as if it had been superseded, without the supersession procedure having been followed, is in breach — not exercising a supersession.
Supersession ≠ Drift. Drift is unacknowledged practice divergence from a governing instrument. Supersession is formal, recorded, authorized displacement. When drift hardens into a de facto new framework that is treated as governing, it may look like supersession but lacks its accountability properties: there is no explicit record of the transition, no preserved history of the prior instrument's cessation, and no authority chain for the new framework.
Common Failure Modes
| Mode | Description |
|---|---|
| Silent overriding | A new instrument begins to govern without an explicit record that the prior instrument has been superseded. The ledger shows two conflicting instruments; future actors cannot determine which governs. Where to look: domains where both an old and a new instrument appear to govern the same matter, with no supersession link between them. |
| Supersession without dependency review | An instrument is superseded without reviewing the instruments that depended on it. Bridge rules, commitments, and recognitions created under the prior instrument may now reference a superseded authority. Where to look: post-supersession periods where prior-instrument-dependent artifacts are still being invoked without assessment. |
| Supersession by practice | Actors begin treating a new framework as governing without formal supersession — because the prior framework is inconvenient, outdated, or simply ignored. The institution drifts into de facto supersession that lacks the accountability properties of governed supersession. Where to look: governance domains where the formal instrument and the actual practice have diverged completely. |
| Erasure masquerading as supersession | The institution supersedes an instrument but deletes or destroys the prior instrument rather than archiving it. Future actors cannot reconstruct what was governed under the prior instrument or assess whether the transition was legitimate. Where to look: supersession events after which the prior instrument cannot be located. |
| Retroactive supersession | A superseding instrument is applied to acts performed before its effective date — either treating those acts as governed by T′ when they were governed by T, or retroactively invalidating prior-authorized acts. Where to look: supersession events that are cited to challenge acts predating the supersession. |
Minimum Viable Test Case
Prior instrument (T): CLAUDE.md v1 — model_assistant may draft posts and encyclopedia entries
New instrument (T′): CLAUDE.md v2 — model_assistant may also draft wiki architecture pages
This is an Amendment (not Supersession) if:
T survives in amended form
The specific clause is modified within the same document
History: CLAUDE.md v1 → CLAUDE.md v2 (same document, updated)
This becomes Supersession if:
The entire collaboration protocol is replaced with a different framework
T′ is a new protocol document, not an updated version of T
T (CLAUDE.md v1) is archived: status = superseded_by(CLAUDE.md v2, at: date)
T′ governs from the effective date; T governs prior sessions historically
Supersession(s):
Prior(T) = CLAUDE.md v1
Superseding(T′) = CLAUDE.md v2
EffectiveDate = [date of adoption]
AuthoritySource = human_author decision
Reason = new project scope requiring expanded assistant capabilities
RECORDS(AlwaysBecoming, s, editorial log)
ARCHIVES(AlwaysBecoming, CLAUDE.md v1, status: superseded_by(v2))
Anti-silent-overriding check:
If model_assistant begins operating under v2 scope without a recorded supersession event
→ silent overriding violation
→ the ledger does not show when or why the prior constraints ceased to apply
Cross-References
Required
- Constitution — constitutions may be superseded; supersession requires recognized procedure
- Authority — supersession requires specific constitutional authority, typically higher threshold than amendment
- Ledger — every supersession requires an explicit link: prior instrument archived, successor enacted
Consequential
- Continuity — supersession events must be explicitly linked in the ledger for continuity to survive
- Commitment — active commitments under a superseded instrument require explicit treatment; supersession does not automatically discharge them
- Recognition — recognitions granted under a superseded instrument may need review for continued validity
- Repair — when supersession is botched (silent overriding, dependency omission), repair must address the gap
Evidential