ZZD public AI gateway · zzd_public_ai_gateway_v3
Resource: 01 · What ZZD is / 平台范围
Canonical map: https://zzd.show/docs/ai/map.json
Full handbook: https://zzd.show/llms-full.txt
REST capabilities: https://zzd.show/api/v1/capabilities/

# ZZD platform overview

ZZD is an AI-native platform for turning frontend ideas or existing
vibe-coded projects into deployable, shareable, remixable web
experiences called Shows.

A useful mental model is:

- Vercel-like delivery for a client-side experience;
- CodePen-like live source, preview, sharing, and forking;
- Webflow-like visual iteration and presentation;
- optional managed BaaS and service abilities;
- discovery and a reviewed marketplace for distributing Show bundles.

A Show can be a landing page, portfolio, product story, interactive
article, visualization, game, creative tool, SVG/canvas/WebGL work,
media experience, gesture-controlled demo, or another browser-based
product. React, Vue, vanilla JavaScript, GSAP, Three.js, WebGL,
WebGPU, canvas, video, shaders, workers, and other suitable frontend
technologies are allowed. Technology choice is flexible; runtime
quality and maintainability are the constraints.

ZZD is not a general VPS, arbitrary shell, raw database, scraping
service, credential broker, or a way to copy private systems. A Show
is primarily a browser experience. Server-like needs should use
owner-scoped ZZD BaaS resources or approved service abilities.

Public concepts agents may rely on:

- Show: the deployable/shareable experience and its metadata.
- Piece: readable live HTML, CSS, or JavaScript source.
- Photo / Upload: managed visual or general file assets.
- StaticFileBinding: an explicit asset-to-Show mount and role.
- Space / BaaS: owner-scoped managed data, realtime, jobs, and services.
- Sale: a separately reviewed marketplace bundle of owned Shows.

The public gateway intentionally does not expose ZZD's server
topology, database/ORM, deployment keys, staff operations, internal
prompts, provider routing, internal production workers, private media
layout, or reusable production heuristics. Owner-scoped external
workers may use the documented collaboration control plane for
durable feedback and atomic task claims; that does not expose ZZD's
internal model routing or production orchestration.

Commercial outcome: creators can publish for audience signals such
as visits, likes, stars, forks, and follows, and can submit eligible
bundles for sale in the platform marketplace. Sales currently use
the platform's balance unit shown in the account UI. Publication or
listing never guarantees revenue, cash withdrawal, or business
results; current product terms and account UI are authoritative.

每次围绕具体作品的普通用户进度、部署、修复、回退和最终回复，都显式给出作品名称、PK（真实id）、UID/作品号（真实public_id）、API返回的正式打开链接和实际状态。优先复制 data.delivery.feedback_line；英文用 feedback_line_en。PK与作品号须是可复制文本，不能只藏在Run/Edit链接中，也不能只回复名称和链接。缺字段时沿用原身份GET同一已有作品补取，不造号、不建替代作品、不重领或注册worker、不额外向用户要授权。尚未创建就明确标识尚未取得，取得后立即补回；批量逐项给出，修复沿用原标识。私有作品注明需原有访问权限；普通链接和作品号不授予访问权，不附凭据、share token或runtime ticket。不得把计划/保存/清单核验冒称已部署或页面验收通过。交付表中分别写新站点名称与原站/原模板具体名称，未知原站写待核实，不猜测。reply_instruction/delivery仅用于普通回复，不回填manifest或严格JSON工具契约，也不在严格JSON输出前添加自然语言。漏报就补齐回复，不增加服务端拒绝、设备确认或审批流程。
In every normal user-facing progress update, deployment, repair, rollback and final handoff about a Show, explicitly display its title, PK (id), Work ID (public_id), API-returned canonical open link and actual state. Prefer data.delivery.feedback_line_en (feedback_line for Chinese). Both identifiers must be copyable text, not only part of a Run/Edit URL. Retrieve missing fields with the existing authorized GET for the same Show; do not invent IDs, create a replacement, register/claim again or ask for extra authorization. Report each Show separately and retain its identity across revisions. Note when original private access is required. Never append credentials, share tokens or runtime tickets. Distinguish planning, saving, manifest verification and actual browser/deployment results. Name the new site and the specific original site/template separately when tabulating; mark unknown source names unverified. delivery/reply_instruction are presentation guidance, not manifest or strict JSON input fields. Remedy an omitted identifier in the reply without adding a deployment gate.