criticalcontent-freshness-sla
Official store, rating-board, support, refund, edition, bonus, price, preload, or platform metadata appears or changes.
Owner: buyer safety · Status: watch-for-stale-copy
Next local action: Official store, rating-board, support, refund, edition, bonus, price, preload, or platform metadata appears or changes.
Evidence gate: Use the platform/store/source router first; keep price, edition, preload, and affiliate copy out until official evidence and disclosure rules are present.
Affected routes: /buying-guide/ /blog/gta-6-preorder-editions-watchlist/ /newsletter/ /data/platform-store-source-router.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: retailer placeholders as facts; fake edition tables; affiliate urgency copy; unverified screenshots; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
criticalcontent-freshness-sla
Any newer official date, platform, delay, store, or support signal changes the current launch answer or platform availability.
Owner: source operations · Status: watch-for-stale-copy
Next local action: Any newer official date, platform, delay, store, or support signal changes the current launch answer or platform availability.
Evidence gate: Rockstar, Take-Two, official platform-store, Rockstar Support, or launcher page must be reviewed; facts, timeline, FAQ/search, corrections log, sitemap/feed, and answer-engine packet must be regenerated together.
Affected routes: /release-date/ /timeline/ /confirmed-vs-rumoured/ /faq/ /data/facts.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks; newsletter campaign sends
Blocked inputs: retailer placeholder dates; influencer date claims; screenshots without public official URLs; leaked schedules; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
criticallaunch-preflight
Buyer and monetisation safety
Owner: commercial/editorial · Status: local-ready / activation-gated
Next local action: No invented preorder tables, fake scarcity, unsupported prices, or implied Rockstar approval.
Evidence gate: No invented preorder tables, fake scarcity, unsupported prices, or implied Rockstar approval. Affiliate/sponsor surfaces have production-safe disclosure rules, partner-fit criteria, rejection rules, and aggregate-only measurement language. Live partner links, affiliate redirects, outreach, public sends, provider changes, and commercial claims remain activation-gated until David approves the exact partner and destination.
Affected routes: /deployment-readiness/ /launch-command-center/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: unreviewed public copy; unverified commercial claims; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
criticallaunch-preflight
Editorial/legal read-through
Owner: editorial/legal · Status: required before public push
Next local action: Read homepage, release date, PC, preorder, Online, Jason/Lucia, Trailer 2, map, vehicles, features, source policy, and buying-guide pages in one sitting.
Evidence gate: Read homepage, release date, PC, preorder, Online, Jason/Lucia, Trailer 2, map, vehicles, features, source policy, and buying-guide pages in one sitting. Confirm every lead answer uses an approved status label. Confirm no leaked footage, private docs, datamined UI, extracted files, or fake complete lists are embedded, quoted, or required.
Affected routes: /deployment-readiness/ /launch-command-center/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: unreviewed public copy; unverified commercial claims; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
criticallaunch-preflight
Production smoke gate
Owner: engineering/operator · Status: required after deploy
Next local action: Run npm run verify:production immediately after deploy/DNS/API/Worker changes.
Evidence gate: Run npm run verify:production immediately after deploy/DNS/API/Worker changes. Smoke apex, www, sitemap, robots, search index, CSS/JS, 404, newsletter endpoint, analytics endpoint, release date, PC, preorder, Online, source policy, and newsletter. If smoke fails, pause promotion, capture failing URL/status, rollback or fix with approval where needed, and rerun smoke.
Affected routes: /deployment-readiness/ /launch-command-center/
Verification, approvals, rollback
Verification gates: npm run verify:production
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: unreviewed public copy; unverified commercial claims; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
criticallaunch-preflight
Source-change receipt gate
Owner: source editor/operator · Status: required before promotion
Next local action: For any official source change, record a durable receipt with source URL, exact changed wording, reviewed timestamp, affected routes, exported data, correction entry, verification output, screenshot/artifact path, approval boundary, and rollback note.
Evidence gate: For any official source change, record a durable receipt with source URL, exact changed wording, reviewed timestamp, affected routes, exported data, correction entry, verification output, screenshot/artifact path, approval boundary, and rollback note. Update every affected route and export named by the launch decision matrix or source update workbench before changing metadata, FAQ answers, newsletter copy, or answer-engine packets. Do not promote from memory, social reposts, screenshots, or a single-page edit; source-driven changes require the receipt plus npm run build && npm run validate before public promotion.
Affected routes: /deployment-readiness/ /launch-command-center/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: unreviewed public copy; unverified commercial claims; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
criticallaunch-preflight
Technical local gate
Owner: engineering · Status: required before deploy
Next local action: Run npm run verify:all before public push.
Evidence gate: Run npm run verify:all before public push. Review visual QA summary and inspect changed desktop/mobile screenshots. Confirm sitemap, robots, feed, llms.txt, data exports, social metadata, and canonical URLs are generated.
Affected routes: /deployment-readiness/ /launch-command-center/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: unreviewed public copy; unverified commercial claims; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
criticalsource-review-queue
Rejected for hub use; do not host, summarize private documents, or rely on leaked/extracted assets.
Owner: source operations · Status: reject
Next local action: Rejected for hub use; do not host, summarize private documents, or rely on leaked/extracted assets.
Evidence gate: Do not promote. Keep this source class rejected unless a future official/public evidence policy supersedes it.
Affected routes: n/a
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
criticalsource-review-queue
Do not promote pricing, editions, timelines, or expected bonuses from third-party speculation.
Owner: source operations · Status: untrusted-discovery-only
Next local action: Do not promote pricing, editions, timelines, or expected bonuses from third-party speculation.
Evidence gate: Do not promote. Keep this source class rejected unless a future official/public evidence policy supersedes it.
Affected routes: public search results
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
criticalsource-review-queue
Official store, rating-board, support, refund, edition, bonus, price, preload, or platform metadata appears or changes.
Owner: source operations · Status: scheduled-review
Next local action: Official store, rating-board, support, refund, edition, bonus, price, preload, or platform metadata appears or changes.
Evidence gate: Use the platform/store/source router first; keep price, edition, preload, and affiliate copy out until official evidence and disclosure rules are present.
Affected routes: /buying-guide/ /blog/gta-6-preorder-editions-watchlist/ /newsletter/ /data/platform-store-source-router.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: retailer placeholders as facts; fake edition tables; affiliate urgency copy; unverified screenshots; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
criticalsource-review-queue
Any newer official date, platform, delay, store, or support signal changes the current launch answer or platform availability.
Owner: source operations · Status: scheduled-review
Next local action: Any newer official date, platform, delay, store, or support signal changes the current launch answer or platform availability.
Evidence gate: Rockstar, Take-Two, official platform-store, Rockstar Support, or launcher page must be reviewed; facts, timeline, FAQ/search, corrections log, sitemap/feed, and answer-engine packet must be regenerated together.
Affected routes: /release-date/ /timeline/ /confirmed-vs-rumoured/ /faq/ /data/facts.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: retailer placeholder dates; influencer date claims; screenshots without public official URLs; leaked schedules; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance keep affiliate, sponsor, purchase, and retailer copy approval-gated
Affected routes: /blog/gta-6-accessibility-options-watchlist/ /accessibility-evidence-router/ /buying-guide/ /launch-checklist/ /blog/gta-6-parent-guide-age-rating-watchlist/ /post-launch-verification-lab/ /data/accessibility-evidence-checklist.json /data/accessibility-buyer-decision-matrix.json /data/answer-engine-packet.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks; affiliate links, sponsor copy, or purchase CTAs
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance
Affected routes: /blog/gta-6-account-linking-login-security-watchlist/ /blog/gta-6-early-access-beta-review-embargo-watchlist/ /blog/gta-6-mobile-apk-download-watchlist/ /blog/gta-6-server-status-online-error-code-watchlist/ /platform-store-source-router/ /server-status-source-router/ /reader-action-router/ /data/account-security-evidence-matrix.json /data/answer-engine-packet.json /data/site-inventory.json /data/product-feature-suite.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance
Affected routes: /blog/gta-6-activities-minigames-sports-fishing-watchlist/ /guides/ /features/ /map/ /blog/gta-6-collectibles-100-percent-completion-watchlist/ /blog/gta-6-interiors-enterable-buildings-businesses-watchlist/ /blog/gta-6-wildlife-animals-watchlist/ /blog/gta-6-money-businesses-properties-watchlist/ /data/blog-posts.json /data/query-to-page-map.json /data/search-index.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance
Affected routes: /blog/ /data/article-safe-answer-strips.json /data/answer-engine-packet.json /data/site-inventory.json /llms.txt /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance keep affiliate, sponsor, purchase, and retailer copy approval-gated
Affected routes: /blog/gta-6-controller-keyboard-mouse-steering-wheel-vr-accessory-watchlist/ /buying-guide/ /platform-planner/ /blog/gta-6-ps5-vs-xbox-pc-switch-2-platform-buying-watchlist/ /blog/gta-6-accessibility-options-watchlist/ /blog/gta-6-console-performance-60fps-ps5-pro-watchlist/ /blog/gta-6-cloud-gaming-remote-play-handheld-streaming-watchlist/ /creator-toolkit/ /data/blog-posts.json /data/query-to-page-map.json /data/article-search-intent-packets.json /data/article-share-packets.json /data/search-index.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks; affiliate links, sponsor copy, or purchase CTAs
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance keep affiliate, sponsor, purchase, and retailer copy approval-gated
Affected routes: /blog/gta-6-controller-keyboard-mouse-steering-wheel-vr-accessory-watchlist/ /buying-guide/ /platform-planner/ /blog/gta-6-accessibility-options-watchlist/ /blog/gta-6-cloud-gaming-remote-play-handheld-streaming-watchlist/ /blog/gta-6-photo-mode-rockstar-editor-capture-tools-watchlist/ /blog/gta-6-voice-chat-text-chat-moderation-privacy-watchlist/ /data/controller-accessory-evidence-matrix.json /data/answer-engine-packet.json /data/site-inventory.json /data/product-feature-suite.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks; affiliate links, sponsor copy, or purchase CTAs
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance
Affected routes: /internal-link-opportunities/ /data/internal-link-opportunities.json /data/answer-engine-packet.json /data/site-inventory.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance keep affiliate, sponsor, purchase, and retailer copy approval-gated
Affected routes: /blog/is-gta-6-coming-to-pc/ /blog/gta-6-preorder-editions-watchlist/ /blog/gta-6-online-watchlist/ /buying-guide/ /online/ /release-date/ /platform-planner/ /preorder-safety-centre/ /reader-action-router/ /data/blog-posts.json /data/article-search-intent-packets.json /data/article-share-packets.json /data/search-index.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks; affiliate links, sponsor copy, or purchase CTAs
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance
Affected routes: /reader-action-router/ /data/reader-action-router.json /data/reader-action-receipt-packets.json /data/answer-engine-packet.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance
Affected routes: /blog/gta-6-story-character-switching-coop-watchlist/ /characters/ /blog/who-is-lucia/ /blog/who-is-jason/ /blog/gta-6-mission-walkthrough-spoiler-safe-guide/ /spoiler-source-router/ /spoiler-policy/ /post-launch-verification-lab/ /data/story-character-structure-evidence-matrix.json /data/answer-engine-packet.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance
Affected routes: /blog/gta-6-voice-chat-text-chat-moderation-privacy-watchlist/ /data/voice-chat-safety-evidence-matrix.json /data/article-search-intent-packets.json /data/article-share-packets.json /data/answer-engine-packet.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcorrection-impact-router
Reader-facing route copy, labels, internal links, or CTAs may need review before promotion.
Owner: editorial/source operations · Status: published
Next local action: confirm the correction summary, reason, affected routes, and source status remain accurate
Evidence gate: confirm the correction summary, reason, affected routes, and source status remain accurate rebuild generated HTML, JSON exports, sitemap, robots, feed, and llms.txt verify affected data exports parse as JSON and are listed in site inventory when crawler-facing check source-policy, official-source, answer-engine, and llms.txt references for stale guidance
Affected routes: /blog/gta-6-weather-hurricanes-water-physics-watchlist/ /map/ /features/ /vehicles/ /blog/gta-6-map-size-rumours-explained/ /blog/gta-6-vehicles-cars-customization-watchlist/ /blog/gta-6-photo-mode-rockstar-editor-capture-tools-watchlist/ /blog/gta-6-wildlife-animals-watchlist/ /post-launch-verification-lab/ /data/weather-environment-evidence-matrix.json /data/answer-engine-packet.json /data/site-inventory.json /data/product-feature-suite.json /data/corrections-log.json
Verification, approvals, rollback
Verification gates: npm run build && npm run validate; npm run verify:sources; run visual/editorial QA on affected reader-facing routes when layout or copy changed
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Revert or supersede the affected local copy/export change, add a new corrections-log entry if readers already saw the old state, then rebuild and validate before promotion.
highcontent-freshness-sla
Any canonical route, source rule, correction policy, reader action, crawl priority, or data export contract changes.
Owner: SEO/AEO · Status: watch-for-stale-copy
Next local action: Any canonical route, source rule, correction policy, reader action, crawl priority, or data export contract changes.
Evidence gate: Regenerate all JSON exports and llms.txt in the same build; validate JSON parseability, inventory presence, and no-leaks policy references.
Affected routes: /data/answer-engine-packet.json /data/query-to-page-map.json /data/reader-action-router.json /data/content-freshness-sla.json /llms.txt /site-inventory/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: stale generated JSON; manual edits to dist exports without source update; missing correction route after material claim changes; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
highcontent-freshness-sla
Official gameplay footage, screenshots, support docs, platform metadata, or verified released-game testing changes a guide/database answer.
Owner: editorial/database · Status: watch-for-stale-copy
Next local action: Official gameplay footage, screenshots, support docs, platform metadata, or verified released-game testing changes a guide/database answer.
Evidence gate: Update source labels first, then database rows, guide pages, search index, image sitemap where relevant, and corrections log when reader-facing claims change.
Affected routes: /guides/ /spoiler-policy/ /vehicles/ /features/ /map/ /map-claim-ledger/ /blog/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked maps; datamined rosters; private trophy lists; AI-generated feature tables; unsourced full species or vehicle lists; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
highcontent-freshness-sla
Rockstar publishes Online, GTA+, crossplay, transfer, creator-tool, policy, server, or support details.
Owner: community/product · Status: watch-for-stale-copy
Next local action: Rockstar publishes Online, GTA+, crossplay, transfer, creator-tool, policy, server, or support details.
Evidence gate: Separate official Online facts from independent RP product analysis; update feature records, FAQ, source monitor, and correction impact routes before promotion.
Affected routes: /online/ /rp/ /features/ /blog/gta-6-online-watchlist/ /blog/gta-6-modding-fivem-roleplay-watchlist/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: paid compatibility promises; private server access claims; mod menu rumours; leaked Online footage; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
highlaunch-preflight
RP/product boundary
Owner: product/editorial · Status: source-safe
Next local action: RP tools stay game-agnostic.
Evidence gate: RP tools stay game-agnostic. No promise of GTA 6 Online compatibility, server access, official integration, or mod support. Design-partner messaging stays product-discovery only until explicitly approved.
Affected routes: /deployment-readiness/ /launch-command-center/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: unreviewed public copy; unverified commercial claims; leaked assets
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
highsource-review-queue
Use the accessibility decision layer to route assistive-needs, buying, launch-checklist, and source-policy decisions without promoting unconfirmed settings or leaked settings screens.
Owner: source operations · Status: watchlist-gap
Next local action: Use the accessibility decision layer to route assistive-needs, buying, launch-checklist, and source-policy decisions without promoting unconfirmed settings or leaked settings screens.
Evidence gate: Promote only after a public official source exists and the affected route, source coverage ledger, correction log, and answer-engine exports are regenerated together.
Affected routes: /blog/gta-6-accessibility-options-watchlist/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
highsource-review-queue
No preorder/edition details promoted; keep buyer-intent pages as official gaps until official store/pages exist.
Owner: source operations · Status: watchlist-gap
Next local action: No preorder/edition details promoted; keep buyer-intent pages as official gaps until official store/pages exist.
Evidence gate: Promote only after a public official source exists and the affected route, source coverage ledger, correction log, and answer-engine exports are regenerated together.
Affected routes: https://www.rockstargames.com/newswire/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
highsource-review-queue
Use support/launcher evidence for PC requirements, preload, accessibility, account, or technical setup only after a GTA VI-specific public support page exists.
Owner: source operations · Status: watchlist-gap
Next local action: Use support/launcher evidence for PC requirements, preload, accessibility, account, or technical setup only after a GTA VI-specific public support page exists.
Evidence gate: Promote only after a public official source exists and the affected route, source coverage ledger, correction log, and answer-engine exports are regenerated together.
Affected routes: /blog/is-gta-6-coming-to-pc/
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
highsource-review-queue
May seed FAQs and watchlist questions; requires primary-source confirmation before factual promotion.
Owner: source operations · Status: watchlist-only
Next local action: May seed FAQs and watchlist questions; requires primary-source confirmation before factual promotion.
Evidence gate: Promote only after a public official source exists and the affected route, source coverage ledger, correction log, and answer-engine exports are regenerated together.
Affected routes: n/a
Verification, approvals, rollback
Verification gates: npm run build && npm run validate
Approval required for: production deploy; public posts or social announcements; external alerts/webhooks
Blocked inputs: leaked assets; private build screenshots; datamined files; retailer placeholders as facts; unsourced social reposts
Rollback path: Keep the current static route and data export unchanged, record any material correction, rebuild, and rerun npm run build && npm run validate before promotion.
