Skip to content

Add kadamba-fit, a harder synthetic fixture with an answer list - #3

Merged
prathikcannotcode merged 3 commits into
masterfrom
eval/kadamba-fit
Nov 9, 2026
Merged

prathikcannotcode merged 3 commits into
masterfrom
eval/kadamba-fit

Conversation

@prathikcannotcode

Copy link
Copy Markdown
Owner

examples/acme-demo overstates Vigil's accuracy: its comments state its bugs, and its answer list has one should-not-flag item. This adds examples/kadamba-fit, a harder synthetic app whose files state no gap, with an answer list that also names clean controls, so false positives can be measured.

What's here

  • examples/kadamba-fit/: a made-up fitness and cycle-tracking app for members in India and the EU, in 55 files of code, migrations, deployment config, vendor contracts and policies. Every person, company, credential and domain is invented, and domains are reserved for documentation.
  • examples/kadamba-fit.expected.json: 16 planted issues, 13 should-not-flag items, and known real gaps a finding may correctly report.
  • examples/kadamba-fit.run-sheet.md: how to run a blind audit from an exported commit, and how a separate session scores it.
  • One CHANGELOG.md line.

First run

One cold audit ran on master at 259d7e0, and a separate session scored it against the original answer list:

  • 16 of 16 planted issues found, with 45 of 48 citation anchors exact or more specific
  • 3 of 13 should-not-flag items flagged
  • no fixture value in any output, and no absolute path in any finding

The scorer judged two of the three flagged items to be defects in the answer list. a2083c0 narrows those notes and adds the real gaps the run found as known_gaps. The app is unchanged, and the first score stands against the original list.

These are still one run on synthetic code, scored by a model. The run's own output is gitignored and not in this PR.

Keep it blind

The answer list is public once this merges. A fair run copies the app out of the repo and never opens examples/*.expected.json or the run sheet, as the run sheet describes.

Checks

npm run validate -- --strict: 0 errors. npm test: 23 pass, 0 fail, 1 skipped. The branch already contains current master and merges cleanly.

Compliance tooling, not legal advice.

🤖 Generated with Claude Code

prathikcannotcode and others added 3 commits November 5, 2026 19:58
examples/acme-demo overstates accuracy: its comments state its bugs and
its key has one should-not-flag item. This fixture states no gap in any
comment, doc line or identifier, and its key lists clean controls so
false positives can be measured. The run sheet covers a blind audit from
an exported commit and scoring by a separate session.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first scored cold run found real gaps the key missed, and three
should-not-flag notes were too broad or wrong. Narrow those notes and
add known_gaps, so a matching finding counts as correct. Each gap was
checked against the app, which is unchanged. The run sheet records the
change; the first score stands against the original key.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@prathikcannotcode
prathikcannotcode merged commit 9d8d9e1 into master Nov 9, 2026
1 check passed
@prathikcannotcode
prathikcannotcode deleted the eval/kadamba-fit branch November 9, 2026 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant