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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:40:20 UTC

A.2.2:14 - Neighboring Claims

Keep the direct governor of each neighboring value needed by the ability or fit claim:

  • local system-role kind, direct system-role assignment, SystemRoleAssignmentStateRelation, structure of relations among system-role kinds, or system-role-kind description;
  • method, method family, method description, or algorithm description;
  • work plan, work occurrence, run record, or measurement trace;
  • evidence graph, source record, model card, standard, report, dashboard, publication, or specification-use relation;
  • promise content, commitment, permission, authority relation, or policy decision;
  • U.Characteristic, scale row, coordinate, score, metric, indicator, or threshold;
  • C.25 Q-Bundle, quality-family label, mechanism, status, or evidence slot;
  • architecture-characteristic starter head, project criteria row, eval program, eval reading, selected-structure adequacy claim, or architecture-description concern;
  • capability-fit predicate, gate, admission relation, or work-entry readiness record;
  • structural part, module, interface, port, or functional structure unless the current claim is the ability of a holder system expressed through that structure.

These values may contribute to a holder-ability claim, its support or a receiving fit check. Name the neighboring value, record, relation, or predicate through its own governing pattern when that neighboring claim is current.