Skip to main content

2 docs tagged with "framework"

View all tags

What the author already knew

The dry run proved that signal coverage — not granularity — was what kept 57% of the routing on low-confidence guesses. The fix was almost free. The person creating a unit of work already knows whether it's design, implementation, an audit, or mechanical labor; they know it for the cost of typing one word. So Baton discontinued title-scanning entirely and made a declared verb the single authoritative signal — then graduated it to the framework.

Who the audit thought it was

StrayMark's audit is only worth anything if independent model families converge on a finding by themselves — agreement is the signal. A run of releases hardened that guarantee against three ways to fake it. The freshest is the sharpest — a router CLI injects its own product name, so an auditor stamped its report "qwen-code" even after the operator had switched the backend model. The convergence math was being fed a lie about who did the work.