Senior Application Developer

loc: Maynooth, ON K0L 2S0tel: 613-553-0960email: rgsamways@gmail.com
Robin Samways

$ Sreditor · Testing & Verification

How Sreditor actually gets verified — against its own build, and against a codebase four times its size.

As of the most recent count: 26 TypeScript source files, 1,222 non-blank lines of code, 52 passing tests across 12 test files. Every command works end to end against real Anthropic API calls, not fixtures.

Two real tests, not one. Judged against its own build first, Sreditor found itself SR&ED-ineligible at every single phase. Then, judged against Farpost's real, unrelated OpenSpec history — 48 archived changes, roughly four times Sreditor's own build — it returned exactly one defensible claim, a project rollup synthesized from three individually-ineligible changes.

Testing against a codebase four times Sreditor's own size broke things dogfooding never touched: rollup failed outright against Farpost's mostly-ineligible 48-change log — first an opaque parse error, then a clean token-limit error once diagnosed — fixed by having code assemble the ineligible-change bucket instead of the model.

Worth stating plainly rather than implying full determinism: rollup's exact grouping showed real run-to-run variance — an earlier run pulled a fourth, unrelated change into the dispatch narrative; the saved run kept it at three, same underlying story, a different boundary.

Feedback on this page