How I Build a Reproducible Spatial Prototype With Tripo3D Shapezo InfraWorks Archshaper and Cityweft

I learned that a 3D prototype becomes difficult to debug when every model arrives with the same label: draft. A generated object, a map-derived site scene, regional infrastructure, building mass, and city context have different sources, risks, and useful outputs.
This is the lightweight workflow I use to keep Tripo3D, Shapezo, InfraWorks, Archshaper, and Cityweft traceable.

Define five artifact types before importing anything

I start by giving each file one purpose. Tripo3D is an object artifact. Shapezo is generated selected-area context. InfraWorks is regional infrastructure context. Archshaper is conceptual building form. Cityweft is connected urban context.
The name determines the pre-export checks: scale and origin for Tripo3D, selection boundary for Shapezo, coordinates and dates for InfraWorks, form constraints for Archshaper, and scenario extent for Cityweft.

Keep a small artifact record beside the model

I use a plain text or JSON sidecar file. The schema is deliberately boring:

• artifact name and version
• tool and export date
• source, prompt, rule set, or input layers
• coordinate reference, units, and origin
• area boundary or geographic extent
• status and next allowed use I keep the record beside the exported artifact, not in a separate meeting note. That makes review more repeatable. When a file changes, its record changes in the same commit or handoff folder. I can then tell whether a difference came from a changed map extent, a new object source, an infrastructure layer, or a revised building assumption. For Shapezo, the record includes the selected polygon, date, and a generated-context status. I draw a boundary around an area, then AI generates a model for that selected area. The record stops inferred geometry being mistaken for a surveyed feature. ## Build from the largest constraints inward I look at InfraWorks early when transport, water, terrain, or corridor access could shape the project. The goal is to establish constraints a smaller site model must respect: grades, crossings, road hierarchy, rail geometry, drainage routes, and major networks. Then I use Cityweft to inspect the urban side: where movement comes from, how blocks connect, and whether a new edge interrupts the local pattern.

Add the selected-area model without inflating its status

Shapezo is useful when I need a quick model of a specific location. I select the area on a map and let AI generate the model inside that boundary. I use it for provisional adjacency and spatial discussion, then compare important parts against trusted sources.
I do not export it as though it were a base survey. It belongs in a generated-context directory with a clear version. If it informs Archshaper massing, the record links to the selected-area version.

Treat building form as a constrained branch

Archshaper is where I turn a site question into a building-form question. I record boundary, access side, assumed grade, height range, setbacks, open-space target, and the context version used. That makes options comparable without pretending they are construction-ready.
When an option changes, I keep the previous version and a short reason. The answer is easier to find when an option has readable history.

Add Tripo3D assets late and label them clearly

I bring in Tripo3D after larger spatial relationships are in place. An object can clarify a review but should not decide the layout. For every asset I store prompt or reference, import scale, origin adjustment, and intended use. Edits create a new version.
The model may be a presentation object, temporary placeholder, or reviewed asset. Each label sets expectations for the next person.

Run a small handoff check

Before I send the prototype onward, I check five things:

• Does each file say whether it is generated, conceptual, contextual, or verified?
• Can I locate its map extent, prompt, rules, or input layers?
• Are coordinates, units, and origins explicit?
• Are the current versions of city and infrastructure context named?
• Does the next allowed use match the evidence behind the model? This workflow does not make early models more exact. It preserves why each model exists. The five tools remain compatible because they stay distinct, traceable artifacts instead of one undifferentiated scene.