G.9:4.1 — Objects and publication records
Preface node
heading:g-9-4-1-objects-and-publication-records:140511
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
All objects below are notation‑independent; serialisations (if any) are handled in shipping and interop publication forms, not here.
(1) ParityPlan (one U.WorkPlan episteme; ParityPlan is the local application name)
A plan that fixes what is being compared and under what pinned conditions.
Minimal fields (conceptual; ids/pins only):
ParityPlanRef := <ParityPlanId, planEdition> designates one immutable plan edition. Changing its subject, baseline binding, comparator edition, or another active value that can change the run or its interpretation creates a new planEdition.
When a G.5 selector consumes this comparison, pin its TaskSignatureRef in the plan. If that selector uses G.4 CAL gates, also pin its TaskMapRef and require the map's task-signature reference to match. Omit these selector inputs from a parity run that needs no selector.
A later edition may retain the lineage ID only if it continues the same plan. Earlier ParityPlanRef values still resolve their original editions.
Exactly one subject branch is present. Use entityOfConcernRef when the report compares results about one EntityOfConcern. Use targetRefs[] when the targets themselves are compared; each ref keeps the kind and edition defined by its existing subject pattern. In particular, a G.5 method-family target is an exact MethodFamilyRowRef, and a generator-family target is an exact GeneratorFamilyRowRef.
For example, a comparison of <ThresholdTrendReview-local, R3> and <SpectralResidualReview-local, R2> puts those two row refs in targetRefs[]; the plan may explicitly use the same two refs as its BaselineSet. A comparison of their results for Pump-P17 instead puts Pump-P17 in entityOfConcernRef, leaves targetRefs[] absent, and uses BaselineBindingRef to say how the two method rows supply results about that pump.
BaselineSet names the alternatives treated as the comparison baseline; it supplies targetRefs[] only when the plan explicitly says that the same exact refs serve both purposes. Otherwise the subject and baseline remain separate, and BaselineBindingRef records how that baseline applies to the named subject.
These values determine what is compared and when the parity claim is usable; do not add ParityContextId. If the plan relates expressions with distinct source-local meanings, first recover the exact F.17 cells and establish the required F.9 relation. A shared label, source note, or generic context identifier does not establish comparability.
(2) ParityPinSet (pin set)
A declared set of pins required for reproducibility and audit (editions + policy‑ids + UTS/Path pins).
G.9 specifies the contents of ParityPinSet under the common pin rules in G.Core.
(3) ParityReport (UTS publication record; work-result or audit-facing publication record only when the neighboring source exists)
A UTS-publishable parity publication record produced by a parity run under one ParityPlanRef. Work or audit occurrence claims use A.15/A.15.1; evidence-path claims use A.10/G.6; a separate named assurance claim uses B.3; and a gate decision uses A.21 under its applicable profile. Keep each such occurrence, path, or result distinct from the report.
The report carries the ParityPlanRef and echoes the BaselineBindingRef used in that edition. For example, if <PumpParityPlan, E4> used PumpBaselineBinding-E7 and a later E5 changes the binding or comparator, an old report still resolves E4 and PumpBaselineBinding-E7. A missing historical plan edition or binding is an unresolved required input; it is never replaced with the current value.
Naming discipline.
- Head names follow the existing kind definitions and LEX discipline.
- The older labels
ParityPlan@ContextandParityReport@Contextare retired. The suffix did not identify the object or the comparison basis. UseParityPlanandParityReport, with all operative conditions carried in explicit fields and exact refs. - Tech/Plain twins follow E.10 rules (no drift‑inducing synonyms in Tech).
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)