#Emergence and MHT Precision Restoration

B.2.P · Stable · Part B precision-restoration pattern · Normative unless a section is explicitly informative · Part B - Trans-disciplinary Reasoning Cluster

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Part B precision-restoration pattern Status: Stable Normativity: Normative unless a section is explicitly informative

Use this pattern when wording such as emergence, emergent, synergy, higher-level property, meta-system, meta-epistemic, meta-functional, MHT, MET, MFT, promotion, post*, or collection words mixed with those terms could be pointing to several different FPF objects.

#Relations

#Content

#Use This When

Use this pattern when wording such as emergence, emergent, synergy, higher-level property, meta-system, meta-epistemic, meta-functional, MHT, MET, MFT, promotion, post*, or collection words mixed with those terms could be pointing to several different FPF objects.

The first useful move is:

Recover the claim kind before choosing replacement wording.

B.2.P is selected only when the source wording hides one of these recurring questions:

• Is this a B.2 whole-reidentification claim?
• Is the candidate new whole a system or episteme, or do capability and functioning facts make whole reidentification necessary?
• Is this only a characteristic, capability, functioning, architecture, evidence, measurement, or mathematical-lens claim?
• Is a collection, fleet, community, pool, or base being admitted as a whole, acting collective, whole-level characteristic bearer, or merely a membership set?
• Is a metric jump or benchmark result being overread as a new whole?

What goes wrong if missed. A word like "emergent" becomes a shortcut to a new U-kind, a collection receives agency by name, a metric jump becomes MHT, or source title mnemonics survive as if they were current pattern authority.

What this buys. B.2.P gives one local recovery profile for emergence-family and MHT wording. It keeps B.2-family subject patterns centered on whole reidentification while ordinary capability, characteristic, function, architecture, evidence, math-lens, publication, and collection claims remain with their direct owners.

Not this pattern when.

• If the text already names the governing pattern and object by value, use that pattern directly.
• If the question is ordinary collection admission without emergence, synergy, MHT, metric mirage, or whole-reidentification wording, use [A.14](/generated/patterns/A.14), [C.13](/generated/patterns/C.13), [B.3.5](/generated/patterns/B.3.5), [A.1](/generated/patterns/A.1), [A.15](/generated/patterns/A.15), A.2 patterns, or [C.16](/generated/patterns/C.16) directly.
• If the question is phrase-level plain technical rewriting after the object is recovered, use [F.19](/generated/patterns/F.19).
• If the question is general wording-use architecture, use [E.10](/generated/patterns/E.10) and [E.10.ARCH](/generated/patterns/E.10.ARCH).

#Problem Frame

Emergence-family wording is overloaded. It can point to a new system whole, an episteme whole, a capability envelope, a characteristic crossing, an architecture residual, a mathematical scale expression, a benchmark artifact, a publication claim, or a collection-as-whole question.

It asks which exact EntityOfConcern, world-side or claim-side fact, and direct governing pattern are current, and whether the same whole still carries the claim.

#Problem

Without B.2.P:

1. Generic emergence becomes ontology. U.Emergence or an equivalent hidden kind appears even though no such root kind is selected.
2. Collections become systems by poetry. A fleet, community, pool, or base is treated as an acting system because the phrase sounds collective.
3. Capability becomes MHT. A new capability envelope or functioning relation is treated as a new whole without checking existing-whole explanations.
4. Mathematics becomes declaration. A graph, scaling law, RG-like expression, benchmark jump, or MSPD score is treated as whole reidentification.
5. Old mnemonic titles become current owners. Source labels such as MET or MFT hide whether the claim concerns an episteme whole, capability or functioning facts, evidence for those facts, or something else.
6. Semio-bias returns. Publication, dashboard, model, or source interpretation claims displace the in-life holon or characteristic under concern.

#Forces

#Solution

Recover the claim kind and direct owner before any wording replacement.

#Emergence Claim-Kind Recovery

Read the sentence once and recover five things before rewriting it:

1. Practical use. What decision, explanation, design move, or stop depends on the sentence?
2. Exact object. Is the concern an existing whole, candidate new whole, collection, characteristic, capability, functioning relation, structure, transformation, measurement result, assertion, or mathematical expression?
3. Concrete claim. What changed or obtains: construction, identity, capability, characteristic value, evidence, publication, representation, or only the wording?
4. Direct owner. Which pattern governs that object and claim without using emergence as a substitute?
5. Disposition. Keep the exact direct claim, open B.2 only for a remaining whole-reidentification question, or stop with the exact missing object or governor.

A temporary author note may retain the source phrase, exact object, direct owner, blocked overread, and replacement or stop. The note is not a U-kind, relation, result object, or required project record. Do not ask a practitioner to fill a generic emergence card before the direct object can be named.

#Claim-Kind Recovery and Owner Selection Table

#Whole-Reidentification Recovery

When a whole-reidentification question remains after claim-kind recovery, do not create a second MHT schema. Return to B.2 with this concrete account:

1. name the exact existing whole, admitted kind, and identity or reidentification rule;
2. name each changed delimitation, constituent, constructive relation, assembly, supervision, objective, capability, characteristic, or temporal fact and its direct owner;
3. try the existing-whole explanation and state whether it preserves the existing whole;
4. if a new whole is still needed, return to B.2 and execute the complete A.1 criterion: name the exact candidate, its constituents, obtaining constructive relations, assembly, reidentification rule, and composition-grounded whole characteristic; show that its actual boundary, interfaces, relevant characteristics, and identity-preservation conditions satisfy at least one applicable governed larger-assembly construction method or rule under which it can remain a constituent; then name its already admitted kind and satisfy the direct kind-specific criterion;
5. state whether the direct identity rules preserve the same whole or require a new whole for the current subject claim;
6. only when a specific downstream task must inspect or cite the decision, identify any separate assertion or record, supporting evidence and warrant, G.11 currentness result, and rely, decline, defer, or reopen decision.

Evidence availability, an evaluation value, a record field, and receiving reliance neither construct the candidate nor decide whether the existing whole continues or a new whole must be identified. If the exact candidate, one required constructive fact, or the larger-assembly compatibility condition has no governor, stop with that missing object or governor rather than writing candidateResultRef, resultKindRef, mhtWitnessRef, or a context-shaped placeholder.

#Collection Boundary

Collection words enter B.2.P only when they are entangled with emergence, synergy, MHT, metric mirage, or whole-reidentification wording.

If the claim is plain collection admission:

• use A.14 for membership and part-whole relation vocabulary;
• use C.13 for collection-as-whole constructional grounding;
• use B.3.5 for working-model assurance grounding;
• use A.1 with A.15 and A.2 patterns for an acting collective admitted as U.System;
• use C.16 for a whole-level characteristic.

B.2.P may point to these direct owners; it does not own their claims. An unassembled collection remains an unassembled collection even when a list, dashboard, or project card names it as one whole. A C.13 collection construction does not by itself establish an integrated assembly, acting system, or A.1 holon.

#Source Mnemonics and Result Fields

Treat source labels and short forms as recognition cues until the concrete thing or claim and its direct pattern are identified.

• MET may point to a claim that the candidate new whole is an episteme, source-title wording, episteme morphing, publication synthesis, or a source-only phrase. Identify the concrete claim before use.
• MFT may point to capability and functioning whole reidentification, a functional-structure view, function-like wording, method and work collapse, or source-only phrase. Recover before use.
• promotion may hide whole reidentification, status change, release, gate, publication, or project process wording. Recover before use.
• post* fields do not survive as generic governed names. When B.2 is current, name the exact candidate new whole and its already admitted holon kind directly; cite an optional classification assertion or reidentification record only when receiving work needs that episteme.

Do not keep the source label as the pattern owner merely because it is recognizable.

#Archetypal Grounding (Worked Cases)

#"The Fleet Emerged As A New Actor"

Recover:

• Is "fleet" a membership set, collection-as-whole, acting collective system, or the candidate new system named by an MHT claim?
• Does the agency wording name a system in role, an agency-threshold claim, or only ordinary prose?
• Does the candidate new system have its own delimitation, objective, coordination, and capability envelope, and is the reidentification claim separately supported by evidence and assurance?

If the candidate new whole is an acting system, use B.2 and B.2.2. If the case is only a managed collection with a whole-level metric, use A.14, C.13, B.3.5, and C.16.

#"The Model Shows Emergent Robustness"

Recover:

• Is the model a description episteme or mathematical-lens expression?
• Is robustness a characteristic-space claim?
• Is the result a benchmark artifact?
• Is there an in-life holon whole-reidentification question?

Most cases use C.29, C.16, A.10, and source-use owners. Use B.2 only if the in-life whole has to be reidentified.

#"A Meta-Functional Transition Happened"

Recover:

• Is there capability or functioning evidence?
• Do separately governed capability or functioning facts make a whole-reidentification question live, with evidence only supporting the claim about those facts?
• Is the concern function-like wording, a functional-structure view, a method-and-work relation, or a candidate new holon?

Use B.2.4 only for the B.2-facing whole-reidentification case. Otherwise use A.6.F, A.2.2, C.16, A.3.4, C.30.TFS-REL, A.15, or architecture owners.

#"The Selected Context Became A Meta-System"

Recover the exact selected relation organization. If it is BoundedModelUseStructure, keep it as dependent U.Structure under A.1.1 and A.22. A context label, Context Map, diagram, or selection decision supplies no constituents, part relations, agency, holonhood, or MHT. If the source instead concerns an actual system whole, identify that system and its construction independently before B.2.

#"The Evidence For Emergence Was Lost"

Recover the exact whole-reidentification assertion, its evidence or assurance relation, the selected assertion edition, and the receiving work. Missing evidence can make a governed evaluation return unknown; a stale edition can fail G.11 currentness; receiving work can decline, defer, or reopen. None of those results reverses an actual construction or changes the direct rule that decides whether the existing whole continues or a new whole must be identified. Do not rewrite evidence loss as absence of the whole or as a new MHT.

#"The Assembly Changes Form One Higher-Level Change"

Identify each actual change independently under A.3.4. A shared work occurrence, flow, changed referent, time window, method decomposition, or C.13 construction trace does not make those changes parts of one transformation. If the use requires a composite transformation and no direct governor supplies constituent contribution, compatibility, boundary, interfaces, whole identity, and reidentification, return that exact blocker. Do not infer either composition or atomism.

#Bias-Annotation

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

Positive consequences:

• B.2-family emergence language no longer creates hidden U-kinds.
• B.2, B.2.2, B.2.3, and B.2.4 stay centered on their subject claims instead of carrying repeated first-stage precision restoration.
• Collections, capabilities, functions, characteristics, architecture residuals, mathematical expressions, and publications keep their direct owners.

Costs:

• Ambiguous emergence-family phrases take one recovery step before use.
• Some attractive umbrella claims become narrower direct-owner claims.
• Old mnemonic labels may survive only as quoted source wording or reduced-use cues unless the concrete thing or claim and its direct pattern are identified.

#Rationale

Emergence-family wording is useful because it marks a possible explanatory concern. It is dangerous because it can hide the actual object: a holon, system, episteme, capability, characteristic, architecture structure, mathematical expression, evidence relation, source publication, or collection.

B.2.P follows the E.10.ARCH algorithm: recover ontology first, then choose wording. This prevents one word from creating several local ontologies.

#SoTA-Echoing

#Relations

• Builds on: E.10, E.10.ARCH, E.24, F.18, and B.2.
• Returns whole reidentification to: B.2, with B.2.2, B.2.3, and B.2.4 as current specializations.
• Keeps collection admission with: A.14, C.13, B.3.5, A.1, A.15, A.2 patterns, and C.16.
• Coordinates with: A.2.2, C.16, A.6.F, A.3.4, C.30, A.22, A.1.1, C.30.ASV, C.30.TFS-REL, C.30.ILC, C.32.P2S, C.29, A.10, B.3, C.2.1, G.11, E.17, and source-use patterns.

#B.2.P:End

Last Updated: 2026-08-04 — upstream FPF commit 8b727cba (github.com/ailev/FPF)