FA-99871 / Agent workflow termination / Open access
Workflow: empty final payload is treated as completion · case 01
A blank assistant payload terminates the workflow as a successful answer.
ROOT CAUSE
The completion predicate checks only the final marker.
THE FAILURE
The completion predicate checks only the final marker.
Unsuccessful approach: Requiring truthy payload without the marker accepts unfinished commentary.
Case contract
Return true iff final_seen and payload contains at least one non-whitespace character.
Why this case matters
This toy decision rule isolates one bounded agent-loop completion contract.
1 / The failure
Exit 1"""Failure Map reference implementation. Python standard library only."""
import json
N = 1
observations = []
def solve(final_seen, payload):
return bool(final_seen)
def check(label, actual, expected):
observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('ordinary final', solve(True,'done'),True)
check('blank final', solve(True,''),False)
check('spaces final', solve(True,' '),False)
check('payload without final', solve(False,'done'),False)
check('empty unfinished', solve(False,''),False)
check('newline only', solve(True,'\n\t'),False)
check('single character final', solve(True,'x'),True)
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 |
|---|---|---|---|
| ordinary final | True | True | Passed |
| blank final | True | False | Failed |
| spaces final | True | False | Failed |
| payload without final | False | False | Passed |
| empty unfinished | False | False | Passed |
| newline only | True | False | Failed |
| single character final | True | True | Passed |
SHA-256 / 8d724bfc903ad26fd450f61ea354c90a8352f49a8a47d2f26f34e1f7b65966e7
2 / The unsuccessful fix
Exit 1"""Failure Map reference implementation. Python standard library only."""
import json
N = 1
observations = []
def solve(final_seen, payload):
return bool(payload.strip())
def check(label, actual, expected):
observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('ordinary final', solve(True,'done'),True)
check('blank final', solve(True,''),False)
check('spaces final', solve(True,' '),False)
check('payload without final', solve(False,'done'),False)
check('empty unfinished', solve(False,''),False)
check('newline only', solve(True,'\n\t'),False)
check('single character final', solve(True,'x'),True)
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 |
|---|---|---|---|
| ordinary final | True | True | Passed |
| blank final | False | False | Passed |
| spaces final | False | False | Passed |
| payload without final | True | False | Failed |
| empty unfinished | False | False | Passed |
| newline only | False | False | Passed |
| single character final | True | True | Passed |
SHA-256 / d90a0be764275ced84b77a830a66c2976149ccf8d751d91f158b491a0e413958
HELD IN THE MEMBER ARCHIVE
The verified repair and its recorded checks are member-only.
This mechanism has 7 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.
Sign in to the archive ↗Verification & scope
Payload is a string; schema and content quality are not assessed. 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-30T16:48:28.969710+00:00.
Case digest / 76dcede08d0cda03f6b24fd7992c710905ab886413fe404478d1f63887bd3524