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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:10:10 UTC

A.6.RCD:5.1 - Promise-content fulfilment: use the existing direct A.2.3 predicate

Situation. PromiseContent_Housing42_v3 says that exact housing Housing_42 must be delivered to AssemblyCell_B during Interval_42, satisfy OutcomeSpec_Housing42_v3, and satisfy the acceptance predicate in AcceptanceSpec_Housing42_v3. The actual delivery work is the independently identified U.Work occurrence Work_DeliverHousing42; it is not the delivered entity, the post-delivery state, the evaluation, or the acceptance result.

A.2.3 predicate and required subset. A.2.3 already supplies the direct predicate fulfilsPromiseContent(W, SC), so disposition 1 is available. For this exact promise-content edition, the necessary and sufficient world-side subset is:

  1. PromiseContentUse(Work_DeliverHousing42, PromiseContent_Housing42_v3, Interval_42) obtains;
  2. PromisedOutcomeDeliveryRelation(Work_DeliverHousing42, OutcomeSpec_Housing42_v3) obtains because the selected work facts, exact delivered entity Housing_42, and its post-delivery state satisfy that OutcomeSpec; and
  3. the acceptance predicate in AcceptanceSpec_Housing42_v3 is satisfied for those exact facts and states.

No production or entity-inception claim is current because Housing_42 already existed before this delivery work. This edition requires no additional generic transfer or institutional-acceptance relation beyond the two A.2.3 relations and its acceptance predicate. If another edition requires one, it must name that exact direct relation and its participants rather than adding a delivery work bundle.

Evaluation, result, and evidence. Separate evaluation work Work_InspectHousing42 applies the declared acceptance method. Its exact operation-result binding carries the verdict value; optional episteme InspectionVerdict_Housing42 states that evaluation result. An A.10 evidence-use relation may support reliance on the affirmative fulfilment assertion. The evaluation work, result binding, verdict episteme, and evidence-use relation neither become parts of Work_DeliverHousing42 nor make PromiseContentFulfilmentRelation obtain. The three world-side conditions above make the direct relation obtain; evaluation and evidence only support an assertion about it.

Positive case. All three required conditions above are satisfied, so the direct predicate is satisfied and a claim-bearing episteme may state fulfilsPromiseContent(Work_DeliverHousing42, PromiseContent_Housing42_v3) without creating the occurrence.

Discriminating failures. Work_DeliverHousing42 can occur and Housing_42 can be in the target post-state while PromiseContentUse is absent or concerns another promise edition; then PromisedOutcomeDeliveryRelation for this promised outcome does not obtain and the promise is not fulfilled. Or the delivery relation can obtain while one acceptance condition is false; an accepted label or report cannot repair that failure. Missing evidence leaves reliance on the assertion unresolved; it creates neither fulfilment nor non-fulfilment.

Disposition and stop. Stop at disposition 1 under A.2.3. No new compound-law episteme, predicate definition, relation kind, or RelationSignature is needed. Use A.6.REL only if a later use must distinguish this fulfilment occurrence from another occurrence of the same admitted relation.