skills/planner5d-webmcp/references/picture-reconstruction.md

# Build from pictures and measured references

Use this for an exterior/room photo, a perspective render, a picture-led design, or a mixed plan/photo set. First distinguish a faithful reconstruction from a design inspired by the pictures. Preserve the user's intended result; do not call an approximate concept an exact replica.

## Establish what the sources prove

Keep a compact working map of source → room/floor/facade → facts. It is reasoning data, not a WebMCP payload.

| Evidence | What it supports |
| --- | --- |
| Dimensioned floorplan, measured coordinates or user measurements | Geometry with explicit units, scale, datum and dimension basis. |
| Exterior photo | Visible massing, roof silhouette, facade openings, materials and relative proportions in that view. |
| Interior photo | Visible furniture, finishes, local adjacencies and openings; not hidden rooms or complete dimensions. |
| Perspective render / inspiration image | Visible design intent; exact buildability, dimensions and hidden geometry remain unproven. |

Identify pages, versions and product variants before combining sources. A brochure's hero photo may illustrate a family rather than the selected size. Do not mix one variant's photo and another variant's dimensions without stating that the photo is an appearance reference. A photo of a printed plan is still a plan; a photo of a room is not. Select the actual plan pages/regions rather than sending a brochure, elevation sheet or room photo to floorplan recognition.

Mark facts as measured, observed, inferred or proposed. Keep a known plan as geometry authority and use photos for compatible visible detail. Resolve material conflicts in room/opening count or orientation before modifying existing geometry. An omitted feature in one view is not proof of absence behind an occlusion.

For exact reconstruction, obtain a plan or enough reliable dimensions and views to constrain the requested geometry. A single unscaled photo cannot establish building depth, hidden partitions or exact floor heights. Ask a concise question for the missing anchor/plan; meanwhile inspect available references and native capabilities without inventing geometry. For an explicitly approximate concept, choose sensible dimensions/layout and label them as assumptions. Do not use a guessed standard door or furniture size as a measured scale.

## Map the reference into one coordinate system

Use one ground-plane frame across all sources and floors. If compass direction is unknown, call a face front/back/left/right and record the chosen mapping to X/Y; do not infer north from shadows. Default 2D is X right, Y downward. Match persistent landmarks to link views; do not treat a mirrored image as another facade without evidence.

Pixels under perspective are not world lengths. Use known dimensions on the same plane, explicit source drawings or measured anchors. A scale inferred on the front wall does not automatically apply to the receding side wall. Distinguish wall-face dimensions, native reference paths, inner spans, roof overhangs, log/trim extremities and opening/frame sizes. For simple equal-wall rectangles, derived inner spans from known outer dimensions and thickness are assumptions to corroborate with area and native measurements, not values to relabel as directly measured.

## Build the shell before detail

Use native rooms/perimeter walls for enclosed spaces. When reliable source dimensions/areas are supplied, resolve the room-construction measurement check before placing openings, furnishings or finishes. A derived correct target written in the final answer is not an applied correction. Native wall paths need not sit at the physical mid-thickness, so do not blindly subtract half a wall width to derive them. Preserve one consistent floor alignment and actual access graph.

Use native floor creation/selection for additional stories. Read each floor's actual elevation, select the intended floor and refresh its revision before writes. Position/elevation arguments are not all world Z: distinguish floor-relative elevation from loaded world bounds. Multiple-floor 3D previews use the advertised all-floor visibility and can change the active floor; re-read context afterwards.

Attach doors/windows with native opening tools and inspect both the longitudinal center and model/frame extents. Window panes/sashes are not necessarily separate openings. Compare the candidate's leaf/pane divisions, resize access and material parts before placement, then verify that it becomes a real wall opening. Catalog candidate type may be generic `Ns`; placed object type and wall attachment are the evidence. Preserve glass separately from frame finishes. Unspecified clear aperture sizes remain approximate even when the model's overall dimensions are known.

For a roof, discover live roof catalog candidates and compare geometry in a contact sheet; do not invent a Pascal-style roof command. Read actual placement, loaded bounds, material slots and resize access. Treat catalog descriptions as shortlist hints: verify the actual profile in a side view before repeating a model. A curved/flared slope, offset ridge or extra wing can defeat a fit despite matching bounding dimensions. Match ridge direction, eave/ridge datums and overhangs. A roof's lowest bounding point is not necessarily its bearing height at the wall, especially with overhangs. Inspect for a floating roof, walls protruding through slopes, and open gable ends. When no suitable roof asset is available, a few native architectural elements can model planar slopes or gables; preserve ordinary rooms and disclose the substitution. After tilting an element, re-read its loaded bounds: its elevation property may locate the unrotated base, not the rotated lowest point. Do not replace a whole assembly repeatedly without identifying the mismatched profile. State approximations instead of hiding missing structure with camera angle. Check roof visibility before diagnosing an absent asset.

A stair model alone does not establish vertical access. Verify lower/upper landings, the upper-floor opening and usable travel/headroom. Overall bounds may include handrails rather than the top tread. Use matching native support/geometry evidence or the ordinary UI when needed. If the necessary opening/landing evidence or control is unavailable, state that connection as unverified rather than hiding an entire normal floor or claiming a walkable route.

For a separately modeled, empty stairwell, inspect its room-level `fhidden` property. The native control removes that room's visible floor and support surface; it is not an all-floor setting. Confirm the exact room outline and contents, preserve occupied-room and landing floors, then inspect the resulting void and overhead path. An opening formed between separate floor polygons need not appear in a surviving surface's `holes` array. This operation alone does not establish usable stairs, threshold contact or headroom.

## Furnish and finish from the images

Preserve source-relevant object proportions, facing and access; do not identify a brand/SKU from appearance alone. Compare shortlisted catalog assets before repeating them. Read exact product dimensions when supplied; otherwise state substitutions and estimated sizes. Use the clearance workflow for measured fit, not a screenshot estimate.

Match finishes through inspected material parts and native texture/UV controls. Lighting and white balance make sampled photo colors approximate. Preserve glass/metal/hardware rather than tinting the whole object. Prefer a suitable texture to dozens of decorative geometry strips. Roofs, stairs and facade parts may be `Ns`; classify by purpose, not that legacy type alone. Add grounds/landscape only within the requested scope; a background photo does not establish property boundaries.

## Verify against the source and hand off

For dimension/basis and opening-fit checks, read [room construction](room-construction.md), including during a read-only audit. The checks there are needed even when no construction or repair is requested.

For a reconstruction or fidelity audit, turn the defining source requirements into a short checklist before inspecting or building. Close each applicable row with evidence and passed/failed/unverified status; noticing one defect does not close the other rows:

| Requirement group | Evidence to reconcile |
| --- | --- |
| Shell size | Source dimension basis, native spans, area, thickness and heights. |
| Envelope | Roof profile/axis, overhang, wall contact and closure in revealing views. |
| Openings | Count, facade/room connection, horizontal **and vertical** fit, actual leaf/pane/glazing appearance. |
| Use and access | Intended room functions, entry routes, requested furniture fit; landing/opening evidence for stairs. |
| Visible finish | Relevant material parts and proportions against the picture, with substitutions identified. |
| Handoff | Useful requested views, validator limitations, restored view settings and any requested reload result. |

Omit inapplicable groups, such as roofs in an interior-only task. Within a group, a matching count or footprint does not pass its other properties. If evidence or time runs out, retain those properties as unverified in the handoff. For creation, repair failed defining checks before adding optional detail; for an audit, report them without mutating the scene.

For house/facade work, compare a matched exterior view, another angle that exposes depth/roof contact, and the relevant plan/floor views. For interior-only work, compare the requested room views and 2D arrangement without adding unrelated exterior work. Check geometry and visual features separately: correct room counts or a valid structure response do not prove photographic fidelity. Make unresolved, hidden and approximate details explicit.

Use public WebMCP where it expresses the operation; use the ordinary native UI for a real capability gap if the host supports it. Never substitute private editor state/API mutation. If the host lacks the needed UI/data-processing capability, return the concrete missing step and preserve valid work.

Return the verified project link, what matches each source, measured values and their basis, substitutions/proposals, and remaining checks. For an exact request, unresolved defining geometry means partial, even when the render looks convincing. For an approximate design, identify the assumed layout/scale. Apply the normal autosave and requested reload checks; do not promote a screenshot into persistence or engineering certification.