jq Gate Sketch for march_post_fest_sprint_receipt_v1.json Weekly BUILD_RECEIPT Row Diff - 2026

March 2027, week two: 7-day evidence sprint finished E7 GREEN. Engineering merged three post-fest branches. Producer asks "did we drift from February closeout?" Someone pastes a Thursday row review diff—but that ritual diffs promotion columns weekly, not post-fest sprint truth against Sunday February closeout. Another teammate proposes copying February hourly jsonl—wrong cadence, wrong schema.

March needs march_post_fest_sprint_receipt_v1.json filed once per ISO week with row_diff[] against the prior week snapshot and a february_closeout_pointer to february_fest_closeout_receipt_v1.json—not a second hourly log.

This Programming & Technical sketch ships march_post_fest_sprint_receipt_v1.json, verify_march_post_fest_sprint.sh, gates J1–J6, copy-paste jq for CI and facilitator laptops—strategy above per-evening tutorials, below Guide #40 forward.

Non-repetition note: February hourly jq owns D1–D7 per-hour february_fest_live_ops jsonl. Thursday row review owns ten-minute weekly promotion diff. January reentry pointer owns pre-live capstone crosswalk. This URL owns March weekly march_post_fest_sprint row diff with February closeout pointer.

Pair Monday debrief facilitator, evidence sprint E1–E7, empty annex recovery, cluster #1–#7, forward #9 March engineering cash runway.

Why this matters now (March 2027 post-fest sprint)

1. Weekly drift after fest — build_label, velocity baselines, and MERGE exceptions change across March—not only on Thursdays.
2. Closeout pointer debt — Teams diff BUILD_RECEIPT without anchoring Sunday closeout jsonl_annex[]—partners ask "which fest truth?"
3. Evidence sprint handoff — E7 sets march_post_fest_evidence_ok; weekly receipt extends that latch week over week.
4. October prep collision — March merges without weekly diff reintroduce setlive drift before October RC label.
5. Friday March capstone — Forward #11 expects march_post_fest_sprint_weekly_log.jsonl trail—not reconstructed Slack.

Direct answer: File weekly march_post_fest_sprint_receipt_v1.json with february_closeout_pointer, append march_post_fest_sprint_weekly_log.jsonl, run verify_march_post_fest_sprint.sh, gates J1–J6, set BUILD_RECEIPT march_post_fest_sprint_weekly_ok: true before declaring Friday sprint stand-up GREEN.

Who this sketch is for

Time: ~45 minutes first weekly template; ~3 minutes per week after scripts pinned.

Mental model — weekly sprint vs hourly live vs Thursday review

Rule: March weekly jq does not replace Thursday review—it anchors post-fest work to February closeout and feeds forward #11 Friday capstone.

Beginner path — weekly diff vs daily hourly cousin

Memorize one sentence: hourly = live fest noise; weekly = post-fest sprint signal.

Beginner mistake: Appending hourly lines in March—use one jsonl line per ISO week.

march_post_fest_sprint_receipt_v1.json (schema)

{
  "schema": "march_post_fest_sprint_receipt_v1",
  "sprint_window": "2027-03-post-fest-sprint",
  "iso_week": "2027-W11",
  "build_label": "fest-demo-2027-02-rc3-postfest-1",
  "february_closeout_pointer": {
    "path": "release-evidence/february-live/FEBRUARY_FEST_CLOSEOUT_RECEIPT.json",
    "february_fest_closeout_ok": true,
    "post_fest_debrief_allowed": true
  },
  "snapshot": {
    "march_post_fest_evidence_ok": true,
    "wishlist_velocity_baseline_ok": true,
    "merge_exception_list_ok": false,
    "engineering_runway_ok": null,
    "build_label": "fest-demo-2027-02-rc3-postfest-1"
  },
  "row_diff": [
    {"field": "build_label", "before": "fest-demo-2027-02-rc3", "after": "fest-demo-2027-02-rc3-postfest-1", "delta": "bump"},
    {"field": "march_post_fest_evidence_ok", "before": true, "after": true, "delta": "unchanged"},
    {"field": "merge_exception_list_ok", "before": null, "after": false, "delta": "new_column"}
  ],
  "gates": {
    "J1_schema": "pass",
    "J2_closeout_pointer": "pass",
    "J3_prior_week": "pass",
    "J4_evidence_ok": "pass",
    "J5_row_diff_honest": "pass",
    "J6_receipt_filed": "pass"
  },
  "march_post_fest_sprint_weekly_ok": true
}

Weekly log (jsonl)

release-evidence/post-fest/march_post_fest_sprint_weekly_log.jsonl — one line per ISO week:

{"iso_week":"2027-W10","build_label":"fest-demo-2027-02-rc3","march_post_fest_sprint_weekly_ok":true,"receipt_path":"release-evidence/post-fest/MARCH_SPRINT_RECEIPT_W10.json","closeout_pointer":"release-evidence/february-live/FEBRUARY_FEST_CLOSEOUT_RECEIPT.json"}

Gates J1–J6

J2 fail-closed: Missing or empty closeout annex → run recovery before weekly sprint W11. Do not copy february_fest_live_ops_hourly_log.jsonl into March—weekly log is a separate file with one line per ISO week and a stable closeout_pointer column for capstone #11 audit.

Gate-by-gate facilitator notes (working dev depth)

J1 — schema and sprint_window latch

J1 prevents March receipts from colliding with February hourly or January pointer schemas in release-evidence/post-fest/.

jq -e '.schema == "march_post_fest_sprint_receipt_v1" and .sprint_window == "2027-03-post-fest-sprint"' "$REC"

J2 — February closeout pointer (the March-specific gate)

March weekly diff is meaningless without fest-end truth. Resolve pointer before computing row_diff:

CLO="$(jq -r '.february_closeout_pointer.path' "$REC")"
jq -e '.february_fest_closeout_ok == true and (.jsonl_annex | length >= 1)' "$CLO"

If jsonl_annex empty but february_fest_closeout_ok true, route empty annex recovery—do not waive J2 silently.

J3 — prior week continuity

W10 first week may document prior_week: null in notes. Later weeks must chain jsonl lines:

tail -n 1 release-evidence/post-fest/march_post_fest_sprint_weekly_log.jsonl | jq -e '.iso_week'

J4 — evidence sprint prerequisite

Block weekly receipt when E7 incomplete:

jq -e '.march_post_fest_evidence_ok == true' BUILD_RECEIPT.json

J5 — row_diff honesty

Recompute with jq slurp; attach output to stand-up when MERGE or build_label rows change.

J6 — verify script + BUILD_RECEIPT latch

Mirror march_post_fest_sprint_weekly_ok only after verify_march_post_fest_sprint.sh exit 0.

Cluster integration table (March #1–#7)

Weekly receipt indexes paths—it does not re-run E1–E7 nightly.

Beginner path — five-command weekly stand-up

# 1) Latest receipt exists
REC=release-evidence/post-fest/MARCH_SPRINT_RECEIPT_LATEST.json
test -f "$REC"

# 2) Verify gates
./scripts/verify_march_post_fest_sprint.sh "$REC"

# 3) Print build_label drift only
jq -r '.row_diff[] | select(.field=="build_label") | "\(.before) → \(.after)"' "$REC"

# 4) Confirm closeout pointer
jq -r '.february_closeout_pointer.path' "$REC" | xargs test -f

# 5) Append weekly log (facilitator)
jq -c '{iso_week, build_label, march_post_fest_sprint_weekly_ok, receipt_path: $rec, closeout_pointer: .february_closeout_pointer.path}' \
  --arg rec "$REC" "$REC" >> release-evidence/post-fest/march_post_fest_sprint_weekly_log.jsonl

Success check: Script prints march_post_fest_sprint verify: OK.

Exit code table (snippet-friendly)

Worked example — synthesized 2027-W11

Producer rule: Do not authorize post-fest branch merges until J2 closeout pointer GREEN—not verbal "fest went fine."

jq one-liners (copy-paste)

Diff BUILD_RECEIPT vs prior week export

jq -s '
  .[1] as $now | .[0] as $prev |
  ($now.build_label) as $a | ($prev.build_label) as $b |
  {field:"build_label", before:$b, after:$a, delta: (if $a==$b then "unchanged" else "bump" end)}
' prior_week.json now.json

Validate closeout pointer + annex non-empty

CLO="$(jq -r '.february_closeout_pointer.path' "$REC")"
jq -e '.february_fest_closeout_ok == true and (.jsonl_annex | length > 0)' "$CLO"

Flag MERGE column appearance in row_diff

jq -r '.row_diff[] | select(.field | test("merge")) | "MERGE column \(.field) \(.delta)"' "$REC"

Pair forward #10 MERGE exception opinion.

Weekly jsonl ISO week uniqueness

jq -s '[.[].iso_week] | length as $n | unique | length == $n' \
  release-evidence/post-fest/march_post_fest_sprint_weekly_log.jsonl

Crosswalk evidence + velocity booleans

jq -e '
  .snapshot.march_post_fest_evidence_ok == true and
  .snapshot.wishlist_velocity_baseline_ok == true
' "$REC"

Python cousin — recompute row_diff for J5 audit

# audit_march_sprint_diff.py
import json, sys
prev, now = json.load(open(sys.argv[1])), json.load(open(sys.argv[2]))
fields = ["build_label", "march_post_fest_evidence_ok", "merge_exception_list_ok"]
for f in fields:
    b, a = prev.get(f), now.get(f)
    delta = "unchanged" if b == a else ("new_column" if b is None else "bump")
    print({"field": f, "before": b, "after": a, "delta": delta})

verify_march_post_fest_sprint.sh

#!/usr/bin/env bash
set -euo pipefail
REC="${1:-release-evidence/post-fest/MARCH_SPRINT_RECEIPT_LATEST.json}"

jq -e '.schema == "march_post_fest_sprint_receipt_v1"' "$REC" || exit 1

CLO="$(jq -r '.february_closeout_pointer.path' "$REC")"
test -f "$CLO" || exit 2
jq -e '.february_fest_closeout_ok == true' "$CLO" || exit 2

jq -e '.march_post_fest_sprint_weekly_ok == true' "$REC" || exit 6
jq -e '.row_diff | length >= 1' "$REC" || exit 5
jq -e '.row_diff[] | select(.field=="build_label")' "$REC" >/dev/null || exit 5

# J4 — evidence latch on BUILD_RECEIPT
jq -e '.march_post_fest_evidence_ok == true' BUILD_RECEIPT.json || exit 4

echo "march_post_fest_sprint verify: OK"

PowerShell verify cousin

$Rec = "release-evidence/post-fest/MARCH_SPRINT_RECEIPT_LATEST.json"
$j = Get-Content $Rec -Raw | ConvertFrom-Json
if ($j.schema -ne "march_post_fest_sprint_receipt_v1") { exit 1 }
$clo = $j.february_closeout_pointer.path
if (-not (Test-Path $clo)) { exit 2 }
if (-not $j.march_post_fest_sprint_weekly_ok) { exit 6 }
Write-Host "march_post_fest_sprint verify: OK"

BUILD_RECEIPT wiring

{
  "build_label": "fest-demo-2027-02-rc3-postfest-1",
  "march_post_fest_evidence_ok": true,
  "march_post_fest_sprint_weekly_ok": true,
  "march_post_fest_sprint_receipt": "release-evidence/post-fest/MARCH_SPRINT_RECEIPT_LATEST.json",
  "march_post_fest_sprint_weekly_log": "release-evidence/post-fest/march_post_fest_sprint_weekly_log.jsonl",
  "february_closeout_pointer": "release-evidence/february-live/FEBRUARY_FEST_CLOSEOUT_RECEIPT.json"
}

Latch order during March sprint:

1. Sunday closeout GREEN with non-empty annex (or recovery filed).
2. Evidence sprint E7 → march_post_fest_evidence_ok.
3. Weekly march_post_fest_sprint receipt each ISO week.
4. Forward #11 Friday capstone consumes full weekly jsonl.

CI weekly job sketch (GitHub Actions)

name: march-post-fest-sprint-weekly
on:
  schedule:
    - cron: "0 9 * * 1"  # Mondays during March sprint window
jobs:
  verify:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: verify latest weekly receipt
        run: |
          test -f release-evidence/post-fest/MARCH_SPRINT_RECEIPT_LATEST.json
          bash scripts/verify_march_post_fest_sprint.sh release-evidence/post-fest/MARCH_SPRINT_RECEIPT_LATEST.json

Pin if: to March sprint dates—do not run weekly year-round on stale receipts.

Printable weekly facilitator card

Copy into release-evidence/post-fest/march-sprint-weekly-facilitator-card.md:

# March post-fest sprint — weekly jq stand-up (3 min)
iso_week: ______
closeout_pointer: release-evidence/february-live/FEBRUARY_FEST_CLOSEOUT_RECEIPT.json

[ ] J2 — closeout GREEN + jsonl_annex non-empty (or recovery filed)
[ ] J4 — march_post_fest_evidence_ok on BUILD_RECEIPT
[ ] build_label row_diff pasted to #post-fest-sprint
[ ] verify_march_post_fest_sprint.sh exit 0
[ ] jsonl line appended for this iso_week
[ ] MERGE bump? → forward #10 exception list
[ ] runway column new? → forward #9 cash worksheet

Laminate beside Thursday row review card—different cadence, same "receipt before narrative" discipline.

jsonl integrity checks (Friday capstone #11 prep)

Forward #11 Friday March capstone will consume the full weekly log before April content update authorization. Run before March ends:

# Expect 4 lines for a four-week sprint (± documented waivers)
wc -l release-evidence/post-fest/march_post_fest_sprint_weekly_log.jsonl

# Unique iso_week stamps
jq -s '[.[].iso_week] | length as $n | unique | length == $n' \
  release-evidence/post-fest/march_post_fest_sprint_weekly_log.jsonl

# closeout_pointer stable across all weeks
jq -s '[.[].closeout_pointer] | unique | length == 1' \
  release-evidence/post-fest/march_post_fest_sprint_weekly_log.jsonl

# build_label tail — more than one label requires MERGE exception trail
jq -s '[.[].build_label] | unique' \
  release-evidence/post-fest/march_post_fest_sprint_weekly_log.jsonl

If unique build_label count exceeds one without matching MERGE exception rows, pause April upload planning until forward #10 completes.

Partner diligence zip (weekly slice)

Attach one weekly receipt to partner threads—not the entire jsonl unless requested:

march-sprint-W11-weekly-proof.zip
├── march_post_fest_sprint_receipt_v1.json
├── FEBRUARY_FEST_CLOSEOUT_RECEIPT.json (pointer target excerpt path only in README)
├── row_diff_build_label.txt
└── verify_log.txt

Pointer-first email: "Weekly sprint diff filed W11; anchored to Sunday closeout annex count N; E7 evidence latch still true." Attach verify_log.txt exit 0 line for partners who run scripts locally.

February hourly vs March weekly comparison

Proof table

Scenarios A–G

Facilitator weekly stand-up script (3 minutes)

1. Closeout pointer GREEN? (J2) — path + annex count
2. build_label row_diff — bump or unchanged?
3. march_post_fest_evidence_ok still true?
4. MERGE / runway columns — forward #9/#10 if new
5. verify_march_post_fest_sprint.sh exit 0 → append jsonl

Paste receipt path—not screenshots—in #post-fest-sprint.

Common mistakes

Counterarguments (honest limits)

"Weekly Thursday review is enough."
Thursday diffs promotion columns; March sprint diffs post-fest engineering against closeout truth.

"jq is overkill for four March weeks."
Four lines in jsonl beat four weeks of "what did we merge?" Slack archaeology.

"Same gates as February hourly."
Same J1–J6 labels, different J2 semantics—closeout pointer vs HOTFIX policy.

Outbound references

• jq manual — slurpfile and diff patterns
• ISO week date formats — iso_week field convention

Related GamineAI reads

• February hourly jq cousin
• Thursday row review
• Sunday February closeout
• 7-day March evidence sprint
• Monday debrief facilitator
• Empty annex recovery
• BUILD_RECEIPT beginner pipeline
• January reentry jq pointer

Key takeaways

1. March 2027 post-fest sprint needs weekly jq—not February hourly jsonl.
2. february_closeout_pointer anchors weekly diff to Sunday closeout truth.
3. march_post_fest_sprint_receipt_v1.json stores row_diff[] vs prior ISO week.
4. Gates J1–J6; J2 and J4 are March-specific blockers.
5. Prereq: march_post_fest_evidence_ok from E7 evidence sprint.
6. march_post_fest_sprint_weekly_log.jsonl — one line per week for capstone #11.
7. Thursday row review cousin—different columns, same ten-minute discipline spirit.
8. Forward #9 March engineering cash runway when engineering_runway_ok appears in weekly snapshot.
9. Forward #10 MERGE opinion when build_label bump without exception list.
10. verify_march_post_fest_sprint.sh gives CI one exit code.
11. Guide #40 forward owns extended jq preflight cousin.
12. Empty closeout annex → recovery case study before J2 waiver.
13. Cluster #1–#7 indexed in weekly snapshot—not re-run nightly.

FAQ

Is this the same as February hourly jq?

No—weekly cadence, march_post_fest_sprint_receipt_v1 schema, closeout pointer instead of HOTFIX J3.

Can we run weekly before evidence sprint E7?

No—J4 requires march_post_fest_evidence_ok.

How does Thursday row review relate?

Thursday owns promotion diff; this sketch owns post-fest sprint diff with closeout anchor.

What if closeout passed with empty annex?

Run empty annex recovery—J2 should not pass on hollow annex.

Does this replace Sunday closeout?

No—weekly receipts point at closeout; they do not recreate jsonl_annex[].

When does Friday capstone (#11) consume this log?

End of March—full march_post_fest_sprint_weekly_log.jsonl becomes capstone annex cousin.

Can we reuse February hourly jsonl paths in March?

No—different schema, cadence, and anchor. Copy scripts and discipline, not file paths or fest_window strings.

RED / YELLOW / GREEN routing (J gates)

Closing

March post-fest engineering without weekly jq becomes merge folklore—build_label bumps, velocity baselines, and MERGE exceptions drift from February closeout truth while October prep starts. File march_post_fest_sprint_receipt_v1.json with february_closeout_pointer, append march_post_fest_sprint_weekly_log.jsonl, and run verify_march_post_fest_sprint.sh each ISO week. Beginners use the weekly-vs-hourly table; working devs wire Monday CI; producers block merges until J2 GREEN. Forward #9 cash runway when contractor overtime columns appear in weekly snapshot, and forward #11 Friday capstone expects this trail—not a second hourly schema copied from live week.