SONIX / SYNTHFLX / SOURCE HANDOFF

One room.
Two editors.

← Back to the Launch Room

Shared editing is enabled. Drew’s two-person verification is pending.

Kavi signed in and saved the agreed test note to shared storage, then reloaded successfully. Local drafts are not proof of sharing. The test is complete only when Drew sees Kavi’s note after reloading and Kavi sees Drew’s reply after reloading.

The exact project

Account: Kxvi@sonix.audio’s Account
Pages project: synthflx-launch-plan-20261018
Production: synthflx-launch-plan-20261018.pages.dev

Drew’s existing account membership is active with Developer Platform Admin for the entire account. That role includes Pages deployment permissions. There is no pending membership invitation in the inspected account. An operation from Drew’s own session still needs to be tested.

Get the editable source

This is a direct-upload site with no connected Git repository. “main” is its production deployment label. Download the plain HTML, CSS, JavaScript and assets, then open the folder in your preferred code editor. No password or API token is included or required in the source.

Download editable source ZIP ↗Open the Cloudflare project ↗

The ZIP is a source snapshot, not a synchronized editor. Pass the latest full source between editors and coordinate code deployments. GitHub was not introduced, so no GitHub invitation is needed.

Save planning edits

  1. Use Sign in with your existing Cloudflare account: Kavi or Drew’s approved identity.
  2. Edit task notes/review marks, reference task links/adaptation notes, or artwork. Existing device-only drafts remain local until you choose to share them.
  3. Select Save shared on the item. Wait for the saved version confirmation. The other person can use Refresh shared or reload.
  4. If someone changed the same item first, your draft stays local. Copy any text you want to keep, load the shared version, compare, then save deliberately.

These shared edits do not redeploy the website or convert proposals into agreed decisions. Changes to the baseline task titles, dates, scope or decision labels are source edits in data.js. Historical email copy stays historical.

Preview and publish source edits

  1. Sign into Cloudflare using your own account. Select Kxvi@sonix.audio’s Account and the exact Pages project linked above.
  2. Edit the source locally. The bundle’s README.md and packaging script explain how to prepare the upload. Keep private files and credentials outside the site folder.
  3. Choose Create deployment → Preview, upload the ZIP with index.html at its root, and inspect the generated preview. Preview deployments do not share production database access.
  4. When approved, create a Production deployment from the same reviewed ZIP. Reload the main site and record the deployment ID. Retain the prior good ZIP for rollback.

A source deployment changes code and baseline content. Shared database edits are separate; rolling back a Pages deployment does not roll back notes.

The agreed two-person test

  1. Kavi has saved a temporary note on Launch SYNTHFLX: “Shared sync test — Kavi”. Preserve any existing note first.
  2. Drew reloads from his own signed-in browser, confirms the note, changes it to “Seen by Drew”, saves and reloads.
  3. Kavi reloads and confirms Drew’s change. Restore the prior note after recording success.
  4. Drew also creates a small Preview deployment from his own Cloudflare account to verify deployment access without changing production.

Invitation acceptance, account visibility and two tabs using the same local storage are not a substitute for these checks.

Isolation

Shared storage uses the dedicated synthflx-launch-room database through this project’s LAUNCH_DB binding. Song Wars databases, buckets, Workers and domains are not part of this setup.