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:16:27 UTC · snapshot created 2026-10-03 05:17:06 UTC · last check 2026-10-03 05:16:56 UTC

E.18.NET:7 - Conformance Checklist

IDRequirementFailed-check repair
CC-E18-NET-01 Three-way discriminatorThe case is explicitly distinguished from several valuations of one exact TFS and from one E.18 SubflowRef.Return to member identity and relation basis; do not decide from diagram shape, team labels, or stage names.
CC-E18-NET-02 A.22 identityExact direct members, selected obtaining cross-flow occurrences, applied constraints, and one concrete selection-use frame are recoverable.Recover the missing discriminator or stop at a proposed description.
CC-E18-NET-03 Independent membersEvery member keeps its own TFS or independently identified E.18.NET-conforming network identity, transformations, Work, valuations, boundaries, and local state.Split any merged object; reidentify each member under E.18 or E.18.NET and restore its own Work, valuation, boundary, and state.
CC-E18-NET-04 Finite acyclic membershipEvery member path is finite and no member path returns to the same network.Repair the selected member set or return the cyclic-membership blocker; do not add level kinds.
CC-E18-NET-05 Exposed positionEvery ExposedFlowPositionRef resolves hop by hop to an exposed leaf TFS position.Recover the missing member hop or boundary exposure; do not flatten the nested network.
CC-E18-NET-06 Leaf-local stateEvery valuation, path slice, and DesignRunTag remains attached to one exact leaf-TFS binding.Remove the network-global state field and restore the local bindings.
CC-E18-NET-07 Direct relationsEvery selected cross-flow relation has an admitted kind, applicable predicate, exact positive obtaining occurrence, complete participant order, and grounded endpoint bindings. The governing pattern’s relation result remains distinct from E.18.NET selection blockers.Carry that pattern’s exact missing-governor, missing-information, factually unsupported, or positive result; carry an inapplicable or negative result only when that pattern defines it and the case basis establishes it. After a positive result, name a missing endpoint binding separately; do not rewrite it as a relation failure.
CC-E18-NET-08 N-ary preservationParticipant count, order, kinds, positions, and direction match the direct relation.Restore the direct participant signature and remove invented binary decompositions.
CC-E18-NET-09 Record and row-locator separationMember rows and relation rows describe already identified objects and occurrences; the record does not create them, and every NetworkCrossFlowRelationRowRef resolves exactly one nested row by record, occurrence, and ordered endpoint-binding identity.Separate the C.2.1 episteme from the selected U.Structure; repair or remove any locator that resolves zero or several rows.
CC-E18-NET-10 Non-agentivityThe selected network is non-agentive. Its identity needs no actor or selection-Work claim; any actual selection Work has a separately identified System performer and occurrence.Describe the network through direct members, selected obtaining occurrences, endpoint bindings, applied constraints, and its use frame. If actual selection Work is current, cite every precise performer’s A.13 core and the independent A.15.1 Work admission; cite F.6 only when exact assignment-bound attribution is also current. Keep result episteme, choice, decision, and accountability relations separate.
CC-E18-NET-11 Representation boundaryMathematical descriptions, graphs, views, publications, and demonstrations are identified separately and state preserved/lost structure when relied on.Apply E.18.2, C.29, E.17, A.22.CGUS, or E.18.3 as appropriate.
CC-E18-NET-12 Useful result or stopThe practitioner receives one exact network ref and return condition, or a proposed description with one exact reason selection cannot close: the governing pattern’s relation-claim result, or a separate absent member, applied constraint, use frame, endpoint, or position binding.Restore the exact result or blocker at its own layer; do not end with a local status taxonomy or make a network-selection blocker change the relation result.