FA-1107 / Workflow orchestration / Member archive

Start a durable workflow execution: The workflow starts on an unavailable definition version · case 02

The workflow start operation is admitted even though the workflow starts on an unavailable definition version.

Member previewVariant 2 · 3 implementations · 9 checks per implementation

Case contract

Return a Boolean admission decision for start a durable workflow execution. The record r must satisfy all of: r['execution_unique'][0] not in r['execution_unique'][1]; r['version_available'][0] in r['version_available'][1]; set(r['input_required'][0]) <= set(r['input_required'][1]); r['parent_live'] == 'running'; r['start_deadline'][0] < r['start_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
The workflow starts on an unavailable definition version	`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.