5-Night February Fest Live Ops Pager Duty Challenge - 2026

February fest night three: #playtest reports a menu crash, hour-one funnel routed YELLOW, moderators escalated L1, and the engineer answered Discord until 2 a.m. without updating BUILD_RECEIPT. Morning stand-up asks whether demo_smoke_ok still matches the binary players downloaded—and whether fest_live_moderation_ok covered last night’s handoffs.

February 2027 live week needs pager accountability, not heroics. 7-day RC smoke challenge proved pre-live discipline; live week timebox capped hours; moderation tools named facilitators—this Challenges & Community Hooks sprint is the five-night pager ladder: ~20 minutes per fest evening, gates P1–P5, file february_live_ops_challenge_receipt_v1.json, hashtag #FebruaryLiveOps2027.

Non-repetition note: 7-day RC challenge owns C1–C7 pre-live RC week. 3-day Addressables challenge owns F1–F6 CI false-green. This URL owns five live fest nights of pager BUILD_RECEIPT diffs—cousin format, different gates and receipt schema.

Pair February timebox, hour-one funnel, moderation listicle, forward blog #5 setlive mismatch case study, Course 278 forward.

Why this matters now (February 2027 live week)

1. Crashes spike at night — Players cluster in evening hours; pager lane needs a ritual, not ad-hoc threads.
2. BUILD_RECEIPT drifts without diffs — *_ok booleans go stale while Discord argues.
3. Community ≠ pager — Timebox separates lanes; challenge enforces pager-only nightly truth.
4. HOTFIX temptation — HOTFIX exception opinion (blog #10 forward) needs receipt evidence before setlive.
5. Public accountability — #FebruaryLiveOps2027 posts catch skipped nights before Sunday closeout.

Direct answer: Five fest evenings (~20 min each); gates P1–P5; artifacts under release-evidence/february-live/challenge-2027/; file february_live_ops_challenge_receipt_v1.json; set BUILD_RECEIPT february_live_ops_challenge_ok: true when P5 passes.

Who this challenge is for

Prerequisites: Live week timebox filed; moderation receipt M1–M6 GREEN; fest D1 open or scheduled.
Time: ~1.5–2 hours total over five nights.

Challenge vs cousin ladders (format ladder)

Order: RC challenge complete → timebox + moderation preflight → fest opens → this 5-night pager ladder on D1–D5 (extend to D7 if hotfix cadence demands—document extension in receipt).

Rules of the challenge

1. One pager owner signs each night (night_N_owner in receipt).
2. Fail stops HOTFIX — RED P3 blocks setlive until smoke reruns (Wednesday smoke).
3. Twenty-minute cap — Ritual is diff + stand-up post, not full repro (repro lives in pager cap hours).
4. Post nightly with #FebruaryLiveOps2027.
5. Community facilitators do not sign pager nights—roster escalation_contact only.
6. HOTFIX requires HOTFIX exception list entry ID in night JSON when hotfix_considered: true.
7. Producer reviews P5 capstone before D6 feature work.

Five-night calendar at a glance

Nights N1–N5 map to fest D1–D5 by default—if your fest opens mid-week, shift labels but keep gate order.

Before you start — readiness checklist

• [ ] release-evidence/february-live/challenge-2027/ folder exists
• [ ] February timebox receipt fest_live_timebox_ok: true
• [ ] Moderation receipt fest_live_moderation_ok: true
• [ ] Pager owner named in facilitator roster
• [ ] #FebruaryLiveOps2027 channel or public thread chosen
• [ ] RC label receipt GREEN
• [ ] Producer agrees: no HOTFIX without nightly P2–P3 GREEN when crashes reported
• [ ] jq installed for diff helpers

Night 1 — P1 live-open latch (~20 minutes)

Goal: Prove pre-live cluster #1–#3 evidence valid at fest open.

Stand-up script:

## #FebruaryLiveOps2027 — Night 1 (D1 open)

- P1 latch: timebox + moderation GREEN
- build_label: fest-demo-2027-02-rc1
- funnel D1: filed / pending (honest)
- pager owner: @engineer
- HOTFIX: none tonight

Night 2 — P2 pager column diff (~20 minutes)

Goal: Diff pager-critical BUILD_RECEIPT columns vs prior night snapshot.

cp BUILD_RECEIPT.json release-evidence/february-live/challenge-2027/night-1-BUILD_RECEIPT.snapshot.json
# next night
diff -u night-1-BUILD_RECEIPT.snapshot.json BUILD_RECEIPT.json | tee night-2-row-diff.txt
jq -s '
  .[0] as $a | .[1] as $b |
  ["demo_smoke_ok","build_label","hour_one_funnel_snapshot_ok","fest_live_moderation_ok"] |
  map({key: ., was: $a[.], now: $b[.]}) |
  map(select(.was != .now))
' night-1-BUILD_RECEIPT.snapshot.json BUILD_RECEIPT.json

File night-2-row-diff.txt as P2 evidence.

Night 3 — P3 mid-fest smoke (~20 minutes + smoke time)

Goal: Run Wednesday smoke on installed build—not Editor.

If P3 RED, moderators use T1 template only (moderation listicle) until rerun GREEN.

Night 4 — P4 funnel + moderation crosswalk (~20 minutes)

Goal: Prove analytics and community receipts align with pager truth.

jq -e '
  .hour_one_funnel_snapshot_ok == true and
  .fest_live_moderation_ok == true
' BUILD_RECEIPT.json

jq -e '.prior_day_diff.hour_one_quit_rate_delta' \
  release-evidence/analytics/HOUR_ONE_FUNNEL_SNAPSHOT_RECEIPT.json

Pair hour-one funnel routing RED/YELLOW/GREEN table.

Night 5 — P5 challenge capstone (~20 minutes)

Goal: File master receipt and set BUILD_RECEIPT challenge flag.

{
  "schema": "february_live_ops_challenge_receipt_v1",
  "fest_window": "2027-02-next-fest-live",
  "hashtag": "#FebruaryLiveOps2027",
  "nights": [
    {"night": 1, "fest_day": "D1", "gate": "P1", "owner": "engineer", "pass": true},
    {"night": 2, "fest_day": "D2", "gate": "P2", "owner": "engineer", "pass": true},
    {"night": 3, "fest_day": "D3", "gate": "P3", "owner": "engineer", "pass": true},
    {"night": 4, "fest_day": "D4", "gate": "P4", "owner": "engineer", "pass": true},
    {"night": 5, "fest_day": "D5", "gate": "P5", "owner": "producer", "pass": true}
  ],
  "evidence_dir": "release-evidence/february-live/challenge-2027/",
  "february_live_ops_challenge_ok": true
}

BUILD_RECEIPT:

{
  "february_live_ops_challenge_ok": true,
  "february_live_ops_challenge_receipt": "release-evidence/february-live/FEBRUARY_LIVE_OPS_CHALLENGE_RECEIPT.json"
}

verify_february_live_ops_challenge.sh

#!/usr/bin/env bash
set -euo pipefail
REC="${1:-release-evidence/february-live/FEBRUARY_LIVE_OPS_CHALLENGE_RECEIPT.json}"

jq -e '.schema == "february_live_ops_challenge_receipt_v1"' "$REC" || exit 1
jq -e '(.nights | length) == 5' "$REC" || exit 2
jq -e '[.nights[].pass] | all' "$REC" || exit 3
jq -e '.february_live_ops_challenge_ok == true' "$REC" || exit 5
echo "february_live_ops_challenge verify: OK"

Developer path — gates P1–P5 summary

Proof table

Scenarios A–G

A — Solo founder pager
Owner signs all nights; community contractor signs mod handoffs only—valid if roster documents split.

B — D2 crash before P3
Run smoke early; P3 moves to D2 night if RED—document schedule_shift in receipt.

C — Funnel YELLOW, community wants ETA
P4 blocks HOTFIX promise; moderators stay on T1 template.

D — HOTFIX merged on D3
Re-run P2–P3 same night with new build_label; do not edit prior night JSON in place.

E — No public social account
Post #FebruaryLiveOps2027 to private #fest-ops—hashtag still required for search discipline.

F — RC challenge incomplete
Do not start N1—finish 7-day RC first.

G — Fest ends D7
Extend nights 6–7 optional; P5 capstone can cover D5 only if producer documents shortened ladder.

Integration with timebox pager cap

Common mistakes

Pager answering Discord all night — Violates timebox; challenge is 20 min receipt, not marathons.

Skipping N2 diff — build_label drift undetected until setlive mismatch (blog #5).

Editor smoke on N3 — P3 fails; players do not run Editor.

Community owner signing pager nights — Invalid sign-off; breaks lane separation.

Printable nightly pager card (pin in #fest-ops)

# February live ops pager — Night _N_ (fest D_N_)

- [ ] P_ gate ritual complete (20 min max)
- [ ] BUILD_RECEIPT snapshot saved to challenge-2027/
- [ ] row_diff reviewed (P2 nights)
- [ ] demo_smoke_ok matches installed binary (P3)
- [ ] funnel + mod paths valid (P4)
- [ ] #FebruaryLiveOps2027 post published
- [ ] HOTFIX: none / HOTFIX-00_ documented
- pager owner sign-off: ___________

PowerShell verify cousin

$rec = Get-Content "release-evidence/february-live/FEBRUARY_LIVE_OPS_CHALLENGE_RECEIPT.json" | ConvertFrom-Json
if ($rec.schema -ne "february_live_ops_challenge_receipt_v1") { exit 1 }
if ($rec.nights.Count -ne 5) { exit 2 }
if ($rec.nights | Where-Object { -not $_.pass }) { exit 3 }
if (-not $rec.february_live_ops_challenge_ok) { exit 5 }
Write-Host "february_live_ops_challenge verify: OK"

BUILD_RECEIPT column catalog (pager nights)

Thursday row review mid-fest can reuse P2 diff format—cousin ritual, weekly cadence.

Nightly jq pack (copy-paste)

# P1 latch
jq '{timebox:.fest_live_timebox_ok, mod:.fest_live_moderation_ok, funnel:.hour_one_funnel_snapshot_ok}' BUILD_RECEIPT.json

# P2 drift detector (pager columns only)
PAGER_COLS='["demo_smoke_ok","build_label","hour_one_funnel_snapshot_ok","fest_live_moderation_ok","fest_live_timebox_ok"]'
jq -s --argjson cols "$PAGER_COLS" '
  .[0] as $a | .[1] as $b |
  [$cols[] | {key: ., was: $a[.], now: $b[.]} | select(.was != .now)]
' night-1-BUILD_RECEIPT.snapshot.json BUILD_RECEIPT.json

# P5 capstone boolean
jq -e '.february_live_ops_challenge_ok == true' BUILD_RECEIPT.json

Engine-specific pager notes (N3 smoke)

Community hook templates (#FebruaryLiveOps2027)

Night 2/5 #FebruaryLiveOps2027 — D2 pager diff GREEN. build_label unchanged. funnel YELLOW (+0.06 quit delta). HOTFIX hold until P3 smoke.

Night 5/5 #FebruaryLiveOps2027 — P5 capstone filed. february_live_ops_challenge_ok true. D6 community cap resumes per timebox.

Rule: Posts state gates, not feature promises—moderation templates own player-facing tone.

Comparison pack (challenge receipts)

Related GamineAI reads

• 7-day February RC smoke challenge
• February live week timebox
• 14 moderation tools
• Hour-one funnel snapshot
• Wednesday demo smoke
• Thursday row review
• Forward: setlive mismatch case study (blog #5)

Key takeaways

1. Live fest pager needs five nightly ~20-minute BUILD_RECEIPT rituals—not hero Discord marathons.
2. february_live_ops_challenge_receipt_v1.json gates P1–P5 across fest nights N1–N5.
3. #FebruaryLiveOps2027 adds public accountability without promising features.
4. P2 diff catches build_label drift before HOTFIX.
5. P3 smoke requires installed binary—cousin Wednesday smoke.
6. P4 crosswalk pairs funnel routing with moderation templates.
7. 7-day RC challenge is pre-live cousin—run before N1.
8. Pair cluster #1–#3 receipts as P1 latch.
9. verify_february_live_ops_challenge.sh gives CI one exit code.
10. Course 278 forward owns BUILD_RECEIPT milestone; this owns five-night ladder.
11. setlive mismatch case study when P2 shows label drift.
12. Sunday closeout row review indexes P5 sign-off in C3—#11 consumed.

Producer sign-off block (P5 attachment)

## February live ops challenge sign-off

- Receipt path: release-evidence/february-live/FEBRUARY_LIVE_OPS_CHALLENGE_RECEIPT.json
- Nights P1–P5: all pass true
- Open HOTFIX exceptions: none / HOTFIX-002 only
- D6 feature work: allowed / hold until Sunday closeout
- Producer: ___________  Date: ___________

Attach to Sunday closeout row review evidence folder (blog #11 forward).

Extended FAQ

Can N1 happen before fest hour one?
Yes—P1 latch should complete before store traffic spikes; funnel D1 row may be pending with documented ETA in stand-up.

Does P4 require GREEN funnel?
P4 requires filed funnel receipt and honest routing band—YELLOW is valid; RED blocks HOTFIX promises.

How does this interact with refund dashboard?
Refunds lag funnel; P4 notes funnel band for producer, not refund CSV—pair refund dashboard on D6+.

What if we skip a night?
Challenge fails P5—document night_skipped waiver with producer ID or restart ladder from failed night.

Is Course 278 required?
Forward reference only—challenge receipt satisfies micro-studio stand-ups without course enrollment.

Can two engineers alternate pager nights?
Yes—night_N_owner may differ per row; producer still signs P5 capstone.

Where do snapshots live?
release-evidence/february-live/challenge-2027/night-N-BUILD_RECEIPT.snapshot.json—never overwrite without copying to archive/ first.

Is this the same as the 7-day RC challenge?
No—RC challenge is late January; this is live fest nights D1–D5.

Can we run six or seven nights?
Yes—document extension in receipt notes; minimum five for P5 default schema.

Do moderators post #FebruaryLiveOps2027?
Pager owner posts; moderators may reply with handoff links only.

What if P3 fails twice?
Stop HOTFIX; escalate producer + HOTFIX exception policy.

Should N3 include Thursday row review?
Optional cousin pass—if D3 is Wednesday, run Thursday row review immediately after smoke and attach row_diff[] to P3 evidence.

How long is each night really?
Ritual script targets 20 minutes of receipt work; P3 adds 15-minute Wednesday smoke outside the cap—budget separately in timebox pager column.

What ships next in February cluster?
Blog-Create #7 — February fest co-stream overlay safe-zone art pass.