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

C.37:4.8 - Direct exits and boundary cases

CaseC.37 disposition
One direct domain Method already selects one representation–operation configuration for the same one use and returns its limits, as RHY.5 does for rhythmic-representation choice.Use that Method and result; do not invoke C.37 for a duplicate account.
A candidate is called a view but EpistemeViewpointConformanceRelation(E,P) fails or cannot be evaluated.Decline it for the view-dependent use or mark that row unresolved. C.37 cannot grant U.View membership. Another independently positive direct basis may support a different row and claim.
A candidate is a mathematical graph or other mathematical object.First identify the object and obtaining subject relations under their direct patterns; then use C.29 for the explicit lens, mapping, preserved and lost structure, admitted use, and stop. C.37 neither admits the object nor makes the mapping obtain.
A candidate is an ordinary non-graph diagram.Identify its episteme and subject. Require an exact positive conformance, representation, correspondence, or domain result for the selected claim. Add A.10 when evidence is relied on. Publication, carrier, provenance, or C.2.P.DR repair cannot supply the missing basis or receiving result.
Several project, process, or case viewpoints concern one Work.Co-record them only when each can change the same exact action about that independently identified Work. A viewpoint for another action starts another account.