Rehearse the approval before you file.

Product

Run a rehearsal

Pick a venue and step through a review the way the engine runs it. Objections pin themselves to Lot 15 as the simulated agency raises them. You answer each one with one of four responses, the referee decides what closes, and the run ends with a result card. This is the Review Room staff would use in Land Explorer, on a daylight satellite plan of the real lot. Every scenario here is an example, not a real run.

How it works

Two teams, one engine, one referee

The pro team on the left proposes and answers. The regulator team on the right challenges, grouped the way Michigan authorities actually work: the township's own review cluster, the bodies that vote, the county and state agencies you apply to separately, and the building department. In the middle sits the machinery that keeps the contest honest. The engine owns every number and every state change. The referee decides which objections and answers count. You sit at the bottom, in the Review Room.

Select any node to open its role card beside it; Esc closes it. Every card is also in the roster tables further down. On a phone, scroll the diagram sideways.

One round

Twelve steps from a saved project to a result card

This is one review round on one venue, such as the county road commission's driveway permit. The same machinery runs for zoning, health, soil erosion and the building department. Only the rule pack and the authority change. Use Next, or press Play.

Thousands of runs

Where the thousands actually go

Your instinct to test a design thousands of times is right. The research says where to spend them. Repeated runs of the same language model are correlated, drift toward the same answers and cannot be replayed by a seed. So the thousands run in code, on seeded engines, and agents work where judgment is needed. Six layers do the work.

Network effects

Every real outcome makes the next project cheaper

Regulation is layered: one state code, then county agencies, then each township. Onboard a county once and its road, health and drain packs serve every township in it. Each real letter, permit and inspection result calibrates the authority that issued it, so the next project there starts with fewer surprises. The flywheel only turns on real outcomes. Until those are logged, the system has data, not network effects.

Roadmap

Prove it on one real lot first

Each phase names one outcome, an owner, what it excludes, and the gate to the next. Local proof is reported separately from signed-in live acceptance.