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

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 05:05:10 UTC

A.6.RSIR:1 - Problem frame

The RSIR cluster sits at a common failure point in FPF texts. A project team sees one word and treats it as if it already selected the ontology:

  • bare “role” whose E.10.ROLE branch may be a system-role kind, assignment, direct relation-participant meaning, declaration-local SlotKind, representation position, evidence use, another exact object, or ordinary wording;
  • “interface” in a module relation, functional port, API description, protocol, signature, or publication view;
  • “slot”, “field”, “parameter”, or “argument” in wording about an actual relation participant, a RelationSignature declaration, an A.6.1 argument or result declaration, one actual operation application and bound value, a data, formula, or method-call representation, or ordinary prose;
  • “signature” in a law-governed declaration, API shape, interface specification, or plain sign-off phrase;
  • “function” in architecture, capability, method, work, mathematical modeling, or quality wording.

A.6.RSIR is the first-level recovery pattern for this bounded cluster. It does not decide every neighboring subject ontology. It helps the practitioner recover which object or claim is current, identify the rule that defines or tests it, and then stop the RSIR repair.