Identity resolution in this sample rests on an exact parcel match built from block/parcel identifiers and the shared coordinate chain, but it still does not replace final legal title verification.
Sample report · decision dossier
The Suadiye 347/50 sample Verify dossier is presented like underwriting infrastructure, not demo copy.
This sample is anchored to the Suadiye block 347 parcel 50 record and preserves the real system structure: manifest lineage, missing-field disclosure logic, and snapshot contract. Identity, cadastral geometry, zoning, and risk context are read in one dossier.
Identity confidence 0.97 · exact_parcel_match
Location Suadiye · Block 347 / Parcel 50
Risk context 1A seismic · ZD soil
Building model Ground retail · 4 residential floors · 26 units
Section 01
Dossier identity and snapshot frame.
EmlakIQ ID tr_34_kadikoy_suadiye_347_50
Snapshot ID dos_2026_06_sample
Resolution scope parcel + building
Address context Suadiye quarter · Bagdat Ave. / Akin St. / Osman Hizlan St. triangle · Kadikoy / Istanbul
Parcel reference Block 347 · Parcel 50
Coordinate set 40.9619-40.9625 N · 29.0774-29.0781 E
Sheet 82
Section 02 · Parcel view
The property identity is shown together with the parcel and building footprint.
Cadastral legend
Parcel boundary
Digital twin legend
Residential floor Ground retail
Title area 1,856.50 sqm
Title basis Construction servitude
Geometry summary 7 sides · 175.30 m perimeter
Floor stack Ground + 4 upper floors
Use pattern Retail at ground, residential above
Independent units 26 units
Section 03
Identity resolution and cross-product traceability.
Resolution status exact_parcel_match
Identity score 0.97
Building ID tr_bld_34_kadikoy_suadiye_347_50
Building basis construction servitude · 26 independent units
Manifest chain imar_ibb_2026_03 · afad_seismic_2018 · market_may_2026
Output class replayable dossier
Section 04
Zoning context is delivered without hiding source dates.
Field state known
Zoning function mixed_residential
Maximum height 21.5 m
FAR 2.07
Source date 2026-03-15
Section 05
The risk layer carries both the signal and the limitation.
Seismic zone 1A
Soil class ZD
Flood risk low
Method geospatial overlap + source grid join
Limitation not a structural safety certificate
Section 06
Market context quantifies the background behind a property decision.
Period 2026-05
District Kadikoy
Activity level high
Median sale value TRY 118,400/sqm
Year-over-year change 41.2%
Section 07 · Evidence chain
Fields are read together with batch and manifest references.
| Field | Source family | Operational note |
|---|---|---|
| Identity and geometry | TKGM / Cadastre + address resolution | source window 2026-06 · exact geometry lineage |
| Zoning fields | IBB / municipal zoning manifest | manifest:imar_ibb_2026_03 |
| Risk fields | AFAD seismic + MTA soil layers | manifest:afad_seismic_2018 |
| Market context | District-level market batch | manifest:market_may_2026 |
Section 08
Missing fields are carried into the decision note instead of being hidden.
Fields that are missing or below source-quality thresholds are not softened into positive assumptions.
energy_class
building_age_verified
earthquake_insurance_status
Section 09 · Committee note
The output does not only publish data, it also defines the interpretive boundary.
Energy class, verified building age, and earthquake insurance status are marked missing in this snapshot instead of being assumed.
Risk outputs are derived from geospatial joins and grid layers; they are not a building performance report.
Section 10 · Technical output
JSON and snapshot metadata are the machine interface of the same dossier.
GET /v1/property/resolve
200 OK Versioned payload Source trace Missing-field disclosure
{
"emlakiq_id": "tr_34_...",
"resolved_scope": "building",
"identity_confidence": "bounded",
"zoning": {
"status": "known",
"source_freshness": "2026-06-..."
},
"risk_context": {
"seismic_hazard": "available",
"confidence": "derived"
},
"market_context": {
"grain": "district_month",
"period": "2026-04"
},
"missing_fields": ["energy_class"],
"provenance_refs": ["source_manifest:..."],
"snapshot_id": "dos_..."
}Trust contract
Every output surface runs on the same evidence contract.
Control dimension Example display Why it matters
Identity resolution tr_34_kadikoy_bagdat_cad_0412 · building · confidence 0.84 Address, geometry, and parcel reference resolve into one property identity.
Snapshot contract snapshot dos_2026_06_sample · replayable dossier The same inputs can reproduce the same dossier deterministically.
Source manifests imar_ibb_2026_03 · afad_seismic_2018 · market_may_2026 Fields are served with the exact batch and source family behind them.
Freshness contract zoning 2026-03-15 · market 2026-05 · seismic 2018-12-01 Source date and load window stay explicit on the output surface.
Coverage and field state supported / partial / missing · known / inferred / missing Derived or missing fields are disclosed directly instead of being softened.
Decision outputs Verify report · Analyst queue · Radar view · API payload The same evidence contract is enforced across every product surface.
Machine-readable outputs
Reference artifact pack for external teams.
Next step