Source
Name the authority
Record the system version, application template, and artifact used as the visual reference.
10 / Reference
The artifact is not done when it looks right. It is done when the intended meaning survives the smallest view, the still frame, the keyboard path, and the published file.
10.1 / Web release
Automated checks catch structural failure. Human review determines whether the composition communicates clearly and still feels like the system.
10.2 / Responsive
Mobile is not a scaled desktop. When topology changes, reading order, marginal labels, and system diagrams are deliberately recomposed.
| Viewport | Inspection | Failure conditions |
|---|---|---|
| 1440 × 1000 | Canonical desktop composition, 80px gutters, 12 columns. | Reduced hierarchy, weak negative space, incorrect type wrap. |
| 1024 × 768 | Tablet/desktop boundary and system-index behavior. | Navigation collision, narrow proof field, oversized monument. |
| 768 × 1024 | Tablet gutter and two-to-one column transitions. | Premature squeeze or inconsistent section order. |
| 390 × 844 | Canonical mobile composition and typography. | Clipping, horizontal scroll, miniature desktop topology. |
| 320 × 700 | Personal-site safety floor. | Unreachable controls, broken words, hidden state. |
| 640 × 360 | Player-scale film comprehension. | Tiny labels, ambiguous diagram, missing semantic proof. |
10.3 / Film release
Source, narration, timing, geometry, render, audio, and release proof remain bound. A visually similar export is not the same artifact.
10.4 / Privacy + provenance
A public system site may document the grammar of a protected briefing without copying its source material, recipient data, or licensed identity assets.
Source
Record the system version, application template, and artifact used as the visual reference.
Content
Do not paste sensitive project copy into a public design-system demo.
Identity
Borrow rules and reusable fonts; do not transplant another entity’s wordmark.
Secrets
No credentials, tokens, local file paths, unpublished links, or environment data in the artifact.
10.5 / Definition of done
The release note should name what was tested, what was visually inspected, what source governed the design, and where the artifact is live.
The canonical Ontology contract and latest approved production application were inspected before design decisions were locked.
Fonts, weights, token values, breakpoints, local assets, and theme behavior match the declared contract.
Theme, index, motion controls, focus, and state announcements work with mouse and keyboard.
A second reviewer inspects hierarchy, responsive composition, accessibility, and drift against the source.
The live URL is fetched and inspected after deployment; a successful build alone is insufficient.