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

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

A.15.3:2 - Problem

Without this boundary, five failures recur:

  1. Generic slot creation. Any description field named input, output, role, result, or parameter is treated as a SlotSpec.
  2. Declaration-family collapse. RelationSignature SlotSpecs and operation arguments or results are placed in one undifferentiated slot schema.
  3. Plan-as-actual inference. A planned value is treated as a participant in an obtaining relation or an actual operation binding.
  4. Description-as-declaration inference. A U.MethodDescription that mentions an input or effect is treated as if it declared a reusable participant locus.
  5. Baseline rewrite. Performed values are copied back into the plan, erasing substitution and variance.