A.6.1:5.7 - Recognition evaluation: Pump #37
A project repeatedly evaluates the A.1 holon-recognition criterion. In ordinary language, one bounded evaluation act applies the selected criterion to Pump #37 and returns true, false, or unknown. For this replay, resolving HolonRecognitionMechanism-E1_Ref under its effective reference scheme returns exact mechanism episteme HolonRecognitionMechanism-E1; neither label nor suffix establishes an edition relation. That episteme has SubjectKind = U.Entity, RangedValueKind = RecognitionJudgmentValue, no separate ResultKind, and operation recognizeAdmittedHolonCandidate.
RecognitionJudgmentValue is one local finite U.Kind under C.3, used here as the operation’s RangedValueKind; its membership rule admits exactly true, false, and unknown. It is an operation-local kind, not a public U-kind or universal claim-status algebra. Candidate facts, evidence status, episteme-currentness values, and receiving-work dispositions use their direct kinds. The argument and result rows are A.6.1 declarations, not A.6.5 SlotSpecs.
For this exact mechanism episteme, the declaration-local designation, cardinality, and binding predicates are:
| Member | ValueKind and designation rule | Cardinality | Declaration-local binding predicate |
|---|---|---|---|
candidate | U.Entity; an exact U.EntityRef must resolve to the entity | exactly one | recognitionCandidateBound(P, E) holds only when application P actually evaluates E as its candidate |
admittedHolonKind | one already identified C.3 U.Kind value for an admitted holon kind, carried by value; that holon kind’s direct pattern supplies any kind-specific condition | exactly one | recognitionKindBound(P, K) holds only when P evaluates the candidate against admitted kind K |
recognitionCriterion | U.Episteme; an exact U.EpistemeRef must resolve to the selected criterion-bearing episteme | exactly one | recognitionCriterionBound(P, C) holds only when P applies the claims in C as its recognition criterion |
criterionParameter[constructionFacts] | U.Episteme (the exact ValueKind of this separately declared criterionParameter argument); an exact U.EpistemeRef resolves to the candidate-facts episteme used by the evaluation | exactly one | recognitionParameterBound(P, constructionFacts, V) holds only when P uses V under that meaning |
criterionParameter[reidentificationRule] | U.Episteme (the exact ValueKind of this separately declared criterionParameter argument); an exact U.EpistemeRef resolves to the reidentification-rule episteme used by the evaluation | exactly one | recognitionParameterBound(P, reidentificationRule, V) holds only when P uses V under that meaning |
interpretationBasis | U.Episteme; an exact U.EpistemeRef must resolve to the selected basis episteme | exactly one | recognitionBasisBound(P, B) holds only when P uses B as its interpretation basis |
recognitionJudgment | RecognitionJudgmentValue, carried by value | exactly one | recognitionJudgmentReturned(P, J) holds only when P returns J under this result meaning |
These predicate names are local to HolonRecognitionMechanism-E1; they do not admit public binding relation kinds. Pump_37_Ref can be type-correct without a binding: the candidate predicate is current only when the exact application actually uses its resolved referent under the candidate meaning. The same rule applies to each argument, and a result predicate is current only after the application returns that value.
For this mechanism episteme, ApplicationPredicate(P) holds only when bounded evaluation act P fixes exactly one value for every required argument above, applies recognizeAdmittedHolonCandidate from HolonRecognitionMechanism-E1, and returns exactly one RecognitionJudgmentValue. Its ApplicationExtentRule sets the maximal extent from the moment all required argument bindings are fixed and evaluation begins through the terminal judgment return. Its ApplicationIdentityRule reidentifies one application by <HolonRecognitionMechanism-E1, recognizeAdmittedHolonCandidate, independently grounded evaluation-act locus, maximal application extent>. A later invocation is another application even with the same bound values. A trace token or reused work label can designate an act but cannot merge the two.
For the worked case, Pump37RecognitionApplication-2026-07-21T100000Z designates the evaluation act that began at 10:00:00 and returned at 10:00:04. It used Pump_37_Ref -> Pump_37 : U.Entity, admitted kind U.System, A1-Holons-Criterion-E1_Ref, Pump37-Construction-Facts-E1_Ref, Pump37-Reidentification-Rule-E1_Ref, and Pump37-Interpretation-Basis-E1_Ref. The six argument-binding predicates have maximal continuous extents from 10:00:00 through the terminal return. A required fastening-relation fact could not be resolved during this act, so the bound values could determine neither satisfaction nor failure. The act returned unknown; the extent of recognitionJudgmentReturned(Pump37RecognitionApplication-2026-07-21T100000Z, unknown) is the terminal return event at 10:00:04 and does not begin earlier. The application did occur; Pump #37’s world-side satisfaction or failure did not change; and unknown is not an admission refusal.
If the project also claims that dated classification Work occurred, first recover the exact actual performer S : U.System through A.13 and let A.15.1 independently admit a separate Work occurrence W from its performance history, temporal extent, at least one obtaining enactsMethod -> U.Method relation, and at least one obtaining locally declared containing-system relation with its exact boundary. Add the same obtaining A.13 assignment RA and F.6 performedUnderAssignment(W, RA) only when this classification-work claim or its receiving use expressly consumes precise assignment-bound attribution; then check S = RA.HolderSystemSlot and assignment coverage. F.6 identifies neither assignment nor performer, and missing or failed F.6 leaves W intact. The candidate application binding above can establish Pump #37’s participation in the application; add a separate work-to-candidate or resource-use claim only when its declared predicate obtains, and add workContinuityPolicyRef only when an identity or segmentation question needs it. Any materialized classification-assertion or evaluation-result episteme remains under C.2.1. Evidence and assurance support or warrant its claim content through their own relations, and G.11 tests edition currentness. That result binding records only the returned recognition judgment. Work and episteme identity, evidence and warrant, world-side criterion satisfaction, and B.2 whole reidentification each remain independently governed.
Practical payoff: another evaluation can reuse the same typed operation while binding another candidate or basis, and evidence loss can change the returned value to unknown without rewriting the candidate or criterion.