FA-99836 / Tool call schema validation / Open access

Property name rule checks values instead of keys · case 01

Property name rule checks values instead of keys.

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

ROOT CAUSE

The name constraint is applied to property values.

THE FAILURE

The name constraint is applied to property values.

Unsuccessful approach: Checking at least one key misses a disallowed sibling key.

Case contract

Every property name must begin with the supplied prefix; an empty object is valid.

Why this case matters

Tool argument validation prevents malformed structured payloads from entering a deterministic downstream operation.

1 / The failure

Exit 1

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

N = 1
observations = []
def solve(obj, prefix):
    return all(str(v).startswith(prefix) for v in obj.values())
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('all matching',solve({'arg_a':1,'arg_b':2},'arg_'),True)
check('bad name with matching value',solve({'other':'arg_value'},'arg_'),False)
check('one bad sibling',solve({'arg_a':1,'x':2},'arg_'),False)
check('empty object',solve({},'arg_'),True)
check('empty prefix',solve({'x':1},''),True)
check('exact prefix key',solve({'arg_':None},'arg_'),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
all matching	`False`	`True`	Failed
bad name with matching value	`True`	`False`	Failed
one bad sibling	`False`	`False`	Passed
empty object	`True`	`True`	Passed
empty prefix	`True`	`True`	Passed
exact prefix key	`False`	`True`	Failed

SHA-256 / 6cfc076481a799e43987222a48c358b1220284fcd00d80d18f66a83442749dcd

2 / The unsuccessful fix

Exit 1

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

N = 1
observations = []
def solve(obj, prefix):
    return any(k.startswith(prefix) for k in obj)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('all matching',solve({'arg_a':1,'arg_b':2},'arg_'),True)
check('bad name with matching value',solve({'other':'arg_value'},'arg_'),False)
check('one bad sibling',solve({'arg_a':1,'x':2},'arg_'),False)
check('empty object',solve({},'arg_'),True)
check('empty prefix',solve({'x':1},''),True)
check('exact prefix key',solve({'arg_':None},'arg_'),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
all matching	`True`	`True`	Passed
bad name with matching value	`False`	`False`	Passed
one bad sibling	`True`	`False`	Failed
empty object	`False`	`True`	Failed
empty prefix	`True`	`True`	Passed
exact prefix key	`True`	`True`	Passed

SHA-256 / 538a32af15f0418944a618f9f3b7d0454a5a02927383c0d07ba521cce76d285c

HELD IN THE MEMBER ARCHIVE

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

This mechanism has 6 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

Self-contained toy JSON-like schema contract over in-memory Python values; no compatibility with a production schema standard or callable binding is claimed. 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.554565+00:00.

Case digest / 4901c67ee99dd1f2000518b636a6805c862bbb22d51c62fe528a610c9e70d1a9