Deploy and Publish
Develop from a Local Directory
Use a linked local directory before publishing:
On desktop, link the project root or its tapMiniapp.output directory once from Apps > Marketplace > Develop > Local Directory. On mobile, use Workspace Settings > Miniapps > Develop > Local Directory. The AI Platform infers dist/manifest.tap.json from a project root, watches the linked directory, and stages each complete generation. A failed or incomplete build does not replace the active generation.
Permission removals and narrower authority activate automatically. New, broader, or incomparable authority, plus any local service contribution change, moves the installation to Review required before activation.
Linked local development is device-local and workspace-scoped. It does not create a Marketplace package or release.
Publish with Zephyr
Publish the assembled output with a deployment provider that supports the tap-app build target. The standalone Zephyr publisher adapter uploads ordinary assets and returns one immutable deployment URL.
The provider does not receive or create TAP package identity, release identity, dependency graphs, Marketplace state, trust, acquisition receipts, installation state, or update policy. Those concepts belong to TAP.
Your deployment root must be one exact HTTPS origin:
The root must use HTTPS with no credentials, custom port, path, query, or fragment. The AI Platform does not maintain a deployment-host allowlist. Dashboard URLs, tags, environments, and version selectors are not Marketplace import inputs.
Authentication is owned by the developer or CI environment that performs the build. Never put deployment credentials, sign-in links, or local session data in the repository.
Publish Through TAP Marketplace
TAP Marketplace is the only supported installation path for published Miniapps. On desktop, open Apps > Marketplace > Publish. On mobile, open Workspace Settings > Miniapps > Publishing. Select the Zephyr deployment and publish its verified release to Marketplace.
TAP imports and verifies the exact Zephyr deployment bytes, then mints and owns the package and release identities. The deployment root remains a private byte-delivery locator. Publishing a new Zephyr deployment does not change an installed Marketplace release or workspace assignment.
Release an Update
- Build and publish a new immutable Zephyr deployment.
- Verify the new root independently.
- Import it as a new exact TAP Marketplace release.
- Explicitly update the Marketplace publication or workspace assignment when the new release should replace the prior release.
The AI Platform does not follow provider tags or environments. It does not poll for changes or activate a new provider deployment automatically.
Default Miniapps use the exact repository-reviewed bundle included in each desktop binary. Code and Browser are current defaults, and future reviewed packages can join the same bundle. Defaults start enabled in every workspace, can be disabled, and receive newer bundled releases when The AI Platform updates.
Roll Back
Explicitly restore the previous exact release in the relevant Marketplace publication or workspace assignment.
During runtime activation, The AI Platform retains the last known good release until the new release becomes ready. Descriptor, integrity, compatibility, mount, or readiness failure leaves the prior release active.
Publication Evidence
Retain a sanitized record of the immutable deployment root, descriptor digest, artifact digests, source revision, readiness result, and timestamp. When TAP Marketplace is involved, also retain the TAP package ID, release ID, and release-root digest.
Never record deployment credentials or private authentication URLs.