🗣️ QuizWizz shared language

Canonical product and WRDP bench terms used by code, probes, evidence, and agents. The eight initial definitions come from .omp/skills/qwizz-shared-language/SKILL.md:106-117; current work and executable evidence remain in the Program Masterplan and the probe harness. This page defines bench and code terms with file:line citations; the admin design and interaction vocabulary — layers, truth statuses, visual grammar, sticky and interaction lingo, measurement locks — is decoded separately in 📖 Qwizz Admin jargon.

Language

Product surface

Exposure settings: QuizWizz’s site-owned policy matrix that makes each supported presentation control hidden, forced, or visitor-selectable and supplies its effective default. The stored option and hard-allowlist sanitizer are at wp/wp-content/plugins/quizwizz/includes/ExposureSettings.php:75,137,407-410; the rendered controls expose Hidden, Forced, and Visitor states at includes/Admin/views/settings-page.php:59-93. Avoid: visibility settings — answer visibility is a separate policy boundary.

Settings tier: An operator-assigned disclosure level from 1 to 4 that controls which settings rows the Screen Options selector shows (wp/wp-content/plugins/quizwizz/includes/Admin/SettingsPage.php:107-138; configured labels and assignments at wp/wp-content/plugins/quizwizz/config/settings-tiers.json:3-86). Avoid: exposure settings — that term is the visitor-control policy matrix above, not admin disclosure.

Craft: The QuizWizz Builder workflow that selects questions from the enabled pool under generation criteria and produces an allowed play or PDF outcome. The public shortcode is registered at wp/wp-content/plugins/quizwizz/includes/Frontend/Shortcodes/ShortcodeRegistry.php:12; generation criteria and the redirect/PDF outcomes are at includes/Frontend/Craft/CraftService.php:51,207,276. Avoid: build — the release pipeline also builds artifacts.

Settings visual language: Settings visual language = Apple inset-grouped, single purple accent, geometry contract unchanged — 2026-09-14. One containment edge per settings group with hairline-separated rows, switches and segmented controls in place of native WordPress form chrome, one brand token family scoped to the premium Settings root (--qw-brand: #6d28d9 at wp/wp-content/plugins/quizwizz/assets/css/qwizz-tokens.css:398-406, with the group and control radii at :91-93), and no change to the scroll-spy offset, the 52px toolbar geometry or the superglued-rail stacking the gates defend. The dated decision and its limits are in the phase G receipt. Avoid: premium theme, settings redesign — both imply a shipped product theme and neither separates what changed (surface) from what is fixed (geometry).

Version and release boundary

releaseEligible: false: The mandatory classification that a WRDP bench patch is evidence for the release owner, not an artifact eligible to bypass the locked source pipeline (.omp/skills/qwizz-shared-language/SKILL.md:29). Avoid: unreleased, release candidate — both imply a release state the bench cannot grant.

Plugin version vs schema version: QuizWizz is plugin 1.10.0 with database schema 1.6.8; migrations advance the schema and do not independently advance QUIZWIZZ_VERSION. The plugin constant is at wp/wp-content/plugins/quizwizz/quizwizz.php:22; the migration schema constant and stored schema update are at includes/Installer.php:20,183-217. Avoid: version — name which version is meant.

Bench change and evidence

Probe wave: One numbered, independently selectable contract slice of scripts/quizwizz-probe.sh; --wave all runs waves 1–11 and closes with TAP 1..94, assertions=94 failures=0. Wave 7 contributes six assertions after the 2026-09-01 entry-mode re-contract. The selector/dispatch/counter contract is at scripts/quizwizz-probe.sh:8-14,3240-3257; the standing all-wave result is recorded at probe harness — current bench result. Avoid: programme wave — historical W6–W10 programme labels are not probe selectors.

Stage-and-install: The live-file replacement protocol that stages a complete file under /tmp/qwfix/ and atomically installs it as www-data:www-data mode 0644 with sudo -n install -o www-data -g www-data -m 0644 (.omp/skills/qwizz-shared-language/SKILL.md:24). Avoid: deploy, edit live — neither names the staging and atomic replacement boundary.

Browser-authoritative: A rendered UI claim is true only after cache-disabled Chromium observation; source inspection and shell probes can establish supporting contracts but not paint or interaction truth (.omp/skills/qwizz-shared-language/SKILL.md:27,114). Avoid: code-verified UI, probe-verified UI — neither observes the rendered surface.

Matched A/B pair: Before and after measurements use the same live bench and workload with the fix as the sole intended variable, obtaining the before state by reverting the fix and then restoring it (.omp/skills/qwizz-shared-language/SKILL.md:115). Avoid: inherited baseline — an unmatched prior figure is not the before half of the pair.

Ledger routing

Completion class: The single next-move category assigned to every row in the open-work ledger: shipped, bench-actionable, owner-decidable, terminal-blocked, or deferred — corpus replacement inbound. The ledger retains 126 baseline rows and adds twelve canonical 2026-09-01 drive follow-ups, for 138 current rows. The class routes work; it does not replace a row’s separate policy and implementation status. Avoid: status — policy state, implementation state, and next-move class answer different questions.

Section match: A settings-search fallback row emitted when the query describes section metadata rather than directly matching a control. Direct control hits remain individual, while section-only matches collapse into the fallback built at wp/wp-content/plugins/quizwizz/assets/js/qwizz-admin-settings.js:1305-1319 and consumed by the deduplication pass at :1321-1343. Avoid: search result — name whether the row is a direct control hit or a section fallback.

Deferred — corpus replacement inbound: The completion class for corpus, taxonomy-content, and census work deliberately postponed because a corrected replacement corpus is already announced. It is distinct from terminal-blocked: an upstream event is expected, rather than an authority or artifact being absent. The classified rows and census are in the open-work ledger. Avoid: blocked — that hides whether the missing condition is an announced replacement or an absent authority.

Owner-decision sheet: The one batched decision intake under 2026-08-31 corpus triage, where each design or product choice carries a recommendation and measured cost. It records choices for an owner to answer and grants no implementation authority by itself (q5vault/audits/qwizz/2026-08-31-corpus-triage.md:114-116). Avoid: second sheet, decision backlog — either would split the authority the batch exists to keep singular.