precedent-research

name	precedent-research
version	1.0
description	Researches nearby and comparable planning cases for Ontario site-feasibility. This skill should be used when `normalized_data.json` exists and the pipeline needs a `precedent_packet.json` of relevant decisions, approvals, refusals, and OLT outcomes.
source	Toronto AIC, Ontario Land Tribunal, Toronto Building Permits API
authority	City of Toronto, Ontario Land Tribunal
data_as_of	2026-03-07
pipeline_position	3
pipeline_inputs	normalized_data.json
pipeline_outputs	precedent_packet.json
pipeline_upstream	parcel-zoning-research
pipeline_downstream	approval-pathway, constraints-red-flags, report-generator

Precedent Research

Purpose

Find relevant planning history without overstating what precedent can prove. Prioritize nearby official case history first, then expand to comparable cases and tribunal decisions.

Use when

• The subject site and project concept are known
• The pipeline needs precedent signals for entitlement-risk analysis
• Nearby approvals, refusals, or appeals could change the recommendation

Do not use when

• The task is to discover baseline parcel or zoning sources
• The task is to extract current zoning standards
• The task is to write the final report without supporting case research

Inputs

{
  "project_id": "uuid",
  "subject_address": "123 Main St, Toronto ON",
  "municipality": "Toronto",
  "project_concept": {
    "project_type": "multiplex"
  },
  "search_radius_m": 500
}

Outputs

Produce precedent_packet.json.

Workflow

1. Search nearby official application history first

For Toronto, prioritize:

• Application Information Centre
• official staff reports
• official committee or tribunal records linked from the application record

Start with the subject site, then the immediate surrounding area.

2. Expand to comparable cases only when needed

If nearby history is thin or not directly comparable:

• search for the same relief type
• search for the same zone or land-use context
• search for recent tribunal decisions that clarify the issue