Type: Node / Governed Change
Working Definition: Amendment is the governed alteration of an existing constitution, rule, commitment, status, or institutional structure through the procedure the institution itself has specified — the legitimate mechanism by which an institution changes without breaking.
Function in the Grammar: Amendment is how institutions remain answerable to both their past and their present. Without amendment, institutions face a false choice: maintain their original form as circumstances change (brittleness) or drift from their original form without acknowledgment (dishonesty). Amendment is the third path: change that is acknowledged, authorized, procedurally correct, and recorded — so that the institution's history remains traceable even as its rules evolve. The amendment procedure is not bureaucratic overhead; it is the mechanism that makes governed change possible and distinguishes it from mere drift.
The anti-retroactivity principle governs all amendments unless explicitly and validly overridden: an amendment changes future authority. It does not reach back and reinterpret the past. Acts that were legitimate under the prior rule remain legitimate from the moment they were performed. Acts that were illegitimate do not become legitimate because the rule has changed. The institution's history is anchored to the rules in effect at the time of each act; only the future bends when an amendment is adopted.
Formal Grammar Representation
Amendment(a, target: T, institution: I) iff
T is an existing rule, constitutional provision, commitment, or institutional structure in I
a is produced through I's recognized AmendmentProcedure(K, I)
a is authorized: the agent(s) performing a hold the authority to amend T
a specifies: PriorText(T), AmendedText(T′), EffectiveDate, ReasonsIfRequired
a is recorded in Ledger(I) with predecessor reference to T
a is prospective: a changes authority from EffectiveDate forward
Anti-retroactivity:
For all Acts(α) performed before EffectiveDate(a) under T:
Validity(α) is assessed under T, not T′
a does not alter Validity(α) retrospectively
Exception: retroactive amendment is valid iff
I's constitution expressly permits retroactive amendment for this class
the retroactive amendment follows the procedure for retroactive change
no party whose rights vested under T is prejudiced without consent or compensation
Amendment(a) is complete iff
a passes the threshold specified in AmendmentProcedure(K, I)
a is recorded with a link to T (predecessor_authority_id)
a is announced through the notice procedure I requires
a's EffectiveDate has passed
Semantic Constraints
The formal expression Amendment(a, T, I) is well-formed when a was produced through the institution's recognized amendment procedure, is authorized, specifies the change precisely, and is recorded with a predecessor reference. Whether an amendment functions as legitimate governed change — whether the institution and its community actually treat T′ as the governing rule, whether prior acts under T are not retroactively invalidated, whether the amendment procedure was genuinely open and not captured — requires institutional integrity the form cannot ensure. The most insidious failure is a formally valid amendment adopted by a procedure that was, in practice, controlled by the parties the amendment benefits.
Formal Pattern
Amendment(a, target: T, new: T′, institution: I)
AMENDS(Amendment(a), Rule(T), producing: Rule(T′))
AUTHORIZES(Institution(I), Agent(s), to: AMEND(T))
RECORDS(I, Amendment(a), Ledger(L), predecessor: T)
TAKES_EFFECT(Amendment(a), at: EffectiveDate)
PRESERVES(Amendment(a), Validity_of: Acts(α) performed under T before EffectiveDate)
SUPERSEDES(T′, T) — T′ governs going forward; T governs historical acts
Core Relations
| Relation | Notes |
|---|---|
| Constitution governs | Constitutions may be amended, but only through their own amendment procedures. An amendment that bypasses the procedure is a breach, not an amendment. The amendment procedure is the constitution's protection against capture. |
| Institution enables | Institutions create and maintain the amendment procedures through which they can govern their own change. An institution without an amendment procedure cannot adapt without violating its own form. |
| Authority requires | Amendment requires specific authority — usually a higher threshold than ordinary acts. The authority to amend is a special authority that the constitution grants only under specified conditions. |
| Continuity preserves | Amendment is the mechanism that allows continuity to survive change. An amended institution remains accountable to its amended history; the amendment itself must be traceable in the ledger. |
| Ledger records | In governed institutions, amendments should be recorded with a predecessor reference. The ledger should show not just the current state of the rule but its entire amendment history where accountability is required. |
| Recognition activates | An amendment takes effect when it passes through the institution's recognition procedure — when the authorized body recognizes it as duly adopted. |
| Standing requires | Proposing and adopting amendments requires standing — agents without recognized status in the relevant amendment procedure cannot participate in the amendment process. |
| Commitment affects | Amendments may change the rules governing existing commitments. They may not retroactively discharge existing commitments except through waiver or supersession with consent. |
Typical Questions
- Does this institution have an amendment procedure, and is it accessible?
- Was this amendment adopted through the institution's recognized procedure?
- Who held the authority to propose and adopt this amendment?
- When does this amendment take effect, and what is its scope?
- Does this amendment reach backward, and if so, is that retroactive effect authorized?
- What is the ledger record of this amendment, and does it link to the prior rule it replaces?
- Has the amendment procedure been captured by parties who benefit from the change?
Examples
| Domain | What was amended | Procedure | Anti-retroactivity |
|---|---|---|---|
| Constitutional law | A constitutional provision | Supermajority in legislature + state ratification | Prior laws enacted under the old provision remain valid until themselves amended or repealed |
| Corporate governance | The company's bylaws | Board resolution or shareholder vote, depending on the provision | Prior transactions governed by old bylaws are valid; new bylaws govern going forward |
| Science / publishing | A journal's editorial standards | Editorial board vote | Papers already accepted under old standards may be published; new submissions governed by new standards |
| Contract law | A contract's payment terms | Signed amendment agreed by all parties | Prior payments are settled under old terms; future payments governed by new terms |
| Digital governance | A bridge rule's scope | Governed review event producing a new rule version | Receipts generated under the old rule version remain valid; future acts governed by new version |
| Religious institutions | A community's membership criteria | Congregational vote or council decision | Current members retain membership; future applicants governed by new criteria |
| Ordinary life | A household agreement | Mutual acknowledgment and agreement between parties | Prior obligations discharged under old agreement; future obligations under new one |
Distinctions
Amendment ≠ Revision. A revision is an informal or editorial change — correcting an error, updating language, clarifying meaning — that does not alter the substance of the rule. A revision may not require the amendment procedure; an amendment always does. The distinction matters because it determines which procedure applies. Calling a substantive change a "revision" to avoid the amendment procedure is a common form of institutional bad faith.
Amendment ≠ Supersession. Supersession replaces one instrument with another: the old instrument is rendered void and the new instrument governs entirely. Amendment modifies part of an existing instrument, leaving the rest intact. Supersession is wholesale; amendment is targeted. An institution that supersedes its constitution adopts a new one; an institution that amends its constitution preserves continuity with its prior constitutional history.
Amendment ≠ Waiver. Waiver is the relinquishment of a specific claim or obligation in a specific instance, without changing the underlying rule. Amendment changes the rule for future cases. Waiving a commitment does not amend the rule that generated it; amending the rule does not discharge existing commitments.
Amendment ≠ Breach. Breach is an unauthorized failure to comply. Amendment is an authorized change to the rule. An act that violates a rule is a breach; an act that changes the rule through proper procedure is an amendment. The two are systematically confused when parties characterize their breach as if they were exercising an amendment authority they do not hold.
Amendment ≠ Drift. Drift is the unacknowledged change in institutional practice — when what the institution actually does diverges from what its rules specify, without anyone formally acknowledging or authorizing the change. Amendment is the legitimate path that drift is not. An institution that drifts from its rules has not amended them; it has developed an informal practice that competes with the formal rule.
Amendment ≠ Replacement. Replacement substitutes one institution, constitution, or instrument for another without continuity. Amendment preserves continuity — the amended institution is the same institution with a changed rule. Replacement severs continuity. Calling a replacement an amendment, or vice versa, mischaracterizes the relationship between the prior and current governance structure.
Common Failure Modes
| Mode | Description |
|---|---|
| Procedure bypass | A rule or constitutional provision is changed without following the amendment procedure — through informal agreement, executive fiat, or gradual practice. The change is real but illegitimate. Where to look: rule changes that cannot be traced to a formal amendment event in the ledger. |
| Retroactive reach | An amendment is applied backward, recharacterizing past acts as valid or invalid under the new rule. Unless the constitution specifically permits retroactive amendment for this class, retroactive reach is a violation of the anti-retroactivity principle. Where to look: amendments that are cited to justify actions taken before their effective date. |
| Amendment procedure capture | The amendment procedure is controlled by those who benefit from the change. Formally valid amendments are adopted by a process that was not genuinely open. Where to look: amendment procedures where the proposing party also controls the adoption threshold, or where procedural requirements were waived for this amendment. |
| Amendment without record | An amendment occurs — a rule genuinely changes — but the change is not recorded in the ledger with a predecessor reference. Future actors operate under the new rule without knowing it was changed or what it replaced. Where to look: rules that differ from their original version without a traceable amendment in the ledger. |
| Cascade omission | An amendment changes one provision without assessing its effect on provisions that depend on it. Dependent rules are not updated; the institution now contains internal inconsistencies that were not acknowledged at the time of amendment. Where to look: amendments that changed a foundational provision without triggering a dependency review. |
Minimum Viable Test Case
Target: CLAUDE.md, clause granting model_assistant drafting authority
Prior rule (T): "model_assistant may draft posts and encyclopedia entries"
Proposed amendment: "model_assistant may also draft principles and wiki architecture pages"
Amendment procedure (AlwaysBecoming):
Proposer: human_author (has standing to propose)
Required threshold: human_author decision (no other parties required)
Record requirement: updated CLAUDE.md + notation in editorial log
Notice: no advance notice required (sole authority holder)
Amendment(a):
Authorized: yes — human_author holds amendment authority
Procedure followed: human_author decides, records in CLAUDE.md
Effective date: date of recording
Predecessor reference: prior clause text + git commit
Anti-retroactivity:
Drafts of posts and encyclopedia entries produced before amendment: governed by T (valid)
Drafts of wiki pages before amendment: outside T (not covered by model's authority)
Drafts of wiki pages after amendment: governed by T′ (authorized)
Invalid amendment attempt:
model_assistant proposes expanding its own authority by editing CLAUDE.md
→ model_assistant lacks standing to propose amendments to its own authority constraints
→ the edit would be ultra vires, not an amendment
Cross-References
Required
- Constitution — amendments change constitutions; constitutions specify amendment procedures
- Institution — the body within which amendments occur; institutions require amendment procedures to adapt legitimately
- Authority — amendment requires specific, constitutionally granted authority
- Standing — proposing and adopting amendments requires recognized standing
Consequential
- Continuity — amendment is the mechanism that preserves continuity through change
- Ledger — amendments must be recorded with predecessor references
- Recognition — an amendment takes effect through the institution's recognition of its adoption
- Commitment — amendments may change rules governing commitments; they may not retroactively discharge existing commitments
Evidential
- Breach — bypass of amendment procedure may itself constitute breach; amendment and breach are distinct responses to the same pressure to change
- Supersession — wholesale replacement vs. targeted modification; the stronger form of amendment
- Waiver — non-enforcement in a specific instance vs. change to the underlying rule