Duration Matched Commitment Design

Do not fund short-clock promises with only long-clock resources unless rollover loss, liquid coverage, and rebalancing paths are already designed.

Overview

Duration-Matched Commitment Design handles the failure hidden inside maturity mismatch: a system can have enough resources in total and still fail because the resources do not become usable on the same clock as the obligations. The short side must be refreshed, rolled over, renewed, or satisfied now. The long side may be valuable, productive, or contractually committed, but it cannot mature immediately.

The archetype turns duration into an explicit design variable. It asks what comes due when, what can be safely converted when, what depends on repeated refresh, how long the system can survive if refresh stops, and who can rebalance the structure before the short clock outruns the long one.

Key components

Component	Description
Commitment Tenor Inventory ↗	The inventory records the maturity, notice, renewal, cancellation, exit, replenishment, and conversion horizons of commitments on both sides. It prevents the common error of treating a one-day claim and a one-year asset as equivalent because they have equal nominal value.
Maturity Ladder Map ↗	The maturity ladder places obligations and resource releases on one timeline. The key question is not only whether inflows exceed outflows, but whether they do so in each relevant time window under normal and stressed conditions.
Rollover Dependency Register ↗	Many maturity-mismatch systems work only because short commitments keep renewing. The register makes that assumption visible: who must renew, what makes renewal credible, what could close the window, and how correlated the renewal dependencies are.
Liquid Coverage Floor ↗	The liquid coverage floor states how much immediately usable or reliably convertible resource is needed to survive a short-side refresh failure. It is more specific than a generic reserve because it is sized against a maturity ladder and stress scenario.
Rebalancing Authority ↗	Maturity mismatch often persists because no one owns both sides. One team accepts short promises; another invests long; another controls reserves or contracts. Rebalancing authority gives someone the mandate to lengthen the short side, shorten the long side, add liquidity, throttle growth, or activate contingency paths.

Common mechanisms

Common mechanisms include maturity ladder analysis, asset-liability matching policies, liquidity coverage floor metrics, rollover-failure stress tests, staggered maturity schedules, committed backup facilities, notice-period alignment, duration-gap dashboards, contingency funding playbooks, and triggered maturity-rebalancing clauses. These mechanisms instantiate the archetype but do not replace it; the archetype is the full diagnosis and governance of the duration mismatch.

Parameter dimensions

Important parameters include the short-side renewal interval, the long-side resource-release horizon, the cost of forced conversion, the concentration of maturities, the reliability of rollover channels, the liquid coverage horizon, the correlation of exits or nonrenewals, the authority lag for rebalancing, and the acceptable tradeoff between efficiency and resilience.

Invariants to preserve

Obligations due in a given window should be backed by resources or contingency paths available inside that same window. Long-duration value should not be counted as short-duration liquidity unless conversion time and loss are modeled. Rollover assumptions should be visible and stress-tested. No single renewal cliff should be able to transform an apparently healthy system into an immediate failure.

Tradeoffs

The archetype does not say to eliminate all maturity transformation. Some mismatch can create useful investment, access, yield, or efficiency. The design problem is to keep the mismatch inside a governed runway. Too much matching can make the system rigid and expensive; too little matching can make it fragile and confidence-sensitive.

Neighbor distinctions

This archetype is distinct from Liquidity Reserve because a reserve is only one response to a duration gap. It is distinct from Resource Liquefaction because converting locked resources is only one way to repair the long side. It is distinct from Capacity Reservation because holding back capacity does not necessarily align maturities. It is distinct from Coupling Latency and Time-Delay Effects because the issue is not just delayed interaction; it is a short claim backed by a long resource.

Examples and non-examples

A bank that funds long loans with short deposits is the canonical finance example. A public program that makes multi-year service promises from annually renewed grants is a policy example. A platform that sells long service commitments while relying on short-renewed infrastructure capacity is an operations example. A simple emergency fund, ordinary task schedule, or discount-rate analysis is not enough by itself; the maturity mismatch must involve two sides whose durations fail to align.

Common Mechanisms

• asset_liability_matching_policy
• committed_backup_facility
• contingency_funding_playbook
• duration_gap_dashboard
• liquidity_coverage_floor_metric
• maturity_ladder_analysis
• notice_period_or_lockup_alignment
• rollover_failure_stress_test
• staggered_maturity_refinancing_schedule
• triggered_maturity_rebalancing_clause

Compression statement

Duration-Matched Commitment Design applies when a system is balanced in amount but not in time. One side can demand, withdraw, cancel, renew, or fail on a short clock, while the other side releases value only on a long clock. The archetype inventories both sides, builds a maturity ladder, identifies rollover dependence, sets duration-gap limits, sizes liquid coverage to stressed runoff, and installs rebalancing authority so the system does not fail merely because resources are locked beyond the moment when obligations mature.

Canonical formula: short_clock_obligations + long_clock_resource_lockup + rollover_dependence -> liquidity_timing_failure; tenor_inventory + maturity_ladder + duration_gap_limit + liquid_coverage_floor + rollover_stress_test + rebalancing_authority -> survivable_commitment_timing

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (10)

• Buffering: A maintained intermediate capacity that absorbs excess and releases it during shortfall, smoothing variation and decoupling a source from a consumer whose rates do not match.
• Commitment: An agent binds itself in the present to a future course of action or to the truth of a proposition, creating a new constraint on future behavior that others can rely on.
• Coupling: Interdependence among subsystems.
• Flow: Structured movement of energy, matter, or information.
• Liquidity: Ease of conversion.
• Lock-In: Forward-looking cost of switching exceeds the forward-looking cost of staying, even when a superior alternative exists.
• Maturity Mismatch: A system holds two-sided commitments whose durations differ — a short side that must be repeatedly refreshed against a long side that cannot accelerate — so it fails when refreshing stops, not because it lacks resources but because they are locked in durations longer than the moment requires.
• Reserve: Deliberately maintained surplus held beyond expected need so the system can absorb variation, uncertainty, or shock without failing.
• Resource Management: Allocation of finite assets.
• Temporal Dynamics: System outcomes depend fundamentally on timing, sequencing, duration.

Also references 35 related abstractions

• Constraint: Limits possibilities to guide outcomes.
• Correlated Capacity Demand: When demands on a shared finite resource are tail-correlated rather than independent, capacity sized for independent peaks fails at the rare joint exceedance.
• Decoupling Point: The buffered interface where a flow splits from forecast-driven push upstream into order-driven pull downstream, and whose position sets the lead-time, inventory, and customisation trade-offs.
• Dependency: Directed relation in which one element relies on another being present, prior, compatible, or supplied, with a specifiable failure mode if the condition is unmet.
• Fail-Safe: Default to safe state on failure.
• Feedback: Outputs influence inputs.
• Intermittency: Irregular bursts.
• Load Balancing: Distributing work across resources so none is overloaded.
• Maintenance Rehearsal: Holding a decay-prone state above its disappearance threshold by repeated low-cost refresh actions that re-assert it without enriching or moving it.
• Margin of Safety: Buffer capacity.

▸ Show 25 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Asset-Liability Tenor Matching · domain variant · recognized

A finance-centered variant that aligns asset maturities, liability maturities, funding stability, and liquid buffers.

• Distinct from parent: The parent applies to any two-sided commitment-duration system; this variant uses finance-specific terms, metrics, and controls.
• Use when: Long assets or investments are funded by shorter liabilities or withdrawable claims; The institution depends on repeated refinancing, deposit retention, or wholesale funding rollover; Failure would occur through timing and confidence before accounting resources are exhausted.
• Typical domains: banking, treasury management, insurance, project finance
• Common mechanisms: maturity ladder analysis, asset liability matching policy, liquidity coverage floor metric, rollover failure stress test

Rollover Runway Fragility Control · temporal variant · recognized

A variant focused on systems that remain viable only while a short-side promise can be repeatedly rolled forward.

• Distinct from parent: The parent covers all duration mismatches; this variant emphasizes the fragile repeated-refresh assumption.
• Use when: Obligations are not repaid from maturing resources but from continued renewal; The system has enough long-run value but too little runway if renewal stops; Confidence, access, or attention can close the renewal window abruptly.
• Typical domains: finance, platform operations, supply chain, staffing
• Common mechanisms: rollover failure stress test, staggered maturity refinancing schedule, contingency funding playbook

Contractual Notice-Period Alignment · governance variant · recognized

A contractual variant that aligns cancellation, withdrawal, termination, renewal, and delivery windows with the time required to release or replace resources.

• Distinct from parent: The parent is cross-domain; this variant focuses on the governance and contract design surface.
• Use when: One party can exit, withdraw, cancel, or demand delivery faster than the other side can unwind commitments; Service promises depend on locked staffing, inventory, infrastructure, or capital; Contract terms create a timing asymmetry invisible in nominal service capacity.
• Typical domains: service contracting, supply chain, employment, infrastructure access
• Common mechanisms: notice period or lockup alignment, triggered maturity rebalancing clause

Operational Runway Commitment Alignment · domain variant · recognized

An operations variant that aligns short-cycle delivery promises with the slower replenishment, hiring, production, or repair cycles that make delivery possible.

• Distinct from parent: The parent includes financial and contractual versions; this variant focuses on operational capacity timing.
• Use when: Demand or service promises can be made faster than supply, capacity, staff, or infrastructure can be replenished; The organization appears resource-rich but cannot convert resources into usable capacity in the decision window; Failure occurs when the renewal cadence of supporting resources breaks.
• Typical domains: healthcare operations, cloud operations, manufacturing, logistics
• Common mechanisms: staggered maturity refinancing schedule, committed backup facility, duration gap dashboard

Near names: Duration Gap Control, Tenor Alignment Design, Rollover Risk Containment.