Revisiting the “Velvet Glove” versus the “Iron Fist”: Canadian Police Tactical Teams and Community Policing
Bibliographic record
Abstract
The mandate of a specialized police tactical (TAC) team is to respond to high-risk and violent calls for service in society where patrol officers may struggle to mitigate calls for service safely. Yet TAC teams have come under public scrutiny for their (in)actions during calls for service within their primary and secondary mandates and for their appearance and presence at community events. Existing research has raised red flags about a community policing Trojan horse, where the police present a false chimera to the public that they are democratizing via community policing while synchronously increasing military-style tactics, equipment, and training for their TAC teams. The suggestion arises that police militarization is antithetical to community policing. We draw on 24 interviews with two similarly sized full-time municipal TAC teams from two different provinces in Canada to further unpack how TAC teams engage in community policing. We find evidence that mobilizing TAC teams at community events can be pro-social for community interactions, can assist in combating negative public opinion about TAC, and can provide job fulfillment and job satisfaction and increase purpose for TAC officers.
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.004 | 0.009 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.029 | 0.017 |
| Scholarly communication | 0.007 | 0.003 |
| Open science | 0.002 | 0.005 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 0.000 |
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".