FA-1298 / Workflow orchestration / Member archive

Complete workflow cancellation: Cancellation waits beyond its explicit cleanup deadline · case 03

The workflow cancel operation is admitted even though cancellation waits beyond its explicit cleanup deadline.

Member previewVariant 3 · 3 implementations · 9 checks per implementation

Case contract

Return a Boolean admission decision for complete workflow cancellation. The record r must satisfy all of: all(r['child_propagation']); r['activity_cleanup'] is True; r['terminal_stability'] not in ['completed','failed']; r['request_generation'][0] == r['request_generation'][1]; r['cleanup_deadline'][0] <= r['cleanup_deadline'][1]. Extra tracing fields are ignored; validation does not mutate the record.

Why this case matters

A deterministic local contract for workflow orchestration. Each negative fixture violates exactly one invariant. No transport timing, persistence, cryptographic verification, or full protocol implementation is claimed.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
Cancellation waits beyond its explicit cleanup deadline	`true`	`false`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.