Feasible-Frontier Mapping¶
Envelope construction — instantiates Realized-Possible Outcome Gap Mapping
Derives the possible-outcome envelope from an explicit constraint model — what the system could reach given its real limits — rather than from any single achieved result.
Feasible-Frontier Mapping builds the "possible" side of the comparison from constraints upward. Instead of pointing at what someone already achieved or imagining a friction-free ideal, it enumerates the binding limits the system actually operates under — resource ceilings, physical laws, stage-gate throughput, regulatory floors — and computes the boundary of what those limits jointly permit. Its defining commitment is that every point on the frontier is backed by a registered, defensible assumption: change an assumption and the frontier moves, visibly and accountably. The output is not a single target but the edge of a reachable region, plus a signal of how much of that region is still unrealized (latent) capacity. It is the disciplined middle between fantasy ceilings and mere copy-the-leader benchmarking.
Example¶
An agronomy team assessing a maize-growing region observes an actual harvest of about 6 tonnes per hectare and wants to know what is genuinely reachable there — not the world record, and not what one exceptional farmer managed once. Feasible-Frontier Mapping constructs the answer from the region's real constraints: solar radiation and temperature set a biophysical potential; rainfall (this is rain-fed land, no irrigation) pulls that down to a water-limited attainable frontier; soil nitrogen and realistic input access pull it further. The registered assumptions — rain-fed, current cultivar set, no new irrigation capital — are written down explicitly. The frontier lands near 10 t/ha attainable.
The gap between 6 and 10 t/ha is now grounded in a constraint model anyone can interrogate: a skeptic who thinks irrigation is coming can change that one registered assumption and watch the frontier rise. The 4-tonne shortfall is flagged as latent capacity — reachable under the stated constraints, not yet realized — which is exactly the signal that separates a closable gap from a hard limit. This mirrors the agronomic yield-gap framework[n1] of potential, attainable, and actual yield.
How it works¶
- Enumerate the binding constraints. List the limits that actually shape outcomes — resource, physical, throughput, policy — and mark which bind and which have slack.
- Register every feasibility assumption. Each assumption that positions the frontier (rain-fed vs. irrigated, current vs. upgraded capital) is written down and owned, so the frontier is contestable rather than asserted.
- Compute the reachable edge. Combine the constraints into the boundary of jointly-permitted outcomes — a region and its edge, not a lone point.
- Flag the latent slice. The distance from realized to frontier, under unchanged constraints, is tagged as latent capacity: the part of the gap the constraint model says is genuinely reachable.
Tuning parameters¶
- Constraint set breadth — how many limits enter the model. More constraints yield a more realistic, usually lower frontier; too few float it toward fantasy.
- Assumption stance — optimistic vs. conservative settings for each registered assumption. The stance is what a critic should challenge; make it explicit rather than baked in.
- Frontier vs. point — report the whole reachable edge or a single attainable target. The edge preserves trade-offs; a point is easier to act on.
- Constraint-relaxation scenarios — how many "what if this limit lifted" variants you carry. Each shows how much frontier is bought by relaxing a specific constraint.
- Latent-signal threshold — how much unrealized reachable capacity must exist before a gap is flagged as worth attention.
When it helps, and when it misleads¶
Its strength is a possibility figure that is auditable: because every frontier point traces to a registered assumption, disagreements resolve into "which constraint is wrong," not dueling opinions. It is the right envelope when a credible constraint model exists but no close real-world exemplar does.
Its failure mode is a frontier only as good as its constraint list: omit a binding limit and the frontier floats too high, indicting the operators for missing an "attainable" that was never attainable; over-constrain it and real slack disappears. A classic misuse is treating the frontier as a committed target rather than a possibility boundary, then punishing teams for not reaching an edge that assumed conditions they never had. The guarding discipline is to keep the assumption register live and to relabel the frontier whenever a binding constraint is added, removed, or shown false.
How it implements the components¶
feasibility_assumption_register— its backbone: the explicit, owned list of assumptions and constraints that position the frontier and make it contestable.latent_capacity_signal— the realized-to-frontier distance under unchanged constraints, flagged as genuinely reachable unrealized capacity.
It builds the envelope from a constraint model, so it does not implement possible_outcome_envelope or best_demonstrated_comparator — those anchor on a real achieved exemplar and belong to its nearest twin, Best-Demonstrated-Practice Comparator. Nor does it name a friction-free theoretical_maximum_label — that is Counterfactual Ceiling Probe.
Related¶
- Instantiates: Realized-Possible Outcome Gap Mapping — supplies a constraint-grounded possibility envelope for the gap table.
- Sibling mechanisms: Realized-Possible Gap Table · Loss-Channel Decomposition · Best-Demonstrated-Practice Comparator · Counterfactual Ceiling Probe · Closability Scoring Rubric · Gap-Closure Experiment Backlog · Theoretical-Ceiling vs Feasible-Target Review · Post-Closure Gap Remeasurement
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Feasible-Frontier Mapping operates as a computation, comparison, model, or analytic representation used to infer, estimate, or choose because it derives the possible-outcome envelope from an explicit constraint model — what the system could reach given its real limits — rather than from any single achieved result.
Independent corroboration: The frozen evidence defines Feasible-Frontier Mapping as 'Derives the possible-outcome envelope from an explicit constraint model — what the system could reach given its real limits — rather than from any single achieved result', so its operative form is Analysis, Modeling & Optimization.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Operations Research
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Operations research supplies the general professional apparatus of feasible regions, binding constraints, and frontier construction. Economics formalized production and efficient frontiers, while agronomy developed attainable-yield frontiers independently; those are genuine alternate origins, not merely later applications.
Related originating lineages:
- Agricultural Science & Agronomy — Yield-gap practice independently developed potential, attainable, and actual production frontiers.
- Economics & Finance — Production-possibility and efficient-frontier traditions materially shaped frontier reasoning.
Review resolution: Operations research supplies the general professional apparatus of feasible regions, binding constraints, and frontier construction. Economics formalized production and efficient frontiers, while agronomy developed attainable-yield frontiers independently; those are genuine alternate origins, not merely later applications.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] The agronomic yield gap framework distinguishes potential yield (set by climate and genetics), attainable yield (potential minus water and nutrient limits under real management), and actual yield. The gap between attainable and actual is the constraint-grounded reachable slack — the direct analogue of a feasible frontier. ↩