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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:20:10 UTC

A.14:5.3 - AspectOf — bearer-dependent structural part under one named facet rule

Intent. State that one identified bearer-dependent part is an aspect of its bearer without turning a Characteristic, viewpoint, representation, concern, partition, or time window into a part.

Participants and qualifier. x and y occupy the U.Holon parthood domain: x is the aspect and y its bearer. Each must already satisfy its applicable holon-kind and identity rule; AspectOf does not grant systemness, agency, or independent-whole status. The qualifier f names the facet rule used in this occurrence; it does not introduce a universal U.Facet kind.

Primitive. AspectOf(x, y; f) means: x is the bearer-dependent structural part of y distinguished under facet rule f. The notation shows the required qualifier; the public sentence may remain “x is an aspect of y under the f rule.”

Obtaining conditions and properties (A14-ASP-*).

  • ASP-1 (Identified occurrence). Name x, y, f, the relation occurrence, and the aspect-identity rule. The facet rule states what distinguishes x from the rest of y and what change preserves or ends this aspect.
  • ASP-2 (Structural dependence). AspectOf(x,y;f) implies ut:StructPartOf(x,y), x != y, and asymmetry for that occurrence. It implies none of ComponentOf, ConstituentOf, PortionOf, PhaseOf, collection belonging, or independent systemhood.
  • ASP-3 (Facet-local and non-transitive). An occurrence under f gives no occurrence under another facet. AspectOf is not assumed transitive through another bearer or facet; state every relied-on relation directly.
  • ASP-4 (Bearer and aspect identity). If the bearer is reidentified, or f and the aspect-identity rule no longer identify x, the old occurrence ends. A changed view, diagram, name, or measurement does not by itself change the world-side occurrence.
  • ASP-5 (Neighbor boundary). A measured quality routes to C.16/A.19; a viewpoint or view to E.17.0/E.17.1; a representation or projection to C.29 or its direct projection pattern; a selected temporal window to PhaseOf or C.27.TA; a selected partition to the pattern governing that structure. None creates AspectOf by selection alone.

Didactic tests.

  • ✓ In Reactor-7, the thermal-boundary rule distinguishes ThermalEnvelope-7 as the connected enclosure of insulation panels, seals, and boundary interfaces that constrains heat transfer across the reactor boundary. ThermalEnvelope-7 is identified by the continuing enclosure under that rule, not by a fixed panel list. AspectOf(ThermalEnvelope-7, Reactor-7; thermal-boundary) obtains while that enclosure and Reactor-7 continue. Replacing one panel under the same rule preserves the aspect; dismantling the enclosure, replacing the facet rule with a different boundary, or reidentifying Reactor-7 ends the occurrence. A changed temperature reading or dashboard view does not.
  • ✗ “Safety is an aspect of the design” when safety is only a Characteristic, concern, viewpoint, or heading. Recover that actual claim first.
  • ✗ “Pump-7 during warm-up is its thermal aspect.” Use PhaseOf for the proper temporal restriction and A.19 for a measured thermal Characteristic when those claims obtain.