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:00:10 UTC

B.2.3 - Meta-Holon Transition With Episteme Result

Type: Part B holonic construction pattern Status: Stable Normativity: Normative unless a section is marked informative

B.2.3:0 - Use This When

Use this pattern when B.2 has identified one candidate new whole and that individual must be recognized under the already admitted U.Episteme kind: a theory, model family, standard, doctrine, specification body, research programme, field-level knowledge body, or other claim-bearing non-agentive holon.

Use B.2 first to decide whether whole reidentification is current and to identify the one candidate new whole. Use B.2.3 when that candidate is to be tested under U.Episteme. For a first constitution or recognition without an established prior whole, use A.1 and C.2.1 as explained in B.2:4.

First useful move. For B.2’s candidate, identify its interpreted claim content, the independently identified EntityOfConcern, and the effective rules for designating that entity and interpreting those claims (C.2.1:4.1.1). Test whether their EpistemeConstitutionRelation obtains.

Keep grounding, viewpoint, view, publication, source use, representation, evidence, and assurance in their neighboring relations.

What goes wrong if missed. A catalogue, literature review, dashboard, model repository, or vocabulary is called a new theory without claim-graph reidentification; or a new episteme whole is treated as a pile of publications.

What this buys. The practitioner can recognize B.2’s candidate as an episteme under C.2.1 and distinguish that result from its publication, use, and assurance claims.

Not this pattern when.

  • If the result whole is a physically embodied holon eligible to act, use B.2.2.
  • When no whole-reidentification question remains, use the episteme, publication or source-use pattern for the remaining question; :4.2 and CC-B2.3-4 distinguish these uses.
  • If the question is effect-free episteme morphing, viewing, retargeting, or controlled semantic coarsening, use A.6.2, A.6.3, A.6.4, or A.6.3.CSC.
  • If the question is synthesis work, use A.15.1 for performed work and A.12 or A.3.4 for acting-side and transformation claims.
  • If the wording is ambiguous emergence-family language, use B.2.P before selecting B.2.3.

B.2.3:1 - Problem Frame

A collection does not become a theory merely because its items are stored together. Distinguish the claim-bearing whole from its publication form and carrier.

A group of papers, models, datasets, design notes, forecasts, standards, or local doctrines may remain a collection. Use B.2.3 when B.2’s candidate new whole is to be tested under A.1 and the C.2.1 constitution criterion for one interpretable claim-bearing episteme.

B.2.3 tests B.2’s candidate under A.1 and C.2.1, then retains B.2’s one resultHolonRef and resultHolonKindRef for the established result. Each neighboring relation keeps its subject pattern.

B.2.3:2 - Problem

Confusing the episteme with its collection, representation, or publication can produce these errors:

  1. Collection as MHT. Storing publications together is treated as sufficient for an episteme-result MHT without testing the candidate’s constitution and the B.2 comparison.
  2. Publication form becomes episteme. A carrier or publication form is mistaken for the claim-bearing episteme it presents.
  3. Episteme receives agency. The theory, standard, or doctrine is described as if it performs work or enforces behavior by itself.
  4. Morphing becomes MHT. A view, retargeting, coarsening, translation, or model transformation is treated as establishing B.2 whole reidentification by itself.
  5. Assurance is inherited silently. Trust in constituent sources is treated as trust in the reidentified episteme whole.
  6. Generic emergence replaces claim structure. “Emergent theory” hides the claim graph, reference scheme, and grounding relation.

B.2.3:3 - Forces

ForceTension
Synthesis vs aggregationA new episteme whole can integrate claims, but many collections remain indexes, reviews, or portfolios.
Episteme identity vs publication formThe episteme may be published in many forms; no publication form is the episteme by appearance.
Claim organization vs agencyAn episteme can organize claims and guide use, but systems perform work with or on it.
Constituent evidence vs result assuranceEvidence for parts may bear on the result. When assurance is required for a result claim, test whether that support applies to the claim and its receiving use.
Source mnemonic vs ontologyShort labels can aid recognition while hiding whether the question concerns B.2 whole reidentification, C.2.1 constitution, A.6 morphing, E.24.PUB publication, an E.17 reader face, or source use.

B.2.3:4 - Solution

Use B.2.3 as the U.Episteme specialization of B.2. Reuse its existing whole, candidate new whole, construction facts, and any optional C.2.1 records needed for this use.

B.2.3:4.1 - Reuse The B.2 Candidate And Complete Episteme Recognition

Start with B.2’s candidate designated as a U.Entity, proposed for the already admitted U.Episteme kind. Execute the A.1 criterion over that candidate, including the larger-assembly applicability and compatibility condition. Apply C.2.1 to that individual:

  1. identify its interpreted claim content, including the semantic relations among its claims, under C.2.1:4.1.1;
  2. identify the independently governed U.Entity that those claims concern;
  3. identify the effective reference scheme: the designation and interpretation rules under which those claims are read about that entity; and
  4. test whether the EpistemeConstitutionRelation among those participants obtains and yields one interpretable claim-bearing whole.

The candidate and its constitution relation are distinct, even though C.2.1 reidentifies them from the participant triple. A reference or representation alone does not establish that the constitution relation obtains. If A.1 or C.2.1 fails, do not identify the candidate as the episteme result; if a required dependency cannot be evaluated, return unknown.

For an established episteme result, B.2’s resultHolonRef designates that individual and resultHolonKindRef resolves to U.Episteme. Preserve a preliminary or unresolved judgment in an optional C.2.1 assertion only when a receiving use needs it; B.2:4.4 governs that distinction.

B.2.3:4.2 - Keep Constitution And Neighboring Relations Separate

The ClaimGraph, EntityOfConcern, and effective ReferenceScheme are the three participants of C.2.1’s EpistemeConstitutionRelation. C.2.1:4.1 identifies the ClaimGraph and ReferenceScheme as epistemic constituents of the interpretable claim-bearing whole. Establish that constitution for the candidate, and recover any further claimed part or composition relation under its pattern.

The EntityOfConcern remains an independently governed entity related through aboutness and reference. Keep all other questions in their relations:

  • empirical grounding uses EpistemeEmpiricalGroundingRelation only when designated empirical claims have current claim-to-world mappings involving the grounding holon;
  • viewpoint selection for a describing use follows E.10.D2; U.View recognition requires E.17.0 conformance of the episteme to a viewpoint;
  • publication occurrence, publication form, carrier, source use, and C.29 representation remain distinct from the episteme and its constitution;
  • an acting System first has the A.13 core and A.15.1 independently admits its synthesis Work under a Method; F.6 enters only if the receiving transition account also consumes precise assignment-bound attribution through the obtaining A.13 assignment, while any transformation remains a separate claim; and
  • evidence and assurance support or challenge the claims being made, including claims about constitution; they add no identity discriminator to C.2.1’s ClaimGraph/EntityOfConcern/ReferenceScheme triple.

Add only the neighboring object or relation required by the receiving use. Establish each such relation under its predicate and participants; keep it separate from the episteme’s identity positions.

B.2.3:4.3 - Episteme Trigger Interpretation

When a receiving use has materialized B.2’s optional MHTTriggerProfile, interpret its cues without giving agency to epistemes:

Cue recorded in MHTTriggerProfileEpisteme-case readingSubject pattern kept visible
Delimitation changeRecover what changed in claim content, EntityOfConcern or effective ReferenceScheme. Identify a claim scope when the claim requires one.C.2.1, A.7, source-use patterns
Objective or evaluation changeThe result episteme contains an answer or evaluation claim for a question that the collection did not answer as one claim-bearing whole.C.2.1, C.16, E.21 or relevant evaluation pattern
Supervision or coordination changeRecover a supervision or coordination relation under its defining pattern. Principles, axioms, invariants, reference schemes, and claim-graph constraints instead organize claim interpretation; inspect that change as a constitution or claim-composition claim rather than filling a relation-occurrence field with it.C.2.1, A.6.0, A.6.1, C.29 when formal lens is current
Capability or closure claimThe candidate episteme supports a new explanatory, predictive, specification, or coordination use; evidence for that claim remains separate.C.2.1, C.16, the pattern for that use; A.10 for a needed replayable source-to-use account
Agency thresholdThe episteme remains non-agentive. For an agency-characteristic claim, recover the System and characteristic predicate, with any scope and window required by the receiving use, and test the characteristic independently; that characteristic claim does not require an assignment. A precise agency claim requires the separate A.13 core. If dated Work is also claimed, recover each performer through A.13 and let A.15.1 independently admit the Work. Add F.6 only when the receiving claim consumes precise assignment-bound attribution; missing or failed F.6 alone leaves independently admitted Work intact. If the same finding also invalidates a premise consumed by the A.13 or A.15.1 admission, recheck that premise and its dependent conclusions.A.12, A.2.1, A.13, A.19, C.16, A.15.1, F.6
Temporal consolidationA chronology or source-currentness change prompts inspection of the knowledge body. Test any changed ClaimGraph, EntityOfConcern or effective ReferenceScheme under C.2.1; currentness alone changes none of those identity values.C.2.1, C.27, G.11, E.17, and source-use patterns
Context reframeNew terms, reference schemes, or EntityOfConcern mapping reframe the knowledge body.C.2.1, A.6.3, A.6.4, F.18

These cues identify claims and relations to inspect. They neither constitute the candidate episteme nor select B.2; the facts, A.1 criterion, C.2.1 constitution test, and B.2 existing-whole/new-whole comparison decide the result.

B.2.3:4.4 - Blocked Readings

Recognition of an episteme result establishes neither agency, publication authority, nor inherited assurance. Use the applicable subject patterns for those separate claims; the non-use cases in :0 identify the other operations.

B.2.3:5 - Archetypal Grounding (Worked Cases)

B.2.3:5.1 - Reliability Doctrine

Reliability work may begin with local runbooks, incident reports, dashboards, and definitions that remain a collection. A first doctrine constitution requires A.1 and C.2.1; the collection supplies no prior holon merely by being named. The following constructed case instead starts with an already recognized episteme and asks whether it can support a stronger deployment claim.

Supplied setting and receiving need. The example stipulates a modeled deployment S = Relay-S/D17, independently identified by its deployment configuration, and a fixed nonempty set of requests. Use classical two-valued logic. Ack(r) means that D17 emits an acknowledgement for request r; PrimaryStored(r) means its primary store holds that request’s payload when the acknowledgement is emitted. The already recognized episteme E0 = <G0, S, R0> has a ClaimGraph containing the sole premise:

P: for every request r, Ack(r) implies PrimaryStored(r).

R0 is the complete scheme interpreting this graph, with those request, acknowledgement, and primary-storage designations. The receiving work now needs one episteme whose stated premises support a derivation of:

Q: for every request r, Ack(r) implies
   (PrimaryStored(r) and ReplicaStored(r)).

Here ReplicaStored(r) means the replica holds the same payload at acknowledgement time. Q concerns the deployment S. The required new object, if established, is an episteme carrying and supporting Q.

Compare with E0. In the comparison vocabulary, retain all R0 meanings and add ReplicaStored. Set Ack(r*) = true, PrimaryStored(r*) = true, and ReplicaStored(r*) = false for one request, with Ack = false for every other request. This valuation satisfies P and falsifies Q, so G0’s stated premise does not entail Q. To obtain the required derivation, supply the additional premise:

T: for every request r, Ack(r) implies ReplicaStored(r).

T is a stipulated premise of this example, not a reliability fact proved about an operating service. Let G1 contain P, T, Q, and the inference deriving Q from P and T by conjunction introduction under the common antecedent. Let R1 retain R0’s meanings and add the replica-storage designation. The candidate is E1 = <G1, S, R1>.

Nonentailment alone would not establish a new identity. Here C.2.1’s declared identity discriminators are the ClaimGraph, EntityOfConcern, and effective ReferenceScheme. Keeping E0 requires retaining G0 and R0. Adding the premise, inference, and effective designation needed for this use changes both G and R, so the result cannot be E0 under that identity rule. This establishes insufficient for E0 and this receiving use. E0 exists and supports P; a different layout or publication of its unchanged triple would leave it E0.

Recognize the candidate. The construction supplies each A.1 ground:

GroundSupplied fact or demonstrated result
Individuated candidateE1 is the candidate <G1, S, R1>.
ConstituentsG1 and R1 are its epistemic constituents under C.2.1; S remains the independently identified EntityOfConcern.
ConstructionR1 interprets every claim and inference in G1 about S, and G1 organizes P and T as premises for Q. This satisfies the C.2.1 constitution predicate for one interpretable claim-bearing whole.
IdentityC.2.1 reidentifies this episteme by that G1/S/R1 triple. A change in one of those values identifies another episteme.
Composition-grounded characteristicG1 supplies the inference organization and R1 its interpretation about S; together they yield an interpretable derivation of Q. P and T each leave one of Q’s conjuncts unestablished.
Compatibility with a larger assemblyThe argument construction below incorporates E1 unchanged and uses Q in a further derivation.

For the last ground, supply a local argument-assembly rule: retain an interpreted argument as an unchanged constituent, preserve its graph and interpretation, and join its conclusion to an additional compatible premise by a named inference. Construct E2 = <G2, S, R2>. G2 contains G1 as an unchanged subargument and adds the supplied lemma L: (PrimaryStored(r) and ReplicaStored(r)) implies Recoverable(r) for each request. R2 retains R1 as the fixed local scheme for that subargument and adds the meaning of Recoverable(r): the modeled recovery method can read back r’s payload at the stated time.

Under the assumption Ack(r), Q gives both storage conditions and L gives Recoverable(r) by modus ponens; discharging the assumption yields Ack(r) implies Recoverable(r). Under this construction rule, E1 is a constituent of E2 with its graph, local scheme, subject, and identity preserved.

E1 therefore satisfies the displayed A.1 grounds and C.2.1 constitution and meets the receiving need. If later work needs a reidentification record, resultHolonRef names E1 and resultHolonKindRef names U.Episteme. The record and any classification assertion concern E1; Q concerns S.

The logical construction establishes the conditional derivation, not the truth of P, T, or L for a real deployment. A use that must rely on those service claims needs their grounds and any assurance required under B.3.

Change the interpretation condition. Suppose the supplied candidate uses G1 with the complete R0, whose declared vocabulary has no interpretation of ReplicaStored. The proposed <G1, S, R0> fails constitution: its scheme cannot interpret the whole graph. Supply a scheme that does interpret it and identify the resulting episteme.

By contrast, if R1 exists but is unavailable to the evaluator, evaluation is unknown; recover the scheme or withhold the classification. Neither result erases E0 or changes the identity of an already constituted E1. A failed or unresolved judgment is not a typed positive result in the optional record.

For a larger reliability doctrine, the comparison uses its claims about user-visible service harm and reliability, its independently identified subject, and its effective designations. Add empirical grounding to operating services, handbook publication, and source use for standards or training materials only when the receiving use needs them.

Systems use and cite the doctrine, use it in training, and let its claims guide their work; any relevant local system-role kind and assignment remain separate claims.

B.2.3:5.2 - Model Family Becomes Theory

A model family can remain a toolbox. It becomes an episteme-result MHT only if B.2’s candidate passes A.1 and one ClaimGraph, EntityOfConcern, and effective ReferenceScheme stand in an obtaining C.2.1 constitution relation. Empirical grounding and explanatory or predictive use are checked through neighboring relations when the receiving use needs them; they are not extra identity constituents.

If the change is only a new model publication or benchmark score, use the publication, source-use or characteristic pattern for that claim. Use A.10 when its source-to-use account must be replayable and C.29 for an unresolved representation-choice, transfer or reliance question.

B.2.3:5.3 - Standard Body

A set of clauses, examples, and annexes can become a standard episteme only when the candidate passes A.1 and its ClaimGraph, EntityOfConcern, and effective ReferenceScheme satisfy C.2.1 constitution. Recover its terms, references, scope, and conformance claims under that constitution; identify publication forms separately.

The standard is not the committee, the PDF, or the Work of enforcement. The committee may be an acting System. If committee or enforcement Work is claimed, recover each performer through A.13 and admit the Work independently under A.15.1. Add F.6 only if the account consumes precise assignment-bound attribution; missing or failed attribution alone leaves independently admitted Work intact. If the same finding invalidates an admission premise, apply CC-B2.3-5.

The PDF file carries an expression of the standard. A selected publication form supplies the reusable rules that this expression follows.

B.2.3:5.4 - Bias-Annotation

Bias riskFailureMitigation
Library as MHTA repository, dashboard, or reading list is taken as sufficient for an episteme-result MHT.Recover the candidate’s claims and constitution under A.1/C.2.1, then test the B.2 whole-reidentification claim. Ordinary episteme constitution alone does not establish that claim.
Publication as epistemeA publication form or carrier is treated as the claim-bearing episteme.Keep the episteme, publication form and carrier distinct under C.2.1 and E.24.PUB.
Episteme agencyA theory, standard, or doctrine is described as performing Work or enforcement.Recover every acting System through A.13 and let A.15.1 independently admit the Work. Add F.6 only when the receiving account consumes precise assignment-bound attribution; a missing or failed attribution alone leaves independently admitted Work intact. For an admission premise invalidated by the same finding, apply CC-B2.3-5.
Morphing as MHTView, translation, coarsening, or retargeting is taken as sufficient for B.2 whole reidentification.Use the A.6 operation; C.2.1 decides whether its source and target are different epistemes. Use B.2 when the whole-reidentification question remains.
Source trust transferTrust in constituent sources becomes assurance for the result episteme.Assess the support and source-use relations against that result claim; reuse a matching current applicability judgment and retain only support that applies.

B.2.3:6 - Conformance Checklist

CheckRequirement
CC-B2.3-1B.2 has left a whole-reidentification question before B.2.3 is used.
CC-B2.3-2A positive episteme-result claim requires B.2’s candidate new whole to pass the A.1 criterion and C.2.1 constitution under the already admitted U.Episteme kind. Failed or unresolved recognition follows :4.1.
CC-B2.3-3Retain B.2’s candidate and established-result references. C.2.1’s ClaimGraph, EntityOfConcern and effective ReferenceScheme remain the identity discriminators; neighboring relations and any optional durable account stay separate.
CC-B2.3-4Use C.2.1 for constitution and the patterns in :4.2 for neighboring claims. Use E.24.PUB for publication availability, form or carrier distinctions and E.17 for a needed reader face of an accepted account. Use C.2.P for unresolved source-expression or source-to-use wording, and C.2.P.DR for claims inferred from declarative form alone.
CC-B2.3-5The episteme is non-agentive. Acting Systems first satisfy A.13, and synthesis or enforcement Work is independently admitted through A.15.1. F.6 enters only when the receiving use consumes precise assignment-bound attribution; missing or failed F.6 alone leaves independently admitted Work intact. If the same finding also invalidates a premise consumed by the A.13 or A.15.1 admission, recheck that premise and its dependent conclusions. Agency-characteristic evaluation remains independent of assignment.
CC-B2.3-6Assurance for the result episteme is not silently inherited from constituent epistemes or publications.
CC-B2.3-7Effect-free morphing, viewing, retargeting, and controlled coarsening are not treated as B.2.3 unless whole reidentification is current.

B.2.3:7 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Collection as MHTAggregation is taken as sufficient for an episteme-result MHT.Recover the candidate and test A.1 plus C.2.1 constitution and the B.2 comparison; if recognition fails, withhold episteme-result recognition. Keep any independently established collection or ordinary episteme claim without inferring that it is sufficient for the use; report unknown when a required test cannot be evaluated.
PDF as epistemeA PDF carrier or its publication form is used as the theory itself.Use publication patterns for the PDF and keep B.2’s resultHolonRef for the independently constituted episteme.
Doctrine receives agency“The standard enforces…” or “the theory decides…”For a literal claim of dated enforcement or decision Work, recover its performer through A.13 and admit the Work independently under A.15.1; add F.6 only when the use consumes precise assignment-bound attribution. Otherwise use F.19 to retain ordinary guidance wording when its capable user and action are recoverable.
Morphism as MHTA view, translation, coarsening, or retargeting is taken as sufficient for B.2 whole reidentification.Use A.6.2, A.6.3, A.6.4 or A.6.3.CSC for that operation and C.2.1 for episteme identity; use B.2 for a remaining whole-reidentification question.
Synthesis as high trustA new theory inherits trust because its sources were reliable.When this assurance claim is needed, assess it under B.3 and retain the source-use relations. Use A.10 for a needed replayable source-to-use account, B.3.5 only when its profile is elected, and C.2.1 for a live constitution question. Reuse adequate existing support rather than inheriting assurance from the sources.

B.2.3:8 - Consequences

Positive consequences:

  • The practitioner can distinguish a new claim-bearing whole from a collection or changed publication.
  • C.2.1 remains the episteme identity pattern.
  • Publications, source use, synthesis work, evidence, assurance, and acting systems remain separate.

Costs:

  • A claimed synthesis must identify and test the C.2.1 constitution, not only cite a portfolio.
  • Result-episteme assurance needs warranted applicability to the result claim and receiving use. A matching current applicability judgment may be reused; reassess when the claim, basis or relevant conditions change.
  • Some “new theory” claims return to publication, source-use, morphism, benchmark, or evidence-use patterns.

B.2.3:9 - Rationale

A knowledge synthesis may yield a new claim-bearing whole. Establish that conclusion through the whole’s construction and identity, then assess its other uses separately.

B.2 is the pattern for whole reidentification; C.2.1 is the pattern for the ClaimGraph/EntityOfConcern/ReferenceScheme constitution relation and episteme identity; publication and source-use patterns contain the defining content for their relations; A.6 episteme-morphism patterns contain the defining content for morphing and retargeting; use A.15.1 for synthesis Work and A.12 for the acting-side split.

B.2.3:10 - SoTA-Echoing

The distinction between episteme constitution and neighboring relations is an FPF construction. B.2.3 requires C.2.1 constitution. State the synthesis claim within the scope needed for its interpretation and use. Recover evidence relations, currentness qualifications, and maintenance conditions only where the receiving use or a binding rule requires them. Assurance and source use remain neighboring relations.

A knowledge body can be represented as related claims, evidence, and sources. The ClaimGraph is a C.2.1 constitution participant. Keep its graph representation, evidence, and sources in the neighboring relations described in B.2.3:4.2; C.2.1 governs episteme identity and B.2 governs whole reidentification.

Fields and theories can consolidate into named bodies with new scope and organizing principles. B.2.3 treats a named consolidation as a cue to inspect; use C.2.1 for the candidate’s constitution and B.2 only for a whole-reidentification question.

A standard, report, model, or dashboard use may concern claim content, a representation, a publication form, or its carrier; its name alone does not decide which. Publication availability, form and carrier distinctions follow E.24.PUB; use E.17 when a reader needs a face of an accepted account.

Source-use claims retain their relations; use A.10 when bounded reliance needs a source-to-use account. Those relations remain separate from the episteme’s constitution. The constructed case in B.2.3:5.1 applies these distinctions to a stronger claim about a deployment.

B.2.3:11 - Relations

  • Specializes: B.2 by testing its candidate new whole under the A.1 criterion and C.2.1 constitution for the already admitted U.Episteme kind.
  • Builds on: B.2 for the candidate new whole and whole reidentification, A.1 for candidate recognition, C.2.1 for the obtaining ClaimGraph/EntityOfConcern/ReferenceScheme constitution relation, and E.24.UK for prior public-kind admission.
  • Coordinates with: C.2.P, C.2.P.DR, E.17, E.17.*, A.6.2, A.6.3, A.6.4, A.6.3.CSC, A.10, B.3, B.3.5, C.29, F.18, and F.19.
  • Uses: B.2.P when source wording such as emergence-family or title-mnemonic wording hides the claim kind.
  • Contrasts with: B.2.2 for system-result MHT and B.2.4 for the capability and functioning decision bridge to whole reidentification.

B.2.3:End

Referenced in the corpus

14 literal mentions in other sections. Read their context to establish the relation.