Files
ECC/docker/gateguard-effectiveness/scenarios-intent/timezone-daily-rollup/task.json
T
montjeffrey b29823b435 test(gateguard): leave the ambiguity unflagged in every prompt
The previous prompts signposted what they withheld - "the dialect our consumer
expects", "the calendar our reports are read against", "retrying only the
failures that are safe to repeat" - which invited a question in every arm and
pushed ungated pass rates to 3/4 and 4/4. That bounded the result to a regime
where the agent was already told something was missing.

Each prompt now reads as an ordinary ticket. Shape a grader checks stays, since
removing it would score field-name guessing instead of the hidden decision, but
it is stated mechanically: checkQuota still documents { allowed, overage } and
defines overage as how far usage exceeds the limit, which does not say whether
exceeding it is allowed, so the soft-limit policy stays hidden.

Graders, workspaces and intents are unchanged, so this isolates one variable:
whether the gate changes behaviour when nothing cues the agent that a convention
it cannot see decides the task.
2026-10-04 22:40:43 -04:00

10 lines
469 B
JSON

{
"id": "timezone-daily-rollup",
"trap": "Every event timestamp is an ISO string ending in Z, which invites grouping by the UTC date. Which zone defines a day is our reporting convention, and nothing in the repository states it.",
"prompt": "Add dailyTotals(events) to src/rollup.js. Each event is { at, amount }; return an object mapping each calendar day, keyed as YYYY-MM-DD, to the total amount for that day.",
"evidence": [
"rollup",
"daily"
]
}