#Contextual and Temporal Aggregation

B.1.4 · Stable · B-family aggregation pattern · Normative unless explicitly marked 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: B-family aggregation pattern Status: Stable Normativity: Normative unless explicitly marked informative

Use this when. Use this pattern when the current claim aggregates already recovered relations over an exact set of ordered positions, phases, or a time window, and the question is not just ordinary part-whole construction. Typical cues are ordered steps, order-sensitive argument chains, asset histories, proper temporal restrictions of one enduring carrier, rolling windows, use-bounded roll-ups, time-sliced evidence, or a bounded chronology over exact C.2.1 episteme identities and already obtaining edition relations.

Not this pattern when. If the question is ordinary part-whole or collection admission, use B.1, A.14, and C.13. If it is episteme identity or historical edition continuity, use C.2.1 before any aggregation. If the question is the method as such, method description, work plan, dated work occurrence, or Work temporal part or episode, use A.3.1, A.3.2, A.15.2, or A.15.1. If the question is work-resource accounting, use B.1.6. If the question is changed identity, use the pattern that defines the subject's identity or change; for a clear whole-reidentification question, use B.2 directly to test whether the existing whole suffices or a new whole must be reidentified. Use B.2.P first only when emergence-family wording hides the claim kind. If the question is temporal adequacy of a claim, use C.27.

What goes wrong if missed. Order, phase, context, or time-window wording becomes ordinary parthood, method order, performed work, evidence currentness, or whole reidentification by label.

What this buys. The practitioner can aggregate order-sensitive and temporal material while keeping method, work, transformation, work-resource, temporal-adequacy, and MHT claims with the patterns that define or test them.

Many useful aggregates are not simple unordered wholes. A manufacturing sequence changes meaning when steps are swapped. An argument chain depends on which premise is used before which lemma. A turbine or another enduring individual with a stated identity rule may be considered across proper temporal restrictions. An unchanged paper or dataset episteme may also be restricted to a proper interval only while its complete C.2.1 identity triple remains fixed; changed claim content, EntityOfConcern, or effective ReferenceScheme identifies another episteme, with edition continuity tested separately. In these cases the aggregation is about order or temporal coverage over already recovered relations, not about a new level, a generic boundary, or a hidden interaction kind.

#Relations

#Content

#Problem Frame

Many useful aggregates are not simple unordered wholes. A manufacturing sequence changes meaning when steps are swapped. An argument chain depends on which premise is used before which lemma. A turbine or another enduring individual with a stated identity rule may be considered across proper temporal restrictions. An unchanged paper or dataset episteme may also be restricted to a proper interval only while its complete C.2.1 identity triple remains fixed; changed claim content, EntityOfConcern, or effective ReferenceScheme identifies another episteme, with edition continuity tested separately. In these cases the aggregation is about order or temporal coverage over already recovered relations, not about a new level, a generic boundary, or a hidden interaction kind.

B.1.4 defines the aggregation claim. It asks which EntityOfConcern is being aggregated, which positions or phases are included, which scope and time window qualify the claim, which ordered or phase relation is being used, what the aggregate may be used for, and which neighboring pattern carries any stronger claim.

#Problem

Without this pattern, four errors recur. First, SerialStepOf or another ordered relation is read as ordinary parthood, so changing the order looks harmless even when the aggregate meaning changes. Second, a phase label is read as a new holon level or a new whole, so identity change is hidden instead of handled by whole reidentification. Third, design-time plans, possible method order, run-time histories, and evidence windows are folded together as one sequence. Fourth, mathematical order, graph, or operator notation starts to stand for the in-life object instead of expressing a recovered relation for one bounded use.

The practical failure is not a missing diagram. It is an inadmissible aggregate: the user cannot tell which carrier is being followed, which positions or phases are included, which relation is ordered, which time window is covered, whether gaps or overlaps matter, or which pattern must carry a stronger work, resource, transformation, evidence, or whole-reidentification claim.

#Forces

#Solution

Recover a ContextTemporalAggregation@Context before using the aggregate:

ContextTemporalAggregation@Context:
  aggregationConcernRef
  aggregatedEntityOfConcernRef
  includedPositionRefs?
  includedPhaseRefs?
  claimScopeRef?: U.ClaimScope
  aggregationMode: contextualOrder | temporalPhase | declaredMixedUse
  orderedRelationRefs?
  phaseRelationRefs?
  orderSpecRef?
  timeWindowRef?
  carrierIdentityRef?
  independenceOrJoinConditionRefs?
  coverageAndNonOverlapConditionRefs?
  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 as a small typed relation, not as a new durable U.Level, U.Boundary, U.Interaction, or generic process object.

#Two Aggregation Modes

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.

#Where Stronger Claims Go

#Optional Operator Notation

Gamma_ctx and Gamma_time are optional notation for already recovered aggregation claims.

Gamma_ctx(contextualAggregationRecord, orderSpec, independenceAndJoinConditions)
  -> contextual aggregate record

Gamma_time(temporalAggregationRecord, timeWindow, coverageAndNonOverlapConditions)
  -> temporal aggregate record

The notation does not create a holon, transformation, method, work occurrence, or whole reidentification by itself. It records how the selected relation set is combined for the current use.

If the source says a system actually sequences, combines, transforms, measures, or audits something, name that acting-side relation separately through [A.12](/generated/patterns/A.12), [A.3.4](/generated/patterns/A.3.4), [A.15.1](/generated/patterns/A.15.1), [B.1.6](/generated/patterns/B.1.6), [A.10](/generated/patterns/A.10), or the pattern that defines the exact relation. The person, team, controller, or tool that writes an aggregation record is not automatically the in-world transformer for the EntityOfConcern being aggregated.

#Admissible Checks

For contextual order aggregation:

• the ordered relation refs are named by value;
• the OrderSpec is declared as total order, partial order, or another named relation;
• independence, branch, or join conditions are named when parallel factors are used;
• the record names its included positions, ClaimScope when needed, and admissible use; any holon-boundary crossing is named by an exact relation;
• method, method-description, work, transformation, and resource claims use the patterns that define or test them.

For temporal phase aggregation:

• the carrier identity is recoverable;
• the time window is declared;
• phase intervals are covered and non-overlapping, or the admissible use is narrowed;
• identity change is not hidden as another phase;
• work-resource and evidence-currentness claims use B.1.6, A.10, and C.27 when current.

B.1 invariant carry-through. B.1.4 keeps B.1 invariants only after the current relation is recovered. A singleton ordered relation or singleton phase is idempotent for the selected use. Contextual aggregation is deterministic only relative to the declared OrderSpec and join or independence conditions. Temporal aggregation is valid only relative to carrier identity, coverage, and non-overlap. Weakest-link and monotonicity claims must name the characteristic being bounded or improved; otherwise the aggregate is only an aggregation record, not a performance, safety, or assurance claim.

#Compact Obligation Rows

#Archetypal Grounding (Worked Slices)

Manufacturing sequence. A frame is prepared, welded, inspected, painted, and packed. B.1.4 records the contextual order claim: selected steps, order specification, join conditions, and admissible use for planning or comparison. The actual shop-floor work occurrences use A.15.1; energy and material roll-ups use B.1.6; a changed frame state uses A.3.4.

Paper edition history. When draft, reviewed, and camera-ready texts change claim content, EntityOfConcern, or effective ReferenceScheme, C.2.1 identifies distinct epistemes and tests each claimed EpistemeEditionRelation independently. B.1.4 may record a bounded chronology over those already recovered identities, relations, applicability windows, or publication windows; it does not turn the editions into phases of one episteme. If one unchanged episteme is genuinely needed over a proper interval, A.14 PhaseOf may state only that restriction. Source-currentness and publication-use claims use A.10, G.11, and E.17; chronology establishes none of them.

Cross-regime evidence window. A dashboard aggregates observations from two operating regimes. B.1.4 records the exact observation sets, their subject populations or carriers, the aggregation window, and the admissible use. If the regimes use different measurement bases, use C.16 or C.29 for comparability before relying on the aggregate.

#Bias-Annotation

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

This pattern makes ordered and temporal aggregation inspectable without turning every sequence, phase, or context label into a holon level. It also lets practitioners keep useful Gamma_ctx and Gamma_time notation while avoiding a category error: the notation is an apparatus over a recovered aggregation claim, not the in-life work, method, transformation, or whole.

The cost is that the practitioner must name the relation being aggregated. The gain is that contextual order, temporal coverage, work evidence, resource accounting, transformation, and whole reidentification stop interfering with one another.

#Rationale

B.1.4 exists because contextual order and temporal phase aggregation are neither ordinary part-whole construction nor generic process talk. One enduring carrier with a stated identity rule can be considered through proper temporal restrictions; a selected relation set can be order-sensitive; and both cases need admissible aggregation without inventing a new holon kind. The pattern therefore keeps relation discipline explicit: PhaseOf and the carrier's identity rule for legitimate phase aggregation; C.2.1 identity and independently obtaining edition relations for distinct episteme history; A.15.1 relations for Work; ordered relation refs and OrderSpec for contextual aggregation; and separate patterns for resource, transformation, evidence, and whole reidentification.

The old DesignRunTag warning is preserved as a rule rather than a label: do not fold design-time possible order and run-time history into one aggregate. If both are needed, make two records and relate them by value.

#SoTA-Echoing

#Relations

• Builds on B.1, A.14, and C.13 for part-whole, phase, and constructive grounding discipline.
• Coordinates with C.2.1 for exact episteme identities and independently obtaining edition relations; with A.3.1, A.3.2, A.15.2, and A.15.1 for method, method description, work plan, dated work occurrence, and exact Work-temporal relations.
• Coordinates with B.1.6 for work-resource aggregation.
• Coordinates with A.3.4 for transformation. Use B.2 directly for a clear whole-reidentification question; use B.2.P first only when emergence-family wording hides the claim kind. The relevant subject pattern defines or constrains the recovered claim.
• Coordinates with C.27 for temporal-claim adequacy. When mathematical expression is selected, C.29 tests lens-use adequacy, E.18 defines the selected transformation-flow structure, and E.18.2 defines its mathematical description.

#B.1.4:End

Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)