FPF Reference

    G.9:4.1 — Objects and publication records

    Preface node heading:g-9-4-1-objects-and-publication-records:105542

    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 exact 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):

    ParityPlan := ⟨ ParityPlanId(UTS), // continuing plan lineage planEdition, // one immutable edition CGFrameId?, // exact cited CG frame when the plan depends on one entityOfConcernRef? := EntityOfConcernRef, // one-EntityOfConcern branch only targetRefs[]?, // exact-target branch only; existing kinds and editions groundingHolonRef := GroundingHolonRef, referencePlaneRef := ReferencePlane, claimScopeRef := ClaimScope, EvaluationWindow, UNM_id?, NormalizationMethodId[]?, NormalizationMethodInstanceId[]?, // when “normalize, then compare” is required (ids only; semantics come from CN‑Spec / UNM) EpsilonDominance?, // optional ε-front thinning (ε≥0; id/param; pinned when used) PortfolioMode?, DominanceRegime?, // may be explicit or inherited via DefaultGoverningDefinition (semantics follow G.5) BaselineSet, // exact method-family or generator-family targets (ids; notation-independent) BaselineBindingRef, // evidence-backed baseline-set reference that says what counts as baseline FreshnessWindows, CNSpecRef.edition, CGSpecRef.edition, ComparatorSpecRef.edition, // edition-pinned refs SCPRef.edition?, // optional (when a specific SCP profile must be pinned/cited) MinimalEvidenceRef.edition?, // optional (when CG-Spec exposes minima profiles by ref) Budgeting?, ParityPinSet, EvidenceGraphId, PathId[], PathSliceId?, PlannedFillingRows[]? // declaration-local A.15.3 content inside this WorkPlan; no independent row refs ⟩

    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. The lineage id may remain only while this is still the same continuing plan; old ParityPlanRef values continue to resolve their old 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 direct comparison of <ThresholdTrendReview-local, R3> and <SpectralResidualReview-local, R2> puts those two exact 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 exact 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). The concrete contents are pattern-local (G.9 declares the pin set), but must satisfy the core pin discipline via 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 running one exact ParityPlanRef. By itself it is not a dated U.Work occurrence, audit performance, evidence path, assurance result, or gate decision; those claims require A.15 and A.15.1, A.10 and G.6, B.3, or A.21 respectively.

    ParityReport := ⟨ ParityReportId(UTS), parityPlanRef := ParityPlanRef, entityOfConcernRef?, targetRefs[]?, // exactly one subject branch is present groundingHolonRef, referencePlaneRef, claimScopeRef, EvaluationWindow, BaselineSet, BaselineBindingRef, FreshnessWindows, CNSpecRef.edition, CGSpecRef.edition, ComparatorSpecRef.edition, SCPRef.edition?, MinimalEvidenceRef.edition?, // echoed iff used/pinned in the plan UNM_id?, NormalizationMethodId[]?, NormalizationMethodInstanceId[]?, // echoed iff used in the plan OutcomeRefs, // selected-set / archive outcomes (as refs to selector outputs) EpsilonDominance?, // echoed when used AbstainReasons[]?, // ids/labels (policy-bound) for abstain/degrade; refusal paths included TelemetrySummary? := ⟨IlluminationSummary?, coverage?, regret?⟩, // report-only by default; promotion requires CAL policy-id pins GuardOutcomeTraceRef?, // pass/degrade/abstain trace + cited reasons (policy-bound) EvidenceTrace := ⟨EvidenceGraphId, PathId[], PathSliceId?⟩, CrossingPins?, // Bridge/CL/Φ/Ψ/Φ_plane pins, when crossings are invoked EditionPinsDelta?, // explicit list of edition pins actually active during the run PolicyPinsDelta?, // explicit list of policy-ids actually active during the run RSCRRefs[] // parity RSCR test ids / trigger emissions ⟩

    The report carries the exact 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.

    • Heads reuse existing U‑types and LEX discipline; no new “strategy” primitive is minted here.
    • The older labels ParityPlan@Context and ParityReport@Context are retired. The suffix named neither identity nor comparison basis; current records are ParityPlan and ParityReport, 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-09-03 — upstream FPF commit b999972c (github.com/ailev/FPF)