G.9:4.2 — Parity planning (one U.WorkPlan)

Preface node heading:g-9-4-2-parity-planning-one-u-workplan:140602

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

Planning records the conditions needed to repeat and interpret the parity run:

  1. Fix the baseline set. Choose the exact BaselineSet (MethodFamilies, and optionally GeneratorFamilies) used as the comparison baseline. When SoS-log or source-maturity values change baseline eligibility or interpretation, cite SoS‑LOGBundleId? and the source-maturity ids by reference; acceptance-gate thresholds remain in G.4 Acceptance.

  2. Bind subject, scope, and evaluation window. Choose exactly one subject branch: one entityOfConcernRef, or exact targetRefs[] under their existing kinds and editions. For G.5 families, use MethodFamilyRowRef or GeneratorFamilyRowRef, not a bare lineage id. Record the ReferencePlane, ClaimScope and EvaluationWindow. An empirical claim identifies its groundingHolonRef. For a comparison of two proven operation-count bounds on a formal domain, identify the bounds, their proofs and the domain. A computer that stores a proof supplies no empirical premise merely by storing it.

  3. Define baseline-set reference. Declare what counts as the baseline and how it applies to the selected subject in BaselineBindingRef (for example, through an EvidenceGraph path slice or an upstream shipped package or publication-record id). If BaselineSet also supplies the exact compared targets, say so and use the same refs by value; otherwise keep baseline and subject refs distinct.

  4. Equalise window (and budget, if pinned). Declare a single FreshnessWindows and apply it across all baselines; if Budgeting is used/pinned, it MUST be shared/pinned across baselines as well.

    When specialization is part of the parity claim, the same plan should also hold constant the declared task family or target scope cut, the work-measure threshold target, adaptation budget, prior exposure declaration, and freshness window. Identify what each candidate performed and what assistance it had. To compare the candidates' own acquisition, account for differences in support that could explain the result. If the arrangements themselves are being compared, retain each arrangement as the bearer of its performance. When transfer, retention, later efficiency, downside or corridor entry matters, keep the observations and the baseline supporting that claim under C.22.1:8.

  5. Pin governance, CSLC comparability and admissibility references, and comparator references. CNSpecRef, CGSpecRef, and ComparatorSpecRef are referenced with explicit edition pins.

  6. Pin measurement/comparator definitions (conditional). Where parity depends on mode‑specific definition records (e.g., DHC/QD/OEE), pin the relevant definition ids/editions/policies. The minimum required pins are declared by the applicable Extensions blocks (e.g., G.9:Ext.DHCParityPins, G.9:Ext.QDArchiveParity, G.9:Ext.OEEParity) and the referenced records they cite.

  7. Bind comparator choice to CG-Spec. Any numeric comparison or aggregation MUST be CSLC-admissible and cite the corresponding CG-Spec entry (ComparatorSpecRef). Compare corresponding coordinates on compatible scales and bases. A Pareto comparator can compare kWh with kWh and minutes with minutes in their own units. When a coordinate needs conversion or the admitted operation uses normalization, declare the applicable UNM_id?, NormalizationMethodId[]? and NormalizationMethodInstanceId[]? and establish that the mapping preserves the distinctions the comparator uses.

  8. Declare the required result. An admitted A.19.CPM comparison returns relation or poset tokens. Preserve established incomparability. CompareEligibility can also withhold comparison if required evidence is missing. Pin the dominance regime when using dominance, including for a frontier. Pin the portfolio mode when the operation uses one. Each can cite its applicable default through G.Core.DefaultGoverningDefinitionIndex. IlluminationSummary, coverage and regret remain telemetry unless a cited CAL policy promotes them.

  9. Attach planned fillings when applicable. If parity depends on planned slot fillings, this WorkPlan contains the relevant A.15.3 rows in PlannedFillingRows[]; each row points to a declaration member defined by its own pattern and has no independent reference or identity. Omit the field when no such row is needed.

  10. Publish the relation and its receiving use (when invoked). For distinct recovered F.17 meanings, establish the F.9 relation and the separate bounded-use claim and matching reliance. Cite G.7 calibration, CL and policy pins when that account uses them; its summary does not decide parity admissibility. Kind correspondence also requires receiving admissibility and fresh target classification under C.3.3. A plane relation keeps its own basis. Any numerical assurance penalty follows the applicable B.3 model for the named use.


Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)