Plan the installation
Inspect the read-only plan from the Anyam checkout.
anyam realm planThe plan lists resources, permissions, domains, secret locations, migrations, rollback, destruction checkpoints, and cost observations. A plan does not create a provider resource.
Prepare the Worker
Copy the example configuration and replace each customer placeholder.
cp apps/realm-worker/wrangler.example.jsonc apps/realm-worker/wrangler.jsonc
npm run realm:installation-manifest
npx wrangler secret put ANYAM_OWNER_BOOTSTRAP_TOKEN --config apps/realm-worker/wrangler.jsoncKeep API tokens, passkeys, refresh credentials, and secret values out of the configuration file.
Install and claim ownership
Run the resumable lifecycle, then deploy the customer-owned Worker.
anyam realm install
npx wrangler deploy --config apps/realm-worker/wrangler.jsoncOpen the owner claim route, enroll a passkey, and authenticate. Inspect /api/operator/status, /api/operator/preflight, and /owner/control-room after authentication.
Add Projects and Targets
Import Git or scaffold a Project. Use the Realm for semantic operations.
Project → Source Space → Workspace → Change → Revision → Landing → Release → TargetConfigure each Target with a complete deployment profile. The Target record owns provider identities. Callers do not submit account, script, or credential identifiers.
Upgrade, export, and recover
Run the read-only plan before changing the installation.
anyam realm plan
anyam realm upgrade
anyam realm doctor
anyam realm export
anyam realm restoreThe lifecycle stores a credential-free checkpoint and resumes after interruption. Restore activates a quarantined checkpoint. Owner reauthentication and provider reconciliation remain separate steps.