approval-pathway

name	approval-pathway
version	1.0
description	Determines the likely entitlement pathway for an Ontario development concept from existing feasibility artifacts. This skill should be used when normalized zoning and analysis outputs exist and the pipeline needs an `approval_pathway.json` that classifies process route, major dependencies, and uncertainty.
source	Planning Act (Ontario), City of Toronto Committee of Adjustment, OLT
authority	Province of Ontario, City of Toronto
data_as_of	2026-03-07
pipeline_position	5
pipeline_inputs	normalized_data.json, analysis_packet.json, precedent_packet.json
pipeline_outputs	approval_pathway.json
pipeline_upstream	buildability-analysis, precedent-research
pipeline_downstream	constraints-red-flags, report-generator

Approval Pathway

Purpose

Classify the most likely process route for the proposed concept. Keep the output conservative and explicit about uncertainty. This skill is downstream of extraction and analysis; it does not perform primary source discovery.

Use when

• normalized_data.json exists
• analysis_packet.json exists
• The project needs a process-path classification and timeline signal

Do not use when

• Zoning or Official Plan applicability is still unresolved
• The task is to evaluate design feasibility from scratch
• The task is to write the final client-facing report

Inputs

{
  "project_id": "uuid",
  "normalized_data_path": "normalized_data.json",
  "analysis_packet_path": "analysis_packet.json",
  "precedent_packet_path": "precedent_packet.json"
}

precedent_packet.json is optional but recommended for minor-variance risk assessment.

Outputs

Produce approval_pathway.json.

{
  "project_id": "uuid",
  "pathway_timestamp": "ISO datetime",
  "primary_pathway": "by_right | by_right_with_site_plan | minor_variance | minor_variance_with_site_plan | rezoning | opa_rezoning | cannot_determine",
  "pathway_confidence"