Confirm true isolation
Record this project’s identifier, URL, backend identifier, and direct evidence that its database is separate from live Synvora’s fleet-toad-86 backend.
Synvora Staging is the separate environment for transferring the existing application, proving backend isolation, and completing security and subscription testing without exposing live data or services.
Access-restricted • production services disabled • promotion requires approval
Separate first
A different URL is never accepted as evidence of backend or database isolation.
Exact source
Revisions, dependencies, tests, fixtures, and security work remain traceable.
No live effects
Email, SMS, calls, models, and real payments stay off until separately approved.
Controlled transfer
The first deliverable is a factual separation and transfer report—not a replacement build and not another audit sprint.
Record this project’s identifier, URL, backend identifier, and direct evidence that its database is separate from live Synvora’s fleet-toad-86 backend.
Preserve the existing source, Convex schema and functions, assets, dependencies, tests, fixture work through e205cac, and prerequisite revisions.
Carry both recent authorization-security states and reports forward, then reconcile omitted handler and test changes before calling the patch complete.
No live users, customer records, secrets, payment products, webhooks, provider credentials, production domains, or database synchronization.
Access
This environment is operational infrastructure for authorized Synvora testing. There are no public subscription tiers or fabricated launch offers.
For approved owners, support staff, and reviewers completing the source transfer and acceptance checks.
Boundaries
Next concrete step
Begin with this project’s identifiers and backend evidence. If MadeThis cannot transfer the source directly, prepare the exact destination-specific request for Jacob and stop there.