PI-PROT-DISTRICT R04 / CURRENT WORKFLOW
01 INTAKE + ATLAS
[ ] Exact approved board/creator decisions and game edition linked.
[ ] Every associated location, touching scene/route, kit and issue extracted.
[ ] Selected/deferred/unresolved scene scope recorded; atlas pixels not used as engine coordinates.
02 FRAME
[ ] Units, axes, origin, datum and each crop transform recorded.
[ ] Three control points and both shared connection endpoints verified.
03 MODERNIZATION
[ ] Preserve/upgrade/avoid; architecture/culture/public realm/technology/era stated.
[ ] Behaviors have source, trigger, response, owner and test scope.
04 MASTER + CONTEXT / GATE A
[ ] Master and full individual images; aerial/orbit/player-height/night roles accounted for.
[ ] Reference consistency checked; controlling source and discrepancies recorded.
[ ] Identity/modernization/preliminary kit approval names exact revision.
05 LAYOUT + 06 TOPOGRAPHY / GATE B
[ ] Roads/parcels/footprints/heights/entrances/service routes authored.
[ ] Plan and two spatial exports come from the same layout/model.
[ ] Shore/ground/landing transitions and sections are buildable.
[ ] Atlas requirements fit or carry an assigned issue.
07 ASSET KIT
[ ] Reuse/new tasks scoped; global asset IDs separate from placement/location/room IDs.
[ ] Dimensions, source, exports, materials, provenance and model-ready status recorded.
08 BUILDING PACKS / R05
[ ] Per-building A-E scope; plans/room/door records and atlas mapping.
[ ] Shell review before final fit; final window views site-verified or neutral.
09 ENGINE + LAUNCHER
[ ] Sources, project/map paths, import/build order and targets supplied.
[ ] Launcher readiness recorded honestly; reviewed command fallback if unverified.
[ ] Job success/failure/cancel/repeatability and district resolution proven before automation claims.
10 BLOCKOUT + SAMPLE / GATE C
[ ] Spatial fit/access verified and discrepancies resolved for sample.
[ ] Matched views, modernization behavior and selected atlas route/space checks.
[ ] Creative/technical acceptance and performance evidence at same revision.
11 EXPANSION + QA
[ ] Every planned item built/deferred/out-of-scope with reason.
[ ] Requirements map to actual implementation and evidence; changes approved as relevant.
12 RELEASE
[ ] Sources, manifest, tests, captures, remaining work and recovery history retained.
[ ] Atlas build evidence/production registry/district page/archive revision synchronized.
[ ] Design/layout/shell/interior/engine/publication/launcher statuses separate.

15 OCTOBER RELEASE CHECKS
[ ] Current family/revision resolved through current.json.
[ ] Required aerial/orbit and measured-view coverage indexed.
[ ] Dimensions, clear room sizes and shell/core fit reviewed at recorded status.
[ ] Shared frame and both ends of neighbor connections reconciled.
[ ] Developer / base shell / kit / appearance / placement identities recorded.
[ ] Package inventory, files, hashes, revisions and ZIP integrity verified.
[ ] Current engine commit/map inspected; source footprints are not claimed as built models.
[ ] Launcher and multiplayer capacity remain unverified until measured tests pass.
