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

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 22:54:38 UTC

E.20:1 - Problem frame

FPF is open-ended by design. Authors can add new U.Mechanism definitions, suite compositions and wiring modules informed by the best-known practice for the problem. Introducing or revising a mechanism often affects several subject patterns, specification sections and extension blocks across Parts A/E/F/G. They can drift apart in several ways:

  • semantics appear in the wrong governing locus (e.g., Part G wiring starts carrying mechanism meaning),
  • suites degrade into “meta‑mechanisms” or hidden gates,
  • planned baselines in exact U.WorkPlan content are conflated with dated performed Work,
  • token drift breaks public references, or
  • the corpus accumulates dangling references and non-normative drafting commitments without a governing definition.

This protocol tells authors how to assign each change to its governing definition. Making those definitions and the extension points visible keeps repeated introductions consistent with the kernel.

Use this when. Use E.20 when a proposed FPF change introduces or revises mechanism meaning, suite denotation, suite closure, suite obligations, suite pins, suite protocol semantics, planned-baseline pins, wiring semantics, governing-definition assignment, or what a citeable token denotes.

First useful move. Classify the edit with MIP trigger triage: MIP not triggered, local wording or alias-docking only, or MIP-run manifest required. If a manifest is required, name a single governing definition for each changed item before writing the pattern text.

When the change also involves a transformation flow. Use E.18 for transformation-flow structure, paths, valuations and crossings, A.20 for internal step validity, A.21 for a gate profile application and decision, and E.20 to assign mechanism meaning to its definition. Open each of the other three only when its own claim is present.

After a wording or publication correction. If E.20 rules out a misleading word, face, alias or source label, name the governing definition, canonical location, alias-docking relation or non-trigger stop that remains available to the author. Classifying the vocabulary or publication face alone leaves the authoring move unspecified.

Subject and relation separation. Keep the selected transformation-flow structure, paths and crossings (E.18), its mathematical description (E.18.2), MVPK publication faces (E.17), internal CV status and witness (A.20), gate profile application and decision (A.21), evidence or provenance relation (A.10/G.6), work plan or work occurrence (A.15), and mechanism-definition assignment (E.20) distinct.

An MVPK face, DecisionLog, evidence value, provenance reference, MIP manifest, or work witness does not supply another subject’s project-side value unless an exact dependent-use assertion and its defining or constraining ClaimGraph establish that relation.

Smallest affected locus. Start with the smallest affected PathSlice or crossing in E.18, CV step in A.20, profile application and bounded action decided in A.21, or governing mechanism definition in E.20. When that locus is sufficient, keep the change there, without widening it to the whole flow or unrelated claims, loci or EntitiesOfConcern.

Do not merge these pairs. Keep CV.Status distinct from GateDecision, E.18 Check locus distinct from GateCheckKind, MIP manifest distinct from DecisionLog, ViewpointMap distinct from graph semantics, PathSlice distinct from a work run, and GateProfile=Lite distinct from PublishMode=Lite.

What the manifest establishes. A complete MIP-run manifest is not a substitute for the governed mechanism result. The cited U.Mechanism episteme must recover <content, EntityOfConcernRef, effectiveReferenceScheme> and the A.6.1 content needed by the receiving use. Realization, refinement, bridge, evaluation, evidence-use, and publication relations remain neighboring claims under the patterns that govern those relations.

What goes wrong if missed. A suite can start defining mechanism meaning, declaration-local WorkPlan rows can start carrying enactment witnesses or gate decisions, a wiring module can carry kernel semantics, or a token rename can break citations while looking like harmless cleanup.

What this buys. Assign the change to the right governing definition. This keeps mechanism, suite, planning, wiring and lexical continuity distinct.

Not this pattern when. For a currentness, typo, reference or old-label cleanup, check whether it changes any semantics or citeable-token denotation. If it changes neither, record the current governing locus and stop. If the question concerns runtime gate passage, gate decision, approval, suite-as-mechanism, plan-as-enactment, or performed work, use the applicable gate, suite, planning, or Work pattern for that question. A MIP-run manifest is not a runtime gate, gate passage, approval packet, or binary pass/fail decision.