fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 100928–100947

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 14:45:10 UTC

E.20:4.1 - Step 1: Classify the introduction

A MIP-run SHALL first classify the change, because different classes have different governing definitions:

  1. New declared operation family or archetypal grounding. The EntityOfConcernRef names an operation family not previously declared at the selected governing locus.
  2. New mechanism declaration or semantic edition. One A.6.1 U.Mechanism episteme receives new identity-bearing content or a new effective U.ReferenceScheme.
  3. Neighboring mechanism-relation change. A realization, refinement, conservative extension, equivalence, bridge, evaluation, evidence-use, or publication relation changes while the mechanism content does not.
  4. Suite change (membership, obligations, spec pins, or suite protocols).
  5. Planned-baseline change (new or revised declaration-local planned-filling rows inside one exact U.WorkPlan, or changes to their pins).
  6. Wiring change (new or revised Part-G extension modules, SoTA method packs, or selectors).
  7. Terminology migration (renames, token splits or merges, or register changes).
  8. Deprecation, supersession, or retirement (status change, successor relation, and preserved citeability; apply E.20:4.9.1).

Mechanism-kind boundary. MechanismDefinitionRef is a designator. Minting it neither creates a U.Mechanism episteme nor admits a new U-kind. A new U-kind claim requires E.24.UK; a new mechanism episteme must satisfy A.6.1 identity and content; a new transformation-flow structure requires E.18.

A.6.1 compatibility. Mechanism identity is <content, EntityOfConcernRef, effectiveReferenceScheme>. Identity-bearing content comprises direct subject and range fields, OperationAlgebra, LawSet, AdmissibilityConditions, Applicability, and an optional SignatureManifest when dependency replay matters. An operation index may be derived from the declaration-local operationDesignator values; it is not another content group. Each operation’s arguments and results remain A.6.1 ArgumentDeclaration and ResultDeclaration content. A.6.5 SlotSpecs remain exclusive to a RelationSignature for an already governed direct relation. Realization, refinement, extension, bridge, evaluation, evidence-use, and publication relations are governed separately.

New-declaration criterion. Treat a change as a new declared operation family when EntityOfConcernRef changes. Treat changed mechanism content or effective reference scheme as a new semantic edition. A changed neighboring relation alone does not create a new mechanism identity, although it may reopen reliance on the current declaration. A single MIP-run MAY span multiple classes, but SHALL treat each class with its correct governing-definition assignment (below).