Site & program
What can this site plausibly support?
- Parcel and acreage confidence
- Conceptual unit yield and parking
- What Site Fit cannot verify
Four learning tracks
What can this site plausibly support?
What is the right level of precision today?
Where did this number come from?
What changed, who reviewed it, and what happens next?
Cost reference hierarchy
DealVeto separates project evidence, licensed references, public signals, screening benchmarks, and assumptions. They are not interchangeable.
Pilot governance cadence
A versioned release note for benchmark, escalation, geography, and methodology changes.
Collect permitted customer actuals, licensed references, and official public signals
Normalize source date, geography, product type, units, and escalation basis
Review outliers, confidence, and construction-market relevance
Publish an effective date, version, change log, and validation notes
No silent rebasing. Existing deal versions keep their original cost basis until a user explicitly adopts a newer release.
Organization knowledge & AI safety
Retrieve from approved organization sources at answer time instead of training a shared model on raw customer files. This preserves citations, makes a source removable, and keeps the deterministic screen—not the language model—as the calculation authority.
Customer deal data is not used to train a shared cross-customer DealVeto model by default. Any exception follows an explicit, customer-specific governance path.
Put the guide to work