Decision–Execution Lead-Time and Margin Calculation¶
Method — instantiates Reversibility-Horizon Detection and Commitment Gating
Subtracts observation, deliberation, authorization, mobilization, execution, stabilization, verification, and uncertainty margin from scenario closure.
Decision–Execution Lead-Time and Margin Calculation computes the time budget rather than the price. It works backward from the moment a return option physically closes, through the whole chain of durations that acting actually takes — observe, confirm, deliberate, authorize, mobilize, execute, stabilize, verify — plus a justified uncertainty margin, to find the latest safe decision time: the last moment authority can commit to return and still complete it before the window shuts. Its defining move is to distinguish decision time from effect time and to sum the full sequential-and-parallel path, so a decision made comfortably before the physical threshold is not mistaken for a decision made in time. The calculation's real product is not only a clock but the naming of the dominant delay — the stage that, if left unattacked, sets the window too late.
Example¶
A crewed vehicle on a lunar trajectory carries a free-return option: a corrective burn that loops it home, available only until the orbital geometry closes. Mission control needs the latest safe moment to decide on an abort, not the moment the physics closes. They lay the chain out backward from that closure: telemetry observation and fault confirmation, crew and flight-director deliberation, capcom and management authorization, propellant and attitude configuration (mobilization), the burn itself (execution), post-burn stabilization and tracking, and verification that the new trajectory is good. Each stage is a measured distribution, not a guess; some run in parallel, others strictly in sequence. They sum them and add an uncertainty margin sized to comms dropouts and one missed burn opportunity. Subtracting that total from the free-return closure yields a latest-safe-decision clock that sits several hours ahead of the physical window — and the calculation names authorization as the dominant delay, so that is where they pre-stage approvals. When a fault appears, the crew is not asked "can we still get home?" but "are we still inside the decision window?"
How it works¶
- Enumerate the full chain observe → confirm → deliberate → authorize → mobilize → execute → stabilize → verify, and keep decision time separate from effect time.
- Use measured distributions per stage, capturing which stages run in parallel and which are strictly sequential, plus coordination bottlenecks and adverse-condition delay.
- Sum to total action lead time, then add an uncertainty margin sized from consequence and controllability — not a round number bolted on for reassurance.
- Compute the clock: latest safe decision time = scenario closure − lead time − margin, produced once per horizon scenario (earliest, expected, and late closure).
- Name the dominant stage. The output that changes behavior is the identification of which delay to attack — pre-authorize, pre-stage capacity, or parallelize it.
Tuning parameters¶
- Stage granularity — how finely the chain is decomposed. Finer decomposition surfaces the dominant delay but risks double-counting stages that actually overlap.
- Distribution vs. point per stage — whether each stage carries a measured spread or a single value. Distributions propagate honest uncertainty into the margin; point values understate it.
- Margin-sizing rule — how the uncertainty margin scales with severity, model error, and controllability. Larger margins move the decision earlier, buying safety at the cost of premature action.
- Parallelism assumption — how aggressively stages are assumed to overlap. Optimistic overlap shortens the lead time on paper and is the classic way the window is set too late.
- Scenario coupling — whether one lead-time budget is applied to every closure scenario or each gets its own. Per-scenario budgets are sharper but multiply the bookkeeping.
When it helps, and when it misleads¶
Its strength is that it turns "we decided before the deadline" into "we decided before the latest safe moment," and it exposes that a decision made before the physical threshold can still complete after it. The named dominant stage is directly actionable. Its failure mode is garbage-in on stage durations — especially optimistic parallelism — which quietly sets the window too late; and a single aggregate clock can hide that one stage, often authorization, consumes the entire margin. The reversal's critical path is only as fast as its slowest strictly-sequential stage, and shortening anything off that path buys nothing.[n1] The classic misuse is modeling only the reversal command and omitting mobilization, stabilization, and verification, so the trigger is set at the physical boundary and return finishes too late. The guarding discipline is to use measured distributions, model verification and stabilization explicitly, and trigger at the latest safe decision time, never at closure itself.
How it implements the components¶
reversal_stage_lead_time_and_execution_path— it decomposes observation-through-verification into a measured, sequenced path and separates the moment of decision from the moment of effect.horizon_scenario_uncertainty_distribution_and_margin_set— it selects the safety margin and produces a latest-safe-decision time for each earliest / expected / late closure scenario.
It computes when the decision must be taken, not how costly return is once taken; the reversal cost, feasibility, and residual-damage curves are the time_varying_reversal_cost_feasibility_and_damage_model output of Reversal-Cost and Feasibility-Curve Estimation, its nearest twin.
Related¶
- Instantiates: Reversibility-Horizon Detection and Commitment Gating — supplies the latest-safe-decision clock the gate fires against.
- Consumes: Return-Path Readiness and Rollback Rehearsal supplies the measured execution and stabilization times that anchor the chain.
- Sibling mechanisms: Reversal-Cost and Feasibility-Curve Estimation · Threshold Hysteresis Dependency and Lock-In Stress Test · Return-Path Readiness and Rollback Rehearsal · Pre-Horizon Commitment Gate and Independent Challenge · Horizon Forecast-Error Trigger and Adaptation Audit
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Decision–Execution Lead-Time and Margin Calculation operates as a computation, comparison, model, or analytic representation used to infer, estimate, or choose because it subtracts observation, deliberation, authorization, mobilization, execution, stabilization, verification, and uncertainty margin from scenario closure.
Independent corroboration: The frozen evidence defines Decision–Execution Lead-Time and Margin Calculation as 'Subtracts observation, deliberation, authorization, mobilization, execution, stabilization, verification, and uncertainty margin from scenario closure', so its operative form is Analysis, Modeling & Optimization.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Operations Research
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Project scheduling and critical-path analysis cohered backward calculation from a required completion time through dependent activity durations, slack, and uncertainty margins.
Related originating lineages:
- Military & Strategic Studies — Operational planning supplied the full chain from observation and authorization through mobilization, execution, stabilization, and verification.
- Organizational & Management Science — Decision and execution governance supplied authorization, mobilization, stabilization, and verification stages that precede realized effect.
Review resolution: Project scheduling and critical-path analysis cohered backward calculation from a required completion time through dependent activity durations, slack, and uncertainty margins.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The critical path method identifies the longest chain of strictly-dependent activities in a project; its length sets the earliest possible completion, and slack on any off-path activity is free. Applied to reversal, it explains why the latest safe decision time is governed by the slowest sequential stage and why attacking the dominant delay — not the whole plan — is what moves the window. ↩