Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:20:20 UTC

E.20:4.2 - Step 2: Declare the governing-definition assignment map (mandatory)

For every new or modified change item, the author SHALL name exactly one governing definition and make the change there. In FPF, that governing definition is a citeable, patchable PatternId, PatternId:SectionPath, PatternScopeId = G.x:Ext.*, or DRRId (E.9). The core MIP-run manifest in a citeable change record is limited to:

  • each changed item,
  • its governing definition,
  • its canonical location (expressed as PatternId:SectionPath, PatternScopeId, or DRRId, not as prose).

Conditional manifest fields appear only when the corresponding claim is present:

  • a forbidden reading or move only when its independently grounded correction changes use under F.19,
  • the change class(es) from E.20:4.1 when needed to disambiguate the assignment,
  • new or changed citeable tokens, including a MechanismDefinitionRef or a public operation, argument, or result designator, when token denotation or citeability changes,
  • the actual-effect Delta-Class (Δ-0 to Δ-3) and affected-reach estimate from E.15 when the run is plausibly Δ-2 or Δ-3,
  • intended RSCR trigger types when a refresh or regression-wiring claim is present, and
  • the PQG (E.19) profile set when the run crosses an E.19-governed review boundary.

Part-G wiring. If the canonical location is a Part‑G wiring module, it SHALL be cited as a PatternScopeId (G.x:Ext.*) and the module SHALL declare GoverningPatternId. The module supplies only bindings. Its cited pattern governs meaning.

Canonical governing-definition map (normative):

Change kindGoverning definitionCanonical locationForbidden move
U.Mechanism identity and content: exact EntityOfConcernRef, effective reference scheme, direct subject and range fields, operation algebra, laws, admissibility, Applicability, and optional dependency manifestMechanism-subject pattern under A.6.1Designated mechanism-subject patternA suite, plan, wiring module, card layout, or MIP manifest does not supply mechanism semantics; neighboring relations stay with their direct patterns.
Suite membership, obligations, spec pins, and suite protocolsSuite-subject patternA.6.7 or A.6.7.<FamilyKey>SHALL NOT carry mechanism semantics, acceptance thresholds, gate criteria, DecisionLogs, or publication tails into the suite.
Planned baseline pins (planned slot fillings, material edition-pinned refs, and a time selector when applicability or selection depends on it)One U.WorkPlan and the planned-filling rows kept inside itA.15.2 plus A.15.3 rows that point to declaration members defined by their own patternsSHALL NOT embed launch values, witnesses, or gate decisions in planning, or give a row independent identity.
A SoTA pack of source-grounded method, comparator, or generator candidates and their synthesisSoTA-pack subject pattern for the pack; the cited subject patterns for the definitions usedG.2 for claims, family cards and handoffs; the cited CHR/CAL, method, provenance or evaluation definition for its semanticsSHALL NOT treat a candidate card or wiring module as an introduced definition, or rephrase a source update as kernel semantics.
Wiring that binds SoTA packs into flows or tasksExtension module governing definitionG.x:Ext.* (GPatternExtension with explicit PatternScopeId)SHALL NOT mint new semantics; SHALL bind only.
Token renames and drift managementLexical subject patternF.18 (alias docking) plus registers per E.10/F.17SHALL NOT silently rewrite tokens or break citations.
Change-cause taxonomy and regression triggersRSCR subject patternG.CoreSHALL NOT invent ad hoc “reason kinds” scattered in patterns.
Project specializations of a mechanismProject specialization patternP.* patterns (using ⊑/⊑⁺)SHALL NOT mutate kernel membership to express project variants.

When a change has no named governing definition. Any proposed change that cannot name a governing definition from the table above SHALL be treated as a non-normative drafting note or candidate intake and SHALL NOT be relied upon as an FPF architectural commitment. Such material may exist only in a source note marked non-normative until assigned to its governing definition.