Confirm current files, checkpoints, package scripts, diff and port state before any activation or customer-facing claim.
- No stale handoff claim
- No unchecked diff
- No missing checkpoint reuse
- No dirty-file overwrite
Green claims need fresh proof, not memory.
This workspace turns RatingE release QA into an approval-ready runbook. It keeps disk truth, guard order, build proof, smoke proof, rollback notes and incident templates visible without deploying, changing routes, writing customer data, activating payments, syncing providers or sending messages.
Fresh evidence before every green claim
QA readiness is source-only. It prepares the evidence order and blocks live work until a separate owner approval exists for the exact runtime, route, customer data, payment and provider action.
- Operational QA runbook readiness workspace
- Fresh disk truth required before green claim
- Dedicated guards must run before full guard set
- Build must pass before smoke
- Runtime smoke evidence must be fresh
- Temporary server must be stopped
- Port 3068 must be clear after smoke
- Rollback note required before deploy approval
- Incident/postmortem template prepared only
- No deploy/runtime switch is triggered
- No DNS or routing change is made
- No Appwrite customer mutation is performed
- No payment activation is performed
- No provider sync/import/OAuth is performed
- No live messaging or outreach is sent
- No support ticket is created
Record the required audit order and evidence expectations before anyone treats RatingE as production-ready.
- No skipped dedicated guard
- No partial guard set
- No build skipped
- No smoke skipped
Local smoke must run against the exact temporary server and the server must be stopped after verification.
- No stale smoke result
- No remote smoke without approval
- No server left running
- Port 3068 must be clear
Keep rollback owner, previous runtime reference and restore notes visible before any future deploy window is approved.
- No deploy is started
- No runtime switch
- No DNS change
- No rollback command is run
Prepare the incident fields and postmortem evidence checklist without opening a ticket or notifying customers.
- No ticket is created
- No owner notification is sent
- No customer message is sent
- No support automation runs
Dedicated guard proof, full guard proof, build proof, smoke proof, server-stop proof and port-clear proof.
Previous runtime reference, owner, restore note, DNS no-change proof and rollback decision record.
Appwrite/customer mutation boundary, import approval note, customer data source and consent evidence checklist.
Payment disabled proof, provider OAuth/API disabled proof, sender readiness and policy checklist.
Escalation lane owner, support hours, incident note template and no-ticket/no-notification proof.
No live action from QA readiness
Operational QA does not trigger deploys, runtime switches, DNS or routing edits, Appwrite writes, customer imports, payment activation, provider sync/import/OAuth, API calls, support tickets, owner notifications, live messaging or customer outreach.