================================================================================
COLLABTUNES RAPID BLOCKER RESPONSE PROTOCOL
Date: 5_13_26 | Status: AUTHORITATIVE
Purpose: When a blocker appears, execute this. No debate. No philosophy.
================================================================================

================================================================================
STEP 1 — IDENTIFY (< 2 min)
================================================================================
Answer these 3 questions immediately:

  What broke?      ____________________________________________________________
  Where?           ____________________________________________________________
  When noticed?    ____________________________________________________________

Source of detection:
  [ ] SGC-1 flag        [ ] SGC-2 flag        [ ] Manual QA
  [ ] Tom reported      [ ] User reported      [ ] Post-deploy alert

================================================================================
STEP 2 — CLASSIFY (< 2 min)
================================================================================
Pick exactly one. If unsure, go higher.

  [ ] CRITICAL — gate missing on R+ page, content exposed, or site down
                 → Skip to ISOLATE immediately. No further classification needed.

  [ ] HIGH     — broken AIO page, dead chapter link, nav failure, canon conflict
                 affecting generation

  [ ] MODERATE — chapter drift, duplicate URL, orphan page, rating mismatch
                 on non-critical page

  [ ] LOW      — cosmetic naming drift, missing date stamp, misplaced file

Deployment impact:
  [ ] BLOCKS_DEPLOYMENT     [ ] DEGRADES_FUNCTION     [ ] COSMETIC

If BLOCKS_DEPLOYMENT: do not proceed with any deployment activity until Step 7.

================================================================================
STEP 3 — ISOLATE (< 5 min)
================================================================================
Contain the blast radius. Do not let the problem spread.

  Affected URLs / files:   ____________________________________________________
  Affected subsystem:      ____________________________________________________
  Other systems at risk:   ____________________________________________________

Actions:
  [ ] If gate is missing on live page → alert Tom immediately, do not ship
  [ ] If canon file was corrupted → freeze that file, do not use for generation
  [ ] If SGC run produced bad output → do not promote output to production
  [ ] If deployment is mid-flight → pause deployment, assess before continuing

================================================================================
STEP 4 — ASSIGN (< 2 min)
================================================================================
One owner. No committee.

  Owner:          [ ] Developer    [ ] Tom    [ ] Mixed Claude    [ ] Tom + Dev
  Deadline:       ____________________________________________________________

  Who else needs to know right now:
  [ ] Tom (content/canon decision)       notified: [ ] YES  [ ] NO
  [ ] Developer (code fix needed)        notified: [ ] YES  [ ] NO
  [ ] No one else — handle autonomously

  Blocker ID assigned:   BLOCK-___-___   (add to BLOCKER_REGISTRY now)

================================================================================
STEP 5 — VERIFY ROLLBACK EXISTS (< 3 min)
================================================================================
Before touching anything:

  [ ] Rollback ZIP exists for current state           ZIP: ____________________
  [ ] Rollback ZIP is dated and accessible
  [ ] Rollback can restore affected files in < 15 min

  If NO rollback exists: CREATE ONE NOW before any fix attempt.
  Filename: {N}_ZIP_PREFIX_ROLLBACK_BEFORE_{BLOCKER_ID}_{DATE}.zip

================================================================================
STEP 6 — RESOLVE
================================================================================
Execute the fix. Use LIVE_SITE_FAILURE_PATTERN_INDEX for fastest fix lookup.
Use CANON_CONFLICT_TRIAGE_SYSTEM for canon issue routing.

  Fix applied:     ____________________________________________________________
  Files changed:   ____________________________________________________________
  Method:          [ ] Code change    [ ] Config change    [ ] File move/rename
                   [ ] Registry update    [ ] Tom decision implemented

  Do NOT resolve:
  [ ] Lady Weaver slug (BLOCK-H04) — Tom required
  [ ] Chapter 18/19 drift (BLOCK-H02) — Tom required
  [ ] Any rating tier change — Tom required
  [ ] Any LOCKED file change — Tom required

================================================================================
STEP 7 — VERIFY FIX (< 10 min)
================================================================================
Confirm the fix actually worked. Do not assume.

  [ ] SGC-1 re-run (DRY_RUN at minimum) — flag is gone
  [ ] Manual browser check on affected page
  [ ] Gate test if gate was involved (bypass test included)
  [ ] No new flags introduced by the fix
  [ ] Affected page returns HTTP 200

  Fix verified by:  ______________________   Date: ___________________________

================================================================================
STEP 8 — CHECKPOINT
================================================================================
  [ ] Post-fix checkpoint ZIP created
      Filename: {N}_ZIP_SESSION_CHECKPOINT_AFTER_{BLOCKER_ID}_FIX_{DATE}.zip

  [ ] BLOCKER_REGISTRY updated — status → RESOLVED, date recorded
  [ ] If fix changed a canon file: new VOL created, old marked REFERENCE

================================================================================
STEP 9 — SIGNOFF
================================================================================
  Blocker ID:        BLOCK-___-___
  Status:            RESOLVED
  Resolved by:       ______________________
  Verified by:       ______________________
  Date resolved:     ______________________
  Tom notified:      [ ] YES   [ ] NO   [ ] NOT REQUIRED

  Deployment cleared to resume?   [ ] YES   [ ] NO — remaining blockers: ______

================================================================================
QUICK SEVERITY RESPONSE GUIDE
================================================================================

GATE MISSING on R+ page
  → Stop everything. Alert Tom. Do not deploy. Fix gate. Verify. Then resume.

CANON FILE CORRUPTED
  → Freeze file. Roll back to last checkpoint. Identify cause. New VOL after fix.

SGC RUN PRODUCED BAD OUTPUT
  → Do not promote. Roll back outputs. Investigate logs. Re-run after fix.

DEAD AIO PAGE (404)
  → Check registry for current slug. Update link. Verify. Log blocker.

CHAPTER DRIFT
  → Log as MODERATE. Tom decides slug vs label fix. Do not auto-resolve.

DUPLICATE ANCHOR
  → Find duplicate. Rename second instance. Update all links to it. Verify.

================================================================================
END RAPID BLOCKER RESPONSE PROTOCOL
================================================================================
