March Engineering Cash Runway Worksheet After February Fest Contractor Overtime - 2026

March 3: your gameplay contractor invoices 32 pager hours from February live week. March 4: audio wants rush mixing for post-fest clips. March 5: engineering starts October RC label evening while the bank account still shows fest-week Uber Eats and unpaid HOTFIX overtime.

March 2027 is when February fest contractor overtime collides with October 2026 prep engineering—two cash hungry lanes that both feel "critical" in Slack. Teams that capped January marketing cash but never capped post-fest engineering invoices discover in April they cannot afford Addressables contractors while still paying pager debt.

December engineering floor capped founder engineering hours during holiday blackout. January marketing cap capped weekly marketing cash when contractors returned. October fest spend cap capped fest marketing pool months ahead. This Money & Business worksheet caps weekly engineering cash for four post-fest ISO weeks when pager overtime invoices land—not marketing dollars, not daily founder hours alone.

Non-repetition note: January marketing cap owns weekly_marketing_cap_usd. December engineering floor owns engineering_floor_hours per day. October fest spend cap owns marketing runway pool. Contractor vs hire owns role selection dollars. This URL owns weekly_engineering_cap_usd + march_engineering_runway_receipt_v1.json + BUILD_RECEIPT engineering_runway_ok after February pager overtime.

Pair jq March weekly sprint, 7-day evidence sprint, Sunday closeout, forward #10 MERGE exception opinion.

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

1. Pager overtime invoices — 5-night pager challenge and jq hourly prove ops truth; contractors bill cash in March.
2. October prep engineering — July signup and RC label evening need engineering contractor weeks in Q2–Q3—not fest debt.
3. Marketing vs engineering confusion — Teams pause ads per October marketing cap while approving unlimited engineering invoices.
4. Weekly jq snapshot — March sprint weekly expects engineering_runway_ok column—this worksheet files it.
5. BUILD_RECEIPT gap — Partners see marketing_spend_planned without engineering_spend_planned post-fest—cash surprises in diligence.

Direct answer: Fill march-engineering-runway-2027.md with four-week engineering caps, pager overtime amortization, October prep reservation, file march_engineering_runway_receipt_v1.json, set BUILD_RECEIPT engineering_runway_ok: true before approving March contractor invoices.

Who this worksheet is for

Time: ~60 minutes first worksheet; 10 minutes each Monday update actual_spend_usd.
Prerequisites: February closeout filed, bank balance post-fest, contractor overtime invoices in hand, evidence sprint E7 GREEN.

Format ladder (March cluster)

Order: Sunday closeout GREEN → evidence sprint E7 → this worksheet → jq March weekly W10 → October prep engineering quotes.

Beginner path — four-week post-fest cap table

Copy into release-evidence/ops/march-engineering-runway-2027.md:

Beginner rule: pager_amortized + gameplay + audio + october_reserve ≤ weekly_engineering_cap. If pager invoice exceeds W10 amortization row, spread across W10–W12 in receipt overtime_schedule[]—do not pay full invoice Week 10 without lowering gameplay.

Success check: Each week has one primary engineering outcome (e.g., "post-fest branch merge with MERGE-001") and one cash outcome (e.g., "pager invoice ≤ $1,200").

What counts toward engineering cap (cash)

Quasi-paid: Founder engineering hours belong in December floor cousin—this worksheet tracks contractor cash out the door.

Developer path — gates K1–K6

march_engineering_runway_receipt_v1.json (template)

{
  "schema": "march_engineering_runway_receipt_v1",
  "generated_at": "2027-03-03T18:00:00Z",
  "sprint_window": "2027-03-post-fest-sprint",
  "march_engineering_pool_usd": 9400,
  "pager_overtime_total_usd": 2400,
  "weekly_caps": [
    {
      "iso_week": "2027-W10",
      "cap_usd": 2800,
      "pager_amortized_usd": 1200,
      "gameplay_contractor_usd": 1000,
      "audio_post_fest_usd": 400,
      "october_prep_reserve_usd": 200,
      "stop_rule": "ER1"
    },
    {
      "iso_week": "2027-W11",
      "cap_usd": 2400,
      "pager_amortized_usd": 800,
      "gameplay_contractor_usd": 800,
      "audio_post_fest_usd": 400,
      "october_prep_reserve_usd": 400,
      "stop_rule": "ER2"
    }
  ],
  "overtime_schedule": [
    {"invoice_id": "pager-gameplay-2027-02", "total_usd": 2400, "weeks": ["2027-W10", "2027-W11", "2027-W12"]}
  ],
  "february_closeout_pointer": "release-evidence/february-live/FEBRUARY_FEST_CLOSEOUT_RECEIPT.json",
  "stop_rules": [
    {"id": "ER1", "trigger": "new_scope_without_MERGE", "action": "pause_contractor_approval"},
    {"id": "ER2", "trigger": "march_post_fest_sprint_weekly_ok false", "action": "pause_gameplay_invoices"},
    {"id": "ER3", "trigger": "build_label_bump_without_MERGE_list", "action": "forward_opinion_10"},
    {"id": "ER4", "trigger": "october_prep_quote_signed_without_reserve", "action": "defer_quote_week"}
  ],
  "gates": {
    "K1": "GREEN",
    "K2": "GREEN",
    "K3": "GREEN",
    "K4": "GREEN",
    "K5": "GREEN",
    "K6": "GREEN"
  },
  "engineering_runway_ok": true
}

BUILD_RECEIPT root rows (same commit)

{
  "build_label": "fest-demo-2027-02-rc3-postfest-1",
  "march_post_fest_evidence_ok": true,
  "march_post_fest_sprint_weekly_ok": true,
  "engineering_spend_planned": 9400,
  "engineering_runway_ok": true,
  "engineering_runway_receipt": "release-evidence/ops/march_engineering_runway_receipt_v1.json",
  "marketing_spend_planned": 4400
}

marketing_spend_planned stays on January marketing cap cousin row—do not merge columns.

Stop rules ER1–ER5 (working dev)

Wire ER2 to Monday jq verify exit code—same discipline as January SR rules on smoke receipts.

Gate-by-gate facilitator notes (K1–K6 depth)

K1 — four ISO weeks minimum

March post-fest sprint is intentionally four weeks—long enough to amortize pager debt, short enough to force weekly honesty. If your studio needs W14, append rows and bump march_engineering_pool_usd in the same commit as BUILD_RECEIPT engineering_spend_planned.

K2 — pager overtime amortization math

Sum pager_amortized_usd across weeks must equal pager_overtime_total_usd (±$1 rounding). If gameplay contractor demands full payment Week 10, lower gameplay column or extend weeks—K2 does not waive because the invoice due date is sooner than your receipt.

K3 — BUILD_RECEIPT parity

The receipt march_engineering_pool_usd must equal the sum of weekly_caps[].cap_usd and match BUILD_RECEIPT engineering_spend_planned in the same commit as engineering_runway_ok: true.

K4 — October prep reserve floor

Minimum reserve per week should trend up toward W13 when October RC label contractors quote in Q2—engineering deposits are not marketing trailer lines from October fest spend cap.

K5 — stop rules must name paths

Each stop_rules[] entry should include receipt_path or blog_url—ER3 cites forward #10 MERGE opinion, not "ask lead in DM."

K6 — verify before invoice approval

Approve contractor payments only after verify_march_engineering_runway.sh exit 0 and weekly column has remaining budget.

Printable sign-off card

# March engineering runway — weekly sign-off
iso_week: ______
weekly_engineering_cap_usd: ______
actual_spend_usd: ______
[ ] K1–K6 GREEN  [ ] jq weekly ER2  [ ] MERGE ER3 if branch work
Signed: __________  Date: __________

CI weekly verify sketch

name: march-engineering-runway-weekly
on:
  schedule:
    - cron: "0 10 * * 1"
jobs:
  verify:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: bash scripts/verify_march_engineering_runway.sh release-evidence/ops/march_engineering_runway_receipt_v1.json

Partner diligence zip

Attach march_engineering_runway_receipt_v1.json + cap table excerpt + verify log—pointer-first, not full bank statements.

verify_march_engineering_runway.sh (sketch)

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

jq -e '.schema == "march_engineering_runway_receipt_v1"' "$REC" || exit 1
jq -e '.weekly_caps | length >= 4' "$REC" || exit 1
jq -e '.engineering_runway_ok == true' "$REC" || exit 6

# K2 — amortization sum
jq -e '
  (.pager_overtime_total_usd // 0) as $p |
  ([.weekly_caps[].pager_amortized_usd] | add) as $a |
  $a <= $p + 1
' "$REC" || exit 2

# K3 — BUILD_RECEIPT parity
jq -e --slurpfile r "$REC" '
  .engineering_spend_planned == ($r[0].march_engineering_pool_usd)
  and .engineering_runway_ok == $r[0].engineering_runway_ok
' BUILD_RECEIPT.json || exit 3

# Closeout pointer
test -f "$(jq -r '.february_closeout_pointer' "$REC")" || exit 4

echo "march_engineering_runway verify: OK"

jq weekly cap sum check

jq -e '
  ([.weekly_caps[].cap_usd] | add) == .march_engineering_pool_usd
' march_engineering_runway_receipt_v1.json

PowerShell verify cousin

$r = Get-Content march_engineering_runway_receipt_v1.json | ConvertFrom-Json
if ($r.schema -ne "march_engineering_runway_receipt_v1") { exit 1 }
if ($r.weekly_caps.Count -lt 4) { exit 1 }
if (-not $r.engineering_runway_ok) { exit 6 }
Write-Host "march_engineering_runway verify: OK"

Worked example — synthesized pager invoice spread

Producer rule: October prep quotes do not borrow from pager amortization rows without receipt amendment and producer sign-off.

January marketing vs March engineering comparison

Run both worksheets in March if marketing restarts—orthogonal columns.

Proof table

Scenarios A–G

Producer Monday workflow (15 minutes)

Block October prep deposits until W13 october_prep_reserve row has sufficient balance.

Micro-studio time budget

Cheaper than April "we cannot afford October RC contractor" after March pager paid in full Week 10.

Common mistakes

"December defer said FREEZE so engineering cash is zero."
FREEZE is scope—pager contractors still invoice in March; this worksheet caps those dollars.

"October fest cap already reserved engineering."
October pool reserves evidence line items at annual grain; March is weekly execution with pager amortization—different worksheets, both required.

"Founder can absorb pager hours unpaid."
Founder hours are not contractor invoices—if you paid overtime cash, K2 applies.

Counterarguments (honest limits)

"We already have October marketing cap."
Marketing pool ≠ engineering contractor cash post-fest—both can be true.

"Founder hours are free."
Pager overtime contractors are not—cash caps matter.

"Four weeks is too short."
Extend receipt with W14+ rows and amended pool—do not skip K1.

Outbound references

• BUILD_RECEIPT beginner pipeline — root row discipline
• Contractor vs hire fest week — role dollars cousin

Related GamineAI reads

• jq March weekly sprint
• January marketing spend cap
• October fest spend cap
• December engineering floor
• 5-night pager challenge
• Sunday February closeout
• 7-day March evidence sprint
• October RC label evening
• Creator key / press budget cap before October fest outreach — protects engineering float (K3/PR4) when T-90 press spend lands during patch season
• Localization Contractor Burn-Down Cap Worksheet Before October String Freeze — LQA/vendor pool; LR4 respects eng float

Key takeaways

1. March 2027 contractor pager overtime invoices collide with October prep engineering cash.
2. Four-week ISO cap table (W10–W13 example)—not annual runway math alone.
3. march_engineering_runway_receipt_v1.json + gates K1–K6 latch discipline.
4. engineering_runway_ok on BUILD_RECEIPT—orthogonal to marketing_spend_planned.
5. Pager amortization across weeks—K2 blocks lump-sum Week 10 panic.
6. october_prep_reserve_usd rows protect RC label quotes.
7. Stop rules ER1–ER5 wire jq weekly + MERGE exception opinion (#10 published).
8. Pair January marketing cap when both lanes spend in March.
9. December engineering floor cousin—hours vs this worksheet's cash.
10. verify_march_engineering_runway.sh gives CI one exit code.
11. Prereq: evidence sprint E7 + closeout pointer.
12. Friday March capstone expects engineering_runway_ok stable before april_content_update_allowed.
13. No invented runway months—worksheet uses explicit USD caps you defend weekly.
14. ER5 full stop when runway months drop below three—recompute October fest spend cap runway floor before any contractor week resumes.

FAQ

Is this the same as January marketing cap?

No—engineering contractor cash vs marketing cash; separate BUILD_RECEIPT columns and receipts.

Can we skip amortization and pay pager invoice immediately?

Only with receipt amendment lowering other columns—K2 fail-closed on hidden overrun.

How does jq weekly diff relate?

Weekly snapshot may include engineering_runway_ok; ER2 pauses invoices when jq weekly RED.

What if we have no pager overtime?

Set pager_overtime_total_usd: 0; shift caps toward October reserve—still file K1–K6.

Does October marketing cap cover engineering prep?

October fest spend cap reserves evidence/ops separately—this worksheet's october_prep_reserve is engineering contractor deposits.

When does MERGE opinion (#10) trigger?

ER3 when build_label bump appears in weekly diff without exception list—forward opinion before merge contractor week.

How does this relate to December engineering floor?

December floor capped founder hours during blackout; this worksheet caps contractor cash after fest—complementary, not interchangeable.

Can publishers advance against this receipt?

Yes—attach march_engineering_runway_receipt_v1.json showing amortization; advances should not bypass K2 lump-sum waiver without written amendment.

Should pager challenge nights appear in overtime_schedule?

Yes—reference 5-night pager receipt paths in notes when invoicing gameplay contractor hours tied to fest nights D1–D5.

RED / YELLOW / GREEN routing (K gates)

Document any K4 YELLOW waiver in receipt notes with producer sign-off date before October prep quotes proceed.

Closing

February fest pager weeks leave March invoices, not just jsonl annexes. Cap weekly engineering cash, amortize pager overtime across W10–W13, reserve October prep before Addressables and RC contractors quote in Q2, and file march_engineering_runway_receipt_v1.json so BUILD_RECEIPT shows engineering_runway_ok beside marketing rows. Beginners use the four-week table; producers run Monday approval gates; working devs wire verify + jq weekly ER2. Pair January marketing cap when both lanes spend in the same month—orthogonal columns, one diligence zip. During July–September patch + T-90 overlap, pair the press budget worksheet so creator seeding cannot silently raid engineering_patch_float. During actual upload week, switch from runway cash to October upload overtime caps: O1–O6 governs billable rebuild, smoke, caption, and setlive hours inside the release window. Prevention beats April engineering broke while October RC contractors wait; MERGE opinion and Friday March capstone expect stable runway truth before April content update authorization.