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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 05:05:10 UTC

A.15.PROD:5.2 - Incomplete but identifiable Ship 27

Identity rule and applicability. Exact ship-identity specification episteme SHIP-ID-2 states the hull-closure rule. Local applicability claim ShipIdentitySpecApplies-2 applies it to exact candidate hull basis Ship27-HullBasis, exact yard context Yard-27, and the ordered candidate boundaries ending at inceptionBoundary.

Entity inception before later Work ends. Exact hull-assembly work can close that specification’s rule at inceptionBoundary while outfitting, software installation, trials, and commissioning continue. The resulting inception claim concerns when Ship 27 first exists and remains indexed by SHIP-ID-2 and ShipIdentitySpecApplies-2.

Ordinary answer. Ship 27 first exists at inceptionBoundary under that exact specification and applicability basis; later Work continues, and production completion remains a separate question.

Continuing edition — assignment declaration. ShipIdentityRuleRevisionAssignmentSpecies is a directly declared U.SystemRoleAssignment species. Its ordered positions are holder and assigned system-role kind, with holder domain U.System and assigned-kind domain ShipIdentityRuleReviserSystemRoleKindDomain.

Continuing edition — assignment predicate. The predicate applies to ship-identity revision Work in Yard-27 under ShipIdentityRuleRevisionMethod. It obtains when the holder supplies that revision contribution throughout the declared interval. Holder, assigned-kind value, Yard-27, and that uninterrupted interval identify one occurrence.

Continuing edition — Work and Method. Applying the common route in section 4.2, A.13 recovers YardIdentityGovernanceSystem through obtaining ShipIdentityRuleReviserAssignment-2R, whose assigned-kind value is ShipIdentityRuleReviserSystemRole and whose interval covers the full Work. A.15.1 independently admits ShipIdentityRuleRevisionWork-2R with the enacted revision Method. Because this branch consumes precise assignment-bound attribution, F.6 then relates the admitted Work through that same assignment.

Source expression and predicate. C.2.P recovers the source expression hull assembly closes Ship 27 identity in SHIP-ID-2. Predicate-definition episteme YardRevisionSourceUsePredicates-v1 declares case-local predicate usesAsRevisionSource(work, sourceEpisteme) with participant order <revision Work, source episteme>.

Source-use obtaining test. The predicate applies only to ship-identity revision Work under ShipIdentityRuleRevisionMethod. It is true only when that Method application opens the source episteme and uses the selected source claim as a premise.

Edition basis. The exact source-use participants are ShipIdentityRuleRevisionWork-2R and SHIP-ID-2. The revision Work opens SHIP-ID-2, selects its hull-closure claim as an explicit premise, and produces SHIP-ID-2R, whose separate C.2.1 ClaimContent says that hull assembly plus installed propulsion closes Ship 27 identity. Those facts make usesAsRevisionSource(ShipIdentityRuleRevisionWork-2R, SHIP-ID-2) obtain.

The applicable continuity rule for this specification family requires exact use of SHIP-ID-2, preservation of the ship EntityOfConcern and listed identity claims, and explicit identification of the corrected claim content without a reference-scheme retargeting. The current source use and preserved and deliberately changed features satisfy that rule, so ShipIdentitySpecEdition-2-to-2R : EpistemeEditionRelation obtains for SHIP-ID-2 and SHIP-ID-2R. The performer, Method, Work, provenance, and replacement facts supply evidence for the test; no label makes continuity true. The lineage carries forward neither old applicability nor a new inception boundary.

Lineage blockers. Keep the two failures distinct:

  • If the source-use predicate is not defined, return missing-governor[SHIP-IDENTITY-REVISION-SOURCE-USE].
  • If its definition is current but the actual premise-selection facts cannot be recovered, return missing-information[SHIP-IDENTITY-REVISION-SOURCE-USE].

Either result keeps SHIP-ID-2R usable as a separately identified specification episteme but blocks ShipIdentitySpecEdition-2-to-2R. A similar title, later date, common publisher, or bare provenance edge does not restore that lineage.

Non-continuing replacement. SHIP-ID-3 is another exact specification episteme, but this fixture establishes no EpistemeEditionRelation from SHIP-ID-2 or SHIP-ID-2R to it. A later date, similar ship terminology, and use by the same yard do not make it an edition. A use selecting SHIP-ID-3 must establish its applicability independently and constitute a separately qualified C.2.1 claim or return the exact blocker; lineage-based refresh cannot substitute it for either earlier specification.

The continuing edition reopens dependent current uses through the named lineage. The non-continuing replacement opens a new applicability question without altering earlier claims.

Author-side substrate. Exact substrate edition YardIdentityHistory-v3 defines time-indexed conjunction over the named work, applicability, actual-effect, work-to-change, change-to-identity, and identity-satisfaction claims. It also defines earliest selection over its declared ordered candidate-boundary domain.

The positive replay returns exact boundary tI because the identity predicate stated by SHIP-ID-2 is false at every earlier candidate boundary and true at tI. Exact Work and transformation witnesses remain named.

Nearest substrate failure. A snapshot substrate can conjoin facts at tI but supplies no ordered boundary domain or earliest-selection law. It cannot establish inception even if a later image satisfies the rule, so the branch returns the exact missing-substrate blocker rather than treating first observation as first existence. The example adds no universal earliest operator or arbitrary minimal-work selection.

Designation is not identity. The current IMO integrated scheme uses an IMO ship identification number as a stable designator across later flag, name, ownership, or type changes and states that allocation does not define ship status. Ship identity and continuity therefore still require their applicable subject rules. If the receiving use cannot recover a separate ship-identity rule for this candidate basis and boundary, the inception branch returns the exact identity-governor blocker.

Larger Work. A larger exact production-work occurrence contains the identity-closing and later Work through declared A.15.1 part relations.

State satisfaction. At completionBoundary, one claim may state that Ship 27’s actual state satisfies the applicable completion criterion.

Work closure. A separate yard closure predicate or local claim must connect that satisfaction to completion of the larger production Work. Without it, preserve the state claim and return missing-governor[SHIP27-PRODUCTION-WORK-COMPLETION].

Delivery, class acceptance, and operational release remain separate. The sentence the yard produced Ship 27 is admissible only after the writer selects Work participation, first existence, state satisfaction, or Work completion.