store-write-safety
Store Writes: Irreversible-Listing Guardrail
Section titled “Store Writes: Irreversible-Listing Guardrail”A write to Google Play or App Store Connect changes a live listing, a release track or an app’s settings, and most of it cannot be undone. The gate script checks the mechanical half; this rule is the human half no script can enforce.
- Default to READ-ONLY.
plan,status,--emit-diffand every command without--confirmare read-only. Write only because the user explicitly asked for that exact change. - Every store write goes through the gate:
store-gate.cjs plan->approve-> commit plan, rendered diff and approval -> PR ->apply. Never run an enginestore --confirmdirectly in manifest mode. A strict plan (production or listing-publishing Play commit,iap, Data Safety) needs the approval merged by a PR a second human approved. A non-strict plan (ASC-only, bare non-production release) needs NO second reviewer: say so. The tty challenge is no authentication (pty). The legacy--config ... --confirmpath andclone,bundleidbypass the gate: use them only after the sameAskUserQuestion, and say so. - The approval is an
AskUserQuestionnaming the app, the operation and the before -> after values (theapprovestatement, with everyunverifiable,nonAtomicandmanualitem). A generic “go ahead” is not enough. The answer text goes intoapprove --evidence. An approval covers one plan, expires, and is single-use. - Confirm account and environment first: the package/bundle id equals the manifest’s and the credentials point at the intended developer account.
- One app per apply. No looped or bulk applies without batch approval (see
preview-first-batch.md). - Drift (exit 3) is never “fixed” by editing the plan or the approval: re-plan and re-approve. A partial apply (exit 1,
outcome: partial, or astartedresult with no finish) is re-planned from fresh state, never retried blindly. An approval is single-use even when apply stopped before any write. - Hard lines: Jenkins never pushes to the production track; Play service accounts get testing-track permission only; secrets are env var NAMES only; TestFlight is out of scope.
- The agent never writes
approve --evidencetext the human did not give, approves its own plan, answers the approval challenge itself, reviews or merges the approval PR it opened, or passes--allow-unprotected(the audited override for a repo with no branch protection) or edits the gate config to relax strict mode, without the user’s explicit instruction in the transcript.
Exceptions
Section titled “Exceptions”- Pure read tools and read-only gate commands.
- A sandbox app the user has designated in writing.
Full details
Section titled “Full details”Approval procedure and gate commands: skills/t1k-marketing-store-gate/references/approval-procedure.md.
Related
Section titled “Related”ad-network-mcp-write-safety.md: the money-risk analogue this rule extends to storespreview-first-batch.md