Source: qdash GovernSheet modal → full edit page (c64, control-detail mock, 2026-08-10)

Define the standard once. The condition is authored against the vocabulary of signals qcontrol actually collects (/api/control-vocab), so every saved control is executable — the findings engine evaluates it on every read.

c64 — control detail as a page: the GovernSheet modal's full edit surface (copy, field order, .ctl/.proj chrome verbatim) re-laid for a page. New vs the modal: a context header (breadcrumb, name, severity + category chips, mono id, live-match count) and a two-column split — Definition (name, condition sentence, severity, category, evidence, remediation) left, Response & mapping (decisions, when-it-happens, satisfies) right — with a bottom save bar. Exemplar state matches the crit control: high · Posture · assign owner + open findings · Alert → Slack · SOC 2 + NIST AI RMF + NIST CSF 2.0. Condition builder is display-only (one clause); vocab/dry-run wiring is the real build's job.

Sentence-family trial: the condition clause and the Alert channel now compose the layer's sentence components (SentenceSelect pills, SentenceNumber) in place of GovernSheet's local .ctl chrome — same v-model composition idiom as policy-detail's rule rows and NotificationRuleCard. Gaps observed for the design pass: the pill style diverges from the sheet (rounded-full + content-dark border vs .ctl's rounded-8 + stroke border); SentenceSelect's reserved chevron padding (pr-12) over-widens narrow content like the < operator; SentenceRow always renders its 90px label slot so it can't wrap unlabeled clause rows; and there's no sentence-native "+ and" / remove-clause affordance (policy-detail hand-rolls a UxIcon plus + UxClose).