Project P.I.T.T. Build Library — Source-Labelled Planning Patterns
Build Library — Source-Labelled Planning Patterns: Browse product and phase planning patterns with startup, failure and validation checklists.
Browse product and phase planning patterns with startup, failure and validation checklists. They are not numerical optimizers or current-build-tested optimal factories.
Product-specific constraints
Choose the product before the layout goal. A Duck reference lane, a Cash Register landing, intact Piñata transport and Cauldron batching have different failure points.
Sources:
Observe, compact or recover
Keep a working reference before reducing footprint. For a jam, stop supply and identify the obstruction before introducing additional force or destructive cleanup.
Sources:
Phase and experimental references
The older phase sequence is explicitly labelled. Experimental Mag Rail discussion is a research lead, while official Cauldron composition remains a separate current fact.
Sources:
Evidence and verification limits
Source retrieval confirms what a source says, not a new in-game replay. Patch notes retain their version; community observations retain their limitations.
Evidence for this section (2)
OFFICIAL CURRENT · checked 2026-09-26
The official store describes making ducks, feeding the Maw and developing physics-based production lines.
Build relevance: Live Steam store checked September 26
SINGLE COMMUNITY REPORT · checked 2026-09-26
An older first-hand guide describes the sequence Duck, Cash Register, Piñata, Anomaly and illustrates their production lines.
Build relevance: Older full-release community observation; no independent 1.0.8 replay
Limit: No universal unlock quantities, optimal layouts or throughput are adopted.
Steam Community — achievement and strategy guide (older-build gameplay; not a 1.0.8 replay) ↗
Sources: Official Steam store page ↗ · Steam Community — achievement and strategy guide (older-build gameplay; not a 1.0.8 replay) ↗
Primary source: Official Steam store page ↗. Scope: full game.
A source-check date is not an in-game test date. Historical fixes and community observations retain their stated scope.