wai-quantum: a person's taste, learned from their own choices between equals #497
Loading…
Reference in a new issue
No description provided.
Delete branch "wai/quantum-taste-r2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Feature 10 of the co-design report: a personal, plural taste model.
Replays #496 on main after #495 merged, as one commit with the same tree. #496's checks were green except one: the macOS energy job's
eoc-metertesta_child_processs_work_is_not_attributed. That is a process-energy test in another workspace, and it failed while the shared macOS host was loaded. The same job passed on #495, and the forge has no rerun, so this is pushed once, fresh. #496 is closed.Engine (
engine::taste)next: the least certain pair that the engine proves equal.CLI and MCP
wai-quantum taste choose | show | rank | next, over files or a specification's elites (--spec). Profiles are kept inquantum-taste.jsonbeside the user's key.taste_rankandtaste_nextread the person's profile. No tool records a choice. At initialize, an agent is told so, and told to call a program new only whennovelty_qasmsays so.Studio
engine_tastein the page,tastein the desktop app.CI: wai-web's native engine test count goes from 10 to 11.
Checked on the build host:
engine::105 pass, 7 of them new;🤖 Generated with Claude Code
Feature 10 of the co-design report: a personal, plural taste model. - engine::taste: - a choice is recorded only when the engine proves the two programs the same circuit or the same state, by a proof (tableau, exact, state), never by random inputs: it is about taste, never correctness; - a Bradley-Terry logistic over differences of measured features (gates, two-qubit gates, depth, two-qubit depth, T gates, modelled error) and of the text (statements, kinds of gate, repetition, comments), ridge penalised and fitted by Newton's method: deterministic everywhere; - the rubric's parts (economy, clarity, insight, precision, utility), each learned from its own choices; a ranking names where a part or the cost puts another first; - profiles personal and plural, by name, never pooled; - typicality (one less engine::novelty's novelty) shown and never learned; the novelty dial blends the standardised order by taste with the order by novelty; a floor on each feature's spread keeps a feature that barely varied from turning into certainty; - measured: choices predicted as made and held out (last 100), the ones nothing measured separates, and whether a ranking's first three are built more alike than the cost's; scores about the candidates' mean; - next: the least certain pair the engine proves equal; call for hosts. - novelty::token is shared with it. - The command line: taste choose | show | rank | next (files or --spec), profiles in quantum-taste.json beside the user's key. - MCP: taste_rank and taste_next read the person's profile; no tool records a choice. initialize tells an agent so, and to call a program new only when novelty_qasm says so. - The Studio: "Your taste" in the Workbench (Compare two with the part a choice was about, Rank by my taste with typicality and the dial, profiles by name); an alternative that is the same circuit as the draft, taken whole or refused whole, is a choice; Improve orders by the profile. - Bindings: engine_taste in the page, taste in the desktop app. - CI: wai-web's native engine tests count 11. Co-Authored-By: Claude Opus 5.5 <[email protected]>