site_plan
Record, update or clear where a stored plan sits in your world—origin, yaw and footprint—without re-solving it, so maps and diffs can reference it.
Instructions
Record, update or clear WHERE a stored plan stands. Nothing is re-solved.
A plan stores what to build; this stores where -- origin (x, y and optionally z, in metres, at the footprint's centre), orientation (yaw about world Z, the same convention the save stores machine facing with), and footprint (width x depth, metres). The footprint defaults to the square plan_layout budgets for the plan's largest floor, and the record keeps track of whether it was measured or derived.
Once sited: plan recalls print the siting; diff_vs_save plan=<name> adds an
approximate what-stands-on-the-pad census; show_on_map at='plan:<name>'
centres a map link on the origin.
The siting is a RECORD of your decision, not a constraint on the solve -- re-running
the plan neither reads nor moves it, and save_as over the same name keeps it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| at | No | site origin (the footprint's CENTRE): 'x,y[,z]' in metres, 'me', a factory name, 'slab:<n>' or a run id. Blank keeps the stored origin | |
| plan | Yes | ||
| save | No | ||
| as_of | No | pin to one world state: a sav:… token from an earlier answer | |
| clear | No | ||
| world | No | ||
| yaw_deg | No | degrees about world Z, positive +X towards +Y; omit to keep | |
| base_rev | No | the plan version you read; needed to change an existing plan | |
| footprint | No | 'WxD' in metres ('96' = square). Blank keeps the stored one, or derives the layout's own square if none is stored |