Audio Motion Music

Safety check before going live

Check that client setup, song registrations, royalty money and backups are safe before going live.

Run the production check. Nothing here deploys or changes DNS.

0%not checked

Publishing & song money has not been checked yet

This gate separates data-integrity blockers from operational work that can continue after launch.

What AMM checks

Confirm the database backup

The operational snapshot above is useful for portability, but it is deliberately not presented as a full disaster-recovery backup. Before production cutover, create a real Cloudflare D1 export/backup and record its filename, checkpoint or reference here.

Check the important pages

These checks confirm that the production package contains the essential publishing/recovery pages. They do not replace a visual browser test on the deployed preview URL.

Before going live

  1. Deploy this package to a preview/test Cloudflare Pages URL, not straight over production.
  2. Confirm AMM_DB, admin authentication and the existing zero-cost safeguards are bound correctly.
  3. Create and retain a real D1 backup/export, then record its reference above.
  4. Run this publishing checks on the deployed preview and resolve every required failure.
  5. Open Publishing & royalties today, Import royalty statements, Find royalty problems, Royalty claims, Match incoming payments, Registration plan, Register songs, Publishing clients and Statements & payments manually.
  6. Run one harmless test through the workflow or use existing data to verify navigation. Do not create fake accounting evidence in production.
  7. Check the publishing client portal with a real test client credential and confirm internal evidence is not visible.
  8. Only after the visual/browser pass should the preview be promoted to the live Pages deployment.