# Artifact app deployment and validation

Build a private draft, inspect readiness, resolve validation blockers, and prepare it for review.

## Where to find it

Open **Apps & Workspaces**, choose the workspace, and open the artifact. Its header and drawers contain the settings for this guide.

Address: `/artifacts/:id`. Open the saved resource from the product rather than typing this address.

## Build a private draft

1. Describe the app or change in its owning chat, or use [Build MCP](/docs/build-mcp-guide).
2. Ask for a deployed private draft and a review link.
3. Open the artifact and inspect the draft's pages, data and secret bindings, and requested workflow.
4. Open **Publishing details** to inspect **App readiness**, deployment evidence, publish blockers, source bindings, refresh schedules, and deployment timeline.
5. Complete the required smoke and validation checks for the exact candidate.

## Resolve readiness blockers

The page may offer **Start app validation**, **Continue app validation**, or **Fix with Coding agent**. Start with the listed blocker and preserve the current draft. Changing viewer access does not satisfy deployment or validation requirements.

## Know when the draft is ready

Review the version, rendered behavior, validation results, and remaining risks. The readiness progression distinguishes **Build draft**, **Check app**, and **Make live**. A source commit, a build, a deployed draft, and live promotion are separate results.

## Related guides

- [Publishing and rollback](/docs/artifact-publishing)
- [Task Monitor](/docs/task-monitor)
- [App Builder Health](/docs/app-builder-health)