Outcome-Defined Adequacy¶
Core Idea¶
Outcome-defined adequacy is the meta-evaluative stance in which the adequacy of an artifact, act, or system is specified by whether it produces a defined outcome in its context of use, not by its internal form, surface properties, or process compliance. The form-side is deliberately left open. Success is judged relationally — against a real-world purpose or downstream consequence — rather than against an inventory of features, a process checklist, or a syntactic template. The essential commitment is that the spec or contract is written in outcome terms, not form terms, and that any form which reliably produces the outcome is adequate.
The arrangement has a small set of recurring roles: an artifact, act, or system being evaluated; a context of use in which adequacy is judged; a defined outcome the artifact is meant to produce in that context; an operational specification of that outcome (measurable, observable); and form-side openness, under which any form that produces the outcome counts. Verification is by outcome-measurement rather than form-inspection. The stance exploits the many-to-one relation between forms and outcomes — many implementations realize the same outcome, and only the outcome is load-bearing. It carries characteristic failure modes — gaming, side-effects, measurement difficulty, accountability opacity — and it sits inside a meta-choice among outcome-defined, form-defined, and process-defined adequacy framings, each with its own trade-offs. The prime's distinctive content is the recognition that this framing choice is itself substantive, not a neutral preliminary to evaluation.
How would you explain it like I'm…
Did It Work?
Judge By Results
Adequacy By Outcome
Structural Signature¶
the evaluated unit — the context of use — the defined outcome — the operational outcome-specification — the form-side openness — the many-to-one form→outcome relation — the outcome-measurement verification — the meta-choice among adequacy framings
A configuration instantiates outcome-defined adequacy when each of the following holds:
- An evaluated unit. Some artifact, act, or system is the object whose adequacy is in question.
- A context of use. Adequacy is judged relative to a situation of use, not in the abstract; the same unit can be adequate in one context and not another.
- A defined outcome. A real-world purpose or downstream consequence the unit is meant to produce in that context is specified as the criterion.
- An operational outcome-specification. The outcome is stated measurably or observably, so adequacy can be checked. Without this the stance collapses into vague results-talk.
- Form-side openness. The internal form, surface properties, and process are deliberately left unconstrained: any realization that produces the outcome counts.
- A many-to-one relation. Many distinct forms map to the same outcome, and only the outcome is load-bearing — this is the relation the stance exploits.
- Outcome-measurement verification. Acceptance is by measuring the result, not inspecting the form or auditing the process.
- A live meta-choice. Outcome-defined adequacy sits beside form-defined and process-defined framings; selecting among them is itself a substantive, non-neutral decision with distinct failure modes (gaming, side-effects, measurement difficulty, accountability opacity).
These components compose into a stance: the spec is written on the outcome side, form is left open to absorb variety, verification is by measurement, and the framing choice is made deliberately with its characteristic failure modes in view.
What It Is Not¶
- Not the act of checking fitness-for-purpose (see
validation).validationis the verification procedure that asks "does this meet the need?"; outcome-defined adequacy is the prior framing choice that locates the spec on the outcome side rather than the form or process side. Validation is the natural acceptance test that follows from an outcome framing, not the framing itself. - Not a results metric or its measurement (see
effect_size).effect_sizequantifies how much of an outcome was produced; outcome-defined adequacy is the stance that only the outcome counts, with form left open. The prime is about where the criterion is written, not how large the measured result is. - Not metric-gaming (see
goodharts_law).goodharts_lawis the failure mode in which a measured proxy decouples from the outcome under pressure; outcome-defined adequacy is the legitimate stance that invites that hazard. The prime names the framing; Goodhart names what goes wrong when its proxy is gamed. - Not a summative grade (see
summative_assessment).summative_assessmentis an institutional end-of-process judgement that may itself be form-, process-, or outcome-defined; the prime is the narrower claim that adequacy is specified by outcome with form open, independent of whether the judgement is summative or formative. - Not pragmatism or "results-orientation." Those are dispositional attitudes; the prime is a precise structural claim about where the spec is written — outcome side, form side, or process side — and that this choice is substantive, not a vague preference for what works.
- Common misclassification. Reading every results-talk evaluation as outcome-defined. Catch it by asking whether the form is genuinely left open: if acceptable realizations are enumerated or a procedure is mandated, the spec is actually form- or process-defined, however much "results" rhetoric surrounds it.
Broad Use¶
The stance appears under different vocabularies across substrates. In speech-act theory, communicative success is felicity — illocutionary uptake and perlocutionary effect, not lexical form. In philosophy of mind and biology, functionalism defines a mental state or biological kind by its causal role, not its material realization. In outcome-based regulation, policy specifies the outcome to be achieved — emission reduction, patient survival, a financial-stability metric — and leaves means to the regulated entity. In HCI and product design, job-to-be-done and task-success treat an artifact as adequate if it lets the user accomplish the task, regardless of feature inventory. In software engineering, black-box testing and behavioural specification judge a module by whether its outputs satisfy the contract, regardless of implementation. In biology, adaptive radiation and functional morphology recognize kinds by ecological role rather than ancestry. In speech-language pathology, "functional communication" treatment is adequate if it lets the patient achieve communicative goals, regardless of grammaticality. In law, performance-based standards — the negligence reasonable-person test, the equitable outcomes of constructive trust — are outcome-defined.
Clarity¶
The arrangement makes visible a stance otherwise blurred under generic terms like "results-oriented" or "pragmatic." It sharpens the contrast with form-defined adequacy (the artifact must have these specific features) and process-defined adequacy (the artifact must have been produced by this procedure), making it possible to ask which adequacy framing a given evaluation regime uses and what the consequences of each are. The clarifying force is to convert a vague preference for "what works" into a precise claim about where the spec is written: on the outcome side, the form side, or the process side.
The arrangement also surfaces the recurring failure modes of each framing. Form-defined adequacy tolerates outcome failure if the form is satisfied — compliance theatre. Process-defined adequacy tolerates outcome failure if the process was followed — audit-pass with reality-fail. Outcome-defined adequacy tolerates form heterogeneity, which can be a feature (flexibility, innovation, local fit) or a bug (gaming, unmonitored side-effects). Naming the three framings side by side makes their characteristic blind spots comparable, so an evaluator can choose the framing whose failure mode is least costly in the case at hand rather than defaulting to one unreflectively.
Manages Complexity¶
Outcome-defined adequacy collapses the design space. Instead of writing an exhaustive feature spec or process spec — which is both under-determined (it cannot anticipate all forms that produce the outcome) and over-determined (it forecloses valid alternatives) — the evaluator specifies the outcome and accepts any form that achieves it. This factoring exploits the many-to-one relation between forms and outcomes: many implementations realize the same outcome, and only the outcome is load-bearing. The cost is harder verification (outcomes must be measured, not features inspected) and harder accountability (locating when a failure occurred is more difficult). The prime makes this trade-off explicit and names the discipline of choosing the framing intentionally.
The leverage is that the form-side openness absorbs variety the evaluator would otherwise have to enumerate. Where a form-defined spec must grow a clause for every acceptable realization, an outcome-defined spec admits all of them at once, bounded only by the outcome criterion. This is the same complexity-management move that black-box contracts and outcome-based regulation make: shift the burden from specifying the space of acceptable forms to measuring a single result.
Abstract Reasoning¶
Outcome-defined adequacy trains a reasoner to ask:
- What artifact, act, or system is being evaluated, and in what context of use is its adequacy judged?
- What outcome is it supposed to produce, and can that outcome be specified operationally — measurably, observably?
- Is the form side genuinely left open, so that any realization achieving the outcome counts?
- Is verification done by outcome-measurement rather than form-inspection?
- What are the characteristic failure modes here — gaming, side-effects, measurement difficulty, accountability opacity — and are they being watched?
- Is the framing choice itself — outcome-defined versus form-defined versus process-defined — being made deliberately, with its trade-offs in view?
The non-obvious inference is that the framing choice is substantive: the same artifact can be adequate under one framing and inadequate under another, and disputes about adequacy often turn out to be disputes about which framing is in force. The opposite framings are legitimate in some contexts — where forms are tightly coupled to outcomes, or where outcome measurement is infeasible — so the discipline is not to prefer outcome-definition universally but to recognize the choice and make it on purpose.
Knowledge Transfer¶
Role mappings across domains:
- Artifact / act / system ↔ utterance / mental state / regulated entity / product / software module / organism / legal conduct
- Context of use ↔ communicative situation / causal role / regulatory regime / task setting / runtime / ecological niche
- Defined outcome ↔ uptake and effect / causal function / emission target / task success / contract satisfaction / fitness
- Operational outcome spec ↔ felicity conditions / functional role / measurable threshold / success criterion / behavioural assertion
- Form-side openness ↔ any realization that achieves the outcome is adequate
- Failure modes ↔ gaming / side-effects / hard measurement / accountability opacity
A regulator choosing between prescriptive and outcome-based standards, a software architect choosing between implementation and behavioural specs, a philosopher of mind arguing functional role over material realization, and a speech-act theorist analyzing felicity are taking the same stance: adequacy specified by outcome, form left open, verification by outcome-measurement. The vocabulary — outcome-defined, form-defined, process-defined, felicity, functional role, performance-based standard — transfers across substrates. A regulator weighing outcome-based versus prescriptive standards can borrow the functionalism debate from philosophy of mind; a software architect weighing behavioural versus implementation specs can borrow from outcome-based regulation. The prime's universal failure mode — gaming, side-effects, hard verification — also transfers and serves as a check on uncritical enthusiasm for outcome-framings. What moves between fields is not a metaphor but the literal stance: the spec written in outcome terms, the form side deliberately open, the many-to-one relation exploited, and the meta-choice among framings made explicit. Recognizing the stance in one substrate lets a practitioner import both its leverage (form-side openness absorbs variety) and its discipline (watch for gaming and side-effects; verify by measuring the outcome) into another, including the recognition that validation is the natural acceptance test when adequacy is outcome-defined, just as verification is the natural test when adequacy is form-defined.
Examples¶
Formal/abstract¶
Functionalism in philosophy of mind is the clean theoretical instance. The evaluated unit is a mental state — say, pain. The context of use is the organism's causal economy: inputs (tissue damage), internal-state transitions, and outputs (withdrawal, complaint, avoidance learning). The defined outcome is the causal role pain plays — being typically caused by damage, typically causing aversion and protective behavior — and the operational outcome-specification is the input-output-transition profile that role can be written as. The decisive move is form-side openness: functionalism refuses to identify pain with any particular substrate. Carbon neurons, silicon circuitry, or a sufficiently organized hydraulic system all count as instantiating pain if and only if they realize the role. This is the many-to-one relation made into a thesis — multiple realizability — where many physical forms map to one functional outcome and only the functional outcome is load-bearing for being-in-pain. Verification is by role-occupancy, not by inspecting the wetware. The meta-choice is explicit and substantive: a type-identity theorist writes the spec on the form side (pain is C-fiber firing), and the dispute between them is precisely a dispute over which adequacy framing is in force. The characteristic failure mode — that a system might fake the outputs without the inner organization (the absent-qualia and "China brain" worries) — is the philosophical analogue of gaming: passing the outcome test without genuinely producing the outcome.
Mapped back: Pain-as-role is adequacy specified by outcome (the causal profile) with form (the substrate) deliberately open; multiple realizability is the many-to-one relation the stance exploits, and the type-identity rival is the alternative form-defined framing the meta-choice selects against.
Applied/industry¶
Outcome-based regulation and black-box software testing are the same stance in two industries. In regulation, a prescriptive (form-defined) emissions rule names the technology — "install this scrubber, run it at this rate." An outcome-based rule instead writes the spec on the outcome side: "keep stack emissions below this measured threshold," leaving the form — scrubber, fuel switch, process redesign — entirely open. The evaluated unit is the regulated plant, the context its operating regime, the defined outcome an emissions level, the operational specification a metered measurement, and verification is by monitoring the stack, not auditing the equipment. The leverage is exactly form-side openness absorbing variety: the regulator does not have to enumerate every acceptable abatement technology, and plants innovate toward cheaper means. The named failure modes bite predictably — gaming (tuning the plant only during test windows), side-effects (shifting one pollutant to another the spec does not measure), and accountability opacity (a missed target is harder to pin on a specific lapse than a missing scrubber). In software, behavioural/black-box testing is structurally identical: the unit is a module, the outcome is a contract over outputs given inputs, the form (the implementation) is deliberately unconstrained, and a passing test verifies the result rather than the code. The intervention catalogue transfers directly between the two: in both, the architect's discipline is to specify the outcome operationally, leave the form open to absorb variety, and instrument against gaming and unmeasured side-effects — and to decide deliberately when a form-defined spec (a mandated algorithm, a mandated technology) is safer because outcomes are hard to measure or forms are tightly coupled to consequences.
Mapped back: The emissions threshold and the module contract are both the spec written on the outcome side with form left open; the regulator monitoring the stack and the test harness checking outputs are both outcome-measurement verification, and the gaming/side-effect risks are the stance's universal failure modes recurring across substrates.
Structural Tensions¶
T1 — Measured Proxy versus Defined Outcome (Measurement). The stance demands an operational outcome-specification, but the operational measure is almost never the outcome itself — it is a proxy standing in for it. The gap between proxy and true outcome is exactly where gaming lives. The failure mode is Goodhart drift: the measured metric improves while the real outcome it was meant to track stagnates or degrades, and the evaluation certifies success because it can only see the proxy. Diagnostic: ask what the metric would have to miss for a unit to pass while genuinely failing — if a cheap form-tweak can move the metric without moving the real consequence, the spec has been written on the proxy, not the outcome.
T2 — Form-Side Openness versus Unmonitored Side-Effects (Scopal). Leaving the form open absorbs beneficial variety, but the same openness leaves everything the outcome-spec does not name unconstrained — including harmful side-effects on dimensions outside the spec's scope. The failure mode is scope leakage: the named outcome is achieved by a form that wins on the measured dimension while shifting cost onto an unmeasured one (the emissions rule that trades one pollutant for another). Diagnostic: enumerate the dimensions the outcome-spec is silent about; if a form can satisfy the spec by degrading any of them, form-side openness is laundering an externality, and a partial form-constraint or a second outcome term is needed.
T3 — Outcome-Verification versus Accountability Locality (Coupling). Outcome-measurement verifies the end state but deliberately discards the process trace, which is where blame and remediation are located. The failure mode is accountability opacity: when an outcome fails, there is no audited step at which the failure can be pinned, so diagnosis and correction stall — the regime can detect failure but cannot attribute it. This is where process_defined_adequacy legitimately takes over: in high-stakes, low-frequency settings, knowing why a failure occurred outweighs the flexibility of form-openness. Diagnostic: ask whether a single observed failure can be traced to a correctable cause; if outcome data alone cannot localize it, the framing has traded accountability for flexibility.
T4 — Stationary Context versus Drifting Context (Temporal). Adequacy is defined "in context of use," and the stance silently assumes that context is stable enough for an outcome-spec written today to remain the right criterion tomorrow. The failure mode is context drift: the form keeps hitting the frozen outcome target while the real-world purpose the target was a proxy for has moved, so a unit stays "adequate" against a stale criterion. Diagnostic: ask when the outcome-spec was last re-derived from the underlying purpose; an outcome-defined regime with a never-revisited target is tracking history, not current need — the same reference-drift hazard that afflicts any fixed setpoint.
T5 — Many-to-One Realizability versus Verification Cost (Scalar). The leverage is the many-to-one relation: many forms, one outcome, so the spec admits all forms at once. But that same multiplicity means verification cannot lean on form-inspection and must measure the result directly — and outcome measurement is often expensive, delayed, or noisy at scale. The failure mode is choosing outcome-definition for its enumeration savings while ignoring that the saved enumeration cost reappears as recurring measurement cost on every evaluation. Diagnostic: compare one-time form-enumeration cost against per-evaluation measurement cost over the regime's lifetime; where outcomes are cheap to specify but costly to measure repeatedly, form-defined adequacy may be the cheaper frame despite its rigidity.
T6 — Framing Choice as Substantive versus Framing as Neutral Preliminary (Scopal). The prime's distinctive claim is that selecting among outcome-, form-, and process-defined framings is itself substantive — yet evaluators routinely treat it as a neutral preliminary and default to one frame unreflectively. The failure mode is hidden-frame disputes: two parties argue about whether a unit is "adequate" while actually disagreeing about which framing is in force, so the dispute is unresolvable until the frame is surfaced. Diagnostic: when an adequacy dispute persists despite agreed facts, ask each side where they think the spec is written — outcome, form, or process; a frame mismatch, not an evidentiary one, is usually the real disagreement.
Structural–Framed Character¶
Outcome-Defined Adequacy sits on the framed side of the structural–framed spectrum, consistent with its frontmatter label and a balanced aggregate of 0.5 across all five criteria. There is a genuine relational skeleton underneath — a many-to-one map from forms to outcomes, with the spec written on the outcome side and form left open — but enough of the prime's content rides on evaluative and human-institutional commitments to pull it across the middle.
The criteria that push it framed are the evaluative and the practice-bound ones. The prime is centered on adequacy, a normative spec-design stance: judging whether something "works" against a purpose is not value-neutral the way a bare set-relation would be, and the framing choice it foregrounds (outcome- versus form- versus process-defined) is explicitly a substantive normative decision, not a neutral preliminary. Its canonical cases — outcome-based regulation, performance-based legal standards, black-box contracts, job-to-be-done product design — are overwhelmingly tied to human evaluative and institutional practices: a spec, a regulator, a contract, a designer choosing what counts as success. The home vocabulary (felicity conditions, functional role, performance-based standard, validation) is portable but carries a half-measure of evaluative freight, and invoking the prime imports the meta-evaluative stance — "where is the spec written?" — rather than merely recognizing a pattern already wired into a physical substrate. Functionalism in philosophy of mind shows the structural core can be stated abstractly, which is why the prime is not fully framed; but the weight of its instances in regulation, assessment, and design, plus its irreducibly evaluative "adequacy" framing, places it at 0.5, exactly the balanced framed grade the frontmatter records.
Substrate Independence¶
Outcome-Defined Adequacy is a highly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. The domain breadth is genuinely wide: the many-to-one form-to-outcome stance recurs in speech-act theory (felicity and illocutionary uptake), philosophy of mind and biology (functionalism, function defined by causal role rather than material realization), outcome-based regulation (specifying emission or patient-survival targets and leaving means open), HCI and product design (job-to-be-done and task-success), software engineering (black-box and behavioural testing), biology (functional morphology, adaptive radiation), speech-language pathology (functional communication), and law (the negligence reasonable-person test, performance-based standards). The structural abstraction is high — the relational core, judge a thing by whether it produces a defined outcome in its context of use rather than by its form, is portable across all these substrates — but what holds the composite at 4 rather than 5 is a residual evaluative cast: the prime is framed as a stance about adequacy, a meta-evaluative judgement rather than a purely structural relation. The transfer evidence sits one notch lower at 3 because, while the vocabulary travels cleanly, the cross-domain carriers are conceptual reframings rather than a single shared formalism.
- Composite substrate independence — 4 / 5
- Domain breadth — 4 / 5
- Structural abstraction — 4 / 5
- Transfer evidence — 3 / 5
Neighborhood in Abstraction Space¶
Outcome-Defined Adequacy sits in a sparse region of abstraction space (67th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.
Family — Unclustered & Miscellaneous (91 primes)
Nearest neighbors
- Pivotality — 0.72
- Realized vs Possible Outcomes — 0.71
- Counterfactual Subtraction — 0.70
- Operationalization — 0.69
- Construct Validity — 0.69
Computed from structural-signature embeddings · 2026-06-14
Not to Be Confused With¶
Outcome-defined adequacy is most readily confused with validation, because in practice an outcome framing is verified by validation and the two travel together. But they answer different questions. validation is an operation: the act of confirming that an artifact meets a real-world need, typically by exercising it against that need and observing the result. Outcome-defined adequacy is a prior commitment about what the spec consists of — a relational criterion written in outcome terms, with form deliberately unconstrained. Validation presupposes some criterion to validate against; the prime is precisely the choice to make that criterion an outcome rather than a feature list or a procedure. The two come apart in both directions: one can validate against a form-defined spec (confirm the mandated algorithm is present and correctly implemented), which is validation without outcome-definition; and one can adopt an outcome framing whose validation is, for now, infeasible (the outcome is real but unmeasurable), which is outcome-definition without practicable validation. A practitioner who collapses the two will assume that "we validate against outcomes" settles the framing question, when the substantive decision — outcome versus form versus process — was made before any validation ran.
The prime is also distinct from goodharts_law, with which it is bound in a stance-versus-pathology relationship. goodharts_law is a failure mode: when a measure becomes a target, the measured proxy decouples from the underlying outcome under optimization pressure, so the metric improves while the real thing it stood for stagnates. Outcome-defined adequacy is the legitimate framing that creates the opening for that pathology — because adequacy is judged by an operational outcome-spec, and the operational measure is almost always a proxy for the true outcome, the gap between proxy and outcome is exactly where Goodhart drift lives. The relationship is generative, not equivalence: outcome-definition is a deliberate, often correct stance whose enabling condition (verification by a measurable proxy) happens to be Goodhart's precondition. Confusing the two leads to opposite errors — treating every outcome framing as inevitably corrupt (over-applying Goodhart as a veto), or adopting an outcome framing while forgetting that its proxy is gameable (ignoring Goodhart entirely). The discipline is to hold both: choose the outcome framing on purpose and instrument the proxy-to-outcome gap that Goodhart predicts.
Finally, outcome-defined adequacy should be separated from summative_assessment, which is often mistaken for it because both render an end-state verdict on whether something is good enough. summative_assessment is an evaluative occasion — a terminal, often institutional judgement passed at the end of a process (a final exam, a year-end review, a certification decision), defined by its timing and finality rather than by what it measures. Outcome-defined adequacy is orthogonal to that timing: a summative assessment can be form-defined (did the candidate follow the rubric's required steps?), process-defined (was the prescribed method used?), or outcome-defined (did the candidate produce the result, however they got there?). The prime picks out only the last of these, and it applies equally to non-summative, continuous evaluation. A practitioner who equates the two will assume that because an assessment is final it must be outcome-based, missing that the most consequential summative judgements are frequently form- or process-defined — and that the framing choice, not the summative timing, is what determines the failure modes in play.
These distinctions matter because each isolates the prime's actual content — the placement of the spec — from things adjacent to it. Confusing it with validation swaps the framing choice for the verification act that follows it; confusing it with goodharts_law swaps a legitimate stance for the pathology it merely enables; confusing it with summative_assessment swaps a criterion-type for an occasion-type. Keeping the prime narrow — adequacy specified by outcome, form left open — lets a practitioner see that disputes about whether something "works" are usually disputes about which framing is in force, and that the choice of framing is the substantive move others treat as a neutral preliminary.
Solution Archetypes¶
No catalogued solution archetypes reference this prime yet.