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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 10:00:09 UTC

A.6.P.WMR:5.2 - ETL data: direct participation, then a receiving-use stop

An ETL note says, RawOrders is the source input and WarehouseOrders is the delivered output. Exact Work ETL_Nightly_0811 and both dataset entities under their admitted subject kinds are known. Exact relation-declaration episteme ETL-DATA-REL-2025 contains the defining ClaimGraph for SourceDatasetParticipatesInETLWork and DestinationDatasetParticipatesInETLWork; separate case facts say that RawOrders_0811 and WarehouseOrders_0811 satisfy the declared source-dataset and destination-dataset participant meanings and predicates for that job.

Write: RawOrders_0811 participated as the source dataset in ETL_Nightly_0811, and WarehouseOrders_0811 participated as the destination dataset in ETL_Nightly_0811. Those facts establish neither delivery nor use by analytics. If decision Work D-0811 is now claimed to use WarehouseOrders_0811 as a premise but no premise-use, reference-use, or application-binding governor is available, stop with missing-governor and name the missing analytics-decision predicate and receiving use. This case demonstrates a positive direct relation followed by a distinct blocked receiving use.

Before calling WarehouseOrders_0811 a new output, decide which dataset continues. If the ETL job updates the same dataset in place, identify that dataset’s bounded change under A.3.4. If a derived dataset begins, apply its dataset-identity rule and use A.15.PROD only when the exact inception basis closes. When a catalog entry, lineage view, or publication is the source from which a reader reaches either dataset, use C.2.P to identify the exact source expression, source-to-use path, allowed use, and reopen condition. An E.17 face or form, or an E.24.PUB publication or availability occurrence, neither creates the dataset nor proves that analytics used it. Row-count, quality, latency, and drift results remain separate measurement or evaluation objects; each evaluation names its own criterion and predicate and cites the SubjectPatternLocator for their defining or constraining content.