ROUTE//FRAMEIndependent public-interest research
MENU
[ EDUCATION CENTER / REVIEWED JULY 22, 2026 ]

Read the system, not just the map.

Start with current reporting. Then learn what a map point, contract, count, or estimate can actually prove.

01 / CURRENT REPORTING

See what is happening now.

Start with a concise RouteFrame source brief, then choose whether to open the complete publisher report. RouteFrame stores links, reviewed summaries, and metadata, not copied articles.

HOURLY SOURCE SCANCHECKING LATEST TIME
16 REVIEWED REPORT LINKS13 REVIEWED PUBLISHERS
Central Current
CONTRACT ACTION

Flock Safety removes its license plate readers, finalizing eight-month breakup with City of Syracuse

Syracuse, New York

GOVERNMENT ACTION REPORTEDREAD ROUTEFRAME SUMMARY
[ RECENT EXPLAINERS AND INVESTIGATIONS ]

Watch the reporting. Check the sources.

Recent means publication date, not verified truth or a social-engagement ranking. RouteFrame links to original publishers and labels creator, newsroom, and technical perspectives separately.

5:59
LOCAL NEWS INVESTIGATION

Flock says its cameras don't track people. Training videos say otherwise.

A newsroom investigation examining product training material, public claims, and concerns about movement reconstruction.

InvestigateTV / 5:59OPEN ORIGINAL VIDEO
10:25
LOCAL NEWS INVESTIGATION

Flock Safety cameras help solve crimes. But who's watching the watchers?

A reported examination of claimed public-safety benefits, mistaken identification, oversight, and access controls.

Atlanta News First / 10:25OPEN ORIGINAL VIDEO
11:05
TECHNICAL RESEARCH

This Flock Camera Leak is like Netflix For Stalkers

A technical investigation into exposed Condor camera feeds. It does not establish that every deployment had the same configuration.

Benn Jordan / 11:05OPEN ORIGINAL VIDEO
INCLUSION IS NOT ENDORSEMENT.

Creator and newsroom claims remain attributed. Technical demonstrations do not prove that every camera or current deployment has the same behavior or configuration.

02 / ALPR BASICS

Six ideas that prevent bad conclusions.

Open one question at a time. The first answer is expanded to get you started.

01 / What an ALPR records

Automatic license plate reader systems are designed to capture plate identifiers and often record time, location, and vehicle images. Exact fields, retention, access, and sharing depend on the system and policy.

02 / How a public purchase happens

A proposal can move through staff review, budget authority, public agendas, council or board approval, contracting, installation, renewal, amendment, and expiration. Approval is not proof of installation.

03 / Why costs differ

Contracts can bundle cameras, cellular service, software, installation, storage, support, search tools, and retention. RouteFrame never treats a bundled effective rate as a universal camera price.

04 / How grants fund deployments

Federal, state, or regional grants can pay initial or expansion costs. A grant shifts the funding source, but it does not eliminate long-term maintenance or renewal questions.

05 / How data sharing can work

Policies may permit searches or sharing across agencies. Scope varies by jurisdiction, agreement, user permissions, audit rules, and state law. A map point alone cannot establish those rules.

06 / Why camera counts are uncertain

Public documents can describe approved, installed, active, inactive, replaced, relocated, or proposed equipment at different dates. RouteFrame separates those states instead of adding them together.

03 / MAP RECORDS

Know what a camera marker means.

RouteFrame retains available public source fields and retrieval dates. It does not turn a mapped point into proof that a system is active, owned by a named agency, or tied to a specific contract.

What the point supports

A source ID and mapped location, plus direction, operator, vendor, dataset version, or retrieval fields only when the public record provides them.

What stays unknown

Current operation, exact hardware, capture range, retention, sharing, installation date, ownership, policy, and cost without reviewed evidence.

When a point disappears

Absence from a later snapshot means the record was not present in that snapshot. It does not prove removal or inactive status.

When a source fails

RouteFrame can use the latest rolling snapshot for resilient loading and labels archived source data instead of calling it live.

04 / EVIDENCE LABELS

Check the label before the number.

Confirmed

A high-quality primary source directly supports the narrow claim displayed.

Estimated

A disclosed model uses named assumptions and source benchmarks. It is not an invoice or exact expenditure.

Unknown

The current research set does not support the field. RouteFrame leaves it empty instead of guessing.

Conflicting

Sources disagree or describe different dates and scopes. Both remain visible until reconciled.

05 / PUBLIC DECISION

Follow a system from proposal to review.

  1. PROPOSAL

    An agency identifies a use case and scope.

  2. AUTHORITY

    A budget, grant, or governing vote may authorize spending.

  3. CONTRACT

    Terms define products, services, duration, and price.

  4. DEPLOYMENT

    Installation must be verified separately from approval.

  5. POLICY

    Retention, access, sharing, and audit rules govern use.

  6. REVIEW

    Renewals, amendments, audits, removals, and disputes change the record.

Diagram of six surveillance system lifecycle stages in a row, connected by arrows: proposal, authority, contract, deployment, policy, and review.
Proposal and authority are not proof of deployment. Any stage can stall, change, or reverse.
06 / DOCUMENT READING

Read a procurement record in six passes.

  1. Find the decision.Identify what the governing body actually approved.
  2. Find the scope.Separate units, add-ons, services, and optional products.
  3. Find the dates.Distinguish proposal, approval, signature, installation target, and expiration.
  4. Find the money.Separate first-year, recurring, total ceiling, grant share, and installation.
  5. Find the policy.Look for retention, sharing, access, audit, and reporting rules.
  6. Record the gaps.Note current quantity, renewal, removal, and policy fields that remain unsupported.