mirror of
https://github.com/affaan-m/ECC.git
synced 2026-10-14 20:25:26 +02:00
montjeffrey
8a7d61299c
Across 240 evaluation trials every question the gate raised was about code structure - importers, callers, public API, data schemas - while every deciding fact in the hidden-intent corpus was an external contract: a consumer's CSV dialect, a reporting timezone, retry safety against a non-idempotent endpoint, collation rules, a quota policy. Obtaining the deciding fact predicted the outcome almost perfectly in both arms, and the gate did not reliably cause it. Add an external-contract question for code targets whose change profile touches data, beside data-schema rather than replacing it: data-schema asks what the change touches, external-contract asks who decides what it has to be. It reuses the existing touchesData signal, so it stays as selective as the question it sits with and adds no new detection, and it therefore does not reach a change with no data involvement - pure retry semantics, for instance - which is a known limit to be measured rather than guessed at. Code edits that touch data now ask four questions instead of three, so the condensed hint for an unknown profile changes too. That string was pinned by a test as legacy-stable; the pin is updated deliberately, because a hint that names fewer questions than the gate asks is worse than a hint that changed. Suites: target-class 31, fact-force 1019, scenario-gate 25, eval 15, and the two effectiveness suites 29 and 26, all passing. The 23 relevantQuestions annotations that listed data-schema now list external-contract as well.