Primitive Sufficiency Review¶
Evaluation — instantiates Geometric Primitives Vocabulary Constraint
A structured test of whether the current primitive alphabet and grammar can express every distinction the work actually requires — before scarcity forces a one-off exception.
A Primitive Sufficiency Review turns the archetype's hardest question on the vocabulary itself: is our alphabet big enough? It takes the set of distinctions the work must carry — every meaning, state, category, or relationship the forms have to communicate — and checks, case by case, whether the existing primitives and their permitted combinations can express each one without inventing a new form. Its defining move is that it evaluates the vocabulary's expressive capacity, not its usage: it is a forward-looking test run when the language is designed or when it starts to feel cramped, and its verdict is a decision about the alphabet — keep it, expand it deliberately, or discover that the strain is really a grammar problem in disguise. It is the disciplined alternative to the failure mode where scarcity is discovered mid-project and patched with an ungoverned one-off.
Example¶
A hospital network is standardizing the glyph vocabulary for its clinical dashboards: a small kit of points, bars, lines, and panels meant to represent every metric a ward displays. Before rolling it out, the data-viz team runs a sufficiency review. They assemble a worklist of the real distinctions the dashboards must draw — trend vs. snapshot, absolute vs. relative, within-normal vs. out-of-range, ordered severity vs. unordered category — and try to express each one using only the approved glyphs and combinations. Most pass: severity maps cleanly onto an ordered bar scale, category onto panel grouping. But two fail. "Confidence interval around a projection" cannot be shown with points and lines alone without reading as a second data series, and "provisional vs. confirmed" has no available encoding at all. The review's output is not a redesign; it is a sized verdict: the vocabulary is sufficient for 22 of 24 required distinctions, the two gaps are named, and each is routed — one to a proposed new primitive entered in the variant register for governed admission, the other reclassified as a grammar fix (a hatching rule) that needs no new form.
How it works¶
The review is a coverage test against a distinction list:
- Enumerate required distinctions. List, concretely, every meaning the vocabulary must carry across representative cases — not "be expressive" but the specific contrasts that must be legible.
- Attempt expression. For each distinction, try to realize it with existing primitives and permitted combinations. Success, awkward-but-possible, and impossible are recorded separately.
- Diagnose each failure. A gap is triaged: is it truly a missing primitive, or a missing composition rule, or two distinctions that should be merged? Most apparent shortages are grammar problems, and the review's discipline is to prove a new form is necessary before admitting one.
- Route the verdict. Genuine gaps become governed proposals in the variant register; false gaps become grammar work; the sufficient majority is certified so the vocabulary can ship with a known, bounded set of exceptions rather than an open question.
Tuning parameters¶
- Distinction-list completeness — how exhaustively the required contrasts are enumerated. A fuller list catches more latent gaps but costs more to assemble and can invent needs that never arise.
- Sufficiency bar — whether "expressible but awkward" counts as pass or fail. A strict bar surfaces more gaps and grows the alphabet; a lenient one keeps the vocabulary small at the cost of forcing hard-to-read encodings.
- Case representativeness — how well the test cases stand in for real future work. Toy cases pass easily and hide real strain; realistic, adversarial cases predict actual sufficiency.
- Gap-to-primitive threshold — how strong the evidence must be before a gap justifies a new primitive rather than a grammar change. A high threshold protects minimalism; a low one lets the alphabet creep.
- Review timing — design-time only vs. re-run at major scope expansions. Re-running catches vocabularies outgrown by new demands but competes for attention with delivery.
When it helps, and when it misleads¶
Its strength is that it decides the alphabet's size on evidence rather than on either dogma or panic: it prevents both the over-large vocabulary that reflexively adds a form for every need and the brittle one that ships too small and gets patched with unlogged exceptions the first time it is stressed. It is the mechanism that operationalizes the archetype's rule that a new primitive is admitted only when a necessary distinction cannot otherwise be made — a form of requisite variety, the principle that a language must carry at least as much variety as the distinctions it has to control.[1]
Its failure mode is that a review is only as honest as its distinction list and its test cases. A vocabulary can pass on a tidy set of representative cases and then fail in the field on the messy distinction nobody listed, so a clean verdict breeds false confidence. The classic misuse is running the review as a rubber stamp — enumerating only the distinctions the vocabulary already handles — so it always concludes "sufficient." The guarding discipline is to source the distinction list from real, adversarial cases (including ones that previously forced exceptions), to record awkward-but-possible passes as latent risk rather than clean wins, and to re-run when scope grows rather than trusting a one-time verdict.
How it implements the components¶
Primitive Sufficiency Review fills the is-the-vocabulary-adequate slice of the archetype — the evaluation that governs the alphabet's size:
primitive_sufficiency_test— this is the mechanism: the case-by-case test of whether required distinctions are expressible without new forms.primitive_alphabet_specification— the review evaluates the current alphabet directly and its verdict certifies or amends that specification.variant_expansion_register— proven gaps are routed into the governed register as candidate additions, so expansion is a recorded decision.
It does not check whether shipped artifacts still obey the vocabulary (exclusion_boundary, composition_rule_grammar) — that conformance sweep is the job of its nearest twin, Vocabulary Drift Audit; this review tests the vocabulary's capacity, the audit polices artifacts' compliance.
Related¶
- Instantiates: Geometric Primitives Vocabulary Constraint — the review decides whether the constrained vocabulary is expressively adequate before it is committed to.
- Consumes: Shape Alphabet Sheet supplies the current alphabet the review tests.
- Sibling mechanisms: Vocabulary Drift Audit · Shape Alphabet Sheet · Primitive Grammar Style Guide · Grid and Alignment System · Icon Construction Template · Parametric Module Library · Exception Register
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Primitive Sufficiency Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it a structured test of whether the current primitive alphabet and grammar can express every distinction the work actually requires — before scarcity forces a one-off exception.
Independent corroboration: The frozen evidence defines Primitive Sufficiency Review as 'A structured test of whether the current primitive alphabet and grammar can express every distinction the work actually requires — before scarcity forces a one-off exception', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Testing whether a constrained component vocabulary can express required distinctions is characteristic engineering design review.
Related originating lineages:
- Art & Aesthetics — Primitive Sufficiency Review is most plausibly rooted in the art_aesthetics tradition because its characteristic form depends on visual composition, formal vocabulary, and aesthetic ordering. The assignment tracks that formative lineage, not the many settings in which the mechanism can now be applied.
- Human-Computer Interaction — The human_computer_interaction tradition materially shaped Primitive Sufficiency Review through its own practice of interface disclosure, user guidance, interaction design, and cognitive load.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of engineering design. NASA Systems Engineering Handbook: Design Solution Definition documents the defining practice, history, or theory described in the selected origin rationale. Other domains are retained only where the blind reviews identify material co-development or translation; broad later application is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among formative lineages.
Attribution caveat: The blind-review boundary with art aesthetics is substantive: those traditions materially developed, translated, or operationalized part of the mechanism. The cited provenance places its defining lineage in engineering design.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
Notes¶
The review and its twin, the Vocabulary Drift Audit, are easy to conflate because both are periodic reviews of a vocabulary — but they point in opposite directions. Sufficiency asks whether the language is big enough for the work (and may grow it); drift asks whether the artifacts are still faithful to the language (and may correct them). Running one when you needed the other is a common and expensive mistake: expanding the alphabet when the real problem was undisciplined usage, or auditing conformance when the real problem was a vocabulary too small to comply with.
References¶
[1] W. Ross Ashby's Law of Requisite Variety (1956) holds that a regulator must command at least as much variety as the disturbances it must handle. Applied to a form vocabulary: the alphabet must carry at least as much variety as the distinctions the work requires — which is exactly what a sufficiency review measures before deciding whether to expand it. withdrawn registry ↩