B.1.4:2 - Solution
Recover a ContextTemporalAggregation@Context before using the aggregate:
ContextTemporalAggregation@Context:
aggregationConcernRef
aggregatedEntityOfConcernRef
includedPositionRefs?
includedPhaseRefs?
claimScopeRef?: U.ClaimScope
aggregationMode: contextualOrder | temporalPhase
orderedRelationRefs?
phaseRelationRefs?
orderSpecRef?
timeWindowRef?
carrierIdentityRef?
independenceOrJoinConditionRefs?
coverageAndOverlapPolicyRefs?
boundaryCrossingRelationRefs?
relatedMethodRefs?
relatedMethodDescriptionRefs?
relatedWorkOccurrenceRefs?
relatedWorkResourceAggregationRefs?
relatedTransformationRefs?
relatedWholeReidentificationRefs?
evidenceOrSourceRefs
admissibleUse
stopOrReturnCondition
nonAdmissibleOverread?
strongerSourceReturnCondition
stopOrReturnCondition states when to stop aggregating or apply another pattern; strongerSourceReturnCondition states the condition for a stronger claim. Include nonAdmissibleOverread? only when it passes F.19’s plausible-reader test. groundedNonAdmissibleOverread? is an alias for that same optional value.
Use the record to describe the exact aggregation claim and its independently established relations. The record is not itself the relation or a new U.Level, U.Boundary, U.Interaction, or generic process object.
B.1.4:2.1 - Two Aggregation Modes
| Mode | Current object | Required relation discipline | Typical use |
|---|---|---|---|
| Contextual order aggregation | An exact set of relation positions whose order, partial order, or join structure changes meaning for the stated use. | Included positions, OrderSpec, ordered relation refs, join or independence conditions, and ClaimScope when needed. | Ordered method relation, order-bound argument chain, staged construction description, controlled sequence. |
| Temporal phase aggregation | One enduring carrier considered through exact proper phases or time slices. | Carrier identity rule, included phases, PhaseOf or another direct phase relation, TimeWindow, declared coverage rule and overlap policy. For an unchanged episteme, the complete C.2.1 identity triple stays fixed. | Asset history, proper restriction of one unchanged episteme, experimental-carrier phases, dated evidence window. Distinct episteme editions first require C.2.1 identities and an independently obtaining edition relation. |
If one source phrase mixes both modes, split the record. A Method may have an ordered relation structure; the Work that enacts it may have exact A.15.1 temporal parts, episodes, operational parts, or separate occurrences, while C.27.TA supplies any independently declared overlap or other interval relation the receiving use aggregates. Those are different claims, and generic PhaseOf does not replace the Work or temporal relations.
B.1.4:2.2 - Where Stronger Claims Go
| Current claim | Pattern to use |
|---|---|
| Method as semantic way of doing | A.3.1 |
| Method description, SOP, algorithm text, simulator configuration, or formal expression | A.3.2, with publication owners when publication use is current |
| Work plan | A.15.2 |
| Dated work occurrence, performed episode, or evidence that work happened | A.15.1 |
| Work-resource roll-up, spent resource, cost, effort, energy, material, or comparable ledger | B.1.6 |
| Episteme identity and historical continuity between distinct epistemes | C.2.1; aggregate only exact identities and an already obtaining EpistemeEditionRelation when the bounded use needs their chronology |
Proper PhaseOf, portion, membership, or other parthood relation for a non-Work carrier | A.14, B.1, and C.13 as appropriate; Work temporal and part relations remain with A.15.1 |
| Holon delimitation or boundary-crossing relation | A.1, B.1, A.12, A.3.4, or the pattern that defines the exact relation |
| Bounded change under conditions | A.3.4 |
| Whole reidentification, emergence-family wording, MHT, MET, MFT, synergy, or metric-mirage wording | Use B.2.P when emergence-family wording hides the claim kind. If a whole-reidentification question remains, including one raised by an autonomy or capability change, use B.2; B.2.2 and B.2.3 handle System and Episteme result recognition, and B.2.4 is the capability/functioning decision bridge. Use B.2.5 separately for an exact two-sided supervisor-subholon feedback claim, whether or not whole reidentification is current. |
| Architecture structural view or selected structure | C.30.ASV, A.22, or the pattern that defines or tests the architecture claim |
| Mathematical order, graph, algebraic notation, graph path, or morphism used as expression | Use C.29 when mathematical-lens adequacy, preserved structure, lost structure, payoff, or stop condition is being evaluated. Use E.18 when the selected transformation-flow structure is current. Use E.18.2 when the mathematical expression of that selected structure is current. |