Normative Assumption Explicitness¶
Make value judgments and ought-claims explicit before treating them as neutral facts.
Essence¶
Normative Assumption Explicitness makes hidden value judgments visible before they harden into policy, metrics, models, rankings, thresholds, or designs. The archetype does not ask teams to pretend values are absent. It asks them to stop treating value choices as if they were neutral facts.
The core move is simple: identify what the decision assumes ought to matter, where that standard comes from, who is affected by it, what competing norms were possible, why the selected standard is acceptable in this context, and when it should be reopened.
Compression statement¶
When a decision, metric, model, policy, or design appears objective while depending on unstated judgments about what ought to matter, Normative Assumption Explicitness identifies the normative claims, names their sources, maps affected parties, compares competing norms, documents rationale, and defines how those assumptions can be contested or revisited.
Canonical formula: apparently_neutral_decision + hidden_ought_claims -> normative_claim_inventory + value_sources + affected_party_map + competing_norms + decision_rationale + contestation_and_review
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A policy, model, metric, design, or decision is framed as objective, technical, natural, inevitable, or merely evidence-based while relying on unstated value judgments about what should count, which outcomes matter, whose interests matter, what risks are acceptable, and which tradeoffs are legitimate.
What this problem means
The structural problem is false neutrality. A system presents a decision as technical, objective, scientific, efficient, or evidence-based, but the decision depends on unstated assumptions about what should count, what should be optimized, what risks are acceptable, and whose outcomes matter.
Hidden normative assumptions create several predictable harms. They prevent affected parties from understanding why a decision was made. They shift value conflict into technical language. They make contestation look irrational because the real ought-claim is never named. They also make later revision difficult because no one knows which value premise the original decision depended on.
Applicability expression4 distinct conditions
groundedpartly groundedopen
Equivalent to the 3 condition sets it replaces, with 2 duplicate condition cards removed.
1Required in every casenumbered 1–1
These hold no matter which pattern applies.
Load-bearing evaluative premise · open
An unstated evaluative premise is load-bearing in the ostensibly neutral decision artifact.
This condition preserves a load-bearing part of the diagnostic problem that was not captured by a source-condition atom. It remains explicit because omitting it would weaken the sufficient condition set.
3At least one of theselettered A–C
Any single one of these completes the pattern.
Claimed value neutrality · open
A decision is presented as value-neutral.
They also make later revision difficult because no one knows which value premise the original decision depended on. The narrower requirement in this condition set is: A decision is presented as value-neutral.
Success-defining metric · grounded
A metric or target defines what counts as success.
The source archetype describes the situation as follows: A metric or target defines success. The normalized requirement above isolates the load-bearing portion used in this condition set.
primeOutcome-Defined Adequacy— Adequacy is specified by whether a defined outcome is produced in context, leaving the form open to any realization that achieves it.
Values disguised as facts · open
Stakeholders' value disagreement is disguised as factual or technical disagreement.
The source archetype describes the situation as follows: Stakeholders disagree but the disagreement is disguised as factual or technical. The normalized requirement above isolates the load-bearing portion used in this condition set.
Other requirements and context (3)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Supporting contextA rule affects rights, burdens, eligibility, or opportunity.
Use this archetype when a decision claims neutrality while allocating benefit, burden, risk, opportunity, credibility, attention, or protection. In this archetype, the relevant contextual consideration is: A rule affects rights, burdens, eligibility, or opportunity. It helps interpret the situation or strengthens the practical case for examining the archetype.
Application gateA model or process automates prioritization.
It is especially useful when a metric defines success, a model automates prioritization, a policy creates eligibility, or a design choice makes one value easy and another value costly. In this archetype, the relevant application gate is: A model or process automates prioritization. It narrows when choosing or applying the archetype is warranted or decision-relevant.
Supporting contextA governance decision needs public or organizational legitimacy.
Coverage
1 of 4 conditions grounded · 3 open.
When to Use This Archetype¶
Use this archetype when a decision claims neutrality while allocating benefit, burden, risk, opportunity, credibility, attention, or protection. It is especially useful when a metric defines success, a model automates prioritization, a policy creates eligibility, or a design choice makes one value easy and another value costly.
It is also useful when people seem to be arguing about facts but are actually disagreeing about standards. For example, a team may debate whether a threshold is “accurate enough,” while the deeper question is whether false positives or false negatives are more acceptable for the people affected.
Structural Problem¶
The structural problem is false neutrality. A system presents a decision as technical, objective, scientific, efficient, or evidence-based, but the decision depends on unstated assumptions about what should count, what should be optimized, what risks are acceptable, and whose outcomes matter.
Hidden normative assumptions create several predictable harms. They prevent affected parties from understanding why a decision was made. They shift value conflict into technical language. They make contestation look irrational because the real ought-claim is never named. They also make later revision difficult because no one knows which value premise the original decision depended on.
Intervention Logic¶
The intervention begins by locating the decision surface: a metric, model, rule, ranking, threshold, policy, budget, product choice, or evaluation frame. The next step is to extract the normative claims embedded in that surface. What is being treated as success? What risk is tolerated? What duty is being prioritized? What kind of fairness is assumed? What is being sacrificed?
The archetype then separates empirical claims from value claims. Evidence can show what is likely, but it does not by itself decide what should matter. Once that boundary is visible, the intervention names value sources, maps affected parties, compares competing norms, records the accepted rationale, and defines contestation and review conditions.
The output is not merely a statement of values. It is a governed assumption record: what value premise guided action, why it was accepted, what alternatives were considered, who is affected, where dissent remains, and when the premise should be reopened.
Key Components¶
Normative Assumption Explicitness converts a decision's hidden value premises into an inspectable record by separating what is being claimed, where the claim comes from, who it affects, and how it can be challenged. The Normative Claim names the ought-statement embedded in the decision — what should outrank what — that would otherwise pass as technical necessity. The Value Source identifies the authority behind that claim, whether law, mission, professional duty, community expectation, or informal norm, so the claim's legitimacy can be inspected. The Fact–Value Boundary does the analytic work of distinguishing empirical estimates from value judgments, so evidence is not used to silently settle questions evidence cannot decide. Together these three components turn an apparently neutral decision into a layered, traceable structure.
The remaining components govern the social and procedural surround. The Affected Party Map prevents value rationales from being constructed only from the position of those with institutional power, and a Competing Norm keeps the chosen standard visible alongside the alternatives it displaced — without that contrast, the rationale is too weak to evaluate. The Decision Rationale records why the chosen priority was accepted in this scope, while a Contestation Channel gives affected parties or reviewers a defined way to push back, preventing explicit values from becoming polished justifications for predetermined choices. The Assumption Record preserves the full memory of the intervention — claim, source, parties, alternatives, rationale, and dissent — so later audit and learning can examine the value premise rather than guess at it. Finally, the Review Trigger defines when the assumption must be reopened, recognizing that legitimacy in one context, stakeholder set, or time period does not silently extend to others.
| Component | Description |
|---|---|
| Normative Claim ↗ | A normative claim is the ought-claim hidden inside the decision. It may say that safety should outrank autonomy, that efficiency should outrank customization, that accuracy should outrank explainability, or that consistency should outrank contextual adjustment. Naming this claim prevents it from disguising itself as technical necessity. |
| Value Source ↗ | A value source explains where the standard comes from. It may come from law, policy, mission, professional duty, community expectation, user preference, safety culture, or informal organizational norms. A value source does not automatically settle the issue, but it makes the claim’s authority and legitimacy inspectable. |
| Affected Party Map ↗ | An affected party map identifies who benefits, who bears risk, who is constrained, and who needs a way to contest the assumption. This component keeps values from being defined only by those with technical or institutional power. |
| Competing Norm ↗ | A competing norm is a credible alternative standard. For example, a school assessment might value test performance, learning growth, inclusion, wellbeing, or long-term capability. The intervention is weak if it only states the winning value. It becomes useful when it also shows what alternatives were displaced. |
| Decision Rationale ↗ | The decision rationale records why a particular normative assumption was accepted in context. It should explain the chosen value priority, the rejected alternatives, the scope of the choice, and the conditions that would justify revision. |
| Fact–Value Boundary ↗ | The fact–value boundary separates empirical claims from value claims. A risk model may estimate likelihood; a policy still decides which risks are acceptable. A performance metric may measure speed; a governance decision still decides whether speed should count as success. |
| Contestation Channel ↗ | A contestation channel gives affected parties or reviewers a way to challenge the assumption. Without this channel, explicit values can become a polished explanation for a predetermined choice. |
| Assumption Record ↗ | The assumption record preserves the claims, sources, affected parties, alternatives, rationale, and review triggers. It is the memory of the intervention and supports future audit, learning, and accountability. |
| Review Trigger ↗ | A review trigger defines when the normative assumption should be reopened. Triggers may include new harms, stakeholder change, legal change, metric drift, deployment in a new context, or evidence that the chosen value priority is producing unacceptable effects. |
Common Mechanisms¶
9 documented mechanisms across 4 implementation forms.
The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.
Assessment, Review & Assurance · 4 mechanisms
- Ethical Impact Assessment — Captures foreseeable ethical consequences of applying or adapting a decision across contexts, including who benefits and who bears risk.
- Ethics Checklist — Prompts reviewers to ask value, harm, consent, fairness, transparency, and responsibility questions. It implements the archetype only when answers are recorded and contestable.
- Metric Value Review — Examines what a metric rewards, ignores, normalizes, or sacrifices, especially when the metric is treated as objective evidence of success.
- Value Audit — Reviews a policy, model, metric, or process to identify hidden value priorities, displaced alternatives, affected parties, and unsupported legitimacy claims.
Communication, Facilitation & Learning · 1 mechanism
- Stakeholder Deliberation — Creates a forum where affected parties and decision makers can compare normative claims, contest assumptions, and clarify acceptable tradeoffs.
Record, Log & Register · 1 mechanism
- Decision Record — Stores the chosen value assumptions, decision rationale, rejected alternatives, and review triggers so the decision remains accountable over time.
Representation, Specification & Plan · 3 mechanisms
- Model Card Value Section — Adds explicit value assumptions, intended uses, excluded uses, affected groups, and evaluation priorities to technical documentation for AI or analytic systems.
- Policy Rationale Statement — Records the values, affected parties, evidence, alternatives, and reasons behind a policy or governance decision.
- Values Statement — Names organizational or project values that can anchor later rationale. It is only a mechanism; the archetype requires linking those values to actual decision assumptions and tradeoffs.
Parameter / Tuning Dimensions¶
Explicitness depth determines how much detail is required. A low-stakes decision may need only a brief note. A high-stakes automated decision may need a full assumption record, stakeholder review, alternatives analysis, and formal review triggers.
Participation scope determines who helps surface and contest assumptions. Internal review may be enough for low-risk work. Public policy, healthcare triage, AI screening, or eligibility systems often require affected-party input.
Rationale formality determines whether the output is a lightweight note, decision record, policy rationale, audit report, or formal documentation. More durable or repeated decisions need more durable rationale.
Norm conflict granularity determines how carefully competing values are compared. Some decisions need a short list of alternatives; others need a matrix that shows how options affect autonomy, safety, equity, efficiency, privacy, dignity, and accountability.
Review cadence determines whether the assumption is reviewed once, periodically, or when triggered by harm reports, drift, new stakeholders, or context change.
Invariants to Preserve¶
The first invariant is the fact–value distinction. Evidence can guide a decision, but evidence does not erase the need to say what should matter.
The second invariant is affected-party visibility. The people who bear risk or burden should not disappear from the value rationale.
The third invariant is competing norm visibility. A chosen value should be visible alongside the credible alternatives it displaces.
The fourth invariant is contestability. Explicit assumptions should be open to challenge through defined channels.
The fifth invariant is scope discipline. A value assumption accepted in one context should not silently govern every context.
Target Outcomes¶
A successful use of the archetype produces more honest decision rationale. Decision makers can explain not only what they chose but what standard made the choice acceptable.
It reduces false neutrality. Technical language no longer hides the underlying value choices.
It improves governance of models, metrics, and policies by making targets, thresholds, rules, and priorities reviewable.
It improves stakeholder trust where disagreement is inevitable, because people can see and contest the assumptions shaping outcomes.
It also improves revision. When a decision later fails, reviewers can examine the value premise rather than guessing what the original choice meant.
Tradeoffs¶
The main tradeoff is speed. Normative explicitness takes time, especially when affected parties must be included. The solution is proportionality: use lightweight records for low-stakes decisions and deeper review for high-stakes or contested decisions.
Another tradeoff is contestability versus closure. The goal is not endless debate. The archetype should define how assumptions can be challenged and when enough review has occurred for action.
A third tradeoff is transparency versus strategic ambiguity. Sometimes ambiguity helps a coalition move forward, but hidden values can later produce mistrust when consequences become visible.
A fourth tradeoff is breadth of participation. Wider participation reveals more values and harms, but it requires representation choices, facilitation, and decision rules.
Failure Modes¶
Ethics theater occurs when the organization fills out a checklist or publishes values without changing actual decision rationale. Mitigation: link every value claim to a concrete decision, affected-party implication, competing norm, and review trigger.
Hidden priority remains hidden occurs when a record lists many values but refuses to say which value wins in conflict. Mitigation: require comparison of competing norms and document the accepted priority for the current context.
False consensus occurs when one value source is treated as universal. Mitigation: record dissent, map affected parties, and provide contestation channels.
Over-philosophizing occurs when the process turns into abstract moral debate. Mitigation: anchor the discussion in a decision surface: a rule, metric, model, threshold, policy, or design choice.
Paralysis from infinite contestation occurs when no closure rule exists. Mitigation: pair this archetype with a regress termination rule or decision closure criterion.
Expert capture occurs when technical or legal experts define the values without affected-party knowledge. Mitigation: combine with epistemic inclusion design, lived experience capture, or stakeholder deliberation.
Neighbor Distinctions¶
Procedural Fairness Design designs fair process: voice, notice, impartiality, reasons, and appeal. Normative Assumption Explicitness names the value premises that guide the decision. They often combine but are not the same.
Objective Weighting Governance governs how objectives are weighted in optimization or scoring systems. Normative Assumption Explicitness is broader and includes nonnumeric decisions, policies, metrics, and designs.
Stakeholder Mapping and Engagement identifies and engages affected parties. This archetype uses stakeholder understanding to expose and govern hidden ought-claims.
Goal Congruence Alignment aligns behavior with accepted goals. Normative Assumption Explicitness asks whether the goals or standards themselves contain hidden values.
Epistemic Inclusion Design protects fairness in knowledge production. Normative Assumption Explicitness protects transparency of value premises. Epistemic inclusion may be necessary when excluded knowers can reveal hidden assumptions.
Purpose Alignment Design aligns means with an accepted purpose. Use Normative Assumption Explicitness when the purpose or the values inside that purpose are hidden or contested.
Cross-Domain Examples¶
In AI hiring, a screening tool may define success using a label that rewards prior corporate experience. The archetype asks the team to state the value assumption, compare it with alternatives such as potential and equity, map affected candidates, and revise the rationale or label.
In public health, a vaccination policy may be described as purely scientific. The evidence matters, but the policy also contains assumptions about liberty, collective protection, trust, and acceptable risk. The archetype separates those layers.
In product design, a platform may optimize engagement and call the choice user-centered. Normative explicitness asks whether engagement should be treated as wellbeing, autonomy, revenue, habit formation, or something else.
In education, a school ranking may reward test scores while ignoring learning growth, inclusion, or wellbeing. The archetype makes the values embedded in ranking criteria visible.
In organizational promotion, a process may claim meritocracy while rewarding visibility, hours, self-promotion, or risk-taking. Normative explicitness reveals what “merit” actually means in the system.
Non-Examples¶
A generic ethics seminar is not this archetype unless it changes how a concrete decision records and governs value assumptions.
A values poster is not this archetype. It becomes relevant only when those values are linked to decisions, tradeoffs, affected parties, and review conditions.
A purely statistical confidence interval is not this archetype. It expresses uncertainty, not what outcome should matter.
A stakeholder list without value analysis is not this archetype. It can support the work, but the intervention requires surfacing and governing ought-claims.
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 (2)
- Normativity: What ought to be.
- Procedural Fairness (Due Process): Due process.
Also references 8 related abstractions
- Consent: Voluntary agreement.
- Epistemic Justice: Fair knowledge production.
- Goal Congruence (Alignment): Alignment of objectives.
- Legitimacy: Accepted authority.
- Moral Relativism: Morality depends on context.
- Trade-offs: Balancing competing priorities.
- Transparency: Open processes.
- Virtue Ethics: Focus on character traits.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Metric Value Review · domain variant · recognized
A metric-focused variant that asks which values are embedded in what is measured, optimized, rewarded, or declared successful.
- Distinct from parent: The parent can apply to any decision or design; this variant focuses on metrics as the carrier of value assumptions.
- Use when: A key decision is being governed by a metric, score, ranking, KPI, threshold, benchmark, or performance target; Stakeholders treat the metric as neutral even though the metric selects what should count as success; Metric gaming, Goodhart-style distortion, fairness concerns, or missing dimensions are plausible.
- Typical domains: AI evaluation, organizational performance, education assessment, healthcare quality
- Common mechanisms: metric value review, model card value section, decision record
Policy Rationale Explicitness · governance variant · recognized
A governance-focused variant that requires policies to state the value premises and balancing judgments behind their rules.
- Distinct from parent: The parent applies broadly; this variant emphasizes formal rules, public reasons, administrative standards, and decision records.
- Use when: A policy affects people who need to understand why the rule exists and what values it protects; The policy could be seen as arbitrary, biased, opaque, or merely bureaucratic if its normative rationale is hidden; Rule exceptions, appeals, or public legitimacy depend on knowing what the policy is trying to preserve.
- Typical domains: public policy, organizational governance, platform rules, professional standards
- Common mechanisms: policy rationale statement, stakeholder deliberation, decision record
Algorithmic Value Assumption Audit · domain variant · recognized
A technical-system variant that surfaces the normative choices embedded in datasets, labels, targets, thresholds, loss functions, deployment constraints, and evaluation priorities.
- Distinct from parent: The parent is technology-neutral; this variant names the recurring AI/data-system pathway by which normative choices become hidden.
- Use when: A model, ranking system, scoring system, or automation workflow is presented as objective because it is technical; Design choices allocate benefits, burdens, false-positive risks, false-negative risks, or opportunities across groups; Documentation needs to explain not only performance but also the values encoded in performance criteria.
- Typical domains: AI systems, credit scoring, hiring tools, healthcare triage
- Common mechanisms: model card value section, ethical impact assessment, metric value review
Objective Weighting Disclosure · governance variant · merge review
A weighting-focused variant that discloses how competing objectives are prioritized when a decision procedure combines them.
- Distinct from parent: The parent covers hidden value assumptions generally; this variant targets the special case where values are encoded as weights.
- Use when: A score, optimization model, prioritization rule, or ranking depends on weights among competing objectives; The chosen weights determine who benefits, who bears risk, or which outcome is treated as more important; Stakeholders may incorrectly assume that the weights are dictated by math rather than value judgment.
- Typical domains: multiobjective optimization, grant scoring, public budgeting, product prioritization
- Common mechanisms: metric value review, stakeholder deliberation, decision record
Near names: Value Assumption Audit, Hidden Value Audit, Normative Assumption Audit, Ought-Claim Disclosure, Ethics Checklist, Values Statement.
Editorial Notes¶
Problem Classification¶
Classification: Goal, Value & Purpose Misalignment → Normative Standard & Weighting Choice
Problem kernel: technical framing conceals contestable value assumptions
Rationale: Earliest causal condition: A policy, model, metric, design, or decision is framed as objective, technical, natural, inevitable, or merely evidence-based while relying on unstated value judgments about what should count, which outcomes matter, whose interests matter, what risks are acceptable, and which tradeoffs are legitimate.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A policy, model, metric, design, or decision is framed as objective, technical, natural, inevitable, or merely evidence-based while relying on unstated value judgments about what should count, which outcomes matter, whose interests matter, what risks are acceptable, and which tradeoffs are legitimate. That is a normative standard and weighting choice problem because A supposedly technical criterion embeds contestable choices about fairness, error costs, stakeholder interests, time, risk, and objective weights.
Review outcome: Independent reviewer agreement; high confidence.