destroyulator/LANES/KICKOFF.md
Monster Robot Party c03bb85c9f Add parallel-lane execution specs for Opus 4.8
LANES/PLAN.md         — verdict, GODVERSE pipeline architecture, shared contracts, 3GOD security note
LANES/LANE1-*.md      — Godot: grab/slide/smash record ritual + find-the-misfiled-disc mode (owns game/)
LANES/LANE2-*.md      — meshgod cell-fracture stage + Destroyulator prop batch -> 3GOD (owns ~/meshgod)
LANES/LANE3-*.md      — thriftgod-based web smash toy, Rapier physics, 3GOD props (owns web/)
LANES/KICKOFF.md      — per-lane opening prompts + collision-safety rules

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-14 16:47:47 +10:00

2.2 KiB

KICKOFF — how to run the three lanes in parallel

Read PLAN.md first (verdict, architecture, shared contracts, the 3GOD security note). Then start each lane as its own Opus 4.8 session with the one-liner below. Each session's FIRST job is to read its lane file + PLAN.md, then execute.

Start each lane (paste as the session's opening prompt)

Lane 1 — Godot record ritual

Read ~/Documents/Destroyulator/LANES/PLAN.md then LANES/LANE1-godot-record-ritual.md and execute it fully. You own game/ only. Build the grab→slide→smash record ritual + the "find the misfiled disc" mode. Pass the headless smoke test before every commit; commit + push to origin main as you go.

Lane 2 — Asset pipeline / fracture

Read ~/Documents/Destroyulator/LANES/PLAN.md then LANES/LANE2-asset-pipeline-fracture.md and execute it. You own ~/Documents/meshgod (a separate repo). Add the cell-fracture stage, build the Destroyulator prop manifest, generate + fracture + push to 3GOD. CHECK THE fal CREDIT before any big batch; do the top-6 props first if it's tight. Commit to meshgod's remote.

Lane 3 — Web smash toy

Read ~/Documents/Destroyulator/LANES/PLAN.md then LANES/LANE3-web-smash-toy.md and execute it. You own web/ (new dir in the destroyulator monorepo). Fork thriftgod's FP interior into a browser smash toy with Rapier physics, 3GOD props, and a juice layer. Do NOT edit thriftgod. Commit + push to origin main under web/.

Collision safety

  • Lane 1 → writes game/ only. Lane 3 → writes web/ only. Lane 2 → writes ~/Documents/meshgod only (never game/; it delivers assets via 3GOD, and Lane 1 pulls approved GLBs in itself).
  • All push to the same remote ssh://git@100.71.119.27:222/monster/destroyulator.git (Lanes 1 & 3) — different top-level dirs, so no merge conflicts. Lane 2 pushes to its own meshgod remote.
  • If two lanes ever need the same file, STOP and coordinate through the human — don't guess.

Definition of done (whole plan)

Godot game has the record ritual + a playable mode; meshgod can fracture and has shipped the prop batch to 3GOD; the web toy is playable in-browser. Each lane green on its own acceptance test.