G.9:4 — Solution
Preface node
heading:g-9-4-solution:140455
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
G.9:4.0 — G.Core linkage (normative)
This pattern binds to G.Core through the following manifest.
GCoreLinkageManifest (G.9) (normative; expands per G.Core:4.2)
Effective obligations/pins/triggers are computed as union(expand(sets), explicit deltas) under Nil‑elision.
-
CoreConformanceProfileIds:= {GCoreConformanceProfileId.PartG.AuthoringBase,GCoreConformanceProfileId.PartG.TriStateGuard,GCoreConformanceProfileId.PartG.ShippingBoundary,GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted} -
RSCRTriggerSetIds:= {GCoreTriggerSetId.CGSpecGate} -
RSCRTriggerKindIds:= {RSCRTriggerKindId.EvidenceSurfaceEdit,RSCRTriggerKindId.PenaltyPolicyEdit,RSCRTriggerKindId.BaselineBindingEdit,RSCRTriggerKindId.TelemetryDelta} (Pattern-local deltas; cross-tradition or Bridge-calibration causes are wired viaG.9:Ext.CrossTraditionParityand MUST NOT over-trigger parity runs that use one already recovered meaning and ReferencePlane.) -
DefaultsConsumed:= {DefaultId.DominanceRegime,DefaultId.PortfolioMode,DefaultId.GammaFoldForR_eff} (Use each default when its operation needs it. G.Core.DefaultGoverningDefinitionIndex identifies the governing definitions CC‑G5.28, CC‑G5.23 and CC‑G5.4 respectively.) -
CorePinSetIds:= {GCorePinSetId.PartG.AuthoringMinimal,GCorePinSetId.PartG.CrossingVisibilityPins} -
CorePinsRequired(pattern delta; pin names only; all are id‑valued unless noted) := {ComparatorSpecRef.edition,TaskSignatureRef?,TaskMapRef?, (when a selector consumes the parity result; TaskMapRef only when its G.4 CAL gates are current)entityOfConcernRef?,targetRefs[]?, (exactly one subject branch)ClaimScope,EvaluationWindow,FreshnessWindows,BaselineSet,BaselineBindingRef,ParityPinSet,PlannedFillingRows[]?,EvidenceGraphId,Budgeting?,EpsilonDominance?,UNM_id?,NormalizationMethodId[]?,NormalizationMethodInstanceId[]?,SCPRef.edition?,MinimalEvidenceRef.edition?} (Nil‑elision applies; mode‑specific definition pins are introduced only by the correspondingGPatternExtensionblocks.) -
TriggerAliasMapRef:=∅
G.9:4.1 — Objects and publication records
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).
G.9:4.2 — Parity planning (one U.WorkPlan)
Planning records the conditions needed to repeat and interpret the parity run:
-
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, citeSoS‑LOGBundleId?and the source-maturity ids by reference; acceptance-gate thresholds remain inG.4Acceptance. -
Bind subject, scope, and evaluation window. Choose exactly one subject branch: one
entityOfConcernRef, or exacttargetRefs[]under their existing kinds and editions. For G.5 families, useMethodFamilyRowReforGeneratorFamilyRowRef, not a bare lineage id. Record theReferencePlane,ClaimScopeandEvaluationWindow. An empirical claim identifies itsgroundingHolonRef. 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. -
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). IfBaselineSetalso supplies the exact compared targets, say so and use the same refs by value; otherwise keep baseline and subject refs distinct. -
Equalise window (and budget, if pinned). Declare a single
FreshnessWindowsand apply it across all baselines; ifBudgetingis 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.
-
Pin governance, CSLC comparability and admissibility references, and comparator references.
CNSpecRef,CGSpecRef, andComparatorSpecRefare referenced with explicit edition pins. -
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
Extensionsblocks (e.g.,G.9:Ext.DHCParityPins,G.9:Ext.QDArchiveParity,G.9:Ext.OEEParity) and the referenced records they cite. -
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 applicableUNM_id?,NormalizationMethodId[]?andNormalizationMethodInstanceId[]?and establish that the mapping preserves the distinctions the comparator uses. -
Declare the required result. An admitted A.19.CPM comparison returns relation or poset tokens. Preserve established incomparability.
CompareEligibilitycan 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 throughG.Core.DefaultGoverningDefinitionIndex. IlluminationSummary, coverage and regret remain telemetry unless a cited CAL policy promotes them. -
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. -
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.
G.9:4.3 — Execution protocol (run‑time / selector‑adjacent)
For one run under the pinned plan, follow these steps:
-
Validate CSLC references and pins. Validate the cited CSLC comparability and admissibility references, active pins, and witnesses. Apply the eligibility or acceptance checks required by the pinned comparison and refuse or abstain on non-admissible operations. When using G.5, record its branch trace in its own result vocabulary and use the planned
TaskSignatureRef. Add the matchingTaskMapRefwhen that selector uses G.4 CAL gates. If a liveA.21gate consumes this check, cite itsGateDecisionResultand add aDecisionLogonly when needed for audit or reuse. The profile application and its action consequence remain governed by A.21; do not create aG.9-local CSLC gate. -
Run the comparison and any required selection. Apply the pinned comparator to the admissible comparison inputs and retain its lawful result shape in
ParityReport. If a selector-facing result is required, apply G.5 under the plan's exact task and conditional map refs and publish its declared outcome. An ordinary parity or benchmark report ends without G.5 when no selector result is needed.Under componentwise minimization, A=(8,3) and B=(10,2) trade cost against time. An admitted comparison can return the singleton
{A ∥ B}. If A and B are all eligible candidates, both are nondominated. Add C=(7,2) and the frontier becomes{C}while the relation between A and B stays the same. Under a comparator that admits intervals, take A=(8,[3,4]) and B=(10,2). Every allowed value for A’s time still gives incomparability. With A’s time in [1,4], A may dominate B or the two may trade off. Report only what the approved comparison supports. If two bounds used as evidence about the same profile contradict each other, resolve that conflict before reporting a relation. If the profiles are consistent and none meets the requested limits, that can settle the eligibility question. Separately, if a required calibration is missing, apply the evidence policy. An admitted narrower comparison can return only its justified tokens. Anabstaindecision leaves the comparison slot unbound.For a bounded-specialization comparison, the report should include the active specialization profiles or equivalent pins so readers can recover the work-measure threshold target, prior exposure, budget-to-threshold, post-threshold efficiency when relevant, transfer, retention, downside field, and any corridor-entry baseline or evidence note from the report.
-
Record the comparability mapping when used. If
UNM_id?,NormalizationMethodId[]?, orNormalizationMethodInstanceId[]?was declared, echo it inParityReportor its explicit pins delta. Record the ids and any scoped notes required by the cited specification in the audit pins and SCR; cite the applicablePathIdvalues. -
Publish trace. Emit
ParityReportwith theParityPlanRef, itsBaselineBindingRef, conditional selector input refs, EvidenceGraph citations, and all active edition and policy-id pins, so the run can be checked and run again. -
Emit telemetry for refresh when produced. Publish the telemetry pins or events used for refresh. Treat the values as report-only unless a CAL policy promotes them and its ID is recorded.
G.9:4.3a — Worked parity slice
Ordinary case: compare two pump-triage method rows. The team from the G.5 example wants a reproducible comparison of the two exact selector-row editions, not a claim that one Method is universally better. Both rows use the same scheme, units, and ReferencePlane, so no normalization or crossing branch is needed.
The plan explicitly says that BaselineSet and targetRefs[] contain the same two row refs. EvaluationWindow bounds the observations and results included in the comparison. FreshnessWindows asks a different question at run or reuse time: whether each required input and evidence path is still recent enough to rely on.
A report from this run carries parityPlanRef=<PumpTriageParity, E1>, BaselineBindingRef=PumpTriageBaselineBinding-E1, the same evidence path, and the unordered Shortlist; it does not invent a scalar winner.
Conditional specialization case. Loop-engineering parity may add further pins after the ordinary comparison boundary above is complete. An evaluation program, benchmark script, or dashboard is part of the evaluation or comparison procedure; it is not the Characteristic being improved.
- Two agentic search setups both claim bounded specialization on the same declared task family.
- Their
ParityPlanalso pins the same threshold target, adaptation budget, prior-exposure declaration, and corridor-entry baseline. One setup reaches threshold sooner but shows low retention and no transfer. The other reaches threshold later, but carries reusable transfer and lower downside field. - Their CSLC-admissible
ParityReportstates what was held constant, which signals remained telemetry, and why the outcome stays a selected set or partial order rather than collapsing into a scalar winner. These specialization values extend the complete comparison boundary; they do not replace its subject, scope, windows, baseline binding, comparator editions, or evidence.
G.9:4.3b — Conditional causal method rung parity
Use this extension only when a parity report compares causal methods or causal-use claims. Start with a cheap screen and stop at degraded parity or abstention when the methods answer different questions.
causalSupportComponentTypeSet records which methods rely on evidence paths/data regimes, identification, estimates, direct counterfactual sampling, simulation, or transport. Expose the difference and justify the proposed comparison under its causal-support conditions; a shared label does not make unlike components equivalent.
Open the full record only when comparison remains meaningful:
The record names every changed transport endpoint that matters; population and semantic scheme do not substitute for domain, environment, or data-generating regime. Different rungs, estimands, windows, endpoints, or support components require a bridge/loss, degraded parity, or abstention. G.9 makes the parity conclusion; C.28 supplies the cited causal-support result and does not authorize the benchmark conclusion.
G.9:4.9 — Extensions (pattern‑scoped; non‑core)
For an ordinary parity comparison that uses none of these modes, you can stop after the worked case in §4.3a. Use §4.3b when comparing causal methods or causal-use claims, and the extension blocks below when their mode is active.
The extensions specify only the pins, references, policy IDs, triggers and links needed for each mode. The referenced patterns define what these mean.
GPatternExtension block: G.9:Ext.CrossTraditionParity
GPatternExtension: CrossTraditionParity
- PatternScopeId:
G.9:Ext.CrossTraditionParity - GPatternExtensionId:
CrossTraditionParity - GPatternExtensionKind:
DisciplineSpecific - GoverningPatternId:
G.7 - Uses:
{G.7, F.9, E.18, A.21} - ⊑/⊑⁺:
∅ - RequiredPins/EditionPins/PolicyPins (minimum; conditional on use):
BridgeId/BridgeCardId[](for an actual F.9 sense correspondence; cite a card when used)BridgeMatrixId?CalibrationLedgerId?/BCT.id?RegressionSetId?/SentinelId[]?(when sentinel wiring is used)CL/CL^k/CL^plane(only the channel values consumed or required by the calibration or named assurance account)Φ(CL) policy-id,Φ_plane policy-id,Ψ(CL^k) policy-id?(only when the receiving model or assurance account requires that policy)CrossingBundleId?(required for an actual flow/gate use whose governing rule requires the bundle)
- RSCRTriggerSetIds:
{GCoreTriggerSetId.BridgeCalibrationKit}(preferred; expands inG.Core) - RSCRTriggerKindIds (delta, if any):
∅ - Notes: Apply the channel and receiving-use conditions of G.Core:4.2.3. A kind or plane correspondence keeps its own relation and receiving grounds; it creates no F.9 Bridge. The pins cite the calibration, loss model or crossing bundle consumed.
GPatternExtension block: G.9:Ext.SoSLogGuardNarration
GPatternExtension: SoSLogGuardNarration
- PatternScopeId:
G.9:Ext.SoSLogGuardNarration - GPatternExtensionId:
SoSLogGuardNarration - GPatternExtensionKind:
MethodSpecific - GoverningPatternId:
C.23 - Uses:
{C.23, G.6, G.4} - ⊑/⊑⁺:
∅ - RequiredPins/EditionPins/PolicyPins (minimum; conditional on use):
SoSLogRuleId[]/BranchId[](ids as cited labels; semantics come fromC.23)FailureBehaviorPolicyId/SoSLogBranchIdEvidenceTrace.PathId[]/PathSliceId?AcceptanceClauseId[](when referenced)
- RSCRTriggerKindIds:
{RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.EvidenceSurfaceEdit, RSCRTriggerKindId.MaturityRungChange, RSCRTriggerKindId.TelemetryDelta} - Notes (wiring-only): Explains why a parity run degraded/abstained by citing SoS‑LOG ids and evidence paths; does not redefine guard semantics.
GPatternExtension block: G.9:Ext.DHCParityPins
GPatternExtension: DHCParityPins
- PatternScopeId:
G.9:Ext.DHCParityPins - GPatternExtensionId:
DHCParityPins - GPatternExtensionKind:
MethodSpecific - GoverningPatternId:
C.21 - Uses:
{C.21} - ⊑/⊑⁺:
∅ - Required replay values and pins (minimum; conditional on DHC parity):
DisciplineRefIntendedUseClaimScopeRefComparisonBasisCharacteristicRef.editionScaleRef.editionUnitRef.edition?DHCMethodRef.editionMethodRefMethodDescriptionRef.edition?MeasurementModelRef.edition?CalibrationBasisRef?TimeOrPopulationBasisDHCDefinitionSetRef.edition?TargetSliceRef?DistanceDefRef.edition?
- RSCRTriggerKindIds:
{RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.EvidenceSurfaceEdit} - Notes (wiring-only): Carry exactly the active fields of the C.21 replay basis.
TargetSliceRefappears only when the parity computation consumes that A.2.6 selection and states its relation toClaimScopeRef. Compatible same-semantics readings use the admitted C.16 comparison basis directly; actual distinct-local-sense use also cites the obtaining F.9 relation, direction, admitted use, and loss. C.21 defines the DHC semantics.
GPatternExtension block: G.9:Ext.QDArchiveParity
GPatternExtension: QDArchiveParity
- PatternScopeId:
G.9:Ext.QDArchiveParity - GPatternExtensionId:
QDArchiveParity - GPatternExtensionKind:
MethodSpecific - GoverningPatternId:
C.18 - Uses:
{C.18, C.19, G.5} - ⊑/⊑⁺:
∅ - RequiredPins/EditionPins/PolicyPins (minimum; conditional on use):
DescriptorMapRef.editionDistanceDefRef.editionCharacteristicSpaceRefwith separatecharacteristicSpaceDescriptionRef: U.EpistemeRef(when discretisation/topology is referenced; resolve the same-space pair under A.19:5.1.1.1)EmitterPolicyRefInsertionPolicyRef
- RSCRTriggerKindIds:
{RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta} - Notes: Pin the QD definitions used by the comparison; their semantics remain in
C.18,C.19andG.5.
GPatternExtension block: G.9:Ext.OEEParity
GPatternExtension: OEEParity
- PatternScopeId:
G.9:Ext.OEEParity - GPatternExtensionId:
OEEParity - GPatternExtensionKind:
MethodSpecific - GoverningPatternId:
C.19 - Uses:
{C.19, G.5} - ⊑/⊑⁺:
∅ - RequiredPins/EditionPins/PolicyPins (minimum; conditional on use):
TransferRulesRef.editionEnvironmentValidityRegionIdExplorationBudgetPolicyId?EvidenceTrace.PathSliceId?(for transfer‑keyed events)
- RSCRTriggerKindIds:
{RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta} - Notes (wiring-only): For open-ended parity, cite the policies and editions above and connect their telemetry to refresh. The extension adds no core rule.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)