Pulse: Municipal Data Ingestion and Correlation for City Oversight

A system for pulling together municipal records, donor relationships, and project evidence so patterns can be reviewed without losing the source trail.

What Pulse Is For

Pulse is built to ingest city data, preserve the underlying sources, and correlate records that should be considered together during oversight work. It follows the chain from public decision to implementation, spending, and observable outcome.

The goal is not to jump straight to accusations. The goal is to surface evidence-backed patterns that deserve review: delays, cost drift, repeated exceptions, incomplete records, unusual donor proximity, and other signals that can indicate mismanagement or deeper governance risk.

What It Ingests

Pulse is designed to gather the material that usually ends up scattered across meeting packages, disclosures, award notices, project pages, and supporting reports.

• Council agendas, minutes, staff reports, and attachments
• Project and consultation pages that publish changes over time
• Procurement notices and award records
• Disclosure, donor, and ownership-related public data
• Other municipal source material needed to preserve a clean trail

Every source is kept in a form that can be traced back to the original claim. That matters more than any single summary result.

How Correlation Works

The system joins records using exact identifiers whenever possible: project numbers, bylaw references, parcel IDs, official page keys, vendor names, and sourced entity matches.

This is deliberate. Broad similarity is useful for triage, but exact joins are what let the system build defensible issue trails. If the evidence is incomplete, Pulse treats the relationship as unresolved rather than filling the gap with assumptions.

That constraint is important because municipal records are often messy. The output needs to show what is actually supported, not what would be convenient to believe.

What the Analysis Looks At

Pulse is focused on the kinds of patterns that show up when municipal management is drifting away from its stated commitments.

• Repeated deferrals and missed milestones
• Contracts, amendments, and spending that do not reconcile cleanly
• Procurement exceptions and concentrated vendor relationships
• Closed-session or consultation gaps that block transparency
• Uneven treatment between similar files or applicants
• Evidence gaps that suggest fragmented ownership or weak controls

For donor analysis, Pulse only treats sourced relationships as valid edges. That keeps the graph focused on disclosed, documentable connections rather than inference-by-vibe.

How the Graph Is Used

One part of Pulse maps decision threads. Another part maps donor and ownership relationships when they are explicitly supported by public records.

The point is to make overlap visible: who is connected to whom, what the link is, and which records prove it. That can reveal surprising proximity between council-side decisions, disclosed donors, and vendor or property relationships without overclaiming what the evidence can actually support.

In practice, that means the graph is a review tool. It highlights patterns for closer inspection and keeps the supporting claims attached to every edge.

Why the Vector Store Matters

Pulse also vectorizes the available corpus so the material can be searched and compared at scale. Once the data has been normalized, embeddings make it easier to retrieve similar issues, compare timelines, and surface related records that would otherwise stay buried.

That does not replace source review. It speeds it up. The original documents remain the authority, and vector search is just the index that helps you get back to them faster.

What the System Is Seeing

Over time, the system has found useful relationships between individuals and donors, plus recurring management patterns that merit closer attention. Some of the strongest signals come from records that look ordinary in isolation but become more interesting once they are laid side by side with procurement, project, and disclosure history.

That kind of result is the reason Pulse exists. It helps reveal where public records line up cleanly, where the trail breaks, and where a human reviewer should probably keep digging.

Why It Stays Conservative

Pulse is intentionally conservative about wording. The system can surface patterns, evidence gaps, and review candidates. It should not turn those into legal or disciplinary conclusions on its own.

That keeps the output useful. It gives a reviewer enough structure to follow the trail, but it still leaves the final judgment to the record, the evidence, and the appropriate authority.