Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:45:12 UTC

A.3.4.P:6 - Bias-Annotation

This pattern intentionally biases toward kind recovery before wording repair. It resists:

  • source-label ontology: familiar labels such as pipeline, process, network, circuit, or workflow become FPF kinds;
  • graph or path overread: graph path, evidence path, and carrier path become action route, evidence sufficiency, assurance, deontic permission, work authorization, release authorization, or work sequence;
  • function collapse: functioning, functional element, module allocation, mathematical function, software routine, and everyday purpose collapse into one “function”;
  • semio displacement: descriptions and publications of transformations replace the transformation under concern;
  • neighboring-object fusion: wording is used to infer a Method, mechanism, Work occurrence, System, influence source, or evidence record and then to treat it as the transformation, its actor, or a transformation participant before its direct kind and relation are recovered. Actor recovery follows A.3.4.P:4.4.