Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 11:55:15 UTC
A.15.1:6.4 - Claim handling (episodes versus monitoring slices)
Top work occurrence:ClaimHandling_Case_8142_2026-06-03.
Actual method and containing-system relation:enactsMethod -> ClaimHandling@InsuranceOps-2026; ClaimWorkOccursWithinOperationsBoundary@InsuranceOps(ClaimHandling_Case_8142_2026-06-03, ClaimsOperations_A) obtains under the operations delimitation declared in ClaimsWorkBoundaryRelations@InsuranceOps-2026.
Claim and resource stop: this fixture names Claim_8142, handler-time intervals, and ClaimsPlatform_A, but supplies no admitted Work-to-claim, handler-time-use, or case-system-time-use predicate. Keep the grounded claim-handling Work and return missing-governor[CLAIM-REFERENT-AND-RESOURCE-USE] for those optional relations. Callback and monitoring records remain neighboring evidence or telemetry, not occurrence constituents.
methodDescriptionRef:Claims_Method_v7.
A.13 Agent basis, performer System, and assignment:ClaimsHandlerSystemRole is a declared local agential kind for claim-resolution action; its criterion requires goal-directed, condition-sensitive regulation of the stated handling action, the fixture classifies ClaimsTeam_A : U.System under it, and cited evidence supports that local criterion and classification for the claim scope and window; no Grade or autonomy-profile claim is used. ClaimsHandlerAssignment is the directly declared assignment species whose signature gives the holder and assigned-kind participant meanings. ClaimsTeam_A_HandlerAssignment_2026-06-03 is the obtaining occurrence: its holder is ClaimsTeam_A, its assigned kind is ClaimsHandlerSystemRole, and its extent covers the claims Work. F.6 states that ClaimsTeam_A performed this Work under that occurrence. The team System acts; the kind, species, and occurrence do not.
Episode policy:InitialReviewEpisodeWork-8142 and ResumedResolutionEpisodeWork-8142 are first independently admitted as Work individuals with their own A.13-qualified actual performers, performance histories, enacted Methods, extents, and containing-System relations. Any precise assignment-bound attribution for either episode is checked separately through F.6 after admission. The named claims-handling continuity use then applies ClaimsWorkContinuityPolicy_v7, a C.2.1 policy episteme interpreted under Claims-Handling-Scheme-2026. Its stated under-one-hour callback criterion supports assertion ClaimsSegmentation-v7-8142 that the two named Work individuals stand in EpisodeOf_work relations to ClaimHandling_Case_8142_2026-06-03. The policy supports the ambiguous grouping; it does not create either episode Work or relation.
Nearest non-continuing replacement: competing episteme ClaimsWorkContinuityPolicy_15min-Alt, interpreted under the same reference scheme, states a fifteen-minute callback threshold. Applied to the same 29-minute gap, it supports assertion ClaimsSegmentation-15min-8142 that the resumed performance is a later Work occurrence rather than an episode under the first parent. No EpistemeEditionRelation between the exact v7 and 15-minute policy epistemes is established, so the second is a non-continuing replacement, not an edition. Either assertion may govern its named receiving use; switching the selected policy changes the use-local segmentation judgment, not either interval’s actual history. Only if C.2.1’s historical-continuation predicate is separately satisfied may the later policy be called an edition.
Temporal monitoring slice:MonitoringSlice_09:15-09:20 is a C.27.TA temporal aspect used for queue-latency evidence. It is not a TemporalPartOf_work participant or an episode. If a later use needs an independently admitted Work sub-occurrence with its own performed content and exact extent, identify that Work first and test the applicable §4.1a part predicate.
Method relation: under ClaimsSegmentation-v7-8142, both episodes enact the same claim-handling method; under ClaimsSegmentation-15min-8142, each of the two Work occurrences enacts that method. The segmentation choice changes neither enactment fact. The five-minute slice does not prove a submethod.