ZZD public AI gateway · zzd_public_ai_gateway_v2
Resource: 07 · Publish and maintain / 生命周期
Canonical map: https://zzd.show/docs/ai/map.json
Full handbook: https://zzd.show/llms-full.txt

# Show lifecycle

Canonical state flow:

`authorized -> private hidden draft -> built_pending_validation ->
validated -> public visible -> maintained or unpublished`

## Create

- Begin `private=true`, `hidden=true`.
- Save accurate metadata and readable authoritative Pieces.
- Upload/bind assets and configure dependencies.
- Configure BaaS only when the product needs it.
- Keep a known-good baseline and validation matrix.

## Validate

Pass rendered-experience, live-source-quality, and environment-parity
checks. A build is only `built_pending_validation` until browser
evidence passes. Use a fresh final-state screenshot as thumbnail.

## Publish

Public visibility is consequential. Ask the user to confirm, then:

- set `private=false` to allow public access;
- set `hidden=false` to allow ordinary discovery;
- reopen detail, blank, editor preview, and embed;
- report stable returned URLs and remaining dependencies.

A public-but-hidden Show is a link-only/unlisted choice, not a fully
discoverable publication.

## Maintain

On every edit:

1. identify affected metadata, Pieces, assets, bindings, BaaS schema,
   and states;
2. preserve or record a last known-good version/duplicate before a
   risky change;
3. edit the smallest source owner;
4. rebuild/clear stale compiled output intentionally;
5. rerun the same state matrix in all environments;
6. refresh the thumbnail if the visible result changed;
7. summarize change, evidence, migration impact, and rollback path.

For BaaS schema changes, use additive/backward-compatible migration
when possible and protect existing user data. For dependency
upgrades, pin versions and compare timing, layout, render output, and
bundle behavior with the known-good version.

## Unpublish

Ask for confirmation before changing a public Show. Set
`hidden=true` to remove discovery while preserving link access, or
`private=true` when access itself must stop. Recheck Sale/buyer impact
before restricting a bundled Show.

Deletion is destructive and is not part of the default deploy flow.
Never delete a Show, asset, collection, or Sale without exact target
resolution, impact review, explicit user confirmation, and a
recoverable path where available.