Tuesday Discord Playtest Thread CSV Receipt Ingest - Twelve-Minute Ritual Before Wednesday Smoke - 2026

Tuesday stand-up opens with: “Any blockers?” Someone says “a few in Discord.” Nobody counted them. Wednesday you promote nextfest-oct-2026-rc5. Thursday a player soft-locks on a boss door your facilitator flagged P0 in a spreadsheet cell buried under a filter.

October 2026 async playtest volume exceeds stand-up time. 18 playtest feedback tools generate Discord threads, Sheets exports, and VODs faster than producers can read them. Wednesday demo smoke proves the binary golden path—it does not read facilitator spreadsheets. Without a Tuesday CSV ingest ritual, P0 rows live in Slack reactions, not BUILD_RECEIPT.

This Process & Workflow post defines a twelve-minute Tuesday ritual: export Discord thread → three-column minimum CSV → jq normalize → P0/P1 blocker counts → playtest_csv_ingest_receipt_v1.json → set Wednesday smoke scope. The ninety-second jq checklist lives in Discord CSV jq preflight (Guide); this article owns facilitator rhythm, time-box, and promotion policy.

Non-repetition note: Whisper→GitHub tag extraction owns VOD quote-only issues; Weblate UTF-8 preflight owns encoding bytes; Wednesday smoke owns binary S4–S6. This URL owns Tuesday async CSV triage counts—not another metadata checklist, not Whisper transcripts.

Who this is for and what you get

Time: 12 minutes every Tuesday (default before Wednesday smoke week).
Prerequisites: Discord thread or Google Sheet export; jq on PATH; BUILD_RECEIPT row for target build_label; playtest-feedback/README.md with column map.

Why this matters now (October 2026)

1. Discord thread volume — Fest weeks produce 30–80 CSV rows; stand-ups cannot enumerate them.
2. Promotion without scope — Teams promote while four P0 rows still reference last week's build_id.
3. Receipt culture gap — Thursday row review cannot answer “how many P0?” without Tuesday counts on BUILD_RECEIPT.
4. Founder time-box — Fest week capacity worksheet sets ingest budget; this ritual is the default twelve-minute block.
5. Multi-channel facilitators — Lesson 206 SOW assumes CSV rows carry honest build_id—not Discord pin memory.

Direct answer: Archive raw CSV, jq-normalize to playtest_feedback_normalized.json, compute P0/P1 counts, crosswalk build_id to BUILD_RECEIPT, file playtest_csv_ingest_receipt_v1.json, set wednesday_smoke_allowed only when D5 policy passes.

Weekly ritual map (Tuesday → Wednesday → Thursday)

Rule: Tuesday CSV GREEN does not replace Wednesday smoke RED—they are different gates. CSV answers “should we promote given open blockers?” Smoke answers “does the binary boot?”

Mental model — triage vs encoding vs binary

Order: jq ingest (Tuesday) → UTF-8 handoff (when localization path) → Wednesday smoke. Do not skip Tuesday because “smoke passed last week.”

Beginner path — three-column CSV export

You do not need jq on day one to start the habit—pin this minimum schema in playtest-feedback/README.md:

Optional but valuable: area, discord_message_url, tester_handle (no PII beyond what players already posted publicly).

Step 1 — Export Discord thread (4 minutes)

Save as playtest-feedback/raw/discord_thread_YYYY-MM-DD.csv.

Success check: File opens in a text editor; first line is headers; at least one data row exists.

Step 2 — Hand-count P0 (3 minutes)

Before jq automation, facilitator manually counts rows where severity is P0 or Blocker. Write count on sticky note or README roster.

Red flag: P0 > 0 and producer has not read summaries—block promotion until triaged.

Step 3 — Crosswalk build_id (2 minutes)

Open BUILD_RECEIPT and confirm every CSV row uses the same build_id as tonight's playtest night. Visible build label on the demo helps facilitators copy the correct string.

Fail-closed: mixed build_id values in one export—split CSV by build before continuing.

Step 4 — File receipt stub (3 minutes)

Even before jq, create minimal receipt:

{
  "schema": "playtest_csv_ingest_receipt_v1",
  "build_label": "2026-11-04-playtest-rc4",
  "source_csv_path": "playtest-feedback/raw/discord_thread_2026-11-04.csv",
  "counts_manual": { "P0": 1, "P1": 3, "P2": 8 },
  "csv_ingest_ok": false,
  "note": "manual Tuesday pass — jq normalize pending"
}

Graduate to full D1–D6 when jq script is pinned (developer path below).

Developer path — twelve-minute D1–D6 gates

Align with Discord CSV jq preflight (Guide). Blog = rhythm; guide = checklist.

D2 — playtest_csv_column_map_v1.json

Pin column aliases so facilitator header drift does not silently empty jq output:

{
  "schema": "playtest_csv_column_map_v1",
  "source_headers": ["Build", "P-level", "Category", "Issue", "Link"],
  "canonical_map": {
    "build_id": "Build",
    "severity": "P-level",
    "area": "Category",
    "summary": "Issue",
    "discord_message_url": "Link"
  },
  "severity_normalize": {
    "P0": ["P0", "p0", "Blocker", "Critical"],
    "P1": ["P1", "p1", "High"],
    "P2": ["P2", "p2", "Medium"]
  }
}

Facilitator rule: new column mid-week → update map before Tuesday ingest (D2 fail if skipped).

D3 — jq normalize (bash)

sha256sum playtest-feedback/raw/discord_thread_2026-11-04.csv | tee /tmp/csv_sha.txt

jq -n --slurpfile rows playtest-feedback/raw/discord_thread_2026-11-04.csv \
  --argfile map playtest-feedback/playtest_csv_column_map_v1.json \
  -f scripts/normalize_playtest_csv.jq \
  > playtest-feedback/normalized/playtest_feedback_normalized.json

Normalized output shape:

{
  "schema": "playtest_feedback_normalized_v1",
  "build_label": "2026-11-04-playtest-rc4",
  "rows": [
    {
      "build_id": "2026-11-04-playtest-rc4",
      "severity": "P0",
      "area": "progression",
      "summary": "Soft-lock after boss door",
      "discord_message_url": "https://discord.com/channels/…"
    }
  ],
  "counts": { "P0": 1, "P1": 3, "P2": 8, "total": 12 }
}

Fail-closed: jq exit non-zero → no Wednesday promotion; fix column map (D2) before retry.

D4 — build_id crosswalk

jq -r '.build_id' release-evidence/BUILD_RECEIPT.json
jq -r '.rows[].build_id' playtest-feedback/normalized/playtest_feedback_normalized.json | sort -u

Pass: exactly one unique build_id matching BUILD_RECEIPT.
Fail: split CSV by build; re-run D3 per file.

D5 — blocker promotion policy

P0 waiver (when you must promote anyway):

## P0 waiver roster
| build_id | P0 summary | approver | UTC | waiver_id |
|----------|------------|----------|-----|-----------|
| 2026-11-04-playtest-rc4 | progression soft-lock | producer@studio | 2026-11-05T08:00:00Z | WAIVER-2026-11-04-01 |

Receipt field: "p0_waiver_id": "WAIVER-2026-11-04-01" — Thursday row review must show waiver Y/N.

D6 — playtest_csv_ingest_receipt_v1.json

{
  "schema": "playtest_csv_ingest_receipt_v1",
  "build_label": "2026-11-04-playtest-rc4",
  "source_csv_path": "playtest-feedback/raw/discord_thread_2026-11-04.csv",
  "source_csv_sha256": "cc99a435…",
  "normalized_path": "playtest-feedback/normalized/playtest_feedback_normalized.json",
  "column_map_path": "playtest-feedback/playtest_csv_column_map_v1.json",
  "counts": { "P0": 1, "P1": 3, "P2": 8, "total": 12 },
  "p0_blockers": ["progression: Soft-lock after boss door"],
  "cousin_receipts": {
    "weblate_utf8_handoff": "release-evidence/localization/WEBLATE_CSV_UTF8_HANDOFF_RECEIPT.json",
    "whisper_issue_tag": "release-evidence/playtest/whisper-tags/WHISPER_ISSUE_TAG_RECEIPT_fragment_03.json"
  },
  "gates": {
    "D1_csv_archived": "pass",
    "D2_column_map": "pass",
    "D3_jq_normalize": "pass",
    "D4_build_id_crosswalk": "pass",
    "D5_blocker_counts": "pass",
    "D6_receipt": "pass"
  },
  "csv_ingest_ok": true,
  "wednesday_smoke_allowed": true
}

Pin under release-evidence/playtest/PLAYTEST_CSV_INGEST_RECEIPT.json.

BUILD_RECEIPT columns (wire on D5 pass)

Lesson 267 forward wires these columns into BUILD_RECEIPT promotion gates.

Twelve-minute timer script (facilitator README)

Copy into playtest-feedback/README.md:

# Tuesday CSV ingest (12 min)
| Min | Task | Owner |
|-----|------|-------|
| 0-2 | Export Discord/Sheet → raw CSV | Facilitator |
| 2-4 | Verify headers vs column_map_v1.json | Facilitator |
| 4-7 | Run jq normalize script | Engineer or facilitator |
| 7-9 | build_id crosswalk BUILD_RECEIPT | Producer |
| 9-11 | P0/P1 policy + waiver if needed | Producer |
| 11-12 | File PLAYTEST_CSV_INGEST_RECEIPT.json | Facilitator |
| Post | Post P0 count in #release (one line) | Producer |

One-line Discord post template:

Tuesday CSV ingest: build_id=2026-11-04-playtest-rc4 P0=1 P1=3 — smoke scope Wednesday PM.

Folder layout

playtest-feedback/
  README.md                          # column map + Tuesday timer + waiver roster
  playtest_csv_column_map_v1.json
  raw/
    discord_thread_2026-11-04.csv
  normalized/
    playtest_feedback_normalized.json
  scripts/
    normalize_playtest_csv.jq
release-evidence/playtest/
  PLAYTEST_CSV_INGEST_RECEIPT.json

Pair Resource #12 facilitator README refresh when published—this folder is the source of truth for column map pins.

Relationship to Whisper and VOD triage

Do not double-count: A P0 in CSV and a Whisper issue for the same bug should share build_id + area—link URLs in receipt cousin_receipts, do not inflate P0 twice without noting duplicate.

Proof table (producer audit)

Export release-evidence/playtest/PROOF_PACK_CSV_INGEST_YYYY-MM-DD/ for Q4 diligence triage integrity questions.

Seven scenarios (A–G)

Common mistakes

1. Promoting with undocumented P0 — refund screenshots follow.
2. Hard-coded English jq headers — facilitator adds 優先度 without map update (D2).
3. Skipping D4 — CSV still lists last week's build_id.
4. Jumping to Weblate before jq GREEN — encoding cousin cannot fix wrong blocker scope.
5. Treating CSV ingest as smoke substitute — Wednesday S4–S6 still required.
6. Merging ingest receipt into Weblate handoff — use cousin_receipts only (Lesson 256).
7. No build_label column — visible label opinion requires facilitators can copy honest build strings.

CI optional gate (jq before promote)

#!/usr/bin/env bash
set -euo pipefail
REC="release-evidence/playtest/PLAYTEST_CSV_INGEST_RECEIPT.json"
jq -e '.csv_ingest_ok == true' "$REC"
jq -e '.counts.P0 == 0 or .p0_waiver_id != null' "$REC"
echo "Tuesday CSV ingest OK for promotion"

Wire as optional GitHub Actions job Tuesday 18:00 UTC before Wednesday smoke workflow triggers.

Facilitator contract and capacity

Multi-channel facilitator contract defines who exports CSV. Fest week time-box allocates twelve minutes engineering-adjacent ingest—not zero because “async means free.”

Resource #12 README refresh should include: column map template, waiver roster, Tuesday timer, jq script path.

Tools and sibling reads

• 18 free async playtest tools
• Discord CSV jq preflight (Guide)
• Playtest analytics event schema preflight
• OBS MKV concat help (Help #5 forward)
• 14 Free Weblate string-freeze tools
• Community playtest ops resource
• Official: jq manual

Key takeaways

1. Twelve minutes every Tuesday — export, normalize, count, receipt—before Wednesday smoke.
2. P0 > 0 blocks promotion unless documented producer waiver (D5).
3. build_id only from BUILD_RECEIPT (D4)—visible label helps facilitators.
4. Column map JSON prevents silent jq empty output (D2).
5. CSV ingest ≠ binary smoke — different gates, same week.
6. Encoding is cousin UTF-8 preflight — run jq ingest first on triage scope.
7. BUILD_RECEIPT columns playtest_csv_p0 / playtest_csv_p1 wire blocker truth.
8. Thursday row review checks Tuesday P0 count Y/N.
9. Guide preflight holds D1–D6 checklist; this post holds facilitator rhythm.
10. playtest_csv_ingest_receipt_v1.json proves Tuesday ran—not Slack vibes.

FAQ

Can we skip Tuesday if smoke passed last week?
No—new Discord rows arrive daily. File skip reason on BUILD_RECEIPT if ritual genuinely N/A (no playtest that week).

Google Sheet vs raw Discord export?
Sheet is fine—D1 archives whatever facilitator exports; column map must match headers.

What if we have zero rows?
File receipt with counts: { "P0": 0, "P1": 0, "P2": 0, "total": 0 } — proves empty week, not forgotten ingest.

Does this replace playtest analytics?
No—analytics preflight owns GA4 allowlist; CSV owns human facilitator blockers.

How does this pair with refund correlation?
Refund playbook tags build_id; Tuesday P0 rows explain known blockers before refunds spike.

Construct-only?
No—jq ingest is engine-agnostic; Construct guide chapter is the pinned checklist for HTML5 teams.

Where does Lesson 267 fit?
Lesson 267 wires playtest_csv_ingest_receipt into BUILD_RECEIPT promotion—pairs this ritual with receipt culture.

Conclusion

Promoting with undocumented P0 rows is how refund screenshots happen. Tuesday twelve minutes—normalize Discord CSV, crosswalk build_id, file blocker counts, pin receipt—buys honest Wednesday smoke scope.

Next reads: Wednesday demo smoke, Discord CSV jq preflight, Whisper tag extraction, Thursday row review, BUILD_RECEIPT beginner pipeline.

Found this useful? Pin the twelve-minute timer in playtest-feedback/README.md before your next fest week—not after the first undocumented P0 promotion.