ZZD public AI gateway · zzd_public_ai_gateway_v2
Resource: 04 · Code and experience quality / 双门槛
Canonical map: https://zzd.show/docs/ai/map.json
Full handbook: https://zzd.show/llms-full.txt

# ZZD Show quality standard

A Show passes only when two independent gates pass.

## Gate A — rendered experience

The intended layout, content, responsive behavior, motion, media,
input, and recursively revealed states must work. Test the experience
rather than a single first-frame screenshot. Where applicable, use
real wheel/touch, pointer movement, hover, click, keyboard, drag,
camera permission, video progress, canvas/WebGL time, routes, menus,
drawers, detail states, and return paths.

## Gate B — live source quality

Editor-visible Pieces must be readable, formatted, maintainable, and
must actually own the result. Vendor/minified/generated binaries may
remain support assets, but meaningful structure, content, state,
media roles, and motion orchestration stay live and editable.

Hard failures:

- a root-only loader that injects an uploaded site;
- an all-in-one uploaded HTML page;
- nested iframe, re-frame, document swapper, or hosted-page wrapper;
- a generic runtime transport or global fetch/XHR rewrite bridge;
- an opaque/minified blob owning the meaningful content or state;
- unused readable sidecar Pieces that do not affect the renderer;
- a giant absolute asset URL map standing in for an asset model;
- only one initial state implemented or tested;
- stale compiled output masking the raw source;
- a generic factory topology reused across unrelated Shows.

Technology is intentionally flexible. Choose vanilla, React, Vue,
GSAP, Three.js, WebGL/WebGPU, SVG, canvas, Lottie, Rive, video, or
other tools based on the experience. Flexibility does not waive the
two gates.

## Environment parity

Verify independently:

1. blank/fullscreen runtime on desktop and mobile;
2. the actual editor preview iframe (`#preview-frame`; it may remain
   `about:blank`, so inspect its inner document);
3. the ordinary embed iframe when available.

Check console errors/warnings, page errors, unhandled rejections,
failed requests and HTTP 4xx/5xx, broken images/video/fonts/models/
decoders/wasm/workers, WebGL errors, unsafe anchors/forms, horizontal
overflow, loading/empty/error states, and explicit backgrounds.

For canvas/WebGL, prove a nonblank result and motion using
time-separated and interaction-separated evidence. For video, check
the final local URL, ready state, dimensions, time progress, and
media error. A successful HTTP response alone does not prove a valid
codec or binary.

Compare maintenance candidates with the last known-good Show at the
same states. Readability that changes timing, camera, layout, media,
or interaction is a regression, not a successful refactor.