FPF Reference

Cross-Disciplinary Bias Audit

E.5.4 · Stable · Part E - The FPF Constitution and Authoring Guides

About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a fpf-memory product feature page.

How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

FPF calls itself trans‑disciplinary, but every author carries implicit metaphors from a home domain. If those metaphors leak into “universal” patterns, practitioners from other fields disengage or mis‑interpret the rules.

Keywords

  • bias
  • audit
  • ethics
  • fairness
  • trans-disciplinary
  • neutrality
  • review.

Relations

E.5.4refinesFour Guard-Rails of FPF
E.5.4outline parentFour Guard-Rails of FPF
E.5.4outline prev siblingUnidirectional Dependency
E.5.4explicit referenceFour Guard-Rails of FPF
E.5.4explicit referencePrinciple Taxonomy & Precedence Model

Content

Problem frame

FPF calls itself trans‑disciplinary, but every author carries implicit metaphors from a home domain. If those metaphors leak into “universal” patterns, practitioners from other fields disengage or mis‑interpret the rules.

Problem

Unrecognised bias hides in wording, examples, unit choices or principle weighting. Once embedded in normative language, such bias is hard to remove and contradicts Pillars P‑2 Didactic Primacy and P‑8 Cross‑Scale Consistency.

Forces

ForceTension
NeutralityOne voice for all disciplines ↔ need for relatable examples.
ConcisenessAudit guidance must be brief ↔ must cover multiple bias types.
LongevityGuidance must survive emergence of new domains.

Solution — Principle‑Taxonomy‑Guided Bias Audit

  1. Bias‑Lens set
    Every normative pattern is assessed through five lenses that match the Principle classes from E.3:
    Gov, Arch, Onto/Epist, Prag, Did.

  2. Equilibrium question
    For each lens ask:
    “Does the pattern over‑privilege this class or silence it?”
    Examples:

    • Over‑reliance on Onto/Epist precision may ignore Prag cost.
    • Dominant Arch metaphors may alienate Did audiences.

  3. Scope‑or‑Balance rule

    • If imbalance is found and universality is intended, re‑phrase to restore balance.
    • If imbalance is intentional (domain‑specific pattern), mark the scope explicitly: “Applies primarily to thermodynamic systems.”

  4. Audit trace
    The pattern carries a short Bias‑Annotation paragraph recording which lenses were tested and any scoping statement. No workflow checklists or reviewer metadata or other data and data format and data governance tips is stored in the Core.

Archetypal Grounding (System / Episteme)

Bias lensExample imbalanceConceptual correction
Arch vs DidPump pattern uses abstract category theory terms.Add plain‑language boundary narrative or move abstraction to appendix.
Onto/Epist vs PragEpisteme trust score defined with complex logic but no guidance on empirical cost.Add pragmatic note on evidence collection burden or scope the pattern.

Conformance Checklist

IDRequirementPurpose
CC‑BA.1Each Core pattern SHALL include a Bias‑Annotation listing the five lenses and any declared scope limitation.Ensures explicit reflection on bias.
CC‑BA.2A pattern labelled “universal” MUST NOT privilege a single lens without justification or scoping note.Preserves trans‑disciplinary integrity.
CC‑BA.3If scope is declared, the pattern SHALL reference the mapping or rationale that enables cross‑domain translation.Keeps pathways open for other calculi.
CC‑BA.4 (QD‑triad evidence for “universal”).Any pattern that labels itself “universal” SHALL cite A.8 CC‑UC 1 + CC‑UC 2 and attach the QD evidence (Diversity_P + IlluminationSummary, with edition and binning) or else scope the claim to its home Context.preserves domain quality diversity

Consequences

BenefitsTrade‑offs / Mitigations
Neutral, inclusive language attracts wider adoption.Authors spend a few extra lines on Bias‑Annotation; mitigated by template snippet.
Bias is surfaced at writing time, not after publication.—

Rationale

Coupling the audit directly to the Principle Taxonomy keeps the guard‑rail concept‑driven, not workflow‑driven. No mention of review boards, CI‑jobs, or checklists appears in the Core; such mechanics belong in the Tooling Guide. This guard‑rail therefore satisfies GR‑1 (Firewall) while securing Pillars P‑2, P‑7 Pragmatic Utility, P‑8.

Relations

  • Parent umbrella: pat:constitution/guard‑rails (E.5)
  • Depends on: pat:constitution/principle‑taxonomy (E.3)
  • Constrains: All normative patterns claiming universality

E.5.4:End