FA-8541 / Form submission / Open access

Submission state transitions: Successful submission retains stale errors · case 01

Successful submission retains stale errors.

Verified by executionVariant 1 · 8 checks per implementationDownload source bundle ↓JSON ↗

ROOT CAUSE

The success operation uses `if event == 'success': return ('succeeded', errors)` where the contract requires `if event == 'success': return ('succeeded', {})`.

THE FAILURE

The success operation uses `if event == 'success': return ('succeeded', errors)` where the contract requires `if event == 'success': return ('succeeded', {})`.

Unsuccessful approach: Returning idle with errors also hides success.

Case contract

A duplicate pending submit preserves pending; invalid submit retains errors; success clears errors; failure installs result errors; editing resets status and stale errors.

Why this case matters

A deterministic model of submission state transitions; this isolates one interface invariant without requiring a browser.

1 / The failure

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json

N = 1
observations = []
def solve(state, errors, event, result):
    if event == 'submit':
        if state == 'submitting': return (state, errors)
        if errors: return ('invalid', errors)
        return ('submitting', {})
    if event == 'success': return ('succeeded', errors)
    if event == 'failure': return ('failed', result)
    if event == 'edit': return ('idle', {})
    return (state, errors)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('duplicate', solve('submitting', {}, 'submit', None), ('submitting', {}))
check('invalid', solve('idle', {'a':'required'}, 'submit', None), ('invalid', {'a': 'required'}))
check('valid', solve('idle', {}, 'submit', None), ('submitting', {}))
check('success', solve('submitting', {'old':'stale'}, 'success', None), ('succeeded', {}))
check('failure', solve('submitting', {'old':'stale'}, 'failure', {'a':'conflict'}), ('failed', {'a': 'conflict'}))
check('edit', solve('failed', {'a':'stale'}, 'edit', None), ('idle', {}))
check('parameterized failure details', solve('submitting', {}, 'failure', {'field':str(N)}), ('failed',{'field':str(N)}))
for repetition in range(N):
    check('repeat edit', solve('failed', {'a':'stale'}, 'edit', None), ('idle', {}))
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)

Boundary fixture	Actual	Expected	Outcome
duplicate	`['submitting', {}]`	`['submitting', {}]`	Passed
invalid	`['invalid', {'a': 'required'}]`	`['invalid', {'a': 'required'}]`	Passed
valid	`['submitting', {}]`	`['submitting', {}]`	Passed
success	`['succeeded', {'old': 'stale'}]`	`['succeeded', {}]`	Failed
failure	`['failed', {'a': 'conflict'}]`	`['failed', {'a': 'conflict'}]`	Passed
edit	`['idle', {}]`	`['idle', {}]`	Passed
parameterized failure details	`['failed', {'field': '1'}]`	`['failed', {'field': '1'}]`	Passed
repeat edit	`['idle', {}]`	`['idle', {}]`	Passed

SHA-256 / affa5873cdd5839b5b5d978bfc9617cd5c6c0ffdb410b6b73051de591dbf4cd1

2 / The unsuccessful fix

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json

N = 1
observations = []
def solve(state, errors, event, result):
    if event == 'submit':
        if state == 'submitting': return (state, errors)
        if errors: return ('invalid', errors)
        return ('submitting', {})
    if event == 'success': return ('idle', errors)
    if event == 'failure': return ('failed', result)
    if event == 'edit': return ('idle', {})
    return (state, errors)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('duplicate', solve('submitting', {}, 'submit', None), ('submitting', {}))
check('invalid', solve('idle', {'a':'required'}, 'submit', None), ('invalid', {'a': 'required'}))
check('valid', solve('idle', {}, 'submit', None), ('submitting', {}))
check('success', solve('submitting', {'old':'stale'}, 'success', None), ('succeeded', {}))
check('failure', solve('submitting', {'old':'stale'}, 'failure', {'a':'conflict'}), ('failed', {'a': 'conflict'}))
check('edit', solve('failed', {'a':'stale'}, 'edit', None), ('idle', {}))
check('parameterized failure details', solve('submitting', {}, 'failure', {'field':str(N)}), ('failed',{'field':str(N)}))
for repetition in range(N):
    check('repeat edit', solve('failed', {'a':'stale'}, 'edit', None), ('idle', {}))
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)

Boundary fixture	Actual	Expected	Outcome
duplicate	`['submitting', {}]`	`['submitting', {}]`	Passed
invalid	`['invalid', {'a': 'required'}]`	`['invalid', {'a': 'required'}]`	Passed
valid	`['submitting', {}]`	`['submitting', {}]`	Passed
success	`['idle', {'old': 'stale'}]`	`['succeeded', {}]`	Failed
failure	`['failed', {'a': 'conflict'}]`	`['failed', {'a': 'conflict'}]`	Passed
edit	`['idle', {}]`	`['idle', {}]`	Passed
parameterized failure details	`['failed', {'field': '1'}]`	`['failed', {'field': '1'}]`	Passed
repeat edit	`['idle', {}]`	`['idle', {}]`	Passed

SHA-256 / a8d97e3a4bfa3cb15dc59f3e08e92795786a9c1c545a8f5a32a01ef1f4d33725

HELD IN THE MEMBER ARCHIVE

The verified repair and its recorded checks are member-only.

This mechanism has 8 recorded checks per implementation. The open-access tier publishes the failure and the unsuccessful fix; the repaired source that passes every check, and the observations that prove it, are available to members.

Every case sharing this mechanism uses the same contract and the same repair, so this one record is held back for all of them.

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

Verification & scope

This reproducer isolates one failure mechanism. Results cover the supplied fixtures. Variants within a family share a test contract and should remain grouped when constructing evaluation splits. Related mechanisms with a shared evaluation_group must also remain together; these controlled models are not independent production incidents.

Observations recorded using Python 3.12.14 at 2026-09-29T14:38:22.371447+00:00.

Case digest / cf2614cb00993ec2d05b7a826abc59345a5c9cede8f2d04011cbbc8fd67c9ddd