Trust and Legitimacy Checklist¶
A pre-adoption legitimacy audit — instantiates Cultural Friction Mediation Design
Verifies the credibility, consent, fairness, accountability, and repair conditions an adoption needs to be seen as legitimate — as a gate before launch, not an apology after.
Trust and Legitimacy Checklist is a structured checklist run as a gate before adoption, testing the social-license conditions an imported artifact needs: is the source credible here, was consent real, who is accountable, is it fair, are data and privacy expectations honored, is there a repair path, and does the host have genuine ownership? Its distinguishing idea is that it treats legitimacy and trust as preconditions to verify, not outcomes to hope for — and it names the nonnegotiable value lines the adaptation must not cross, however well it functions. Where the other mechanisms study fit and meaning, this one asks a prior question: does the host have standing, consent, and recourse in the first place?
Example¶
A university public-health group wants to run a community wastewater-and-health data program in and with an Indigenous community. The function looks fine; legitimacy is the real risk. Before any deployment they run a Trust and Legitimacy Checklist. Is the sponsoring institution credible and untainted by past extractive research here? Was consent collective and informed, not just individual sign-off? Who owns the data, and who can revoke access? Is there a repair path if harm surfaces? The criteria are aligned to the community's own governance expectations — the CARE Principles for Indigenous Data Governance and the OCAP principles of ownership, control, access, and possession — and two items are flagged as hard stops: data cannot leave community control, and no secondary use without renewed consent. Two boxes fail — data would default to the university's servers, and there is no revocation route — so adoption is held until governance is redesigned. Trust is protected before it is spent, rather than apologized for after it is broken.
How it works¶
- Enumerate legitimacy as checkable items. Source credibility, consent quality, accountability, fairness, data/privacy, repair path, local ownership — each phrased as something to verify.
- Require evidence, not assertion. Each item needs proof, not a claim.
- Mark the hard stops. Distinguish nonnegotiable value lines (vetoes) from advisory items.
- Run it as a gate. Unmet items block or condition adoption, rather than being noted for later.
Tuning parameters¶
- Item set and sourcing — which legitimacy dimensions, and whether the criteria are co-authored with the host or imposed. Co-authored criteria are the ones that actually confer legitimacy.
- Evidence bar — assertion versus documented proof per item. A higher bar is slower but is what stops box-ticking.
- Hard-stop designation — which items are vetoes versus advisory. More vetoes protect values but can block pragmatically fine adoptions.
- Gate placement and repeat — one pre-launch pass versus re-checks at each phase. Legitimacy can erode, so re-running matters.
- Who signs — sponsor self-attestation versus affected-party or third-party verification. Independence is what makes the check trustworthy.
When it helps, and when it misleads¶
Its strength is catching the legitimacy failures that doom otherwise functional adoptions, and catching them before trust is spent — because lost trust costs far more to rebuild than to protect. In effect it operationalizes procedural justice: people accept outcomes they would otherwise resist when the process is seen as fair, voiced, and accountable.[n1]
Its failure mode is that the checklist can decay into legitimacy theater — boxes ticked by self-attestation with no evidence, consent that is a signature rather than a choice — producing a paper trail that looks legitimate and confers none of the real thing. Run backwards, it is assembled to document a decision already made. The discipline is to co-author the criteria with the host, require evidence per item, and have affected parties, not the sponsor, verify the sensitive ones.
How it implements the components¶
Trust and Legitimacy Checklist fills the legitimacy-verification slice of the archetype's machinery — the social-license conditions an audit can confirm:
legitimacy_and_trust_check— it is this check: the structured verification of credibility, consent, accountability, fairness, privacy, repair, and ownership.nonnegotiable_value_boundary— it names and gates on the value lines that must not be crossed, marking them as hard stops distinct from advisory items.
It sets and audits the value boundary but does NOT enforce it at runtime — that is the Reversible Rollout Plan's pause trip-wires. Nor does it convene the deliberative body that voices affected interests (that is the Community Review Panel) or map host norms broadly (that is the Emic Context Interview).
Related¶
- Instantiates: Cultural Friction Mediation Design — the pre-adoption gate on the trust and legitimacy an adaptation depends on.
- Consumes: Community Review Panel supplies affected-voice input for the consent and ownership items; a Host Norm-System Map supplies the fairness and privacy expectations to check against.
- Sibling mechanisms: Reversible Rollout Plan · Community Review Panel · Emic Context Interview · Adoption-Barrier Interview · Norm-Conflict Matrix
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Trust and Legitimacy Checklist operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it verifies the credibility, consent, fairness, accountability, and repair conditions an adoption needs to be seen as legitimate — as a gate before launch, not an apology after.
Independent corroboration: The frozen evidence defines Trust and Legitimacy Checklist as 'Verifies the credibility, consent, fairness, accountability, and repair conditions an adoption needs to be seen as legitimate — as a gate before launch, not an apology after', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Decision, Gate & Allocation — Trust and Legitimacy Checklist includes features of a case-specific gate, selection, routing, prioritization, or resource disposition, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Sociology & Anthropology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Checking credibility, consent, fairness, openness, accountability, and repair before action operationalizes institutional trust and legitimacy research. OECD's trust framework identifies reliability, responsiveness, integrity, openness, and fairness as distinct drivers; security contributes risk controls rather than the primary social lineage.
Related originating lineages:
- Computer Science & Software Engineering — Software systems, algorithms, and data structures supplies a distinct formative lineage for the mechanism's trust and legitimacy checklist logic.
- Law & Governance — law_governance contributes legal doctrine, regulatory governance, and procedural accountability to this mechanism's defining operation—Verifies the credibility, consent, fairness, accountability, and repair conditions an adoption needs to be seen as legitimate — as a gate before launch, not an apology after—without displacing the selected primary historical lineage.
- Organizational & Management Science — organizational_management contributes organizational design, management, and operational governance to this mechanism's defining operation—Verifies the credibility, consent, fairness, accountability, and repair conditions an adoption needs to be seen as legitimate — as a gate before launch, not an apology after—without displacing the selected primary historical lineage.
- Political Science — Political science and institutional power analysis supplies a parallel or contributing lineage for the mechanism's defining operation: verifies the credibility, consent, fairness, accountability, and repair conditions an adoption needs to be seen as legitimate — as a gate before launch, not an apology after.
- Public Administration & Policy — Public administration, policy implementation, and program oversight supplies a parallel or contributing lineage for the mechanism's defining operation: verifies the credibility, consent, fairness, accountability, and repair conditions an adoption needs to be seen as legitimate — as a gate before launch, not an apology after.
- Security Studies & Intelligence Analysis — security_intelligence contributes security engineering, threat analysis, and intelligence practice to this mechanism's defining operation—Verifies the credibility, consent, fairness, accountability, and repair conditions an adoption needs to be seen as legitimate — as a gate before launch, not an apology after—without displacing the selected primary historical lineage.
- Ethics of Technology & AI Governance — Technology ethics and ai governance supplies a parallel or contributing lineage for the mechanism's defining operation: verifies the credibility, consent, fairness, accountability, and repair conditions an adoption needs to be seen as legitimate — as a gate before launch, not an apology after.
Review resolution: The blind reviewers disagree on primary lineage (security_intelligence versus sociology_anthropology). Authoritative or primary research supports sociology_anthropology as the best historical origin: Checking credibility, consent, fairness, openness, accountability, and repair before action operationalizes institutional trust and legitimacy research. OECD's trust framework identifies reliability, responsiveness, integrity, openness, and fairness as distinct drivers; security contributes risk controls rather than the primary social lineage. The cited OECD, Updated Framework on Drivers of Trust in Public Institutions directly supports the mechanism's defining operation. All independently supported contributing domains are retained without an arbitrary cap. origin_mode=cross_disciplinary_synthesis records lineage, while domain_reach=universal records later applicability separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
A checklist confers no legitimacy by itself; it only surfaces whether the conditions for it exist. Its entire value therefore rests on the evidence bar and on who verifies — a sponsor self-attesting to its own credibility is not a check but a rehearsal of one.
[n1] Procedural justice — the well-supported finding (associated with Tom R. Tyler's work) that people's acceptance of decisions and authorities depends heavily on whether the process is experienced as fair — voice, neutrality, respect, and trustworthy motives — often more than on the outcome itself. A legitimacy checklist is essentially an attempt to secure those process conditions in advance rather than to defend them after the fact. ↩