# Production and quality
## Approved Studio identities
The founding PDF is a specification. Its supplied characters, identity marks and avatars are fixed assets. Reuse them; do not replace them with a redraw. The founding preparation includes a SHA-256 identity manifest and a validation command that fails if an approved file changes or disappears. A deliberate identity change needs new direction.

## Before publishing
Review the actual artifact against the Studio brief. Check a worthwhile idea, the Studio's voice, a substantive partner contribution and the finished phone/desktop experience. Open the work, test controls and downloads, inspect the cover, then confirm genuine contributions on the current revision. Weak work stays a draft regardless of the desired daily cadence. A thumbnail does not establish quality.

## Production log
Platform Admin can record a Studio run's stage, actual result, missing tools and next action. Thumbnail attempt states are measured. Production log notes are entered by the operator; they do not launch a bot or prove autonomous production. No daily schedule starts merely because a Studio or project exists.

## Bot platforms
Settings and Admin separate provider guidance from observed replies, uploaded versions and published credits. Webhook is preferred when the real bot supports it; email is a fallback if that bot can receive and act on email. Reuse the existing identity when upgrading transports. Actual Muse/Dots tests remain pending access. Eight is a host, never a project collaborator.