LiveOps Content Rollout and Rollback
Overview
Provide an evidence-first contract for live content rollout, cohort, canary, configuration, dependencies, monitoring, approvals, rollback triggers, recovery, and verification.
When to use
Use only for the trigger conditions in the description and when the requested artifact needs explicit owners, evidence, limitations, and verification.
When NOT to use
Do not use as incident response after an outage or to publish without approval.
Required inputs and context discovery
Collect exact project and build identity, requested scope, owners, dependencies, constraints, existing evidence, commands, artifact paths, risks, approvals, rollback or recovery, and unavailable information.
Safety and risk level
Risk level is high. Read-only review never authorizes mutation. Any load, rollout, publication, service, database, credential, or external-system action requires explicit human approval and bounded stop conditions.
Workflow
- Bind content identity, dependencies, environment, owner, approvals, and player impact.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Define cohort, canary stages, timing, compatibility, migration, and configuration controls.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Specify dashboards, guardrails, stop conditions, rollback triggers, and decision authority.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Verify rollback artifacts, data recovery, cache behavior, support, and communication drafts.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Produce a reviewed plan; execution remains blocked until explicit human authorization.
Completion criterion: evidence is recorded and unresolved items are explicit.
Evidence and output contract
Produce liveops-rollout-plan.json with scope, snapshot, findings, owners, commands and exit codes, artifacts, acceptance criteria, Verified facts, Snapshot assumptions, Unverified hypotheses, BLOCKED items, and next actions.
Handoff contract
Record repository and path, goal, owned scope, do-not-touch scope, decisions, files changed, commands, exit codes, artifacts, restore information, blockers, next owner, and reactivation prompt.
Pitfalls and anti-rationalization
- Missing evidence is
BLOCKED, never PASS.
- A plan or review does not authorize production execution.
- Compile success, screenshots, or anecdotes do not prove broader coverage.
- Preserve unrelated work and generated-source ownership.
Verification checklist
References and scripts
No bundled runtime helper is required. Use project-owned plans, evidence, runbooks, schemas, and validation commands; repository governance tools remain full-clone-only.
1---2name: liveops-content-rollout-and-rollback3description: Use when a live game content update needs a governed rollout and rollback plan across cohort, canary, configuration, dependencies, monitoring, approvals, triggers, recovery, communication, and post-rollout verification; not for incident response after failure.4license: MIT5---6# LiveOps Content Rollout and Rollback78## Overview9Provide an evidence-first contract for live content rollout, cohort, canary, configuration, dependencies, monitoring, approvals, rollback triggers, recovery, and verification.1011## When to use12Use only for the trigger conditions in the description and when the requested artifact needs explicit owners, evidence, limitations, and verification.1314## When NOT to use15Do not use as incident response after an outage or to publish without approval.1617## Required inputs and context discovery18Collect exact project and build identity, requested scope, owners, dependencies, constraints, existing evidence, commands, artifact paths, risks, approvals, rollback or recovery, and unavailable information.1920## Safety and risk level21Risk level is `high`. Read-only review never authorizes mutation. Any load, rollout, publication, service, database, credential, or external-system action requires explicit human approval and bounded stop conditions.2223## Workflow241. Bind content identity, dependencies, environment, owner, approvals, and player impact.25 Completion criterion: evidence is recorded and unresolved items are explicit.262. Define cohort, canary stages, timing, compatibility, migration, and configuration controls.27 Completion criterion: evidence is recorded and unresolved items are explicit.283. Specify dashboards, guardrails, stop conditions, rollback triggers, and decision authority.29 Completion criterion: evidence is recorded and unresolved items are explicit.304. Verify rollback artifacts, data recovery, cache behavior, support, and communication drafts.31 Completion criterion: evidence is recorded and unresolved items are explicit.325. Produce a reviewed plan; execution remains blocked until explicit human authorization.33 Completion criterion: evidence is recorded and unresolved items are explicit.3435## Evidence and output contract36Produce `liveops-rollout-plan.json` with scope, snapshot, findings, owners, commands and exit codes, artifacts, acceptance criteria, Verified facts, Snapshot assumptions, Unverified hypotheses, BLOCKED items, and next actions.3738## Handoff contract39Record repository and path, goal, owned scope, do-not-touch scope, decisions, files changed, commands, exit codes, artifacts, restore information, blockers, next owner, and reactivation prompt.4041## Pitfalls and anti-rationalization42- Missing evidence is `BLOCKED`, never PASS.43- A plan or review does not authorize production execution.44- Compile success, screenshots, or anecdotes do not prove broader coverage.45- Preserve unrelated work and generated-source ownership.4647## Verification checklist48- [ ] Scope, identity, owners, and exclusions are explicit.49- [ ] Every verdict cites observed evidence or is labeled Unverified/BLOCKED.50- [ ] Risks have mitigations, triggers, owners, and dates.51- [ ] No unauthorized mutation, publication, deployment, or destructive action occurred.52- [ ] Handoff names the next bounded action.5354## References and scripts55No bundled runtime helper is required. Use project-owned plans, evidence, runbooks, schemas, and validation commands; repository governance tools remain full-clone-only.
hoatv2211