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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 11:55:15 UTC

PRACTICE-ARCHITECTURE — Connect methods with their use, support and development

  • Situation: A decision about methods depends on performed or planned Work, capabilities, providers, descriptions, tools or cultural change whose structures do not align one-for-one.
  • Question: Which relations change how the methods can be used or improved?
  • First useful result or blocker: One readable synthesis, one bounded development action, or the exact missing Work case, relation, or transfer evidence.
  • Mantra: Start from representative Work and its needed result, or a proposed use with a later-test condition. Keep Methods, Work, capabilities, providers, descriptions, tools and cultural processes distinct; compare the structures that conflict; develop a limiting capability when needed; test transfer in real Work; return when the method, provider, evidence or style changes.
  • Start with: C.32.MWA; use E.23.CDI, E.23, or C.36 only for the question actually opened.
  • Stop or return: Stop when the synthesis or transfer result answers the decision. A method description is distinct from the method and from performed Work.