Evidence, Inference & Validation

← Back to Mechanisms by Solution Family

Solutions that gather, test, triangulate, or qualify evidence so claims and decisions match what the observations can actually support.

428 mechanisms across 52 solution archetypes in this solution family. A mechanism inherits the primary family of the archetype it instantiates; family is about the move the solution makes, not the domain where it originated.

Archetype Overview

This unusually large family has a compact overview for orientation. Each archetype name jumps to its fully visible section below.

Solution archetype	Mechanisms	Description
Abductive Explanation Selection	8	Turn a surprising observation into a ranked, provisional best explanation, while keeping rivals, uncertainty, and revision triggers visible.
Aggregation Bias Detection and Correction	8	Protect decisions from misleading aggregate summaries by disaggregating the data, comparing subgroup and overall patterns, correcting composition effects, and restating only the claims the evidence can support.
Alternative-Hypothesis Generation	6	Before treating a conclusion as settled, generate credible alternative explanations and identify the evidence that would distinguish them.
Appearance vs. Reality Distinction Audit	7	Separate what is warranted by experience, perception, report, or instrumented appearance from what is being claimed about underlying or mind-independent reality.
Associative Transfer Warrant Audit	8	Do not let contact, co-membership, resemblance, endorsement, or proximity carry trust, blame, risk, quality, or credibility unless the link has a valid transfer warrant.
Assumption-Light Inference	9	Use inference methods that require fewer fragile assumptions when strong assumptions are unjustified.
Bayesian Belief Updating	6	Revise beliefs by combining prior expectations with new evidence rather than treating each observation in isolation.
Belief Revision Workflow	6	Create a structured path for updating beliefs when new evidence conflicts with prior assumptions.
Blinding and Expectancy Bias Reduction	9	Hide condition identity from the roles that could be biased by knowing it, while preserving safety, correct operation, and auditable exceptions.
Cascade Initiation Bias Diagnosis and Correction	8	Identify who set the cascade in motion, test whether they actually had better information, and re-expose the underlying evidence so later actors can decide independently.
Causal Mechanism Mapping	8	Map the mechanism connecting a proposed cause to an effect before intervening.
Comparative Benchmark Validation	7	Validate a claim by comparing the system against explicit reference standards, gold standards, incumbent alternatives, competitors, or benchmark suites under conditions that make the comparison meaningful.
Confounder Control	10	Prevent hidden third variables from distorting the apparent relationship between cause and effect.
Contrapositive Elimination Reasoning	10	Rule out a candidate by showing that a consequence it must produce is reliably absent.
Counterexample Search	5	Actively search for cases that would break a proposed rule, pattern, or generalization before treating it as reliable.
Counterfactual Comparison	6	Compare what happened with a plausible alternative to isolate causal effect or decision value.
Deductive Chain Validation	7	Validate that conclusions actually follow from stated rules and premises before acting on them.
Distributional-Assumption Governance	10	Make probability-distribution commitments explicit, evidence-grounded, consequence-aware, stress-tested, and revisable before they govern inference or action.
Effect Size Standardization	9	Convert raw inferred effects into comparable, uncertainty-bounded magnitude expressions so evidence can be judged by size and practical meaning, not only by detectability.
Effort-Based Vs. Inherent Ability Attribution	8	Interpret success and failure through controllable effort, strategy, practice, evidence quality, and luck/noise before treating the outcome as proof of inherent ability.
Emic-Etic Dual-Account Interpretation	8	Preserve insider and outsider descriptions as separately governed accounts, then use their mismatch as evidence instead of forcing premature translation into one frame.
Evidentiary Trace Warranting	8	Treat evidence as a defeasible relation between a trace and a claim, not as raw data or free-floating support.
Generalization Validation	9	Test whether a pattern learned from specific cases works on new cases outside the original fit.
Hypothesis Test Power Calibration	7	Design a hypothesis test around the effect that would actually matter, then tune sample size, noise control, allocation, and error rates so the test has adequate power to detect it.
Hypothesis Testing Frame	10	Frame a claim against a default alternative so evidence can change belief or action under explicit error risks.
Independent Convergence Evidence Appraisal	7	Treat repeated independent arrival at the same solution-shape as evidence of fit only after auditing independence, shared pressures, abstraction level, and alternative explanations for the convergence.
Independent Evidence Triangulation	10	Cross-check a scoped claim with multiple meaningfully independent evidence streams, using both convergence and divergence to calibrate confidence and expose hidden dependence, bias, or context.
Informal Fallacy Diagnosis and Repair	10	Repair arguments that can look formally valid but fail because their premises, context, relevance, or category moves are defective.
Information Set Specification and Completeness Verification	8	Do not ask whether a price or signal is simply “efficient”; specify the information set it should reflect, then test whether available information and residual opportunities show complete incorporation.
Knowledge-Warrant Audit	9	Audit what each belief rests on, classify the strength and type of its warrant, and adjust confidence or action accordingly.
Lived Experience Capture	5	Capture first-person lived experience so systems are not designed, evaluated, or governed only from external metrics, expert categories, or institutional assumptions.
Longitudinal Follow-Up Validation	8	Treat validation as a time-extended claim by checking whether outcomes, harms, and operating assumptions still hold after deployment and accumulated exposure.
Metanarrative Coherence and Internal Consistency Check	8	Turn a sweeping story into an auditable claim structure, then test whether its claims, exceptions, evidence links, and implied conclusions can all hold together.
Minimal-Disclosure Verification	10	Make a verifier confident that a bounded claim is true without handing over the underlying witness, record, identity attributes, or computation trace.
Missingness-Aware Estimator Selection	10	Choose the missing-data estimator only after stating why values are absent and what assumption makes the target estimand recoverable.
Multiple-Testing Discipline	10	Control false discoveries when many comparisons, claims, or tests are being tried.
Null Finding Warrant Calibration	8	Treat a failure to find something as evidence of absence only after calibrating whether the search would probably have detected it if it were present.
Parallel Independent Inspection Design	10	Find more hidden defects by having multiple independent and diverse inspectors examine overlapping parts of the same artifact before their findings are reconciled.
Pattern Detection with Validation	5	Detect recurring patterns while guarding against seeing patterns that are not really there.
Propositional Mode Governance	10	Keep propositions in the right epistemic mode and permit only the operations that mode licenses.
Rapid Prototype Learning Loop	8	Build a low-cost version to test a specific assumption before committing to full implementation.
Recursive Triangulation of Triangulation	8	When a conclusion already rests on triangulation, audit the triangulation itself by checking whether its evidence streams are independent, its convergence logic is valid, and its confidence claim survives a second-order triangulation layer.
Regression-to-the-Mean Guardrail	10	Prevent ordinary reversion after extreme observations from being credited to an intervention, person, punishment, reward, or event without a credible counterfactual.
Representative Sampling Design	8	Select observations so the sample can credibly stand in for the population or system being judged.
Revision-Readiness Precommitment	5	Specify in advance what evidence would change a belief, forecast, diagnosis, or strategy so that later revision is easier, more accountable, and less vulnerable to motivated reinterpretation.
Shared or Not Yet Assigned	2	Mechanisms shared across, or not yet assigned to, a single primary solution archetype.
Shared-Source Variance Isolation	8	Prevent a single hidden source from making multiple supposedly independent dimensions look more correlated than they really are.
Source Distortion Modeling	8	Treat a report from a systematically distorted source as a biased channel to be modeled, not as either transparent truth or useless noise.
Source Provenance Triangulation	6	Evaluate an account by tracing source type, origin, proximity, perspective, corroboration, and confidence before treating its claims as settled.
Theory-Responsive Case Sampling Design	10	Select the next case because it can sharpen, challenge, extend, or saturate the emerging account—not because it statistically represents a population.
Use-Time Source Attribution Calibration	12	Before using a commingled memory, note, claim, trace, or generated output, classify where it came from and how certain that attribution is.
User Context Validation	10	Validate a solution against actual user behavior, needs, constraints, and context of use.
Warranted Belief Formation	8	Turn a proposition into a responsible belief only after clarifying its meaning, warrant, confidence, scope, action consequences, and conditions for revision.

Abductive Explanation Selection

Turn a surprising observation into a ranked, provisional best explanation, while keeping rivals, uncertainty, and revision triggers visible.

8 mechanisms · View full solution archetype

• Abduction Log — A running record of explanation changes, retired rivals, new evidence, and revision triggers.
• Anomaly-to-Hypothesis Workshop — A facilitated session that converts anomalies into candidate hypotheses while preserving dissent and uncertainty.
• Differential Diagnosis Workup — Lists candidate conditions or causes, weighs symptoms and tests, and narrows to a working diagnosis.
• Disconfirming Probe Plan — Specifies the observations or tests most likely to overturn the current best explanation.
• Explanatory Case Memo — Records the observation, candidate explanations, comparison rationale, confidence, and next probes for audit or handoff.
• Forensic Scenario Reconstruction — Builds and compares scenarios that could have produced observed traces while preserving uncertainty about alternatives.
• Inference-to-Best-Explanation Matrix — Compares candidate explanations against explanatory fit criteria and records the provisional winner.
• Model-Debugging Hypothesis Loop — Uses surprising model behavior to form, test, and revise explanations about data, architecture, prompts, or deployment context.

Aggregation Bias Detection and Correction

Protect decisions from misleading aggregate summaries by disaggregating the data, comparing subgroup and overall patterns, correcting composition effects, and restating only the claims the evidence can support.

8 mechanisms · View full solution archetype

• Ecological Fallacy Guardrail — Blocks group-level statistics from being read as individual-level claims by fixing the unit of analysis and the boundary of what the aggregate is allowed to mean.
• Multilevel Modeling Review — Reviews whether a nested-data claim needs partial pooling — borrowing strength across groups so small subgroups are neither over-trusted nor erased.
• Poststratification or Reweighting — Corrects an aggregate whose sample composition differs from the target population by reweighting subgroups to a declared, auditable population basis.
• Representativeness and Nonresponse Review — Checks whether differential participation or missingness has skewed the aggregate away from the population it claims to describe, and bounds the claim accordingly.
• Sensitivity Analysis by Group — Re-runs the aggregate under alternative groupings, weights, windows, and exclusions to see whether the conclusion survives the choices that produced it.
• Simpson's Paradox Check — Tests whether an aggregate relationship reverses or materially changes once a confounder or composition variable is conditioned on — the fingerprint of a Simpson reversal.
• Stratified Analysis Protocol — Splits an aggregate into pre-declared strata and compares each subgroup's pattern against the pooled figure, so hidden heterogeneity surfaces before the claim is trusted.
• Subgroup Dashboard with Warning Flags — Shows aggregate and subgroup figures side by side with rules that flag masked harm, unstable small cells, and equity-relevant gaps as they arise.

Alternative-Hypothesis Generation

Before treating a conclusion as settled, generate credible alternative explanations and identify the evidence that would distinguish them.

6 mechanisms · View full solution archetype

• Base-Rate Alternative Prompt — Asks how often the leading explanation actually holds in cases like this — dragging the boring, common alternative that the reference class favors onto the table before a vivid but rare story is accepted.
• Counter-Narrative Probe — Builds the single strongest opposing account of the same facts — the version a sharp skeptic would defend — derives what it predicts we should see, and checks, so the leading story has to beat a real challenger instead of a strawman.
• Differential Diagnosis List — Enumerates a bounded, ranked list of candidate explanations for the same findings — including the unlikely-but-dangerous ones — then rules each in or out as evidence arrives, so the answer is the survivor of a field rather than the first guess.
• Discriminating Test Matrix — A grid crossing rival hypotheses against pieces of evidence, scoring each cell for consistency and each row for reliability — so effort goes to the observations that actually separate the rivals rather than to evidence that fits them all.
• Red-Team Rival Explanation Review — A structured review in which an assigned adversary must generate and defend rival explanations against the group's favored conclusion, and the team must answer them on the record before confidence is allowed to settle.
• Why Else Could This Be True? Prompt — A single forcing question — 'why else could this be true?' — asked before confidence hardens, that makes the reasoner produce several other explanations fitting the same facts, converting one satisfying story into a field of candidates.

Appearance vs. Reality Distinction Audit

Separate what is warranted by experience, perception, report, or instrumented appearance from what is being claimed about underlying or mind-independent reality.

7 mechanisms · View full solution archetype

• Appearance/Reality Audit Checklist — Prompts reviewers to ask whether a statement describes experience, measurement, inference, social convention, or mind-independent reality.
• Bridge Assumption Annotation Protocol — Requires analysts to annotate the assumptions used when converting appearances or observations into stronger causal or object-level claims.
• Claim Tagging Matrix — Lists claims in rows and tags each by source, claim type, warrant level, bridge assumptions, and calibrated wording.
• Observation Warrant Ladder — Defines levels of claim strength from raw report through corroborated measurement to robustly inferred reality claim.
• Perceived-vs-Measured Performance Dashboard — Shows subjective user/operator perceptions alongside behavioral, telemetry, or task-performance measures without collapsing one into the other.
• Sense-Condition Rewrite Template — Rewrites an object-level claim into the possible experiences, observations, or tests that would give it empirical content.
• Symptom–Biomarker Crosswalk — Separates patient-reported experience, clinical observations, biomarkers, and diagnostic inferences in medical contexts.

Associative Transfer Warrant Audit

Do not let contact, co-membership, resemblance, endorsement, or proximity carry trust, blame, risk, quality, or credibility unless the link has a valid transfer warrant.

8 mechanisms · View full solution archetype

• Association-to-Evidence Matrix — Lists each association, the property allegedly transferred, the warrant channel claimed, available evidence, counterevidence, and permitted decision use in one reviewable grid.
• Associative Claim Red Team — Challenges a proposed property transfer by asking what would have to be true for the association to be warrant-bearing and what evidence would refute it.
• Category-Membership Attribution Audit — Tests whether a property has been attributed to an individual or item merely because it belongs to a category, class, cluster, or population.
• Contact/Contagion Warrant Test — Distinguishes actual transmission or shared exposure from symbolic contact, mere proximity, or imagined contamination — and bounds any real channel by distance and decay.
• Endorsement Scope Checklist — Determines whether association with a person, brand, institution, funder, publisher, or platform is an endorsement, a neutral conduit, or an irrelevant co-location — and scopes what a real endorsement covers.
• Guilt-by-Association Review — Checks whether blame, risk, or disqualification is being assigned because of contact, affiliation, or co-membership without a valid transfer rule.
• Halo and Taint Decomposition Table — Separates positive halo, negative taint, aesthetic appeal, status borrowing, contamination fear, and evidence-bearing relations into distinct rated columns.
• Trust Transitivity Breakpoint Review — Identifies where trust, reputation, or certification stops transferring across a dependency or intermediary chain and renewed verification is required.

Assumption-Light Inference

Use inference methods that require fewer fragile assumptions when strong assumptions are unjustified.

9 mechanisms · View full solution archetype

• Assumption Audit Checklist — Enumerates the assumptions a planned inference rests on and flags which ones would change the conclusion if they failed — before any test is run.
• Bootstrap-Like Checks — Resamples the observed data with replacement to see whether an estimate holds still — gauging stability without trusting a parametric error formula.
• Diagnostic Plot Review — Reads fitted-data graphics to see whether a method's distributional and scale assumptions actually hold, catching violations a summary statistic hides.
• Median-Based Summaries — Reports the middle and the spread with order statistics — median, quantiles, IQR — so a few extreme values can't dominate the typical-case claim.
• Model Comparison Table — Lays the same question's answers side by side under strong and assumption-light frames, turning method disagreement into a visible, decidable finding.
• Nonparametric Tests — Compares groups or distributions with distribution-free tests chosen against a named assumption threat, not by software default.
• Permutation Tests — Builds an exact null by reshuffling the labels the hypothesis says are exchangeable, replacing a distributional assumption with a randomization one.
• Rank-Based Methods — Replaces raw values with their order positions so an inference leans on defensible ranking rather than unverified metric distance.
• Robust Statistics — Estimates with outlier-resistant methods whose conclusions survive a handful of extreme observations, then reports what that resistance costs.

Bayesian Belief Updating

Revise beliefs by combining prior expectations with new evidence rather than treating each observation in isolation.

6 mechanisms · View full solution archetype

• Adaptive Decision Threshold — Uses posterior belief levels to change when the system acts, escalates, monitors, or withholds action.
• Bayesian Diagnosis — Combines a base rate or pretest probability with test evidence to revise the plausibility of a condition, cause, or hidden state.
• Likelihood-Ratio Reasoning — Updates beliefs by comparing how likely the evidence is under one possibility versus another.
• Posterior Risk Estimation — Produces a revised probability or risk score after combining baseline risk with new indicators.
• Prior Sensitivity Analysis — Compares posterior conclusions under several plausible priors to see whether decisions are dominated by starting assumptions.
• Sequential Forecast Update — Revises a forecast as new observations arrive while preserving a record of prior forecast states and reasons for movement.

Belief Revision Workflow

Create a structured path for updating beliefs when new evidence conflicts with prior assumptions.

6 mechanisms · View full solution archetype

• Bayesian-Style Update Session — A working session that weighs new evidence against the prior belief — its diagnosticity, its source, and the base rate — to decide how far, and in which direction, confidence should actually move.
• Belief Update Log — A structured entry that pins the prior belief, the evidence that conflicted with it, and what the belief became — so no one can silently slide between the strong and weak versions of what they once claimed.
• Confidence Scale — A graduated vocabulary for stating how strongly a belief is held and how far it reaches — so an update can land as 'less confident,' 'narrower,' or 'watch this' instead of a forced true/false verdict.
• Decision Log Update — An amendment to the standing decision record that ties a revised belief to its governance consequences — which decision, condition, owner, and next-review point changed because the belief changed.
• Dissonance-Safe Dialogue — A facilitated conversation that separates changing your mind from losing face — externalizing the belief as an object under review so a person can revise it without it reading as personal defeat.
• Learning Retrospective — A recurring look-back that asks specifically which beliefs changed over the period, what evidence changed them, and how team practice should differ going forward — folding scattered revisions into shared learning.

Blinding and Expectancy Bias Reduction

Hide condition identity from the roles that could be biased by knowing it, while preserving safety, correct operation, and auditable exceptions.

9 mechanisms · View full solution archetype

• Blind Integrity Questionnaire — A questionnaire that asks masked roles what condition they believe they encountered and why.
• Blinded Data Analysis Plan — Pre-specifies every analytic decision before condition labels are revealed, so analyst discretion cannot be steered toward the favored result.
• Blinded Outcome Adjudication — A procedure in which evaluators judge outcomes from evidence packets that omit condition or source identity.
• Central Randomization and Masking Service — A central system that generates random assignments and releases only the coded, role-appropriate information each site needs to act.
• Double-Blind Trial Protocol — A protocol that masks both recipients and delivery personnel from knowing active versus comparator assignment.
• Emergency Unblinding Procedure — A controlled pathway that reveals one participant's assignment when safety requires it, under authorization and with a permanent record.
• Masked Label Codebook — A protected mapping between neutral labels and true conditions.
• Sham or Placebo Control — An inactive or alternative comparator designed to preserve credibility and mask active-condition identity.
• Single-Blind Participant Masking — Masks the recipient alone from knowing which condition they received, while implementers stay informed.

Cascade Initiation Bias Diagnosis and Correction

Identify who set the cascade in motion, test whether they actually had better information, and re-expose the underlying evidence so later actors can decide independently.

8 mechanisms · View full solution archetype

• Blind Independent Vote Reset — A repeated decision round in which participants reconsider evidence independently after cascade contamination has been disclosed.
• Common Source Citation Check — Traces repeated citations backward until they collapse to their origin, revealing how many endorsements share a single source.
• Decision Sequence Timeline — A timeline showing when visible actors acted and when later actors could observe those actions.
• Evidence Provenance Checklist — A checklist for classifying whether cited reasons are primary, secondary, independent, current, relevant, and verified.
• Initiator Interview Protocol — A structured interview process for recovering what early actors knew and why they acted.
• Network Position Review — Examines actors' network positions to separate structural centrality and status from a real information advantage.
• Private Signal Survey — Confidentially collects each actor's own private signal before social exposure, so genuine independent judgments can be counted separately from the visible cascade.
• Source Disclosure Brief — A concise communication explaining the source independence and confidence status behind a suspected cascade.

Causal Mechanism Mapping

Map the mechanism connecting a proposed cause to an effect before intervening.

8 mechanisms · View full solution archetype

• Causal Diagram — Draws candidate causes, effects, mediators, and confounders as a graph so the structure of a causal claim — including backdoor paths — can be inspected at a glance.
• Causal Inference Review — Audits the identification assumptions, comparison groups, confounders, and evidence behind a causal claim before it is accepted.
• Causal-Loop Map — Maps reinforcing and balancing feedback loops when causal influence cycles through a system rather than moving in a one-way chain.
• Contribution Analysis — Builds a plausible contribution story — assembling evidence and weighing other influences — when a clean control or randomized comparison is unavailable.
• Failure Tree Analysis — Traces an undesired top event down through the combinations of component failures and enabling conditions that can produce it.
• Intervention Test — Deliberately changes a chosen intervention point and watches whether intermediate and final outcomes move as the mechanism predicts.
• Mechanism Map — Decomposes a causal story into an ordered table of links, each with its actor, process, evidence, and uncertainty, so the weak links become visible.
• Theory of Change Model — Lays out how a program's activities are expected to produce outputs, outcomes, and impact through an explicit, testable causal pathway.

Comparative Benchmark Validation

Validate a claim by comparing the system against explicit reference standards, gold standards, incumbent alternatives, competitors, or benchmark suites under conditions that make the comparison meaningful.

7 mechanisms · View full solution archetype

• Benchmark Suite Coverage Matrix — Maps every benchmark case against the tasks, subgroups, operating conditions, and failure modes it exercises, so the blank cells — the parts of the domain nothing tests — become visible before a headline score is mistaken for a passing grade.
• Expert-Adjudicated Reference Panel — Convenes independent domain experts to adjudicate a defensible reference answer for each case — the ground truth a candidate is scored against — resolving rater disagreement by structured deliberation instead of trusting a single fallible authority.
• Gold-Standard Comparison Study — Runs the candidate against an authoritative reference standard and analyzes where they agree, where they disagree, and which of the two is right when they conflict.
• Held-Out Benchmark Dataset — A sealed partition of cases withheld from every stage of development and scored only at the end, so the number it yields reflects genuine generalization rather than what the builders were allowed to memorize.
• Noninferiority Margin Protocol — Fixes, before any data are seen, the largest performance shortfall from the comparator that will still count as acceptable — turning 'not meaningfully worse' into a pre-committed number when the candidate wins on cost, access, or convenience.
• Paired Comparison Experiment — Runs candidate and comparator over the very same units — the same cases, users, or time windows — so every difference in outcome is attributable to the systems and not to which cases each happened to face.
• State-of-the-Art Baseline Study — Pits the candidate against the strongest current alternative — a best-in-class rival made as good as it can be, not a convenient straw man — because a claim of superiority only means something relative to the best thing it must beat.

Confounder Control

Prevent hidden third variables from distorting the apparent relationship between cause and effect.

10 mechanisms · View full solution archetype

• Causal Diagramming — Draws the assumed causal structure — exposure, outcome, confounders, mediators, colliders — as a diagram, so the decision of what to control is made from the assumptions before the data, not by the data after the fact.
• Control Group Design — Builds or selects a comparison group that approximates what the outcome would have been without the exposure, so the exposed result is read against a counterfactual rather than in isolation.
• Instrumental Variable Strategy — Uses an external variable that shifts the exposure but has no other path to the outcome, isolating a slice of exposure variation that is free of confounding — including unmeasured confounding.
• Matched Comparison — Pairs each exposed unit with unexposed unit(s) alike on the measured confounders, so the compared groups are balanced on those variables by construction before any outcome is examined.
• Negative Control Check — Looks for an effect where none should causally exist — a negative-control outcome or exposure — and treats any apparent effect found there as evidence that confounding or bias still remains.
• Random Assignment — Assigns the exposure by chance, so that on average every confounder — named or unknown, measured or not — is balanced across groups without anyone having to identify it.
• Restriction or Eligibility Control — Limits the study to units within a narrow band where a confounder is constant or absent, removing its distorting power by never letting it vary in the first place.
• Sensitivity Analysis for Unmeasured Confounding — Asks how strong an unmeasured confounder would have to be to explain away the observed effect, converting an unanswerable 'what if something is hidden?' into an explicit robustness threshold.
• Statistical Adjustment — Models the outcome (or exposure) as a function of the measured confounders alongside the exposure, so the exposure's estimated effect reflects its relationship net of those variables.
• Stratified Analysis — Splits the data into strata within which a confounder is held roughly constant, estimates the exposure-outcome relationship inside each, then interprets or pools the stratum-specific results.

Contrapositive Elimination Reasoning

Rule out a candidate by showing that a consequence it must produce is reliably absent.

10 mechanisms · View full solution archetype

• Diagnostic Rule-Out Protocol — A stepwise clinical procedure that starts from a differential list of candidate diagnoses and safely removes those whose mandatory finding is absent, narrowing to the diagnoses that remain in play.
• Eligibility Element Exclusion Review — Rules an applicant ineligible by showing that one mandatory element of a conjunctive requirement is absent — while fixing the exact program and period the exclusion binds and the waivers that could defeat it.
• Elimination Decision Log — Keeps an append-only record of every candidate ruled out — the rule used, the absent consequence, and the confidence — so the surviving set stays explicit and each elimination is auditable and reversible.
• Falsification Test Harness — Turns a hypothesis's mandatory consequence into an executable test that actively tries to produce it, so a failure to observe the predicted result falsifies and eliminates the hypothesis.
• Modus Tollens Checklist — Runs a single conditional through the strict logical form — rewrite 'if A then B' as 'if not-B then not-A', confirm B is absent, and only then conclude A is false.
• Negative-Evidence Reliability Review — Scrutinizes a claimed absence before it is allowed to eliminate anything — asking whether the missing footprint could actually have been detected, whether the right place was searched, and whether the absence is strong enough to count.
• Required Consequence Table — Lays out, for every candidate under consideration, the consequences it must produce if true — the mandatory footprints whose absence would rule it out.
• Requirements Traceability Exclusion — Rules out the claim that a requirement is satisfied when its mandatory downstream trace — the test or evidence it must link to — is missing, scoped to a specific build or baseline.
• Rule-to-Observation Matrix — Crosses every candidate rule against every observation actually gathered, flags the cells where a required consequence is missing, and marks which cells could not have shown it anyway.
• Search-Branch Pruning Test — Prunes a branch of a search space the moment a solution down that branch is shown to require a consequence the branch cannot produce — collapsing the space to the branches that remain viable.

Counterexample Search

Actively search for cases that would break a proposed rule, pattern, or generalization before treating it as reliable.

5 mechanisms · View full solution archetype

• Adversarial Example Generation — Constructs hard inputs deliberately engineered to make a rule fail, then keeps only the ones that stay realistic enough to matter in the real operating scope.
• Boundary Condition Matrix — Lays a rule's operating dimensions on a grid and marks each cell tested-pass, tested-fail, or untested, so the coverage gaps become as visible as the found failures.
• Exception Search — Hunts the histories, subgroups, and edge conditions where a rule is most likely to have already broken, and captures the violating cases it finds.
• Falsification Check — Restates a confident claim as an explicit rule with a bounded scope and a pre-committed breaking criterion, so later evidence can actually refute it.
• Negative Case Analysis — Studies the cases that do not fit a theory and uses them to revise its boundary and confidence, rather than defending the theory or throwing it out.

Counterfactual Comparison

Compare what happened with a plausible alternative to isolate causal effect or decision value.

6 mechanisms · View full solution archetype

• Baseline Comparison — Compares actual outcomes with a pre-action baseline, expected trend, benchmark, or no-action projection when direct controls are unavailable.
• Counterfactual History Review — Uses historically plausible alternatives to test whether an outcome depended on a decision, constraint, accident, or structural condition without treating imaginative speculation as proof.
• Matched Case Comparison — Pairs cases or periods that are similar on key attributes so differences in outcomes can be interpreted relative to a more credible counterfactual baseline.
• Scenario Contrast — Contrasts a focal path with one or more explicitly described alternatives, often in strategy, planning, design, or historical interpretation where controlled testing is impossible.
• Synthetic Control Method — Builds a weighted comparison case from multiple units when a single natural control is unavailable, often in policy, economics, public health, or regional intervention evaluation.
• What-If Analysis — Uses a structured hypothetical prompt to define an alternate condition and reason through likely outcome differences; it becomes Counterfactual Comparison only once the alternate is plausibility-checked and used for disciplined comparison.

Deductive Chain Validation

Validate that conclusions actually follow from stated rules and premises before acting on them.

7 mechanisms · View full solution archetype

• Diagnostic Logic Check — Checks whether a case actually meets the stated classification criteria and labels the evidential uncertainty that remains, so a criteria-based label is not mistaken for certainty.
• Legal Syllogism Review — Verifies the material facts, hunts for exceptions and defenses, and bounds the holding of a legal argument so the conclusion is no broader than the proven facts and surviving rule support.
• Logic Checklist — Runs a fixed set of prompts over any argument — hidden premises, equivocal terms, invalid steps — so common reasoning faults are caught by routine rather than by luck.
• Policy Eligibility Review — Traces an approval or denial back to the exact governing policy and the verified case facts, so an eligibility conclusion follows from the rule rather than from discretion.
• Requirements Traceability Check — Links a 'complete', 'safe', or 'compliant' claim down to the specific requirements, assumptions, and tests that ground it, flagging every link that rests on an unverified assumption.
• Rule-Engine Validation — Tests whether an automated decision system's outputs actually follow from its encoded rules and supplied facts, including how it resolves priority rules and behaves at edge cases.
• Syllogism Template — Casts a rule-to-case argument into major premise, minor premise, and conclusion so its logical form becomes inspectable before anyone checks whether it is sound.

Distributional-Assumption Governance

Make probability-distribution commitments explicit, evidence-grounded, consequence-aware, stress-tested, and revisable before they govern inference or action.

10 mechanisms · View full solution archetype

• Candidate-Family Comparison Grid — Lays credible distribution families and assumption-light baselines side by side and scores them on support, rationale, tail behavior, and complexity so the family choice is argued, not defaulted.
• Distribution-Shift Trigger Dashboard — Tracks shape, tail, missingness, and dependence indicators over time against named revision triggers so a once-accepted distribution can't silently expire.
• Distributional Sensitivity Grid — Runs each plausible family, tail, dependence, and parameter choice all the way through to the final decision output to see whether the conclusion actually moves.
• Distributional-Assumption Card — A one-page record that pins a distributional commitment — modeled quantity, family, support, rationale, evidence, decision use, owner, and expiry — into an inspectable, hand-off-safe contract.
• Holdout Calibration and Coverage Backtest — Scores the model's predictions, intervals, and event rates on data withheld from fitting to check whether promised coverage survives out of sample, against pre-set acceptance thresholds.
• Independent Assumption-Challenge Gate — An independent-reviewer checkpoint that must clear a distributional assumption before it can drive a high-stakes decision — or return it with a mandated fallback.
• Predictive Replication Check — Simulates replicate datasets from the fitted model and asks whether they reproduce the observed shape and dependence the decision relies on.
• Resampling Robustness Audit — Re-estimates the conclusion across bootstrap or jackknife resamples to expose how much it rests on finite-sample luck or a handful of observations.
• Support, Shape, and Tail Diagnostic Suite — Assembles plots, quantile comparisons, boundary checks, and tail summaries into one profile of a distribution's support, shape, and tails — with no single view allowed to decide.
• Tail and Boundary Stress Scenario — Invents adversarial tail, zero, mixture, and boundary regimes the data haven't shown and checks whether the decision and its fallback survive them.

Effect Size Standardization

Convert raw inferred effects into comparable, uncertainty-bounded magnitude expressions so evidence can be judged by size and practical meaning, not only by detectability.

9 mechanisms · View full solution archetype

• Absolute Risk Difference Translation — Converts a relative effect into a concrete per-person difference — an absolute risk change and number-needed-to-treat — by grounding it in the baseline event rate.
• Confidence Interval Propagation — Carries a raw estimate's uncertainty through the standardizing transformation so the reported effect keeps a valid interval instead of collapsing to a point.
• Correlation or Regression Coefficient Transformation — Converts association estimates — correlations and regression slopes — into comparable effect-size units, and inter-converts between the correlation and mean-difference families.
• Forest Plot or Effect Table Display — Lays out many standardized effects, their intervals, directions, and comparability caveats in one visual so a reviewer can read magnitude and consistency at a glance.
• Hedges Correction Application — Multiplies a standardized mean difference by a small-sample correction factor to remove the upward bias that inflates effect sizes in tiny studies.
• Meta-Analytic Effect Harmonization — Brings many studies' effects onto one common metric and quantifies how much they genuinely disagree, so a body of evidence can be synthesized without erasing real heterogeneity.
• Minimal Important Difference Anchoring — Judges a standardized effect against an externally established threshold of meaningful change, so magnitude is read as important-or-not rather than merely large-or-small.
• Risk Ratio or Odds Ratio Standardization — Expresses a binary event outcome as a relative ratio between two groups, computed on the log scale so the multiplicative effect can be compared and combined.
• Standardized Mean Difference Calculation — Rescales a difference between two group means into standard-deviation units so effects measured on unrelated continuous instruments land on one common axis.

Effort-Based Vs. Inherent Ability Attribution

Interpret success and failure through controllable effort, strategy, practice, evidence quality, and luck/noise before treating the outcome as proof of inherent ability.

8 mechanisms · View full solution archetype

• After-Action Learning Review — A structured group retrospective that maps the causes of a completed effort across the whole team and feeds the lessons forward through a mentor channel.
• Calibration Conversation Script — A guided two-way conversation that aligns a performer's confidence with the actual evidence at a checkpoint, in language that points at process rather than talent.
• Effort–Strategy Reflection Prompt — A quick self-directed question that converts a raw performance outcome into a specific effort-and-strategy adjustment before it hardens into a talent or inability label.
• Failure Reframe Template — Rewrites the story of a failure from fixed inability into controllable, fixable causes while protecting the performer's identity, so a single loss does not collapse into helplessness.
• Performance Evidence Portfolio — Accumulates many performance episodes into a standing record so ability claims rest on a repeated, quality-weighted sample rather than one vivid result.
• Process Praise Protocol — A feedback protocol that aims praise at the controllable process a performer used, so achievement can be recognized without inflating a fixed-ability label.
• Rubric-Linked Growth Plan — Converts an attribution into a criterion-referenced practice roadmap that names the next skill level and the controllable steps to reach it.
• Success Debrief Luck–Skill Separator — Splits a win into repeatable skill versus luck and noise, so a single good outcome does not inflate confidence past what the evidence supports.

Emic-Etic Dual-Account Interpretation

Preserve insider and outsider descriptions as separately governed accounts, then use their mismatch as evidence instead of forcing premature translation into one frame.

8 mechanisms · View full solution archetype

• Category Loss Annotation — Tags each mapping from a local term to an external category with the exact distinction that is dropped, so category flattening becomes a visible, typed mark rather than a silent default.
• Divergent Account Brief — A decision-facing brief that sorts every finding into emic, etic, convergent, or divergent, states what each may and may not license, and carries the unresolved residue forward instead of smoothing it into one story.
• Dual Codebook Audit — A periodic conformance check on two separately maintained codebooks — one emic, one etic — that verifies their closure rules stayed distinct and no local category was quietly laundered into an analytic one.
• Emic-Etic Contrast Matrix — A grid that places the same cases under both the emic and the etic account at once, so correspondences, partial matches, and outright breaks between the two become visible cell by cell.
• Etic Analytic Coding Frame — A structured, theory-derived codebook that builds the outsider account explicitly — naming the analytic framework, its constructs, and the sampling and competence conditions under which its codes may be applied.
• Insider Review Panel — A standing panel of community insiders with real authority to validate the emic account, contest an outsider framing, and withhold consent for uses that would expose local knowledge to harm.
• Member Checking Session — A working session that takes draft interpretations back to the very participants who supplied the data, so they can confirm, correct, or contest whether the analyst's reading still means what they meant.
• Reflexive Positionality Memo — A first-person memo in which the analyst records who they are relative to the phenomenon — their standpoint, stakes, and power — and traces how that position shapes what each account can and cannot see.

Evidentiary Trace Warranting

Treat evidence as a defeasible relation between a trace and a claim, not as raw data or free-floating support.

8 mechanisms · View full solution archetype

• Admissibility or Relevance Gate — Prevents traces below provenance, quality, or relevance thresholds from being used in high-stakes reasoning.
• Claim-Evidence-Reasoning Card — Captures a compact claim, evidence trace, and reasoning bridge for review.
• Defeater Register — Lists facts, conditions, and counterevidence that would weaken or defeat an evidence relation.
• Evidence Relation Matrix — Maps traces to claims with provenance, relevance, link type, weight, scope, and defeaters.
• Evidence Strength Ladder — Labels evidence strength while preserving scope, uncertainty, and defeasibility.
• Evidence Update Review — Revisits evidence relations when sources, context, measurement, or rival explanations change.
• Relevance and Alternative Explanation Check — Tests whether a trace actually discriminates among hypotheses or is also expected under alternatives.
• Trace-to-Claim Diagram — Visualizes trace, source, inference bridge, hypothesis, and defeaters.

Generalization Validation

Test whether a pattern learned from specific cases works on new cases outside the original fit.

9 mechanisms · View full solution archetype

• Complexity or Regularization Review — Interrogates each feature, exception, or clause a pattern has accumulated and strips out any that improves old-case fit without earning its keep in transfer or clear necessity.
• Cross-Validation Analog — Rotates which cases fit and which grade across many folds, so every scarce case earns a turn as a judge and rival candidates can be ranked on their averaged out-of-fold scores.
• External Validity Check — Compares the conditions that produced a pattern against the conditions where it is meant to be used, and turns each mismatch into a scoped boundary or a demand for fresh evidence.
• Holdout Case Review — Tests a narrative pattern against real cases deliberately withheld from the story that built it — especially awkward, atypical, and counter-examples — and narrows the claim wherever the story cracks.
• Phased Rollout Validation — Expands a change in deliberate waves, with a pre-set gate between each stage that can halt, narrow, or widen the rollout based on what the last wave revealed.
• Pilot Replication — Re-runs a pattern that worked in its origin setting inside one genuinely new setting, to see whether the effect reproduces against a pre-set bar before anyone scales it.
• Post-Deployment Validation Monitoring — Keeps watching a pattern after it is fully live, with a named owner and a standing cadence, so that transfer which held at launch but decays over time is caught before it does damage.
• Robustness Check — Perturbs the assumptions, inputs, segments, and specification behind a result to see whether the pattern holds steady or was propped up by one fragile arrangement.
• Train/Test Split — Cuts the available cases once, before any fitting, into a slice that shapes the pattern and a sealed slice that is only ever used to grade it.

Hypothesis Test Power Calibration

Design a hypothesis test around the effect that would actually matter, then tune sample size, noise control, allocation, and error rates so the test has adequate power to detect it.

7 mechanisms · View full solution archetype

• Closed-Form Power Calculation — Solves the sample-size or power equation analytically, returning required N or expected power for a standard, well-characterized test in a single evaluation.
• Minimum Detectable Effect Table — Reverses the sample-size question — for a design whose size is already fixed by budget or population, tabulates the smallest effect it can detect at the target power.
• Operating Characteristic Curve — Plots detection probability across the full range of plausible true effects, replacing a single power number with the whole sensitivity profile of the design.
• Pilot Variance Estimation — Runs a small pilot to measure the variance, baseline rate, and dropout that every power calculation depends on, replacing guessed nuisance parameters with data.
• Power Sensitivity Grid — Recomputes power across a grid of alternative variance, attrition, and compliance assumptions to expose designs that only clear the bar under optimistic inputs.
• Pre-Analysis Power Statement — Records the target effect, error budget, frame, and interpretation boundaries before data collection, turning power calibration into a pre-committed design contract.
• Simulation-Based Power Analysis — Estimates power for a complex or nonstandard design by repeatedly generating synthetic datasets under an assumed effect and running the actual planned analysis on each.

Hypothesis Testing Frame

Frame a claim against a default alternative so evidence can change belief or action under explicit error risks.

10 mechanisms · View full solution archetype

• A/B Test Interpretation Protocol — Reads a live randomized experiment against a pre-declared primary metric and launch criteria, turning the measured difference into a ship, hold, or iterate decision.
• Decision Threshold Rule — Operationalizes the evidence threshold as a cut point, burden, gate, or standard that changes action status.
• Equivalence or Noninferiority Test — Implements a variant where the goal is to show sufficiently small difference or no unacceptable loss rather than superiority.
• Falsification Protocol — Specifies what evidence would count against a favored claim before the evidence is sought.
• Inspection Pass/Fail Test — Applies predefined criteria to classify an item, process, or condition as acceptable or unacceptable.
• Legal Burden-of-Proof Analog — Uses a formal presumption and evidentiary burden to protect against costly false judgments.
• Null Hypothesis Significance Test — Implements a default-versus-alternative comparison with a formal statistical threshold under specified assumptions.
• Quality Acceptance Test — Uses predefined acceptance criteria to decide whether a product, batch, process, or deliverable meets a required standard.
• Scientific Claim Evaluation Template — Prompts analysts to state claim, default, alternative, evidence, assumptions, thresholds, error costs, and interpretation limits.
• Sequential Review Gate — Re-evaluates evidence at predefined milestones while controlling how interim findings change action.

Independent Convergence Evidence Appraisal

Treat repeated independent arrival at the same solution-shape as evidence of fit only after auditing independence, shared pressures, abstraction level, and alternative explanations for the convergence.

7 mechanisms · View full solution archetype

• Blind Pattern Comparison Round — Has independent judges rate whether candidate solution-shapes truly match, with lineage identities and the convergence claim masked, so the similarity score is not manufactured by expectation.
• Common-Cause and Copying Audit — Runs a fixed checklist of shared sources, incentives, regulations, vendors, and social proof to see whether any of them explains the repeated solution better than independent fit.
• Convergence Evidence Matrix — Tabulates lineages, pressures, solution-shapes, independence evidence, performance, and caveats into one grid so convergence can be read across rows instead of asserted.
• Convergence Warrant Memo — Writes the final calibrated inference as a short defeasible memo — confidence, the scope it applies to, the action it implies, and the conditions that would overturn it.
• Lineage Traceback Protocol — Reconstructs the origin and transmission history of each case to distinguish independent discovery from diffusion or copying.
• Negative-Case Scan — Actively hunts the comparable cases where the solution did not emerge or did not work, and lets those failures recalibrate how strong the convergence really is.
• Pressure–Solution Fit Rubric — Scores, case by case, how well the specific solution-shape answers the specific pressure — the mechanism story that says why this form solves this problem.

Independent Evidence Triangulation

Cross-check a scoped claim with multiple meaningfully independent evidence streams, using both convergence and divergence to calibrate confidence and expose hidden dependence, bias, or context.

10 mechanisms · View full solution archetype

• Blinded Parallel Analysis — Has multiple analysts evaluate the same claim behind an information barrier and reveal results only after each commits, so that later agreement counts as corroboration rather than echo.
• Confidence Update Worksheet — A structured record of prior confidence, stream-specific likelihoods, dependency discounts, contradictions, and sensitivity that resolves to a single bounded confidence claim.
• Contradiction Resolution Workshop — A facilitated session that takes a specific disagreement between streams and tests whether it comes from definition, timing, sampling, incentives, transformation, or real context dependence.
• Convergence–Divergence Rubric — A precommitted rating scale that classifies how a set of streams relate — full agreement, partial compatibility, material conflict, or unresolved divergence — before the favored result is known.
• Cross-Source Corroboration Table — A claim-by-source grid that marks, for each source, whether it independently supports, merely repeats, contradicts, is silent on, or cannot be compared against each claim.
• Evidence Stream Matrix — A one-row-per-stream table recording each stream's claim coverage, origin, method, population, time, quality, uncertainty, and known dependencies before any synthesis begins.
• Independent Replication Protocol — A standing procedure for obtaining a separately executed repeat of a test by a different team, with controlled information sharing and explicit comparability conditions.
• Multi-Method Study Design — A design that assigns deliberately different methods — qualitative, quantitative, observational, experimental, model-based — to one scoped claim so their differing blind spots expose each other.
• Source Dependency Graph — A directed lineage map that traces copied claims, shared datasets, common instruments, overlapping samples, and other paths by which nominally separate streams can fail together.
• Triangulation Audit Trail — A versioned record linking each conclusion back through the weights, dependency judgments, contradictions, exclusions, challenges, and later updates that produced it.

Informal Fallacy Diagnosis and Repair

Repair arguments that can look formally valid but fail because their premises, context, relevance, or category moves are defective.

10 mechanisms · View full solution archetype

• Burden Shift Detection — Catches when the obligation to prove quietly moves from the claimant to the critic, so 'you can't disprove it' stops passing as evidence.
• Category Boundary Stability Check — Holds a key term or category to one fixed meaning across the whole argument, catching definitions that drift to dodge counterexamples.
• Counterexample Probe — Attacks a general claim by manufacturing the case that would make it false, then reports whether the claim survives, narrows, or breaks.
• Fallacy Label Justification Note — Ties a named fallacy to the exact defective inference move and states it as a reasoning correction rather than a stigmatizing label.
• Fallacy Triage Matrix — Sorts a pile of suspected reasoning defects by fallacy family and by how much each actually damages the inference, then routes each one.
• Feasible Alternative Comparison — Scores a real option against the best achievable alternative instead of an idealized one, exposing rejections driven by the nirvana fallacy.
• Formal vs Material Error Gate — Decides whether an argument's defect lives in its logical form or in its content, so formal invalidity is not mislabeled an informal fallacy.
• Option Space Expansion Prompt — Breaks a false binary by regenerating the live options a two-way framing suppressed.
• Premise Relevance & Acceptability Test — Screens each premise for whether it is acceptable in its own right and actually relevant to the conclusion it is offered to support.
• Steelman then Refute Protocol — Rebuilds an argument in its strongest fair form before attacking it, so any refutation lands on the position itself and not a caricature.

Information Set Specification and Completeness Verification

Do not ask whether a price or signal is simply “efficient”; specify the information set it should reflect, then test whether available information and residual opportunities show complete incorporation.

8 mechanisms · View full solution archetype

• Abnormal-Return / Residual Model — Compares observed returns or outcomes to a baseline model to detect unexplained opportunity after information release.
• Arbitrage Opportunity Scan — Searches for cross-price, cross-market, or cross-instrument gaps that should disappear if the information set is incorporated.
• Cross-Market Information-Leakage Check — Compares related markets or instruments to see whether information appears in one signal before another.
• Event-Study Information-Response Test — Tests whether a price or signal reacts to a defined information event within the expected window.
• Information-Source Inventory Matrix — Maps information sources to availability, timing, actor access, cost, reliability, and expected incorporation pathway.
• Lagged-Response Regression — Tests whether old information still predicts later price or signal movement after the supposed incorporation window.
• Market-Microstructure Order-Book Probe — Uses quotes, depth, spreads, order flow, and liquidity to test whether available information appears in trading behavior.
• Post-Announcement Drift Analysis — Looks for predictable movement after public disclosure, suggesting delayed or incomplete incorporation.

Knowledge-Warrant Audit

Audit what each belief rests on, classify the strength and type of its warrant, and adjust confidence or action accordingly.

9 mechanisms · View full solution archetype

• Assumption Conversion Prompt — A prompt that converts 'we know' statements into explicit assumptions when the evidence chain is weak or missing.
• Belief-Warrant Matrix — A table that lists each claim, its warrant type, evidence chain, confidence level, uncertainty, and update trigger.
• Claim-Confidence Warrant Review — A structured check that asks whether the confidence attached to each claim is justified by its warrant strength and stakes.
• Epistemic Status Labeling — A language convention that marks claims as observed fact, inference, assumption, hypothesis, expert judgment, or unresolved unknown.
• Evidence Ladder Labeling — A label set that sorts claims from direct observation and replicated evidence down through inference, testimony, analogy, and unsupported assumption.
• Source-Independence Cross-Check — A check that distinguishes genuinely independent support from repeated citations of the same underlying source or model.
• Unsupported-Certainty Red Flag — A flag used when high-confidence language appears without enough warrant to justify it.
• Update-Trigger Checkpoint — A scheduled or event-based checkpoint that reopens a belief when pre-defined evidence, contradictions, or expiry conditions appear.
• Warrant-Decay Review — A recurring check for beliefs whose supporting evidence is stale, context-dependent, or vulnerable to drift.

Lived Experience Capture

Capture first-person lived experience so systems are not designed, evaluated, or governed only from external metrics, expert categories, or institutional assumptions.

5 mechanisms · View full solution archetype

• Ethnographic Observation — Embeds a researcher in the setting for a prolonged stretch, reading lived practice against the material and social conditions around it, so meaning is inferred from how life is actually conducted rather than from what people say about it.
• Experience Sampling — Pings people at signal-contingent moments across days to capture their state right then, building a picture of how experience varies across moments, contexts, and moods rather than what it averages to.
• Narrative Account Collection — Invites people to tell the whole of what happened as a story, in their own sequence and words, and preserves that account intact rather than breaking it into answers to the researcher's questions.
• Participatory Research Session — Brings experience holders into the room as co-analysts, not just sources — they help interpret the accounts, decide what the findings mean, and shape the action, so authority over meaning is shared.
• Semi-Structured Interview — Runs a one-on-one conversation from a prepared guide of open questions, covering the decision-relevant ground while leaving room to follow the unexpected — with a deliberate choice of whom to talk to.

Longitudinal Follow-Up Validation

Treat validation as a time-extended claim by checking whether outcomes, harms, and operating assumptions still hold after deployment and accumulated exposure.

8 mechanisms · View full solution archetype

• Follow-Up Visit or Survey Protocol — Recontacts the very people a validation claim was made about — patients, trainees, participants — on a defined schedule to measure directly whether the intended outcome still holds.
• Incident and Adverse-Event Reporting — A standing channel that lets anyone report a rare or severe event against a predefined catalog, so latent harms surface as signals and route straight to corrective action.
• Longitudinal Cohort Study — Enrolls a defined exposed group and a matched comparison group and follows both over a fixed horizon, so a sustained-outcome difference can be attributed rather than merely observed.
• Post-Market Surveillance Registry — A standing database that enrolls every deployed unit and links it to its later outcomes, giving field harms a denominator so a rising signal trips a defined action threshold.
• Scheduled Revalidation Review — A calendar-forced governance checkpoint that re-reads the original validation claim against accumulated evidence and issues a recertify, restrict, or retire decision at a hard gate.
• Security Patch Effectiveness Monitor — Tracks whether one deployed security fix stays effective across the fleet as versions and the threat landscape drift, and routes any regression straight back to re-patch.
• Telemetry Drift Dashboard — Aggregates live production telemetry into one longitudinal view that shows whether a deployed system is drifting from its validated behavior, and trips a threshold when it does.
• Warranty and Failure-Return Analysis — Mines the stream of returned and warranty-claimed units — traced back to their production batch — to infer real field reliability and expose latent defects a lab test never saw.

Metanarrative Coherence and Internal Consistency Check

Turn a sweeping story into an auditable claim structure, then test whether its claims, exceptions, evidence links, and implied conclusions can all hold together.

8 mechanisms · View full solution archetype

• Causal-Temporal Trace — Lays the narrative's events, actors, and causal claims onto one timeline so anachronisms and causal-capacity mismatches surface — the places where the story needs something to happen before the thing that makes it possible.
• Claim-Lattice Mapping — Externalizes a sprawling narrative into an explicit graph of its claims and the support, implication, and constraint links between them, so the story can be reasoned about as a structure instead of felt as a flow.
• Contradiction Scan — Applies explicit consistency criteria pairwise across the narrative's claims to flag genuine incompatibilities — X asserted here, not-X implied there — and records each as a logged tension rather than a passing impression.
• Evidence-to-Claim Traceability — Links every load-bearing claim to the specific evidence or warrant meant to support it, exposing claims that ride on borrowed authority, on local evidence stretched to a global conclusion, or on nothing at all.
• Exception Classification — Sorts each anomaly the narrative bumps into — legitimate boundary case, ambiguity needing qualification, repairable contradiction, or fatal disconfirmation — so counterexamples are neither absorbed ad hoc nor treated as automatic refutations.
• Red-Team Coherence Review — Convenes an adversarial reviewer whose job is to break the narrative's coherence from the outside — overreaching its own scope, reading it as a hostile stakeholder would, and pitting rival accounts against it — surfacing incoherences insiders have stopped seeing.
• Revision Diff Review — Compares successive versions of a narrative against the repair each revision was supposed to make, catching the edit that renamed a contradiction, quietly absorbed a counterexample, or reworded a tension instead of resolving it.
• Term-Stability Review — Pins each load-bearing term to a single definition and tracks it through the whole narrative, flagging the passages where a word quietly changes meaning to keep an argument alive — semantic drift used to dodge a contradiction.

Minimal-Disclosure Verification

Make a verifier confident that a bounded claim is true without handing over the underlying witness, record, identity attributes, or computation trace.

10 mechanisms · View full solution archetype

• Anonymous Membership Proof — Proves that the prover belongs to an authorized set without identifying which member they are.
• Commitment Scheme with Opening Rule — Lets a prover bind to a value now and later prove selected relations about it without unrestricted disclosure.
• Interactive Zero-Knowledge Protocol — Uses challenges and responses so the verifier gains confidence that the prover knows a witness without learning the witness.
• Non-Interactive Zero-Knowledge Proof — Produces a reusable proof artifact that can be checked without a live verifier challenge, provided freshness and context binding are handled.
• Policy-Bound Attestation Token — Carries a scoped verdict or claim result tied to a policy, issuer, subject, and expiration window.
• Privacy-Preserving Compliance Oracle — Checks a private record against public rules and emits only a bounded compliance verdict.
• Proof of Possession Without Secret Reveal — Demonstrates control of a key, credential, or token without transmitting the secret itself.
• Range Proof — Proves that a private numeric value lies within an accepted range without revealing the value itself.
• Selective-Disclosure Credential Presentation — Presents only required credential attributes or predicates while withholding unrelated attributes from the verifier.
• Succinct Zero-Knowledge Proof System — Implements compact proofs of computation, membership, possession, or constraint satisfaction under a formal proof system.

Missingness-Aware Estimator Selection

Choose the missing-data estimator only after stating why values are absent and what assumption makes the target estimand recoverable.

10 mechanisms · View full solution archetype

• Doubly Robust Missingness Adjustment — Combines outcome modeling with response weighting so estimates can remain consistent if one of the two model components is correctly specified.
• Full-Information Maximum Likelihood Path — Uses likelihood-based estimation with incomplete observed data when model and missingness assumptions are appropriate.
• Inverse-Probability Weighting Model — Weights observed cases by modeled response probability to reduce bias from differential observation when covariates support the response model.
• MCAR Diagnostic Test and Balance Review — Compares complete and incomplete cases and uses MCAR-oriented tests where appropriate while treating non-rejection as limited evidence rather than proof.
• Missingness Indicator Matrix — Creates response indicators and pattern tables that show which records, variables, waves, or sensors are absent.
• Multiple Imputation Workflow — Creates multiple plausible completed datasets, analyzes each, and combines estimates while preserving imputation uncertainty under the stated assumption.
• Pattern-Mixture Sensitivity Model — Models outcomes by missingness pattern and varies unobserved departures to explore MNAR-sensitive conclusions.
• Process-Based Missingness Audit — Uses field knowledge, collection logs, device records, administrative rules, or interview protocols to infer why data became absent.
• Selection-Model Sensitivity Analysis — Models the response process jointly with the outcome to examine how non-ignorable missingness would affect estimates.
• Tipping-Point Analysis — Shows how extreme missing outcomes or response-process assumptions would need to be before the substantive conclusion changes.

Multiple-Testing Discipline

Control false discoveries when many comparisons, claims, or tests are being tried.

10 mechanisms · View full solution archetype

• Alpha-Spending Plan — Treats the total false-positive budget as a currency spent in pre-planned fractions across repeated interim looks, so peeking at accumulating data never inflates the error rate.
• Bonferroni-Like Correction — Stiffens each test's significance bar in proportion to how many tests share the family, so that clearing it stays hard even after many simultaneous attempts.
• Claim Registry — A living ledger of every attempted claim — its status, owner, and follow-up burden — so selective memory can't erase the failed tries that made a discovery look surprising.
• Confirmatory Follow-Up — Turns one promising exploratory lead into a single pre-specified confirmatory test, so a pattern found by searching must earn its status on fresh ground.
• False Discovery Rate Control — Ranks a whole family of results and draws the significance line to hold the expected share of false discoveries below a chosen rate, trading a little purity for far more power.
• Holdout Validation — Seals a slice of the evidence away untouched during all discovery, then judges the selected finding once against that fresh partition.
• Metric Hierarchy — Ranks metrics into primary, secondary, and exploratory tiers before the data land, so a disappointing primary can't be quietly swapped for a flattering secondary.
• Multiverse Analysis Report — Runs the analysis across every defensible analytic choice at once and shows the whole spread of results, exposing whether the headline depends on one lucky path.
• Preregistration — Timestamps the hypotheses, primary outcome, and analysis plan before the data exist, so what counts as confirmatory is fixed in advance rather than chosen after.
• Replication Study — Re-runs the finding from scratch in independent hands to see whether it survives outside the conditions and choices that first produced it.

Null Finding Warrant Calibration

Treat a failure to find something as evidence of absence only after calibrating whether the search would probably have detected it if it were present.

8 mechanisms · View full solution archetype

• Coverage Map and Blind-Spot Review — Maps searched and unsearched regions so absence claims stay within evidence boundaries.
• Detection Power Checklist — Prompts reviewers to check scope, timing, sensitivity, thresholds, masking, and failure modes before interpreting non-detection.
• Likelihood Ratio for Non-Detection — Quantifies how much less likely the null finding is under target presence than target absence.
• Minimum Detectable Presence Table — States the smallest detectable target level, effect size, defect rate, incidence, or trace intensity.
• Negative Test Interpretation Protocol — Operationalizes how a negative diagnostic, inspection, security, or lab result should update belief.
• Null Finding Warrant Memo — Documents the null finding, search scope, detection assumptions, warrant grade, and conclusion caveats.
• Search Sensitivity Matrix — Compares target forms against observation channels to show what each channel could and could not detect.
• Silent Monitor Assurance Review — Checks whether the absence of alerts is meaningful or merely reflects broken, misconfigured, sparse, or blind monitoring.

Parallel Independent Inspection Design

Find more hidden defects by having multiple independent and diverse inspectors examine overlapping parts of the same artifact before their findings are reconciled.

10 mechanisms · View full solution archetype

• Blind Document Proofing Passes — Splits a locked document among proofers who each hunt one class of defect blind, so no single reader's fatigue or reading-for-meaning hides a whole category of error.
• Capture-Recapture Defect Estimation — Estimates how many defects remain unfound by treating the overlap between two independent inspection passes as a mark-recapture sample.
• Dual or Triple Diagnostic Read — Has a fixed few equally qualified readers each inspect the whole artifact blind, then routes every disagreement to a designated arbiter.
• Finding Reconciliation Board — The post-discovery workflow that deduplicates, adjudicates, severity-triages, and routes independent findings while keeping minority signals alive until resolved.
• Independent Checklist Variant Rounds — Runs the same artifact through different checklist variants across rotated rounds so reviewers don't all walk the same mental path into the same blind spot.
• Independent Security Review Lenses — Inspects one system through several specialist lenses at once — threat, dependency, configuration, access — so different classes of flaw are found by the reviewer trained to see them.
• Multi-Inspector Manufacturing Sort — Routes critical production units through more than one technician with risk-weighted overlap, pulling and re-verifying nonconformities and feeding field escapes back.
• Overlap Heatmap — A per-region view of how many independent inspectors flagged each part of an artifact, making saturated zones and lonely minority findings visible at a glance.
• Parallel Code Review Round — Multiple maintainers independently review the same version-locked change before comments are merged, so a bug one reviewer misses another can still catch.
• Seeded Defect Calibration Exercise — Plants known defects into the inspection stream to measure each inspector's catch rate and calibrate how much the process is really finding.

Pattern Detection with Validation

Detect recurring patterns while guarding against seeing patterns that are not really there.

5 mechanisms · View full solution archetype

• Diagnostic Pattern Checklist — A structured list that forces a suspected signature to be named precisely, weighed against how common it is, and set beside the look-alikes that would explain the same cues — before the label is allowed to stick.
• Multiple-Testing Review — Audits how many patterns were searched before one looked meaningful, then raises the evidence bar to match the size of that search — while watching that the correction does not go so far it buries the real effects.
• Recurrence Tracking Dashboard — A live display that counts how often each kind of event recurs, from which feed, and escalates when a recurrence count crosses a preset line — making repetition visible without claiming it is meaningful.
• System Archetype Matching — Compares an observed system's behavior against a catalog of known feedback-structure archetypes, proposes the closest match, then holds it provisional until its boundary of fit and a fresh pair of eyes confirm the structure is really there.
• Trend Validation Review — A recurring review that stops an apparent upward or downward movement from becoming a trend story until it has been checked against ordinary seasonal variation, against changes in how the data was collected, and against whether it holds up in later observations.

Propositional Mode Governance

Keep propositions in the right epistemic mode and permit only the operations that mode licenses.

10 mechanisms · View full solution archetype

• Assumption Expiry Timer — A date, event, or evidence trigger requiring an assumption to be renewed, tested, replaced, or retired.
• Axiom Boundary Statement — A statement that declares which axioms or primitives are accepted inside the system and how they may be examined from outside that system.
• Claim Status Labeling Standard — A style and metadata standard for marking statements as fact, assumption, hypothesis, axiom, premise, conjecture, belief, estimate, or question.
• Decision Memo Epistemic-Mode Section — A decision memo section that separates facts, assumptions, hypotheses, premises, estimates, values, and unknowns before action is authorized.
• Epistemic Mode Linter — A tool or review pass that flags mode mismatches, such as treating an assumption as a verified fact or citing a conjecture as settled evidence.
• Epistemic Status Ledger — A ledger that lists propositions, current modes, assignment bases, owners, dependencies, obligations, review dates, and transition history.
• Hypothesis Promotion Gate — A review point that prevents a hypothesis from being promoted to accepted claim or operating premise without specified tests, evidence, and caveats.
• Mode-Operation Matrix — A table mapping each epistemic mode to allowed, required, discouraged, and forbidden operations.
• Premise Discharge Checklist — A checklist that ensures temporary premises or proof assumptions are either discharged, scoped, or explicitly carried into the conclusion.
• Proposition Lifecycle Board — A board or workflow that moves propositions through modes while preserving obligations and transition records.

Rapid Prototype Learning Loop

Build a low-cost version to test a specific assumption before committing to full implementation.

8 mechanisms · View full solution archetype

• Clickable Prototype — An interactive interface shell that simulates navigation or user flow without full backend functionality.
• Mockup — A simplified visual or structural representation of a proposed design.
• Paper Prototype — A paper-based representation of screens, forms, steps, or objects that can be manipulated during a test.
• Rough Physical Model — A low-cost physical stand-in used to test spatial, ergonomic, mechanical, or material assumptions.
• Service Walkthrough — A staged enactment of a service, process, or workflow sequence.
• Sketch — A rough visual or spatial representation used to make a concept discussable and testable.
• Small-Scale Pilot — A constrained real-context trial used to learn before broader rollout.
• Wizard-of-Oz Test — A test where humans manually simulate a not-yet-built capability behind the scenes.

Recursive Triangulation of Triangulation

When a conclusion already rests on triangulation, audit the triangulation itself by checking whether its evidence streams are independent, its convergence logic is valid, and its confidence claim survives a second-order triangulation layer.

8 mechanisms · View full solution archetype

• Confidence Scope Update Memo — Publishes the recalibrated conclusion — what remains supported, what scope has narrowed, what dependencies remain, and which uses are now allowed or barred.
• Convergence Logic Rubric — Fixes in advance how agreement, conflict, outliers, and missing evidence should move confidence, so convergence is interpreted by rule rather than by mood.
• Independent Meta-Review Panel — Convenes reviewers with no stake in the original procedure to judge whether its independence, convergence logic, and cross-level conclusions actually hold up.
• Meta-Validation Stop Gate — Decides when recursive validation has done enough — when another layer would not move confidence, when it must continue, and when the procedure must be redesigned.
• Method Provenance Review — Traces backward how each method, source, and interpretation entered the triangulation so circular or copied lineage cannot masquerade as independent corroboration.
• Second-Order Replication Probe — Independently re-runs the triangulation with fresh inputs to see whether the same convergence reproduces or was an artifact of the original setup.
• Triangulation Dependency Matrix — Cross-tabulates the evidence streams against shared dependency dimensions — data source, instrument, analyst, assumptions, incentives, timing, theory frame — so independence that is only nominal becomes visible at a glance.
• Triangulation Red-Team Review — Assigns adversaries to find a way the triangulation could have converged on a wrong answer, hunting for the shared dependency the procedure took for granted.

Regression-to-the-Mean Guardrail

Prevent ordinary reversion after extreme observations from being credited to an intervention, person, punishment, reward, or event without a credible counterfactual.

10 mechanisms · View full solution archetype

• Attribution-Claim Review Gate — A sign-off gate that refuses to approve a causal success or failure claim until selection, counterfactual, expected-reversion, uncertainty, subgroup, and persistence evidence are all on the table.
• Controlled Before–After Contrast — Compares the change over the same interval in the treated group against a comparison group, reporting the difference as the controlled effect rather than the raw rebound.
• Extreme-Selection Risk Flag — Marks an evaluation as triggered by extreme selection, so its before-after story is treated as regression-suspect before any effect is credited.
• Interrupted Series with Pretrend Check — Fits the pre-event trend and seasonality of a single series, then tests whether the outcome shifts level or slope at the event beyond what the extrapolated pretrend and a transient spike predict.
• Matched Extreme-Case Comparator — Builds a comparison group selected by the same extreme threshold and watched on the same schedule, so shared reversion shows up as movement the treated group did not cause.
• Multi-Baseline Measurement Protocol — Collects repeated pre-intervention observations so a case's typical level and measurement reliability are known before the selection spike is treated as its baseline.
• Placebo Time, Outcome, or Threshold Check — Runs the same analysis where the intervention could not have acted — a fake date, an unaffected outcome, or a sham threshold — and flags trouble if an effect shows up anyway.
• Randomized or Staggered Assignment — Assigns extreme-eligible cases to treatment by chance or staggered timing, so treated and comparison paths differ only by luck of the draw rather than by selection.
• Reliability-Based Reversion Simulation — Simulates the follow-up movement you would see with no treatment at all — from measurement reliability and the selection threshold — to give expected reversion a numeric range.
• Shrinkage-Aware Expectation — Pulls a noisy extreme estimate partway back toward the group mean by an amount set by its unreliability, so a single spike is not treated as the case's true level.

Representative Sampling Design

Select observations so the sample can credibly stand in for the population or system being judged.

8 mechanisms · View full solution archetype

• Audit Sample — Selects records from a transaction universe by risk-weighted probability so findings support a bounded assurance opinion, with a documented trail any reviewer can re-walk.
• Benchmark Dataset — Constructs a fixed, versioned evaluation set whose case mix — common, rare, edge, subgroup, and degraded cases — mirrors the real task distribution, with a datasheet and an expiry against drift.
• Field Sampling Plan — Spreads observation effort across sites, seasons, and conditions on a spatial-temporal design so field data speak for a whole environment, not just its most accessible corners.
• Public Consultation Panel — Structures civic input for a single decision by defining who is affected, actively reaching the quiet and hard-to-reach, and bounding the claim so open-mic self-selection can't stand in for the public.
• Quality Inspection Sample — Draws units from across a production process's shifts, suppliers, and lines so a quality judgment reflects the process as it actually runs — not only the defects that happen to be visible.
• Representative Survey Protocol — Carries a population question through a reachable frame, a probability contact-and-selection method, and a live nonresponse monitor, then bounds the claim to who actually answered.
• Stratified Sample — Partitions the population into meaningful strata, samples within each — often oversampling the small or high-variance ones — and reweights so no decision-relevant subgroup disappears from the estimate.
• User Research Panel — Maintains a standing, recruited pool of users as a reusable evidence channel, watching recruitment mix and attrition so the panel keeps matching the user base instead of drifting toward enthusiasts.

Revision-Readiness Precommitment

Specify in advance what evidence would change a belief, forecast, diagnosis, or strategy so that later revision is easier, more accountable, and less vulnerable to motivated reinterpretation.

5 mechanisms · View full solution archetype

• Belief Update Review Template — A repeatable artifact for recording original claim, update condition, observed evidence, and revision decision.
• Forecast Update Trigger Log — A forecast record that pairs predictions with update triggers and later confidence changes.
• Preregistration Refutation Table — A table listing what findings would support, weaken, refute, or leave unchanged a hypothesis.
• Red-Team Update Condition Session — A structured session where challengers help define fair update conditions before outcome evidence arrives.
• Strategic Revisit Gate — A decision gate that reopens a strategy when predefined evidence thresholds are crossed.

Shared or Not Yet Assigned

Mechanisms shared across, or not yet assigned to, a single primary solution archetype.

2 mechanisms

• Co-Interpretation Workshop
• Evidence Provenance Log — Records source origins, custody, transformations, access dates, uncertainties, and unresolved gaps in a reviewable form.

Shared-Source Variance Isolation

Prevent a single hidden source from making multiple supposedly independent dimensions look more correlated than they really are.

8 mechanisms · View full solution archetype

• Batch, Rater, or Instrument Counterbalancing Protocol — Rotates raters, batches, and instruments across the dimensions they touch, by design, so that each source's effect is separable from the signal before any data is analyzed.
• Common Factor or Random-Effect Model — Estimates the shared rater, batch, or instrument component as a latent factor or random effect and shrinks each dimension's estimate toward the group by its precision.
• Leakage Sensitivity Grid — Sweeps a ladder of assumed contamination strengths the source cannot be measured at, and reports the level at which each conclusion breaks.
• Multitrait-Multimethod Matrix — Crosses several traits with several measurement methods so that agreement which replicates across methods can be told apart from correlation manufactured by the shared method.
• Negative-Control Outcome Probe — Plants a dimension that should show nothing if the substantive story were true, then treats any movement in it as a fingerprint of the shared source.
• Residual Correlation Diagnostic — Recomputes the correlation matrix after the shared source has been stripped out and keeps only the associations that survive the adjustment.
• Source Variance Audit Matrix — Lays the output dimensions against every shared source in a grid so that each place a common source touches more than one dimension is written down before any correlation is trusted.
• Variance Partitioning Report — Splits each dimension's variance into true-signal, shared-source, dimension-specific, and noise shares, carries each share's precision, and rewrites the claim to match.

Source Distortion Modeling

Treat a report from a systematically distorted source as a biased channel to be modeled, not as either transparent truth or useless noise.

8 mechanisms · View full solution archetype

• Account/Event Reconstruction Table — Separates what the source says from the reconstructed event sequence, inferred omissions, and uncertain intervals.
• Claim Release Gate — Prevents downstream publication, decision, or automation until claims from a distorted account have scoped confidence and corroboration.
• Contradiction Timeline — Places inconsistent statements, records, and observed events on a timeline to distinguish memory, framing, drift, and strategic revision.
• Corroboration Ladder — Orders independent traces from weak consistency checks to strong external confirmation and contradiction.
• Distortion Model Card — Documents the assumed distortion pattern, supporting evidence, scope, counterevidence, and expiry conditions.
• Motive-Opportunity-Bias Analysis — Checks whether a proposed distortion pattern is plausible given the source's incentives, opportunity, and known bias profile.
• Narrator Reliability Matrix — Scores or describes reliability by claim type, evidence base, motive, vantage, consistency, and corroboration.
• Vantage-Bias Interview Protocol — Elicits what the source could know, why they framed it as they did, and what pressures shaped the account.

Source Provenance Triangulation

Evaluate an account by tracing source type, origin, proximity, perspective, corroboration, and confidence before treating its claims as settled.

6 mechanisms · View full solution archetype

• Audit Trail Review — Inspects logs, version histories, document histories, custody records, or system traces to identify edits, gaps, and handling anomalies.
• Citation Lineage Review — Traces a claim through references and derivative accounts to determine whether sources are independent or reproducing the same origin.
• Conflicting Source Table — Keeps contradictory sources visible by listing the claim, source positions, possible explanations, and unresolved questions.
• Source Criticism Protocol — Uses structured questions about authorship, purpose, audience, context, proximity, and transmission to evaluate a source before accepting its claims.
• Triangulation Matrix — Places claims against multiple sources so agreement, disagreement, independence, and source-type diversity can be seen at once.
• Witness / Source Comparison — Compares firsthand accounts or records by role, access, incentive, timing, memory risk, and corroboration against non-testimonial evidence.

Theory-Responsive Case Sampling Design

Select the next case because it can sharpen, challenge, extend, or saturate the emerging account—not because it statistically represents a population.

10 mechanisms · View full solution archetype

• Boundary Case Probe — Selects a case at the model's suspected edge to find out where the account stops applying.
• Case Selection Audit Trail — Preserves the versioned, time-ordered record of the sampling path — memos, access constraints, and each case's model effect — so the sequence can be reconstructed and defended.
• Constant Comparison Matrix — Compares each new case against prior cases and the current categories, forcing every difference into a model revision.
• Grounded Theory Sampling Memo — Records the current category, the open gap, and the reason for the next case before it is collected.
• Maximum Variation Case Round — Samples deliberately across the widest range of cases to see which findings survive maximum difference.
• Negative Case Sampling Pass — Actively hunts for a case that could disconfirm or puncture the current account rather than confirm it.
• Rival Explanation Discriminator — Chooses the one case whose outcome would separate two still-live rival explanations.
• Saturation Review Memo — Documents whether newly sampled cases have stopped changing the model, and convenes the decision to stop.
• Theoretical Gap Matrix — Maps the model's open gaps against candidate cases to rank which case would teach the most next.
• Transferability Claim Check — Audits the final claims against what the sampled cases can actually support, trimming overreach.

Use-Time Source Attribution Calibration

Before using a commingled memory, note, claim, trace, or generated output, classify where it came from and how certain that attribution is.

12 mechanisms · View full solution archetype

• Borrowed Idea Attribution Scan — Sweeps a shared store of notes and ideas for material that arrived from someone else but now feels self-generated, and routes each item back to the source that deserves the credit.
• Chain-of-Custody or Lineage Check — Reconstructs an item's unbroken trail back to its origin — every handoff and transformation logged beside the content — so its source class is established rather than assumed when it is used.
• Generated Content Disclosure Gate — Holds internally- or model-generated content at the point of release until it carries a label saying it was generated and is phrased so a downstream reader can weight it as such.
• Hallucination Intrusion Triage — Takes items already flagged as possible fabrications or memory intrusions and sorts them by how much rides on them, quarantining, escalating, or releasing each before it is trusted.
• Memory Source Probe — Interrogates one recalled item at the moment of recall for its source cues, then applies a rule to classify where it actually came from.
• Observation Recheck or Replication — Converts a decayed or doubtful memory back into first-hand evidence by going and observing the thing again, instead of trusting the stored trace.
• Provenance Lookup Before Publication — A last-gate check that, claim by claim, traces a draft back to where each piece actually came from and credits anything borrowed before it goes public.
• Reality Monitoring Checklist — A short cue-by-cue checklist run at the moment of recall to decide whether an item was actually perceived from the world or generated inside your own head.
• Source Attribution Confidence Rubric — A graded scale that scores how sure you are of an item's source — separately from whether the content is true — and trips a corroboration gate when the grade is low and the stakes are high.
• Source Attribution Training Set — A curated corpus of real items whose true source class is already known, held as the gold reference that calibrates and teaches an attribution judgment — human or model.
• Source Confusion Matrix Review — A retrospective review that tabulates which source classes get mistaken for which — reading the off-diagonal cells to find systematic, directional misattributions and feed the fixes back.
• Source-Label Preserving Summary Template — A summary format that forces each condensed statement to carry its source class through compression, so shortening a document can't quietly flatten observed, reported, and generated content into equally-confident prose.

User Context Validation

Validate a solution against actual user behavior, needs, constraints, and context of use.

10 mechanisms · View full solution archetype

• Accessibility Review — Checks the solution against inclusion standards and the full range of sensory, cognitive, physical, and linguistic abilities, so no user is excluded by an assumption the design never examined.
• Analytics Behavior Review — Reads the whole population's behavioral traces — abandonment, errors, retention, search — to test a design assumption at scale and to check whether narrower evidence actually generalizes.
• Contextual Inquiry — Studies users in the actual setting where the work happens — watching and asking at the same time — so the situated constraints and workarounds that never surface in a lab become visible.
• Diary Study — Has users log their own experience in the moment, repeatedly over days or weeks, so recurring friction and delayed consequences that no single session can reach come into view.
• Field Observation — Watches users act in the real setting where the solution must work, surfacing the tacit routines, workarounds, and situated constraints they could never report from a conference room.
• Journey Map — Lays a user's end-to-end path out as a single picture — touchpoints, handoffs, delays, and emotional lows — so scattered findings become a prioritized map of where the design fails.
• Participatory Design Session — Brings affected users into the design room as co-authors, so the people who will live with the solution shape the revision instead of only supplying evidence for it.
• Service Pilot — Runs the whole solution as a small, real, bounded service so end-to-end fit, support needs, and outcomes can be seen — and its findings drive revision before full rollout.
• Usability Test — Puts users in front of the solution and asks them to attempt representative tasks, making friction, errors, and comprehension gaps visible where interaction actually breaks.
• User Interview — Surfaces users' own goals, constraints, and felt needs in guided conversation, so the design's beliefs about who the user is and what they lack can be tested against their own account.

Warranted Belief Formation

Turn a proposition into a responsible belief only after clarifying its meaning, warrant, confidence, scope, action consequences, and conditions for revision.

8 mechanisms · View full solution archetype

• Belief Adoption Checklist — A run-once pass/fail gate that blocks a claim from becoming an action-guiding belief until proposition, warrant, confidence, scope, action implication, and a revision trigger are all in hand.
• Belief Premise Register — A standing ledger of the propositions a decision currently rests on, each with its confidence and scope, an owner, an adoption state, and a recheck date.
• Bias and Pressure Prompt — A short self-administered set of questions that surfaces the non-warrant forces — fluency, fear, authority, identity, incentive — that may be doing the real work behind a belief, and asks who is harmed if it is wrong.
• Claim-Warrant Matrix — A side-by-side grid that puts many competing claims on rows and their evidence, source quality, and counter-evidence on columns, so warrant can be compared across rivals before any one is believed.
• Confidence and Scope Label Template — A fixed grammar for tagging a belief with a calibrated confidence level and the bounded conditions under which it holds, so the caveat travels with the claim.
• Doxastic Commitment Ladder — A named ladder of graded belief states — from heard, to plausible, to provisional, to action-guiding — with a confidence band and an action license for each rung.
• Falsification Trigger Card — A one-belief tripwire sheet naming the specific observations that would weaken, suspend, or overturn it, who watches for them, and when to look again.
• Reflective Belief Dialogue — A structured multi-person conversation in which a peer actively challenges why a claim should be believed, what would change it, and what ethical limits bound acting on it.