# Design QA

## Source

- Selected direction: `/Users/chaoyue/.codex/generated_images/019ed02c-a15f-7881-aab3-49ff394627b4/exec-e373a4be-af07-451b-937a-7cd5acbd9b12.png`
- Stack figure refresh: `/Users/chaoyue/.codex/generated_images/019ed02c-a15f-7881-aab3-49ff394627b4/exec-0e105db4-a098-48f5-b3f1-301d07cb21f6.png`
- Runtime map: `/Users/chaoyue/.codex/generated_images/019ed02c-a15f-7881-aab3-49ff394627b4/exec-8abdd5c7-4c6a-4406-bd07-47dfbc6f1721.png`
- Maturity model: `/Users/chaoyue/.codex/generated_images/019ed02c-a15f-7881-aab3-49ff394627b4/exec-ed3a252d-15d6-4836-84cb-21ce313f10bb.png`
- Interactive hero: Three.js `0.185.1`, vendored under `docs/assets/vendor/three/` with its MIT license.
- Local prototype: repository `docs/` build served during QA
- Reference comparison: `/private/tmp/loop-design-comparison.png`

## Viewports And States

- Desktop first viewport: 1440 x 1024, page top, sticky navigation visible.
- Mobile first viewport: 390 x 844, page top, dedicated mobile mental model visible.
- Mobile navigation: menu expanded and collapsed; `aria-expanded` changed correctly.
- Pattern library: mobile, filter value `CI`, one matching pattern visible.
- Contract: mobile, first horizontal diagram position, labels readable.
- Runtime map: desktop and mobile; the mobile figure scrolls within a 358 px frame while the page remains 390 px wide.
- Maturity model: desktop and mobile; levels 00-02 are visible initially and the remaining levels are horizontally inspectable.
- Social preview: 1280 x 640, exact resource, pattern, and contract counts.
- Interactive hero, desktop: 1280 x 720, one ready WebGL canvas, 478 px hero, no horizontal overflow, and the next section visible in the first viewport.
- Interactive hero, mobile: 390 x 844, one ready WebGL canvas, 571 px hero, no horizontal overflow, and the next section visible in the first viewport.
- Interactive hero motion: the frame counter advanced by 47 frames during a 450 ms pointer-parallax check.
- Interactive hero efficiency: the frame counter advanced by zero during a 700 ms offscreen check at the Resources section.

## Comparison History

1. Compared the ChatGPT Image direction and the first implementation in one side-by-side input. The implementation preserved the light technical-field-guide palette, thin rules, flat surfaces, and restrained blue/cyan/green accents. The identity was intentionally centered to honor the repository requirement.
2. The first mobile pass scaled the desktop stack diagram too far down. This was a P2 legibility issue.
3. Added a dedicated mobile mental-model asset and horizontally inspectable contract and lifecycle diagrams. Rechecked at 390 x 844; headings, labels, controls, and section transitions are readable without overlap.
4. Tightened short-query filtering so `CI` returns the CI repair loop instead of substring matches inside unrelated words.
5. Compared the original stack figure and the ChatGPT Image revision side by side. The revision replaces empty overlapping outlines with four populated plates, aligned leader lines, a one-run bracket, and an explicit recurring-work governance badge. OCR and browser checks confirmed the required copy, 1666 x 944 dimensions, and error-free rendering.
6. Audited the live README and site for visual gaps. Added coordinated runtime-selection and maturity-progression figures only where the existing presentation was text-only; retained the hero, cover, social preview, stack, contract, and lifecycle assets unchanged.
7. The responsive pass found the citation block widening the entire page to 618 px at a 390 px viewport. Setting footer grid children to `min-width: 0` restored a 390 px document width while preserving horizontal scrolling inside the four wide diagrams.
8. Compared the published static hero and the Three.js-enhanced hero at the same 1280 x 720 viewport. The enhancement keeps the existing identity, copy, actions, spacing, and section transition while adding a restrained evidence orbit, control-plane stack, verification gate, and six lifecycle nodes behind the content.
9. Moved the control-plane stack and verification gate outward after the first 3D pass so they frame the copy rather than crossing its reading path. Rechecked desktop and mobile rendering after the adjustment.
10. Verified progressive enhancement behavior: the semantic hero remains complete without WebGL, forced-colors and print hide the scene, reduced-motion renders a static frame, and the animation stops when the hero leaves the viewport.

## Findings

- P0: none.
- P1: none.
- P2: none after the mobile diagram and filter fixes.
- Console errors: none.
- Broken or clipped primary controls: none.
- Gradient, large-radius, negative-letter-spacing, and viewport-scaled typography checks: clean.

## Focused Evidence

- Desktop hero: `/private/tmp/awesome-loop-hero-desktop-final.png`
- Mobile hero: `/private/tmp/awesome-loop-mobile-final.png`
- Mobile contract: `/private/tmp/awesome-loop-contract-mobile.png`
- Mobile pattern filter: `/private/tmp/awesome-loop-patterns-mobile.png`
- Desktop runtime map: `/private/tmp/awesome-loop-runtime-desktop.png`
- Mobile runtime map: `/private/tmp/awesome-loop-runtime-mobile.png`
- Mobile maturity model: `/private/tmp/awesome-loop-maturity-mobile.png`
- Three.js desktop hero: `/private/tmp/awesome-loop-hero-three-desktop-final.png`
- Three.js mobile hero: `/private/tmp/awesome-loop-hero-three-mobile-final.png`
- Three.js pointer-motion frame: `/private/tmp/awesome-loop-hero-three-motion-final.png`
- Social preview: `/Users/chaoyue/Library/CloudStorage/Dropbox/Loop Engineering/awesome-loop-engineering/assets/social-preview.png`

final result: passed