Markets/en/Portal:Model/Amendments-and-Addenda:Model
馃挕 In simple words: When people make a deal, sometimes they need to change it. An amendment fixes something that's already there, like a date or amount. An addendum adds something brand new without changing what's already written. Both need everyone to agree and both get saved so you can see what changed.
馃幆 In 20 seconds (scientific summary): We are heading towards contract models that treat agreements as living documents rather than static instruments. This framework proposes amendments and addenda as dual mechanisms enabling iterative adaptation: amendments modify existing terms while preserving audit trails; addenda layer new obligations without destabilizing original clauses. The hypothesis suggests this approach reduces renegotiation friction and supports continuous governance evolution in cooperative frameworks.
Section 3 of the market portal model. Neutral example content: replace with market-specific templates when instantiating. Draft material, intended to be validated by lawyers.
Amendments and addenda
Two ways a contract changes
A WikiDeal contract is a living object. It changes in two clean ways:
- An amendment modifies something that already exists in the contract: a date, an amount, a duration, a clause text. The old version is archived, the new version applies.
- An addendum (avenant) adds something new without touching the existing clauses: a new guarantor, a new annex, an extra obligation both parties want.
Both require the written agreement of all parties, both are versioned, and the original terms are archived, never erased. Amendments are not only for fixing problems: they are the normal mechanism for renewal and continuous adaptation, so that a deal evolves instead of being torn up and renegotiated from scratch.
Amendment template
Amends: [base contract reference] Subject: [what changes, in one line] Original terms (clause [n]): [quote the current text or value] Amended terms: [the new text or value] Reason: [why the parties change this] Financial impact: [none / recalculated amounts] Everything else unchanged. All other terms of the base contract remain in force. Signatures: [Party A] 路 date. [Party B] 路 date.
- Why it makes sense: quoting the original next to the new text makes the change auditable at a glance.
- Advantages: one subject per amendment keeps the history readable.
- Risks: bundling several changes into one amendment hides trade-offs; a party may accept a package they would have refused piece by piece.
- Limits: an amendment binds only from its signature; it does not rewrite the past.
Addendum template
Supplements: [base contract reference] Subject: [what is added, in one line] New element: [full text of the added clause or annex] Relation to existing clauses: this addendum adds to the agreement and modifies none of its existing clauses. Signatures: [Party A] 路 date. [Party B] 路 date. [New third party, if any] 路 date.
- Why it makes sense: additions deserve their own document; mixing them into amendments blurs what changed.
- Advantages: a third party who joins (a guarantor, for example) signs only the addendum that concerns them.
- Risks: an addendum that silently contradicts an existing clause creates two truths; the relation line above exists to prevent this.
- Limits: if the addition actually requires changing an existing clause, use an amendment instead.
When to use which
| Situation | Instrument |
|---|---|
| Extend the duration, change an amount or a date | Amendment |
| Renew a contract for a new period | Amendment |
| Add a guarantor, a pledge, a new annex | Addendum |
| Add an extra obligation both parties want | Addendum |
| Change AND add at the same time | One amendment, then one addendum, signed together |
See also
- Contract model, clause S8
- Follow-up messages: how to propose a change without drama
- Back to the portal model