We are a new studio, so there is no client work to show. Instead this page is one of our own environments taken apart in full: the task, the grader exactly as it was written, the eight attacks that beat it, and the change that closed each hole. It is the same document a client receives.
Post three vouchers into a Tally Prime company file. That is the whole task. The grader, as it was written, scored 1.0 for the string "voucher created" appearing anywhere in the output. Here is what that cost.
| environment | attacks | bypassed as submitted |
bypassed after the fix |
false negatives resolved |
reproducible |
|---|---|---|---|---|---|
| ledger-post-004Tally Prime · voucher posting | 8 | 4 | 0 | 2 of 2 | yessame repo |
The attack returns 1.0 while the ledger state is unchanged. Not a low score, not a partial credit. Full marks, no work.
A correct answer still scored 0 by the grader as submitted. Two real solutions were being rejected before the fix; both pass after.
Each of the eight results was re-run by hand against the ledger, not just read off the test output. The suite is the cheapest tier; it is not the last word.
We score on the same five axes as a published security benchmark does, because it is a better rubric than anything we would invent and it is public: CWE-bench v1 (Collinear, October 2026) grades agent patches on exactly these five and reports a deterministic gate as the score, with an independent panel beside it.
Does a correct submission score 1.0?
pass ✓Do correct-but-unusual answers still pass?
2 of 2 fixed ✓Do variants of each attack also fail?
next: 20 variantsDid the score come from the work, not the grader?
4 → 0 ✓Does it still run on a clean machine?
pendingTwo are open and we are saying so: generalisation currently checks one variant per probe, and soundness has not been re-run on a machine that is not ours. Both are on the public roadmap, and both will be closed before this environment is offered to anyone.
Anyone can ship a sandbox and a test file. The thing that makes it auditable is the record of what was tried against it, what got through, and the diff that closed each hole. Every line re-runs in the repository you were given.
GSTR-2B reconciliation against a purchase register, and a Zoho Books duplicate-detection task. Both are listed as queued because that is what they are. We would rather show an empty slot than a filled one that is not real.
No client engagements are listed on this page. There have not been any yet.