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 07:42:37 UTC · snapshot created 2026-10-03 07:43:27 UTC · last check 2026-10-03 08:00:10 UTC

A.14:9.1 - Global firewall and scope

IDRequirementPurpose
CC-A14-0A local system-role kind MUST NOT occur as a node in any partOf chain by kind identity; a U.System classified by that kind remains eligible for holon mereology on its independent system identity. U.Method MUST NOT occur in A.14 structural ComponentOf or structural partOf chains by method identity alone; A.3.1 and B.1.5 define submethod assembly. If an exact admission predicate establishes a different entity, such as a SystemRoleKindDescription, Work occurrence, U.SystemRoleAssignment occurrence, SystemRoleKindRelationStructure, method relation structure, or episteme, name that entity, assertion, and subject-pattern locator.Keeps local system-role kinds out of holon mereology by kind identity and keeps method holarchy out of structural component mereology while preserving admitted entities.
CC‑A14‑0aU.MethodDescription / U.WorkPlan and other describing epistemes MAY participate in partOf only as U.Episteme nodes: content ConstituentOf, measured text PortionOf, or PhaseOf for a proper interval of one unchanged C.2.1 identity. A changed C.2.1 discriminator identifies another episteme; connect two such identities only through an independently obtaining EpistemeEditionRelation. They MUST NOT be asserted as ut:StructPartOf of any U.System.Allows episteme structure and legitimate temporal restriction without smuggling Methods or automatic edition continuity into structure.
CC‑A14‑0bA collection-belonging relation MUST NOT be inferred or auto-rewritten as any partOf sub-relation. This non-inference does not prohibit a separately grounded constructive part relation for the same entities.Separates collection belonging from parthood without assuming they can never coexist.
CC‑A14‑0cSerialStepOf / ParallelFactorOf MUST NOT appear in any partOf chain or table in A.14; model order and concurrency potential via A.15 and direct method-composition patterns such as B.1.5. If a node linked by those relations is also a submethod, state that U.Method claim separately before using method holarchy.Prevents the “order‑as‑structure” and “edge-as-part” category errors.