Evidence coverage by decision type

Choosing a specific facility or plant location. requiredEvidence's core items are the 5 canonical criteria of the product's own purpose-built site-selection decision engine (analyze_place_decision, S-D1 — docs/HANDOFF-SD1.md); supporting items are persona 09's ('Site-selection consultants') own literal question in web/lib/stakeholder-docs/src/coverage.html: "Locations that maximize logistics efficiency: highway access, rail, ports, industrial land, labour availability, affordable wages, proximity to customers."

A business choosing a new city/county to expand into. Core items are persona 08's ('Business owners & expansion teams') own literal question in web/lib/stakeholder-docs/src/coverage.html: "Cities with growing income, increasing business formation, below-average lease rates, favourable municipal taxes, limited competition in my industry." Supporting items add standard market-sizing/workforce-availability context beyond that literal quote.

Choosing where to develop residential/industrial real estate. Core items are persona 06's ('Real-estate developers') own literal question in web/lib/stakeholder-docs/src/coverage.html: "Cities where household income grows faster than home prices, with rising industrial employment, low industrial vacancy, expanding infrastructure, and a shortage of serviced industrial land." Supporting items add the persona's own named gaps plus standard property-market context.

Place-level due diligence for an acquisition target's operating market(s) — regional growth, land cost, and competitive context. Company-specific financial/ownership diligence (revenue band, market share) is out of THIS registry's scope — see docs/HANDOFF-EVCOV1.md's known limitations; that capability is real and supported via screen_companies, just not modeled as a place_metric or decision_criterion. Core items are persona 01's ('Private equity & investors') own literal question in web/lib/stakeholder-docs/src/coverage.html: "Metros with GDP growth above national average, commercial land below comparable markets, population growth above 2%, engineering companies with $20-100M revenue, no competitor over 20% share." Grain is pinned to metro because this is the one persona question among all sourced personas that names "Metros" explicitly.

Underwriting/risk-context evaluation of a place — grounded in persona 14's ('Insurance companies') own literal question in web/lib/stakeholder-docs/src/coverage.html: "Municipalities combining high property values, increasing commercial development, climate exposure, infrastructure age, and employer concentration." Supporting items add the persona's own named gaps plus standard economic/social-vulnerability risk factors.

Assessing a place's workforce depth, cost, and dynamics — grounded in docs/HANDOFF-S5.md (the sprint that shipped the unemployment/wage/formation axes) and the aggregate labour-market capability described in web/lib/stakeholder-docs/src/coverage.html's 'What changed since v1' summary. Supporting items include a real, disclosed gap named directly in docs/HANDOFF-S5.md (youth-specific unemployment) plus two further labour-market facts this platform does not track.

Buying or leasing a specific industrial asset (warehouse, distribution center, industrial building) in a named place. Distinct from site_selection (greenfield siting) and real_estate_development (building new stock): the decisive evidence here is the ASSET MARKET — transaction economics and vacancy/absorption — which this platform does not and cannot license at its tier; the platform's contribution is the operating-context read plus honest pricing of the asset-market gap. Trigger phrasing per the 2026-08-20 stakeholder ask: 'is now a good time to buy a warehouse in Calgary'. Ratified R3e (docs/METHODOLOGY-CONVICTION.md §4, docs/DRAFT-R3-WAREHOUSE-TEMPLATE.md §2): each requiredEvidence item below carries an explicit `weight` (the legacy core/supporting necessity backfill remains DEFERRED per R3a for the six pre-existing decision types above — this is the only decision_type with weights, not a precedent applied retroactively) and a `decisive` boolean — true only for the three ASSET-market items (transaction evidence, vacancy/absorption, land price); every other item, including financing, is `decisive: false` (R3e's context set). Posture rule (kernel, lineage.ts): zero decisive items answered => context_only regardless of the coverage number.