research-document GV-VE-2026-22D4
Layout Family Catalog
Layout Family Catalog
This catalog records layout families as relationships that an implementation must preserve, with the evidence, assumptions, and verification requirements behind them. A family is not a screenshot, a template, or a component.
Identity
Every family has a permanent LAY-* identifier. The identifier space is shared
with Forma's catalog/layouts.json, which records Forma's verified
implementation of families. Visual Engineering owns the relationships and
evidence; Forma owns the presentation contract and its verification.
Files
index.json— catalog version, support states, and the family list.layout-family.schema.json— the required structure of a family record.families/<ID>.json— one record per family.
Validate with npm run layouts:validate; the validator's own tests run with
npm run layouts:test.
Record contract
A record must state:
- Intended tasks and, where useful, tasks it is not for.
- Semantic regions and whether each is required.
- Authoritative source order and its consequence for reading and focus.
- Recognition path — what a user should identify first, second, and so on.
- Deliberate-verification regions — where the user must check before acting.
- Composition — spatial relationships, alignment, density, landmarks.
- Navigation — keyboard, focus, visual, and reading order, and decision points.
- Preserved relationships — what must survive every recomposition.
- Responsive strategy — wide, narrow, and zoom behavior, and a statement that page-level horizontal overflow is prohibited.
- Content stress — long, missing, extreme, and localized content.
- Accessibility expectations.
- Required Forma primitives and known Forma capability gaps.
- Assumptions and how each will be tested.
- Verification requirements, each tagged static, DOM, browser, or review.
- Evidence and hypotheses by ID. Every cited ID must exist in a registry.
Support states
observed → partial → supported → verified. A Visual Engineering record
is observed when the relationships are evidence-backed but no conforming
implementation has been verified, and supported when an implementation
reproduces them and has passed a recorded conformance run (the record's
implementations field names it). verified follows the implementation's
own promotion to verified (Forma records these in its own catalog); a
Visual Engineering record never claims a higher state than its
implementation records.
Relationship to Forma
Forma's catalog/layouts.json family fields (id, name, tasks,
recognitionPath, verificationRegions, composition,
preservedRelationships, narrowRecomposition, status, evidence, gaps)
are a subset of this record. Forma should consume the record's relationships,
not copy its prose.
Current families
| ID | Name | Status |
|---|---|---|
| LAY-TERMINAL-CHARACTER-GRID | Terminal / character grid | supported |
Families already verified in Forma (LAY-FORM-SECTIONED and others) predate
this catalog and have not been back-filled here. See decision
DF-VE-TCG-2026-2DD5.