fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 76532–76543

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:40:20 UTC

C.36:6 - Bias-Annotation

Scope: Limited to cultural-evolution questions about variants and their generation, transmission, recognition, selection, retention, loss, mediation, and deliberate influence across one named practice, population, collective, or Discipline boundary. C.36 is not a universal culture ontology, a project-authority rule, or a claim that every evolving engineering object is cultural evolution.

LensLikely driftRepair
GovA case card, project choice, intervention proposal, or observed population trend is read as authorization, responsibility, acceptance, or policy.Keep each project decision and authority claim with its direct pattern; C.36 records only the cultural relations and intervention distinctions actually current.
ArchOne platform, archive, genre tree, lifecycle, or dashboard is treated as the cultural architecture.Recover the relevant Methods, Work, subjects, memory epistemes, mediation, recognition, selection, measurement, and refresh relations; use architecture patterns only for actual architecture claims.
Onto-EpistA familiar label, publication, model, score, or intervention card becomes the practice, population, variant, relation, performed Work, or effect.Recover the object and relation under the applicable pattern; keep descriptions and records distinct from the subjects and occurrences they describe.
PragEvery optional card field is filled, while the project still cannot say what is supported or worth continuing or changing.Start with the one-sentence case and open only fields whose identities change the current conclusion, proposal, Work, effect, comparison, or return.
DidSpecialist evolutionary language or formal relation lists hide the recognizable project situation.Use ordinary language first, then add the smallest exact terms and pattern references needed to make the claim and next action clear, including any boundary against a real overread.