ERZ
Eretzon
Denver, CO — modelled
Address in → feasibility package outDenver, CO — modelled

Address in. Feasibility package out — or an honest refusal.

A developer picks a market, types an address or parcel ID, and gets back the zoning rules that apply, the buildable envelope, a benchmarked cost range and the resulting numbers. A market is a way to browse and scope, not a unit of data: the address is resolved to its own local jurisdiction first — zoning in the US is a city and county function — and where that jurisdiction is not the market chosen, the platform renames both and answers with neither. Where the inputs to answer honestly are not in the database yet, the platform refuses and names every reason instead of returning a plausible-looking figure.

1 real parcel with a computed envelopeany address in Denver, CO answered live, plus 13 captured runs kept as the fallbackAcceptance harness: 9 of 9 at capture

Denver, CO — modelled — the reference market: district standards read out of the published Denver Zoning Code by hand, an ingested parcel register and zoning layer, and a cost band built from real City of Denver permit valuations

Berkeley, CA — reconnaissance only — no ordinance read, no zoning layer or parcel register ingested, no cost basis, and California's state layer unread Missing here: market_ordinance_unread, market_zoning_layer_not_ingested, market_parcel_layer_not_ingested, market_state_layer_unread, market_cost_basis_absent.

Outside the modelled markets — browse scope, not a data unit — an address anywhere the deployment does not model is refused by name, never priced with another market's numbers Missing here: market_not_modelled.

This field asks the engine about whatever you type — the engine runs on our own machine, this page's own server puts the question to it (your browser never reaches it, and nothing is computed in your browser), and every answer says where it came from: LIVE means the engine computed it when this page was built, CAPTURED means the engine could not be reached and the answer is one of the 13 real runs captured from that same engine on 10-07-2026 · 5:29 PM UTC at commit 1c90cb4, replayed verbatim. Under Denver, CO the captured inputs are 2323 curtis st · 2307 curtis st · 2307 curtis st mstr · 2323 curtis · 2307 curtis · 5800 tower road · 1100 congress ave, austin, tx 78701 · 0234219013000 · 0234219033999. Anything else gets an honest message rather than an invented package.

liveComputed by the engine just now, when this page was builtengine time 11-21-2026 · 9:11 PM UTCdataset denver-pilot-mixed · sourcedEretzon Denver pilot dataset — sourced Denver source rows (parcel register, zoning polygons and hand-read zoning code, commercial building permits) plus a labelled FIXTURE set of modelling-assumption rows
POST /projects/lookup{"address":"2307 curtis","market":"denver-co"}HTTP 200status: manual_review_requireddata_quality: sourced
dataset denver-pilot-mixedcomputed 11-21-2026 · 9:11 PM UTC

Eretzon Denver pilot dataset — sourced Denver source rows (parcel register, zoning polygons and hand-read zoning code, commercial building permits) plus a labelled FIXTURE set of modelling-assumption rows

Figures marked data_quality='sourced' or 'verified' come from a cited source (see the source_name/source_url/source_note fields on the referenced rows). Figures marked 'fixture' or 'user_supplied' remain placeholders. Estimates are ranges, not guarantees.

INPUT PROVENANCE (read off the records this response carries, not off a dataset label): of the 2 inputs that reached a figure, 2 are sourced (the parcel record; zoning_districts row 3206). No input in this response is a placeholder: nothing here is invented, and every labelled input above is either sourced or derived from a cited dataset. Estimates are ranges, not guarantees.

What resolved

2307 curtis resolved to a real parcel — and then the engine stopped.

Resolved parcel
0234219033999
2307 CURTIS ST MSTR · COMMERCIAL-CONDOMINIUM · 51 existing units
Address resolution
3 match
parcel_address_key — matched on the register's address components (number=2307, street=CURTIS, suffix=inferred, directional=inferred)
District
C-MX-5
Mixed Use (MX, M-GMX) · 2010 code · use-form MX
Site
12,623 sq ft
frontage 125.54 ft · overlay none

The address is ambiguous: the register holds 3 records at it

this address maps to 3 parcel records. The answer below is for the master parcel 0234219033999; pass that parcel_id (or another from the candidate list) to answer for a specific one.

  • 02342190330332307 CURTIS ST R-1

    unit R-1 · land 11,739 sqft · C-MX-5 · prop class 9237 (RESIDENTIAL-MULTI UNIT APTS) · 51 existing units · sourced

  • 02342190339992307 CURTIS ST MSTRthe one this run answers for

    unit MSTR · land 12,623 sqft · C-MX-5 · prop class null (COMMERCIAL-CONDOMINIUM) · 51 existing units · sourced

  • 02342190340342307 CURTIS ST NR-1

    unit NR-1 · land 884 sqft · C-MX-5 · prop class 9259 (COMMERCIAL-CONDOMINIUM) · 51 existing units · sourced

The engine chose. no master parcel could be identified among 3 records at this address (each looks like a unit record), so the largest land area was taken as a provisional site. This is a guess about intent and must be confirmed: pass parcel_id to answer for a specific parcel.

Inferred to match: the address carries no street suffix; the register's 'ST' was used.

Refused for 2 named reasons

Each reason is the engine's own, with the code that raised it. Nothing numeric was returned.

  • boundary_shared_with_other_parcelshighboundary_shared_parcel_count, boundary_shared_parcel_ids, matching_records_shown, boundary_source_note

    the parcel register holds this exact stored boundary against 2 other parcel record(s) (0234219033033, 0234219034034). This is a condominium or unit stack: every unit's record carries the whole building's polygon, so the units all inherit the parent footprint's frontage and none of them has a lot of its own. An envelope built from that frontage would be the building's, attributed to one unit.

    evidence
    {
      "boundary_shared_parcel_count": 2,
      "boundary_shared_parcel_ids": [
        "0234219033033",
        "0234219034034"
      ],
      "matching_records_shown": 2,
      "boundary_source_note": "source=City and County of Denver parcel register; layer_id=245; url=https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_PROP_PARCELS_A/FeatureServer/245; vintage=2026-09-27; read=2026-09-28; fields=geometry_geojson,shape_area_sqft,shape_length_ft; shared_boundary_method=identical_stored_geometry; mean_width_method=register_shape_area_over_perimeter; sliver_criterion=mean_width_ft<5.000; read_from=stored_register_record"
    }
  • cost_baseline_not_sourcedwarningcity, building_type, baseline_data_quality, baseline_row_id, baseline_source_name, baseline_source_url, label_carried_on

    the construction cost basis that priced this response is ours, not market data: it is labelled 'derived' and we derived it from City and County of Denver — Commercial Construction Permits (daily extract from the Accela database) — 317, retrieved 2026-09-29. The city published the data underneath the figure; nobody published the figure. Its limits and its citation travel with it on this response (cost.baseline, and the cost_baselines record in the provenance), and it is a screening range for advancing or killing a site — not a bid, a budget or an engineering figure. Reported rather than refused because the basis is specified, cited and labelled: the envelope and the money may be computed, and the flag stays visible next to them.

    evidence
    {
      "city": "Denver",
      "building_type": "multifamily_5over2",
      "baseline_data_quality": "derived",
      "baseline_row_id": 7,
      "baseline_source_name": "City and County of Denver — Commercial Construction Permits (daily extract from the Accela database) — 317, retrieved 2026-09-29",
      "baseline_source_url": "https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_DEV_COMMERCIALCONSTPERMIT_P/FeatureServer/317/query",
      "label_carried_on": "cost.baseline.source_note"
    }

Nothing numeric was returned

envelope
null
cost
null
feasibility
null
sensitivity
null

The cost basis for this run is our own derivation from a cited dataset, not a published figure. It is reported as a flag rather than a refusal: the basis is specified, cited and labelled, and the label travels with the number.

Rules status for C-MX-5: not_transcribed

1 district rule row is transcribed in this deployment; the engine answered the district identity from the city's zoning layer and then refused, rather than fall back on another district's numbers.

max_dwelling_units_per_acremax_farmax_height_ftmax_lot_coverage_pctmax_storiesmin_front_setback_ftmin_lot_area_sqftmin_parking_ratiomin_rear_setback_ftmin_side_setback_ft

Protected District (§C): the 175 ft condition does not bite

C-MX-5 caps height within 175 ft of a Protected District at 75 ft, which binds the 95 ft incentive height rather than the 70 ft base. Whether that cap applies to this site is measured against the city's own polygons by the engine — never assumed, and never left to the reader to apply.

Verdict
does not bite
established true · applied true · bites false · refused false
Nearest Protected District
562.55 ft
U-RH-2.5 — shortest boundary-to-boundary distance from this parcel's own zone lot polygon to the nearest mapped protected polygon
Margin against 175 ft
387.55 ft
the measured distance is outside the threshold by this much · within tolerance of the threshold false
Measurement tolerance
0.0087 ft
computed from the geometries this measurement used, not chosen — round-off of the stored coordinates plus the projection's differential scale error. What it does not cover is stated in full below
Polygons the measurement read
130 measured
1 excluded as the site's own district polygon — a site cannot be its own protected neighbour
Protected polygons within 175 ft
0
none — nothing protected is inside the threshold
Unclassifiable polygons within 175 ft
0
none — every polygon inside the threshold was classified, so nothing was unreadable
Nearest polygon of any kind
D-AS-12+ at 44.71 ft
not_protected — 2010-code district, not named in DZC Art. 13 Div. 13.3's flat enumerated list (the definition has no character test)

The 175 ft line is ours, not the code's. the code fixes no line for the 175 ft: Article 13 was searched in full and the rule says what is capped ('all portions of a Structure … within 175 feet of a Protected District') without saying from or to what the distance runs. The line used here is OURS — the shortest horizontal distance from the parcel's zone lot polygon to the mapped protected-district polygon — and it can only over-trigger, which is the safe direction.

The nearest polygon of any kind is not_protected. D-AS-12+ at 44.71 ft: 2010-code district, not named in DZC Art. 13 Div. 13.3's flat enumerated list (the definition has no character test). A district the rule does not name cannot trigger it, however close it is.

The engine's own statement. the nearest protected district is U-RH-2.5 at 562.6 ft, outside the 175 ft threshold by 387.6 ft (measurement tolerance 0.009 ft), so the condition does not bite

the rule as printed, how the distance was measured, the tolerance in full, and the engine's own 3 documented limits

The rule the condition comes from. Denver Zoning Code §13.1.3.4.B (printed 13.1-13), 'Feet, within 175 feet of Protected District (max)': "Height of all portions of a Structure, developed with or without height incentives, that is within 175 feet of a Protected District shall not exceed the maximum height specified in the applicable building form table." For C-MX-5 that maximum is 75 ft (Article 7, §7.3.3, GENERAL building form table, printed 7.3-13), which binds the 95 ft incentive height, not the 70 ft base.

How we measured it. our conservative reading (the code defines no line for the 175 ft): the shortest horizontal boundary-to-boundary distance between the parcel's zone lot polygon and the mapped protected-district polygon, in a local equirectangular projection (lon x 111320 x cos(lat), lat x 110540, to metres; x 3.280839895 to feet). The code tests the structure and states the condition 'with or without height incentives'; measuring from the zone lot instead of the as-designed structure can only over-trigger, and a parcel that over-triggers is refused — the safe direction.

the search radius is a scope, not a threshold: the condition is decided at 175 ft, and a polygon within that distance of the site always has a bounding box within it of the site's, so the verdict does not depend on the radius

The tolerance, in the engine's own words. the tolerance is computed from the geometries this measurement used: round-off of the stored coordinates at the decimal places actually stored on the two polygons, plus the differential scale error of the local projection across the latitude span between them — 0.0087 ft for this pair. the tolerance covers the arithmetic of this measurement — the round-off of the coordinates as stored, and the differential scale error of the local projection over the latitude span actually measured. It does NOT cover the positional accuracy of the two publishers' geometries, which neither layer states; the measurement is as good as the two layers are, and that is why a distance inside the tolerance of the threshold is refused rather than answered.

  • the 'adjacent to Protected District' setback rows are subsumed by this test: anything adjacent to a protected district is within 175 ft of it, so they cannot bite on a parcel that passes the distance test. The nuance the code states — an intervening alley (public or private) preserves adjacency, an intervening named or numbered street destroys it — is not modelled: there is no alley right-of-way layer, and this is carried as a limitation rather than assumed away.
  • a height incentive (e.g. C-MX-5: 7 stories / 95 ft under Sec. 10.12.1) is recorded on the rule row and is never applied by this version: it is opt-in, and where the 175 ft cap applies the incentive path is removed — the cap binds the incentive height, not the base.
  • the tolerance covers the arithmetic of this measurement — the round-off of the coordinates as stored, and the differential scale error of the local projection over the latitude span actually measured. It does NOT cover the positional accuracy of the two publishers' geometries, which neither layer states; the measurement is as good as the two layers are, and that is why a distance inside the tolerance of the threshold is refused rather than answered.

the protected-district list, classified on the polygons themselves · Denver Zoning Code, June 25, 2010 | republished February 25, 2025
Denver Zoning Code, Article 13 (Rules of Measurement & Definitions), Division 13.3 (Definition of Words, Terms and Phrases), printed page 13.3-27 — 31 enumerated districts plus item 32; Former Chapter 59 §59-96(a) (printed p. 137) for the seven Former Chapter 59 'protected districts'
what was classified, when, and by whom · definition read by researcher (read 2026-09-29; evidence raw/protected-district-def-13.3-27.png)
zoning polygon layer vintage 2026-06-02; classified in our database on 2026-10-06; definition read: researcher (read 2026-09-29; evidence raw/protected-district-def-13.3-27.png)

Every record that reached the answer is cited (2)

Table, row, what it decided, how good it is and where it came from — the citation chain the engine attaches to every response.

TableRowWhat it decidedQualitySource
parcels14777site geometry and site factssourcedCity and County of Denver — Parcels (ODC_PROP_PARCELS_A layer 245) · layer 245 · read 09-27-2026
zoning_districts3206district identity used to decide whether standards could be appliedsourcedCity and County of Denver — Zoning (CCD_Zoning layer 27) · layer 27 · read 06-02-2026

Dataset denver-pilot-mixed — Eretzon Denver pilot dataset — sourced Denver source rows (parcel register, zoning polygons and hand-read zoning code, commercial building permits) plus a labelled FIXTURE set of modelling-assumption rows

modelling assumptions used (0, of which 0 are still labelled fixture)

    engine_versions {"zoning":"0.1.0","envelope":"0.1.0","cost":"0.1.0","feasibility":"0.1.0","orchestrator":"0.1.0"} · run took 656 ms · project_id · computed live by the engine when this page was built, against the deployment's own database

    Denver, CO — modelled — the reference market: district standards read out of the published Denver Zoning Code by hand, an ingested parcel register and zoning layer, and a cost band built from real City of Denver permit valuations. The engine confirmed the scope: this address resolved to Denver, the market denver-co. market=denver-co travels in the URL with the address.

    Compare with 2323 Curtis St →The same angle, the other Curtis Street address: both in C-MX-5 on CURTIS ST, one returning a full envelope and the other a refusal with its reasons named.

    Every figure, reason code, row id and citation below was returned by the running API or derived from the live database — this page does not type its numbers by hand. A LIVE answer was computed by the engine when this page was built; a CAPTURED one was captured from that same engine on 10-07-2026 · 1:26 PM UTC at commit 409ad7a, and every answer says which of the two it is. Three things here are written by us rather than generated, and we would rather name them than let the sentence above cover them: the acceptance count in the pill (nine checks in scripts/acceptance_denver.py, which the snapshot generator refuses to write past if any of them fails), the count of district codes holding no relief-free parcel, and the prose — including “What is not built yet”, which is a list of what we have not done. The market list in the dropdown is not written by us at all: it is the engine's own GET /markets response, captured with the runs, so the coverage claim on the page — one market modelled, one in reconnaissance — is the engine's claim, not our wording.

    That one envelope parcel is 2323 Curtis St — a single register record in C-MX-5. Its figures are what the district's rules allow on the site, not a survey of what is there today: the note directly above the numbers says what the register records on it.

    What comes back
    envelope · cost · feasibility
    footprint, height, floor area, unit count, parking, then a cost range — all from the rules that actually apply to the parcel
    When we cannot answer
    refuse, and name why
    a missing standard, an unmeasured frontage or an unresolved overlay stops the number rather than guessing it
    Every record is cited
    source · vintage · read date
    no figure reaches a response without the row it came from, labelled by how good that row is
    The flow that works today

    One real address, run end to end

    This is the acceptance case: the owner's own address, run through the real pipeline and checked by an automated harness. It is deliberately the hard case — a pre-2010 district with an overlay, waivers, a use-form sentinel and no published frontage — so the refusal is the feature, not a failure.

    POST /projects{"address": "5800 Tower Road, Denver, CO 80249"}status: manual_review_requiredHTTP 201
    Resolved parcel
    0010208160000
    5800 N TOWER RD · RESIDENTIAL-MULTI UNIT APTS · 120 units existing
    Address resolution
    152 candidates
    parcel_address_key; the master parcel was selected from the unit records and the choice is reported back
    District
    C-MU-20
    Former Chapter 59 Zone · code vintage 1956 · ordinance 131/2000
    Site
    264,461 sq ft
    frontage: no value — this parcel is outside the C-MX-5 measurement scope
    Overlay
    AIO
    an overlay changes which standards apply
    Waivers / conditions
    WVRS · *
    site-specific relief granted by ordinance
    Use-form code
    999
    999 is the sentinel for ‘not a 2010 building form’
    Parcel ↔ polygon
    agree
    register says C-MU-20, polygon says C-MU-20

    Refused for 7 named reasons

    • rules_not_transcribedhigh

      the numeric standards for this district (setbacks, lot coverage, FAR, height in feet, minimum parking) have not been transcribed into zoning_rules yet, and no US city publishes them as data. No limit is invented here: the district identity below is what the data supports.

    • former_chapter_59_districthigh

      this is a Former Chapter 59 (pre-2010) district. It sits outside the 2010 Denver Zoning Code building-form standards, so the modern standards do not govern the site — applying them would be confidently wrong.

    • overlay_districthigh

      the parcel is inside an overlay district. An overlay changes the standards that apply, and its provisions are not modelled, so the base-district numbers (even once transcribed) would not be the whole answer.

    • waivers_or_conditionshigh

      the zoning layer records waivers and/or conditions against this site. Site-specific relief like this is granted by ordinance and must be read before any standard is applied.

    • zone_use_form_sentinelhigh

      the zoning layer gives this site the use-form code '999', its sentinel for 'not a 2010 building form'. A building-form standard cannot be selected from it.

    • lot_frontage_unknownhigh

      the parcel register does not publish a street frontage, and the front setback cannot be applied without one. Supply the frontage (or a surveyed site plan) rather than accept a footprint derived from a guess.

    • cost_baseline_not_sourcedwarning

      the construction cost basis that priced this response is ours, not market data: it is labelled 'derived' and we derived it from City and County of Denver — Commercial Construction Permits (daily extract from the Accela database) — 317, retrieved 2026-09-29. The city published the data underneath the figure; nobody published the figure. Its limits and its citation travel with it on this response (cost.baseline, and the cost_baselines record in the provenance), and it is a screening range for advancing or killing a site — not a bid, a budget or an engineering figure. Reported rather than refused because the basis is specified, cited and labelled: the envelope and the money may be computed, and the flag stays visible next to them.

    Nothing numeric was returned

    envelope
    null
    cost
    null
    feasibility
    null
    sensitivity
    null

    The cost basis for this run is our own derivation from a cited dataset, not a published figure. It is reported as a flag rather than a refusal: the basis is specified, cited and labelled, and the label travels with the number.

    The exact numbers still missing for this district

    Read back from the response — the standard must supply all of them, or the district gets no row at all:

    max_dwelling_units_per_acremax_farmax_height_ftmax_lot_coverage_pctmax_storiesmin_front_setback_ftmin_lot_area_sqftmin_parking_ratiomin_rear_setback_ftmin_side_setback_ft

    Every record that reached the answer is cited

    TableRowRecordQualitySource
    parcels83330010208160000 — 5800 N TOWER RDsourcedCity and County of Denver — Parcels (ODC_PROP_PARCELS_A layer 245) · layer 245 · read 09-27-2026
    zoning_districts3626C-MU-20 — Former Chapter 59 ZonesourcedCity and County of Denver — Zoning (CCD_Zoning layer 27) · layer 27 · read 06-02-2026

    INPUT PROVENANCE (read off the records this response carries, not off a dataset label): of the 2 inputs that reached a figure, 2 are sourced (the parcel record; zoning_districts row 3626). No input in this response is a placeholder: nothing here is invented, and every labelled input above is either sourced or derived from a cited dataset. Estimates are ranges, not guarantees.

    What the database already holds

    Real counts from the primary pilot scope

    These are the numbers that decide which district can produce a first answer, and they are generated by a script against the live database rather than typed into a slide.

    12,407
    parcels in the pilot scope
    all with stored boundary geometry
    92%
    on the current 2010 code
    11,418 on the 2010 code; of the rest, 988 are Former Chapter 59 and one joins to no zoning polygon
    6,560
    relief-free parcels
    no overlay, waiver, PUD or former-code flag
    180
    parcel ↔ polygon disagreements
    surfaced and refused, not hidden — 1.45% of the scope
    District codes present
    66
    of which 41 hold no relief-free parcel at all and can never produce an envelope
    Former Chapter 59
    988
    pre-2010 ground we deliberately never transcribe
    Joined to a polygon
    12,406 of 12,407
    1 joined to none, 3 with nothing checkable
    Scope
    central mixed-use corridor
    bbox -104.99, 39.74, -104.955, 39.77 — the densest current-code mixed-use ground in the city

    Why parcels are held back from an answer

    A parcel carrying any of these is refused rather than modelled, because each one changes what the code means for that site.

    • 988former_chapter_59_district
    • 4,391overlay_district
    • 218planned_unit_development
    • 737waivers_or_conditions
    • 1,866zone_use_form_sentinel

    Street frontage: measured for C-MX-5, with two things we will not smooth over

    The Denver parcel register publishes no frontage field of any kind, so every frontage in the database is ours: the street-facing lot edge, measured against the city's own street centrelines, with the source, the tolerance and the method labelled on every single value. For C-MX-5, 395 of 455 parcels now carry one; 60 carry none and a named reason (no_parallel_street_edge), because a zero would be a wrong number wearing a number's clothes. Range so far: 2–465.49 ft, median 122.42 ft.

    • Some "parcels" are not sites. The smallest readings are honest geometry on land nobody can build on: 0227129055000 (3721 N MARION ST APPRX) is 2 ft; 0235514036000 (2200 E 18TH AVE APPRX) is 2 ft; 0234921021000 (605 E 16TH AVE) is 15.4 ft. The edge genuinely exists and genuinely faces the street, so the measurement is right and the site is wrong. We did not invent a minimum plausibility bound to hide them — that would mean retuning a tolerance we derived from the data, and every number above would have to be re-measured.
    • Many "lots" are stacks. 178 of 455 parcels share their stored boundary with at least one other parcel — 292 distinct boundaries among them, the largest group being 62 parcels on one boundary. These are condominium and unit stacks, so each unit inherits the parent footprint's frontage: honest as geometry, misleading as "the lot". Both this and the strips above now refuse with their own named reason — boundary_shared_with_other_parcels and recorded_boundary_not_a_site — rather than being modelled from a frontage that measures the parent footprint. The 2307 Curtis St run on this page is one of them.

    Measurement is C-MX-5-only so far: 395 of 12,407 corridor parcels and 0 of 9,141 in the airport scope. The rest still refuse with lot_frontage_unknown — which is why the acceptance case above still refuses. 5 frontage values in the database are still fixture test rows, not measurements, and are labelled as such.

    The district the first numbers come from

    C-MX-5, the district those runs came out of

    C-MX-5, in the central corridor: the district the first numbers come from, spread across the district rather than concentrated on one block. It is not the largest code in scope — C-MX-12 holds 456 parcels to C-MX-5's 455 — but all 456 of C-MX-12's carry an overlay and none of them is relief-free, while 204 of C-MX-5's are.

    455
    C-MX-5 parcels
    204 of them relief-free
    29
    city zoning polygons
    the number of C-MX-5 polygons in scope — a polygon count, not a claim that the table is uniform: the same district still carries per-form numbers and overlays
    3
    register disagreements
    out of 455 — each one refused with both codes named
    22 + 78
    further relief-free parcels
    each a SEPARATE district needing its own read — the C-MX-5 row names C-MX-3 and G-MX-3 as not covered, so these are reachable work, not a free extension
    If that table does not read clean
    U-MX-3
    122 relief-free of 135 parcels, with zero register disagreements
    Rule for every district
    no row unless every value is read
    each required value must be either a single unconditional number, or one the code positively states none of — the engine records that second case as stated_absent and says so in the answer. A half-read district gets no row, because a guess would turn a refusal into a number
    Honest status

    What is not built yet

    Listed plainly, because the value of this page is that it does not overstate where the product is.

    PieceStateWhat it is waiting on
    Address → parcel → district → refusalworksNothing. This is the flow shown above, checked by the harness on every run.
    Zoning rules for C-MX-5worksThe GENERAL building-form row was read out of the published code by hand and is loaded live with its citation, effective date and the cells the code states absent. It prices every run the search box answers. C-MX-5's other building forms are carried verbatim rather than averaged into the answer. The site-conditional Protected District rows are computed, not carried: every ingested zoning polygon is classified against the code's own enumerated list, the distance from the site's own zone lot polygon to the nearest protected polygon is measured to that measurement's own stated tolerance, and the parcel is refused where the 175 ft cap bites — or where the condition cannot be established.
    Street frontagein progressMeasured for C-MX-5 only: 395 of 455 parcels, 60 with a named reason and no value. The rest of the corridor still has none. The two data-quality cases above no longer publish a frontage at all — they refuse with their own named reasons, boundary_shared_with_other_parcels and recorded_boundary_not_a_site.
    Cost benchmarkin progressA derived band read from real City of Denver commercial construction permits, labelled 'derived' and carried with its citation on every response. The modelling assumptions underneath it — average unit size, net-to-gross efficiency, storey height, parking areas — are still fixture rows, which is why the cost-bearing packages above are labelled 'mixed' and carry a high-severity fixture flag.
    Buildable envelopeworksComputed for C-MX-5 today: units, floor area, storeys, height, footprint, frontage and parking all come back in the runs above, each with the constraint that bound it and every caveat attached.
    Feasibility numbers + risk flagsworksThe cost band, the $/unit figures, the sensitivity band and the risk flags all come back with the envelope. Missing limits are reported as data flags, never filled in — and the high-severity fixture flag stays on the package until those assumption rows are sourced.
    Marketsin progress3 markets are listed and all but one refuse by name. Denver, CO is modelled — the reference market, the only one with transcribed district standards, ingested layers and a cost basis. Berkeley, CA: reconnaissance only — no ordinance read, no zoning layer or parcel register ingested, no cost basis, and California's state layer unread; Outside the modelled markets: browse scope, not a data unit — an address anywhere the deployment does not model is refused by name, never priced with another market's numbers. The list itself is the engine's own GET /markets response, captured with the runs, so a market can only be described as the engine describes it.
    Search in the browserin progressThe market dropdown and the field at the top answer a fixed set of 13 runs produced by the real engine and captured verbatim, each filed under the market it was asked in, and the page says so in the answer itself. A market whose data this deployment does not hold cannot be answered at all — the engine refuses it by name, and the page shows that refusal rather than a package borrowed from Denver. Answering an arbitrary address needs the API hosted, which we are not paying for yet.
    PDF report, share link, accounts, saved projectsnot startedAfter the first computed envelope.