Origin-Context Constraint Review¶
Review — instantiates Exaptive Function Redeployment
Reconstructs the context a feature was built for and catalogs the assumptions it silently carries, flagging the ones that will misfire once it serves its new function.
A feature that looks like it fits a new function is exactly where inherited assumptions hide, because apparent fit is judged from the new use's point of view — blind to what the origin baked in. Origin-Context Constraint Review works the other way around: it reconstructs the conditions the feature was designed under, enumerates the constraints and assumptions it drags along, and predicts which of them will transfer negatively into the new use. Its defining move is that it reasons forward from provenance — it is a pre-mortem organized by what this was for and what that assumed, not a generic risk checklist. It stops at prediction; it neither preserves the record it reads nor rules on what to do about what it finds.
Example¶
A decommissioned freight-rail corridor is being repurposed as a public greenway. The Origin-Context Constraint Review reconstructs what the corridor was built for — heavy freight — and enumerates what that assumed. Some assumptions transfer positively: the grade was engineered gentle for trains, which is ideal for cyclists. Others transfer negatively, and those are the point: the ballast likely holds decades of diesel and creosote (a contamination hazard for people on foot), the bridges are rated for train loads but were never fitted with fall protection or designed for crowd loading, drainage assumes a sealed track bed, and adjacent parcels carry freight-era easements that may restrict public access. The output is a register in which each inherited constraint carries a transfer sign and severity — contamination (health, high), missing railings (safety, high), easements (legal, unknown) — telling the project what to remediate before opening. It differs from a fresh site survey because it is organized by lineage: it finds the mismatches only visible if you know the corridor was built for trains.
How it works¶
Three moves, in order. First, reconstruct the origin context — consume the lineage record and ask "what was true when this was built that made it work?" Second, register the inherited constraints — the loads, tolerances, dependencies, legal terms, and cultural expectations that came bundled with the feature. Third, check the sign of each transfer — test every inherited constraint against the new function and flag the ones that were harmless or helpful at origin but become harmful in the new use. What distinguishes it is that the register is provenance-indexed: constraints are found because the origin is understood, so it catches mismatches a new-use-only review cannot see.
Tuning parameters¶
- Reconstruction depth — how thoroughly you rebuild the origin context, from a quick "what was this for" to excavating original specs and decisions. Deeper finds subtler assumptions but costs time and can over-index on history.
- Constraint scope — technical only, or also legal, cultural, and semantic constraints. Widening catches legitimacy and meaning landmines but blurs the review into its neighbors.
- Transfer-sign threshold — how confident you must be before marking a constraint as negative rather than neutral. Loose flags everything and floods the register; tight misses slow-acting mismatches.
- Evidence standard — expert judgment versus a required measurement (actually soil-test the ballast). A higher bar is credible but slow.
When it helps, and when it misleads¶
Its strength is catching the mismatches that are invisible from the new function's vantage point — the constraints legible only if you know where the feature came from. It is the direct antidote to "it looks like it fits" optimism.
Its failure modes are two. It can drown the decision in historical constraints that no longer bind, over-preserving a past that has moved on; and it is only as good as the reconstructed origin, so a wrong origin story yields a confident, wrong register. The classic misuse is letting the constraint list harden into a reflexive veto — a reason never to reuse anything — or running it after a reuse to justify a predetermined "too risky." The discipline is to attach a transfer sign and severity to each entry rather than merely noting that a constraint exists, and to separate binding constraints from historical curiosities. The specific harm it predicts is negative transfer: structure that helped at origin actively impairing the new use.[1]
How it implements the components¶
inherited_constraint_register— its primary output: the enumerated assumptions and constraints the feature carries from its origin context.negative_transfer_check— the analytic flag on which inherited constraints will harm the new function, predicted a priori from provenance.
It consumes rather than produces the origin record it works from — origin_function_lineage_record and historical_semantics_note are Lineage-Preserving Documentation's — and it stops at prediction: the keep-or-replace ruling built on these findings is the Purpose-Built Replacement Gate's function_fork_decision_record.
Related¶
- Instantiates: Exaptive Function Redeployment — it supplies the inherited-constraint picture the fitness and stewardship mechanisms depend on.
- Consumes: Lineage-Preserving Documentation — the origin record it reconstructs constraints from.
- Sibling mechanisms: Negative Transfer Red Team · Lineage-Preserving Documentation · Feature Refunctioning Audit · Adaptation Delta Mapping · Dual-Function Compatibility Test · Purpose-Built Replacement Gate
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Origin-Context Constraint Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it reconstructs the context a feature was built for and catalogs the assumptions it silently carries, flagging the ones that will misfire once it serves its new function.
Independent corroboration: The frozen evidence defines Origin-Context Constraint Review as 'Reconstructs the context a feature was built for and catalogs the assumptions it silently carries, flagging the ones that will misfire once it serves its new function', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Reconstructing design assumptions before repurposing a feature is rooted in engineering design review and requirements analysis.
Related originating lineages:
- Biology & Ecology — Origin-Context Constraint Review also draws materially on biology and ecology's study of adaptation, interacting living systems, and evolutionary function, which shaped this mechanism rather than merely adopting it as an application.
- Innovation & Entrepreneurship — Origin-Context Constraint Review is most directly rooted in innovation and entrepreneurship's practices of opportunity discovery, experimentation, product strategy, and disruptive entry. The lineage fits its defining practice: Reconstructs the context a feature was built for and catalogs the assumptions it silently carries, flagging the ones that will misfire once it serves its new function.
Review resolution: Authoritative-source research resolves the primary-origin disagreement in favor of engineering design. NASA Systems Engineering Handbook documents the formative practice or theory represented here. The retained alternate domains identify material co-development or translation, while current applicability is recorded separately as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis describes the historical relationship among lineages.
Attribution caveat: Exaptation supplies the biological concept, while product and engineering practice turn it into a review procedure. This is an encyclopedia synthesis translating exaptation into a design-governance procedure.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
Notes¶
This review and the Negative Transfer Red Team are complementary, not redundant. The review reasons forward from provenance — cheap, and good at catching known-assumption mismatches; the red team attacks from the outcome side — better at surprises the origin story does not reveal. Run the review first, and let its register focus where the red team pushes hardest.
References¶
[1] Perkins, D. N., & Salomon, G. “Transfer of Learning”. In International Encyclopedia of Education, 2nd ed., 6452–6457. Pergamon Press (1992). Defines negative transfer as prior learning that interferes with performance in a new context. registry ↩