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

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 06:35:10 UTC

E.24.UK:5.0 - Five Replays Through One Decision Sequence

Use the same five steps in every replay: (1) identify the decision’s EntityOfConcern and named use; (2) test an existing durable kind, direct relation, and bounded C.3 classification; (3) state governed individuals, membership or identity, intended extent, and the nearest non-member; (4) run all eight conditions, the shared E.24-family settlement, and the A.11/A.8 branch when current; (5) record one result reference, naming result, non-use boundary, and reopen condition. A future genuinely new candidate must complete this sequence before its public name is admitted.

In each closed replay, the E24UK-* reference identifies the exact admission-result episteme or reconstructed result. The five steps summarize that result and, when a current shared decision exists, point to its separate ClaimGraph; the effective reference scheme is FPFCoreReferenceScheme. A stopped replay names the exact blocker instead of pretending that an admission result exists.

Reconstructed root — U.Relation.

  1. Subject and use. The EntityOfConcern is the A.6.REL source construct for the common kind of individuable obtaining relation occurrences. C.2.1 and receiving direct relations need to refer to one exact occurrence without turning an assertion, row, or graph edge into that occurrence.
  2. Coverage. No other admitted durable kind covers all and only those occurrences. A bounded C.3 kind would not supply the cross-pattern root used by direct relation patterns.
  3. Membership. An individual enters the extent only when its direct relation pattern establishes obtaining and supplies an occurrence-identity rule under A.6.REL. Predicate content, an assertion, description, designator, reference, tuple, or edge is the nearest non-member.
  4. Eight tests and settlement. Governed individuals, stable occurrence identity, direct-pattern witness, action-facing occurrence use, non-duplication, A.6.REL plus the direct relation pattern, accepted result E24UK-AR-URELATION-R11-01, and by-value reliance are all present. A.11 retains one common root rather than duplicating it for every direct relation; A.8 does not promote relation-specific names into additional universal roots. This reconstructed result has no fabricated settlement suffix.
  5. Result and flip. E24UK-AR-URELATION-R11-01 records root; NC-U-RELATION retains the Tech label U.Relation. Reopen when the common occurrence criterion, direct identity discipline, dependent use, or settlement law changes. If an already admitted kind is found with the same governed extent and use, the disposition changes to reuse.

Same-individual dependent — U.WorkPlan.

  1. Subject and use. The EntityOfConcern is A.15.2’s WorkPlan kind-source construct; MaintenancePlan_Q3 is a member witness, not the decision subject. Planning and readiness patterns need one durable way to recognize substantive intended-work epistemes.
  2. Coverage. U.Episteme already supplies individual identity, but it does not by itself distinguish epistemes that substantively coordinate intended work. A one-project classification would be tested under C.3 before durable admission.
  3. Membership. C.2.1 identifies MaintenancePlan_Q3; A.15.2’s plan-membership predicate classifies that same individual as U.WorkPlan and implies its root U.Episteme membership. A calendar image or ticket title without substantive intended-work claims is the nearest non-member.
  4. Eight tests and settlement. Identified epistemes, C.2.1 identity, the A.15.2 membership witness, planning use, non-duplication, A.15.2 as direct locus, accepted reconstructed result E24UK-AR-UWORKPLAN-RG-01, and by-value A.15 reliance are present. Under A.11’s test, the result is a same-individual dependent kind rather than a second root or plan object; no new A.8 universal root is claimed. This replay does not invent a separate settlement identifier.
  5. Result and flip. E24UK-AR-UWORKPLAN-RG-01 records same-individual-dependent; the existing Tech label U.WorkPlan is retained and this replay mints no new name. Reopen when C.2.1 identity, A.15.2 membership, the planning use, or settlement law changes. If only one bounded project needs the distinction and one exact C.3.2 declaration suffices, the disposition changes to local-kind.

Same-individual structure specializations — BoundedModelUseStructure and the A.22 conditional crossing-analysis rule.

  1. Subject and use. The decision subjects are the A.22 source constructs for base U.Structure and its two model-use specializations. A.1.1 and crossing-analysis consumers need durable membership without turning a context, team, subsystem, description, or view into another structure individual.
  2. Coverage. U.Structure supplies the one base identity. The two specialization conditions add stable action-facing membership to that same individual; neither needs an independent root or an identity-dependence relation to a context-like bearer.
  3. Membership and near-misses. A.22 first identifies PressControlUse_S from exact constituents PressControlModel-5, Press-3, and PressControllerCode-17; selected obtaining ModelApplicabilityRelation, ModelUseRelation, and ModelExpressionCoherenceRelation occurrences; an exact applied safety-control constraint claim whose proposition refers to the claim scope used by that selection; and the named use “decide whether operating use and controller-code maintenance belong to one bounded model-use organization.” That claim may state a proposition about the scope or its A.2.6 membership predicate; neither the bare scope nor the membership outcome is the constraint claim. Only then may the same PressControlUse_S satisfy BoundedModelUseStructure. The supplier-to-billing material currently supplies only a proposed six-part crossing organization—source SupplierUse_S, target BillingUse_S, direction, required fit, permitted loss, and claim scope. SupplierToBillingTranslation_R and SupplierBillingCrossing_S are not asserted: no compatible exact crossing predicate and current facts make the crossing obtain, so the A.22 relation-occurrence discriminator and base identity are unavailable. Only after that predicate is defined, current facts satisfy it, and all four A.22 discriminators are established may the same identified structure satisfy the conditional crossing-analysis specialization. PressControlTeam, a BillingContext label, ContextMap_v3 as a U.View, its diagram, and its publication occurrence identify none of those structures and grant no specialization membership.
  4. Eight tests and settlement. Governed base-structure and bounded-model-use individuals, A.22 identity and positive bounded-model-use membership witnesses, action-facing model-use needs, non-duplication, A.22 as direct locus, the relevant settlements, and by-value reliance are present. For the conditional crossing-analysis specialization, this replay settles only the same-individual-dependent membership rule and its action-facing need; it has no positive witness and no public F.17 row while the direct crossing governor is absent. A.2.6 contributes only when an applied constraint refers to an exact claim scope. That constraint, not the bare scope, membership outcome, or its representation, occupies the third discriminator.
  5. Result and flip. E24UK-AR-USTRUCTURE-R12-01 records root; E24UK-AR-BMUS-R12-01 records the current named same-individual-dependent specialization; E24UK-AR-A22-CROSSING-RULE-R12-01 records only the conditional same-individual-dependent crossing-analysis rule without asserting a current member or public term. Each specialization implies U.Structure membership only for the same individual that satisfies its exact A.22 condition. If the four base discriminators cannot be recovered, stop at the exact description or representation. If base identity is established but one specialization condition fails, retain only the base U.Structure; do not repair the failure with a context label, another structure identity, holonhood, or view typing. Reopen only when the A.22 identity or specialization condition, the A.2.6 applied-scope interface, the named reliance, or the shared settlement law changes.

Rejected near-miss — a separate U.Capability individual.

  1. Subject and use. The source construct proposes Pump37MaintenanceCapability_2026 as an individual distinct from holder Pump37. Recover what planning, promise, work-fit and development uses actually need: what the pump can do under stated conditions and bounds, with the warrant required for the receiving use.
  2. Coverage. The holder retains U.System identity. An identified ability assertion uses C.2.1 U.Episteme identity. The proposition, its assertion, support and demand-fit result need no second capability individual; no additional local classification is needed for those uses.
  3. Discriminating cases. New evidence can change support without performance change. A stricter throughput demand can change fit. Calibration can change actual ability with unchanged paperwork. Loss and recovery change the qualified predicate at the stated times; replacing the holder changes the assertion’s subject. None requires reidentifying a second individual.
  4. Tests and result. No additional classificatory distinction survives recovery, so E24UK-NAR-U-CAPABILITY-01 records reject. This rejects the new kind commitment, not the reality of the holder’s ability. A holder-indexed tuple cannot substitute for an independently needed subject and identity rule.
  5. Reopening condition. Reopen only for a concrete receiving use in which continuity of a separate object changes the answer and supplies the required identity facts, including any obtaining dependence relation and its identity effect. A new record, evidence window, ability label or local-kind declaration alone does not supply that need.

Rejected near-miss — U.EpistemePublication.

  1. Subject and use. The EntityOfConcern is the proposed kind source construct for an episteme made available to an audience; the use is to speak plainly about that availability.
  2. Coverage. U.Episteme already identifies the episteme, while E.24.PUB defines the exact publication occurrence, selected edition, audience, use, and publication-form boundary.
  3. Failed membership. Publication participation can begin and end without reidentifying the episteme and supplies neither a stable dependent-membership predicate nor a distinct individual. An unpublished edition of the same episteme is the discriminating near-miss.
  4. Failed tests and settlement. Stable membership and non-duplication fail; E24-OS-EPISTEME-ONTIC-01 and the E.24.PUB rules already identify the needed objects and publication relation. Applying the A.11 duplicate-kind test records rejection; do not apply A.8 or begin naming.
  5. Result. E24UK-NAR-EPUB-01 records reject. Use Plain published episteme only in a claim that identifies or permits recovery of the obtaining EpistemePublicationRelation; admit no U.EpistemePublication name. Reopen only if a later cited rule defines a stable classificatory distinction not reducible to publication participation.