Skip to content

How we intend to build.

AeroTerra is developing an AI-native system for designing structured, explorable future cities. This page sets out the intended way of working — what a person does, what the system does in response, and where the line is. It describes intent and a plan, not a service we are selling and not behaviour you can use today.

In development

AeroTerra Version 1.0 Public Early Access targeted for November 1, 2026.

Concept diagram

The eight steps below are planned for Version 1.0. None of this exists yet, and none of it has been independently verified.

  1. A project begins with Coastal City — Remote Greenland, Ocean City — Offshore Honduras, or a synthetic blank canvas whose land, water, terrain and elevation you set yourself. The two regional environments are conceptual AeroTerra design canvases using real-world geography; their exact areas of interest remain to be defined after geospatial screening and are not selected sites or development proposals.

  2. Before describing anything, you fix the terms: a primary civilization class and an optional secondary influence, a population target, a minimum open-space share, a maximum building height, a private-car policy, a technology horizon, and a labour-automation scenario. Each is set as a hard requirement, a target, or a preference, so it is clear what may bend.

  3. You brief AERIS in your own words — a resilient coastal city, a dense district, a place organised around a different way of moving. An incomplete brief is expected: AERIS is designed to infer the most reasonable reading and get on with it rather than interrogate you, and to say afterwards what it assumed.

  4. Nothing is meant to change the city directly from a conversation. AERIS will produce a plan as data — the interpreted goal, the assumptions, the constraints and dependencies, the operations it intends to call, its checkpoints and the outcome it expects — which will then be checked against the project’s constraints, its locked objects and the current state of the city.

  5. A bounded set of AeroTerra operations will apply the plan to CityGraph, the structured model that is to hold what the city actually is: districts, blocks, parcels, buildings, open space, water, artificial islands, mobility, conceptual infrastructure, constraints and warnings. Each object is to have a stable identity, and every change is to be recorded as a transaction.

  6. From the model, procedural systems will lay out districts, subdivide blocks and parcels, generate mobility, mass the buildings, place open space and position the infrastructure the city depends on — shaped by the civilization class you chose. The render is to refer back to the model; it should never become the source of truth.

  7. You will move through the result with a free camera or from above, select major objects to inspect them, and keep going with further prompts or limited manual edits. A follow-up is meant to change the same city: the parts you did not raise are to be left as they were, and a change that breaks a dependency should offer to repair it rather than quietly redesigning around it.

  8. Large operations are to run as at most three checkpoints you can pause, adjust, stop or revert. Undo is to reverse a recorded changeset. Autosave is to leave a valid state after every committed edit. Projects are to save and reopen with their history, constraints and locks intact, and export to GLB/glTF, project JSON and PNG, with GeoJSON limited to top-level geographic objects.

The professional boundary

Version 1.0 is a conceptual city-design and early-planning environment. It does not replace licensed engineering, permitting, professional review, or detailed BIM or CAD authoring.

That boundary is a design decision, not a temporary gap. The figures a project produces — capacity, open-space share, district counts — are conceptual planning estimates, and each one is labelled as a target you set, a direct calculation from the model, an estimate, or not calculated. They are not structural, energy, environmental or economic conclusions, and none of that output is a basis for construction, procurement or approval.

Version 1.0 also performs no engineering-grade structural analysis, no validated energy or environmental simulation, and no economic validation; it reads no live telemetry or market data; and it does not integrate with municipal systems. The intended role is upstream of all of that: a place to think a city through before anyone commits to drawing it.

Where this is going

The near-term work is Version 1.0 — one release that proves a person can describe a city, receive it as a structured 3D environment, and keep editing that same city. What comes after it, including any analysis or simulation, depends on being able to validate it rather than on a roadmap date.

The planned Version 1.0 in full