Bibliographic record
Abstract
This paper describes and evaluates the process for negotiating and distributing density for benefit agreements (DBAs) in Toronto and Vancouver. DBAs allow municipalities to secure cash contributions or amenities from developers in return for allowing them to exceed existing height and density restrictions. The City of Toronto employs Section 37 agreements, while Vancouver secures Community Amenity Contributions. It examines how the two cities determine the value of the benefits; the type of benefits they secure from developers; how the cities determine which type of benefits to secure; and who benefits from the agreements. It also examines the three most common rationales to justify their use: sharing the wealth created by development, funding related infrastructure, and compensating those negatively affected by the development. The analysis shows that the process of negotiating DBAs lacks transparency, and that there are valid arguments for abolishing DBAs or for replacing them with alternative tools such as inclusionary housing provisions.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.005 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.003 | 0.009 |
| Science and technology studies | 0.003 | 0.001 |
| Scholarly communication | 0.005 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.024 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".