bcquality/microsoft
wenjiefan 3eed0bba38 experiment: shift the adjudication burden of proof toward rejection
The first arbitration smoke run showed the gate changing nothing: comment
volume stayed inside baseline noise, and on a clean fixture the two
AppSource-affix findings the gate exists to stop survived untouched.

The likely cause is the contract's own wording. 'When the evidence is
genuinely ambiguous, keep the finding' let any finding whose precondition
could not be positively disproved pass through, which is most of them - a
reviewer cannot prove from a bare src/*.al diff that the app is not an
AppSource submission. That framing asked the gate to disprove findings
rather than to confirm them.

This inverts it. Applicability must now be affirmatively evident in the
diff or in observable repository context, project-wide assumptions
(packaging model, deployment target, tenancy, release state) may not be
invented to support a finding, and an unresolved doubt resolves to
rejection instead of a pass.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: e33a7b96-4821-4797-9f72-96880f3c6412
2026-09-02 14:55:49 +02:00
..
knowledge Add precision guards for systematic agent false-positive patterns (#112) 2026-07-17 14:17:04 +02:00
skills experiment: shift the adjudication burden of proof toward rejection 2026-09-02 14:55:49 +02:00