A public launch-week update playbook for converting official GTA 6 source, store, spoiler, correction, distribution, product, and data changes into safe local actions.
Short answer: The launch-week update playbook is the public runbook for what to update first when GTA 6 evidence changes: capture the source, update the smallest supported claim, refresh affected routes and exports together, run npm run build && npm run validate, and stop before deploys, sends, posts, accounts, analytics, affiliates, or credentials unless explicitly approved.
Use this before editing source-sensitive pages, buyer guidance, spoiler guides, distribution drafts, public exports, or correction records. It is public and static; it does not perform the external work it names as approval-gated.
update affected page short answers and source verification tables
record the correction with reason and affected routes
rebuild generated exports and review llms.txt/site inventory references
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Blocked inputs: leaked assets; datamined files; private build screenshots; retailer placeholders as facts; unsourced social reposts; credential or browser-session data
Approval required for: production deploy; newsletter send; public/social post; analytics activation; sponsor/affiliate link; account login or API use; runtime/config/credential change
Rollback path: Revert or supersede the local export/content change, rebuild generated files, and add a corrections-log entry if readers or crawlers could have consumed the prior state.
criticalbuyer/editorial operations
Official store, platform store, Rockstar Support, or publisher page publishes preorder, edition, price, preload, file-size, rating, refund, or bonus details.
Evidence gate: Official store/support evidence must exist; affiliate, sponsor, or scarcity language remains blocked without approval.
keep retailer placeholders separate from official claims
update buyer safety copy and affected watchlist rows
check commercial disclosure text before any CTA changes
record correction or source-policy note if prior unknown labels changed
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Blocked inputs: leaked assets; datamined files; private build screenshots; retailer placeholders as facts; unsourced social reposts; credential or browser-session data
Approval required for: production deploy; newsletter send; public/social post; analytics activation; sponsor/affiliate link; account login or API use; runtime/config/credential change
Rollback path: Revert or supersede the local export/content change, rebuild generated files, and add a corrections-log entry if readers or crawlers could have consumed the prior state.
highguides/spoiler operations
Post-launch guide evidence becomes available for missions, trophies, story beats, map locations, activities, or completion routes.
Evidence gate: Use official/public launch evidence, direct verified capture, platform metadata, or reputable spoiler-controlled guide evidence; never leaked assets.
gate story names, hidden trophies, endings, and walkthrough details behind clear labels
reject non-public or leak-dependent materials
record source and correction impact if public guidance changes
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Blocked inputs: leaked assets; datamined files; private build screenshots; retailer placeholders as facts; unsourced social reposts; credential or browser-session data
Approval required for: production deploy; newsletter send; public/social post; analytics activation; sponsor/affiliate link; account login or API use; runtime/config/credential change
Rollback path: Revert or supersede the local export/content change, rebuild generated files, and add a corrections-log entry if readers or crawlers could have consumed the prior state.
criticalQA/corrections operations
Any existing confirmed, unknown, speculative, rejected, or product/RP label proves wrong, stale, or materially incomplete.
Evidence gate: Correction must include source trail, affected routes, reader impact, local actions, and rollback path.
refresh correction impact and source escalation exports
run validation before any external receipt or deploy claim
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Blocked inputs: leaked assets; datamined files; private build screenshots; retailer placeholders as facts; unsourced social reposts; credential or browser-session data
Approval required for: production deploy; newsletter send; public/social post; analytics activation; sponsor/affiliate link; account login or API use; runtime/config/credential change
Rollback path: Revert or supersede the local export/content change, rebuild generated files, and add a corrections-log entry if readers or crawlers could have consumed the prior state.
highdistribution operations
A local change appears alert-worthy for newsletter segments, Discord receipts, creator updates, or social channels.
Evidence gate: Local draft can be prepared, but external delivery, campaign sends, public posts, and account-connected automations require explicit approval.
remove spoilers from subject/preview text unless explicitly gated
confirm no private memory, credentials, cookies, or browser state appear
record the local artifact and verification result
stop before sending or posting unless approval exists
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Blocked inputs: leaked assets; datamined files; private build screenshots; retailer placeholders as facts; unsourced social reposts; credential or browser-session data
Approval required for: production deploy; newsletter send; public/social post; analytics activation; sponsor/affiliate link; account login or API use; runtime/config/credential change
Rollback path: Delete or supersede the local draft/artifact, correct the receipt if one overstated capability, and rebuild exports if public routing changed.
highproduct/data operations
A launch dashboard, planner, creator tool, source feed, map evidence board, social trust layer, or JSON export gains a new field or behavior.
Evidence gate: Product changes must preserve local-only behavior, source labels, no-leaks policy, and explicit approval boundaries.
advertise preferred data routes in answer-engine packet and llms.txt when crawler-facing
add validation for required fields or route presence
record artifact note when product direction, QA, source policy, or handoff changes
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Blocked inputs: leaked assets; datamined files; private build screenshots; retailer placeholders as facts; unsourced social reposts; credential or browser-session data
Approval required for: production deploy; newsletter send; public/social post; analytics activation; sponsor/affiliate link; account login or API use; runtime/config/credential change
Rollback path: Revert or supersede the local export/content change, rebuild generated files, and add a corrections-log entry if readers or crawlers could have consumed the prior state.
What it gives operators
A visible companion to /data/launch-week-update-playbook.json so future agents and editors can act without reading raw JSON first.
Six trigger lanes covering official date/platform changes, store/preorder evidence, spoiler-guide promotion, correction blast radius, distribution drafts, and product/data export changes.
Ordered local actions, affected routes, evidence gates, blocked inputs, verification gates, approval boundaries, and rollback paths on every row.
What it keeps blocked
Leaked assets, datamined files, private build screenshots, retailer placeholders as facts, unsourced social reposts, credential/session data, and unreviewed spoiler material.
Production deploys, newsletter sends, public or Discord/social posts, analytics activation, sponsor/affiliate links, account logins/API use, runtime/config changes, and credential work all remain explicit approval gates.
Playbook questions
Is this a live incident automation system?
No. It is a static local-safe runbook and JSON handoff. It does not monitor, deploy, send, post, subscribe, log in, scrape, or mutate external systems.
How should the next agent use it?
Pick the lane matching the evidence change, complete only the ordered local actions supported by the source, update public page and JSON exports together, run npm run build && npm run validate, then record a concise artifact and correction when reader-visible meaning changed.
No rumour spam: only official release/preorder/Online changes, launch guide updates, creator prompts, and RP tooling notes. Powered by Buttondown with an email fallback if the API is unavailable.
