OUTCOMES
What this Prompt helps you deliver
- Installable software and deployment are ready
- Acceptance, rollback, and operations material are complete
BEFORE YOU START
Before you start
- Features and brand are approved
- The customer environment and approver are known
What AI should inspect first
deploymentapps/tabtin-electronapps/tabtin-iosapps/tabtin-androiddocs/agent/electron-production-release-sop.mdREADY TO RUN
Complete Prompt
Copy the complete Prompt with its execution and acceptance boundaries.
Deliver my TabTin-based product so the customer can install, use, accept, back up, and later upgrade it—not receive a folder of build files. Read AGENTS.md, deployment, apps/tabtin-electron, apps/tabtin-ios, apps/tabtin-android, and docs/agent/electron-production-release-sop.md. Confirm version, environment, domain, migration, brand, clients, signing, approver, maintenance window, rollback, frozen scope, known issues, and exclusions.
From clean inputs build Web, backend, and required clients, recording version, commit source, and lock state. Complete signing, notarization, installers, service images, DB migration, and environment configuration; transfer secrets through a secure channel. Deploy near the customer environment, seed required data, and create the minimum administrator. Run automated acceptance and critical customer flows with evidence and approval. Prepare backup, restore, monitoring, incident contact, upgrade, and rollback playbooks and rehearse the handoff.
Verify clean install, existing upgrade, restart, first sign-in, core business loop, isolation, backup/restore, brand, domains, certificates, metadata, and redaction. Rehearse one safe rollback and data recovery. Report version/hash, addresses, installers, migrations, acceptance, backup, rollback, known issues, customer duties, and support boundary. Never put passwords/keys in normal documents; publishing, store upload, or push requires explicit approval.