Repository navigation
weightclass 0.31.1
Highlights
wclass runandwclass routerequire you to say where the tier comes from: exactly one of
--tier(you choose) or--suggest-tier(the local classifier suggests, and prints its own
measured record next to the suggestion). The refuted heuristic classifier is no longer the
default front door, and a suggested tier cannot start a vendor without a review.- When stdout is a terminal,
wclass runshows the task-free route on the controlling terminal
and asks before starting it. No copied fingerprint is needed there.--no-review, an explicit
--jsonbefore the command, or--ack-route-fingerprintselects the non-interactive path, and a
pipe never gains a prompt. - Every
runandrouteflag now has help text.--source-vendorand the tier selection lead
the usage line, and each--helpends with a first command to try. wclass --helplists the seven daily commands and names the seven advanced ones in one line.
profile,select,review-cost-profile,recommend,render,delegate, andv2still
parse, run, and answer their own--help; they are only absent from the listing.- The packaged presets are now
<vendor>-model-override, which is what they do: bind opaque model
and effort labels onto the built-in route shapes. The old<vendor>-cost-focusednames claimed
a saving nothing here has measured. They remain accepted as aliases everywhere a preset is
selected, and the policy files, command bytes, and fingerprints are unchanged. - The README leads with what the tool does, then Install, Quick start, and "What you get, and what
you do not". The measured classifier record and the paired token study were moved, not removed:
see "Why the classifier is opt-in" and "Measured results for tier routing".
Core routing
- The tier requirement is an argparse mutually exclusive group, so it fails before the task is
read, and the diagnostic stays the closedinvalid_inputobject. The usage line is where the
requirement is discoverable, and a test pins that. --suggest-tiercarriesCLASSIFIER_MEASURED_AGREEMENTin the receipt and in the console
review: agreement 10/24 (41.7%), high-tier recall 1/9 (11.1%), over-routing 6/24 (25.0%), and
under-routing 8/9. An explicit tier adds no receipt field, so the frozen schema-1 route bytes are
unchanged and no fingerprint moved.- The terminal review default is keyed to one signal: stdout is a terminal. An explicit
--human
in a pipe does not open a prompt; an explicit--jsonon a terminal does not either.--review
and--no-reviewtogether are rejected rather than resolved in one direction. A pty-backed
harness looks like a terminal, so give it--no-reviewor a fingerprint. review-presetandroutereceipts report the canonical preset name in theirpresetfield. A
script that compares that field to an old-cost-focusedstring needs the new one; nothing else
about the receipt changed.docs/integrations.mdexamples that ranroute/runwithout a tier source were fixed, and a
test now scans every shell block in every markdown file for that defect.
Guidance and documentation
- Project guidance is split by directory scope. The root
AGENTS.mdcarries shared rules and an
index;src/weightclass/AGENTS.md,src/weightclass/advisory/AGENTS.md,tests/AGENTS.md,
.weightclass/AGENTS.md, andpackaging/AGENTS.mdare authoritative inside their subtrees. HANDOFF.mdrecords the direction research done with external reviewers, what survived
checking and what did not, and the usability batch above.
Compatibility and safety
Breaking change — run and route require a tier source. An invocation without --tier or
--suggest-tier now exits 2 with {"error": "invalid_input"} instead of classifying silently.
Automation should pass --tier; interactive use can pass --suggest-tier and review.
Breaking change — terminal runs review by default. A wclass run whose stdout is a terminal
now asks on the controlling terminal before starting a vendor, including for built-in routes that
previously started directly. Scripts driven through a pty should pass --no-review or
--ack-route-fingerprint. Non-terminal behaviour, including the fingerprint requirement for policy
runs, is unchanged.
Breaking change — preset receipt field. The preset field in route and review-preset
output carries the <vendor>-model-override name even when an alias selected the preset.
The one-foreground-child contract, the credential, network, and task-persistence boundaries, the
advisory companion, campaign records, statistical gates, sealed manifests, and every route
fingerprint are unchanged. The core native agy and grok routes still deliver the task in argv;
that boundary is unchanged and still documented in src/weightclass/AGENTS.md. The packaged
advisory Skill bundle is byte-identical to 0.30.0; the 0.30.0 bundle is registered in the upgrade
ledger, which the release workflow requires for the previous tag whether or not the bundle changed.
v0.31.0 was tagged first and failed that ledger check before build. Nothing was published under
it; the tag is retained and not reused, as the release policy requires.
Not in this release
Cheap-first execution with automatic escalation, the only lever the repository has measured as
large, remains unimplemented. It conflicts with the one-foreground-child contract and is a separate
decision, recorded in HANDOFF.md.