If-Then Revision Contract¶
Revision protocol — instantiates Commitment Lifecycle Governance
Agrees in advance, in writing, that a specified trigger of evidence will produce a specified change to the commitment — so a live promise adapts by pre-set rule instead of by silent breach or fresh negotiation.
An If-Then Revision Contract builds the change path into a commitment at the moment it is made: a concise written rule of the form if this evidence appears, then the commitment changes in this way. Its distinguishing move among its siblings is that the revision is pre-agreed and conditional — both the trigger and the response are fixed before the triggering evidence arrives, so when circumstances shift the commitment updates by rule rather than by anyone's discretion in the moment. That is what separates it from a Renegotiation Notice Protocol, which opens fresh bargaining when change is needed, and from a Release or Exit rule, which ends the commitment. The if-then contract keeps the commitment alive and honoured — just flexed along a track everyone consented to up front.
Example¶
Rather than promise a fixed path for interest rates, a central bank issues state-contingent forward guidance: the policy rate will remain at its floor until inflation is projected to run above ≈2% on a sustained basis. The trigger is an evidence condition; the response — liftoff — is stated in advance. When the incoming data crosses the threshold and rates begin to rise, the bank is not accused of breaking its word, because the revision was part of the promise from the start. Markets can plan against the rule — pricing in the conditions under which the commitment changes — instead of against a fixed forecast that would have had to be publicly abandoned. The commitment adapts to evidence while its credibility survives the change, precisely because the change was pre-wired.
How it works¶
At formation, the drafter writes the revision rule itself: a defined evidence trigger ("if X is observed or measured") bound to a defined response ("then the commitment changes to Y"), so the update is a pre-consented move rather than a renegotiation or a breach. The rule specifies the observation that counts as the trigger, the change it produces, and often the window within which that change may or must be applied. Because trigger and response are set ex ante, no one has to re-open the agreement — or quietly ignore it — when conditions move. It adapts the commitment; it does not create or end one.
Tuning parameters¶
- Trigger specificity — a sharply measurable condition ("inflation above X for two consecutive quarters") versus a judgement-laden one ("if conditions warrant"). Sharp triggers fire predictably and resist gaming; vague ones preserve discretion but reintroduce the ambiguity the contract exists to remove.
- Response definiteness — whether the "then" is fully specified (a formula, a new value) or only a direction ("revisit"). Full specification removes fresh negotiation; a bare direction leaves room but can collapse back into ordinary renegotiation.
- Symmetry — whether the rule fires in both directions (tighten and loosen) or only one. Two-sided rules are fairer and harder to invoke selectively when only one side is convenient.
- Revision window — the period in which a triggered change may or must take effect, and whether it applies automatically or needs a confirming step. Automatic is fast and credible; a confirm step adds a guard against a false trigger.
- Evidence source — who measures the trigger, and how independently. A promisor-controlled trigger invites gaming; an external or shared data source keeps the rule honest.
When it helps, and when it misleads¶
Its strength is that it lets a commitment stay credible through change. Because the update was agreed in advance, adapting to new evidence is honouring the promise rather than breaking it — which heads off both the silent breach (changing without saying so) and the coercive rigidity of a commitment that cannot bend when the world does. It converts "the situation changed, so the deal's off" into "the situation changed, so the pre-agreed clause fired."
Its failure modes cluster around the trigger. A trigger set so it never realistically fires makes the promised flexibility vacuous, and a promisor-controlled trigger can be quietly gamed. The classic misuse is writing the if-then after the evidence is already in — dressing up a change decided on other grounds as a rule-following update, the "run backwards" move applied to revision. The discipline that keeps it honest is to fix the trigger and the response before the evidence arrives, tie the trigger to an independently observable measure, and make the rule two-sided so it cannot be invoked only when it suits — the same ex-ante commitment discipline that pre-registration enforces in science.[n1]
How it implements the components¶
If-Then Revision Contract fills the change side of the archetype's machinery — the components that let a commitment adapt without breach:
repair_or_renegotiation_path— it is the pre-agreed path by which a commitment is updated when circumstances change, without re-opening the whole agreement.response_coupling_rule— it couples a defined response to a defined evidence trigger; the "if X then Y" is exactly this coupling made explicit and binding.reversibility_or_revocation_window— it defines the conditions and the window within which the commitment may flex, reverse, or revoke, rather than leaving change to ad-hoc discretion.
It does not create the original commitment it revises (commitment_object, commitment_terms, authority_or_standing) — the Contract Speech-Act Clause does — nor does it fully retire or release a commitment (release_and_exit_rule, expiry_or_renewal_rule), which the Renegotiation Notice Protocol and Escrowed or Conditional Commitment own. It flexes a live commitment by pre-set rule; ending one is a different mechanism.
Related¶
- Instantiates: Commitment Lifecycle Governance — it builds the lifecycle's change path in advance, so a commitment can adapt to evidence without breach or fresh negotiation.
- Consumes: the original commitment it revises, e.g. a Contract Speech-Act Clause; it posts the resulting state changes to the Commitment Register.
- Sibling mechanisms: Contract Speech-Act Clause · Commitment Register · Renegotiation Notice Protocol · Readback Confirmation · Performance Bond or Deposit · Escrowed or Conditional Commitment · Performance Contract · Precommitment Device · Public Commitment · Service-Level Commitment · Warranty or Guarantee
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: If-Then Revision Contract operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it agrees in advance, in writing, that a specified trigger of evidence will produce a specified change to the commitment — so a live promise adapts by pre-set rule instead of by silent breach or fresh negotiation
Independent corroboration: The frozen evidence defines If-Then Revision Contract as 'Agrees in advance, in writing, that a specified trigger of evidence will produce a specified change to the commitment — so a live promise adapts by pre-set rule instead of by silent breach or fresh negotiation', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Statistics & Experimental Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Precommitting before observing results to how evidence will revise a claim follows scientific preregistration and statistical analysis plans.
Related originating lineages:
- Law & Governance — Retained as a formative lineage because the independent reviewer identified it as primary: Pre-agreeing a conditional modification to a live commitment is principally a contractual governance mechanism.
- Organizational & Management Science — Decision rules and escalation contracts materially institutionalize conditional revision in organizations.
- Psychology — Implementation-intention research independently formalized if-X-then-Y commitments for action.
Review resolution: Registered Reports require methods and analysis plans to be reviewed before outcomes are known, institutionalizing conditional commitments and later deviations. Contract language contributes enforceability, but the evidence-protecting if-then revision discipline originates in experimental design. The retained alternate domains identify independent or materially shaping provenance, not downstream reach alone. domain_reach=universal because the mechanism is portable across essentially any field. The encyclopedia entry deliberately composes those lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- https://www.cos.io/initiatives/registered-reports — Center for Open Science description of prereviewed protocols and controlled deviations in Registered Reports.
Notes¶
The If-Then Revision Contract and the Renegotiation Notice Protocol both handle change, but from opposite ends: the if-then fixes the change rule before the trigger, so no bargaining is needed when it fires; a renegotiation notice opens new bargaining when change becomes necessary. Choose the if-then when the contingencies are foreseeable enough to pre-price; choose notice-and-renegotiate when they are not, and pre-committing to a rule would only lock in the wrong response.
[n1] Pre-registration — the scientific practice of writing down, before the data are seen, exactly what will be measured and how the analysis will respond to each outcome. It binds the analyst to a rule in advance so that a later change of course is a pre-committed update rather than a post-hoc rationalization — the same discipline an if-then revision contract imposes on a commitment. ↩