Skip to content
Andrew Gillfillan
Case study 02AI Innovation Lab · Public records · Editorial systemsBuilt nights and weekends · 2026

AI Innovation Lab · built on nights and weekends · entirely separate from WKAR

I build the product around the problem.

On nights and weekends, I build focused AI-assisted newsroom tools: scrapers, agenda trackers, permit pipelines, sourced briefs, live maps, dashboards and the workflow that keeps every claim connected to its evidence.

I believe AI can help journalists research farther and find leads earlier when it is used inside clear source and editorial guardrails. The journalist still uncovers the real story, finds the human perspective and explains why the impact matters. Everything here was built outside my role at WKAR; nothing on this page is a WKAR or MSU product.

The authentic Michigan Data Center Tracker front page with a live news wire, interactive map and briefing
Michigan Data Center Tracker · authentic working prototype

137,000+

Permits

2.5M+

Permit workflow events

234,000+

Recorded documents

532,000+

Parcel records

Source-linked

Every public claim keeps its receipt

Human gate

AI assists; a journalist decides

Experimental newsroom tools

Let the machines work through the records. Give the journalist more time with people.

I architect AI-assisted research systems that collect, normalize and connect fragmented public records while preserving the evidence behind them. The current platform spans 137,000+ permits, 2.5 million+ permit workflow events, 234,000+ recorded documents and 532,000+ parcel records. The goal is not to automate judgment. It is to give a journalist a stronger, better-organized evidence base for deciding what deserves reporting.

AI can accelerate research, monitoring and repetitive data work. It cannot interview the person living with the consequences, test what the records really mean or explain why the impact matters. That remains the journalist’s work.

Prototype 01 · Michigan Data Center Tracker

One map for projects, power, water, policy and public decisions.

I built a source-first Michigan tracker that connects data-center proposals to the systems around them: local pauses and meetings, power generation and transmission, policy and geography. Every plotted record retains its public source and verification context.

The live build tracks 20 projects and puts the record, map, meetings, stories and dashboard into one public product. The map layers project status, local pauses, infrastructure, policy and county activity so journalists and residents can see both a proposal and the system around it.

Independent working prototype · built outside WKAR

View the live prototype →

The Michigan Data Center Tracker home page combining a live news wire, interactive map and daily briefing
The live front door · news wire, map and daily briefing
The live Michigan Data Center Tracker interactive statewide map with project, pause, infrastructure and policy layers
Live interactive map · statewide source-linked layers

Map design rule

A point without a source is decoration, not journalism.

Blank load stays “undisclosed,” reported and confirmed records remain visibly different, and every layer retains its underlying public source.

Rapid issue products

A hot topic deserves a purpose-built front door.

I love building focused “pop-up” websites around fast-moving public issues. The point is not a disposable microsite. It is a scoped, timely product with its own data model, visual language, source rules, live map, dashboards, explainers and alerts. It is built quickly enough to matter and rigorously enough to trust.

This tracker moves from breaking updates to records, maps, public meetings, trend diagrams, election accountability and a practical FOIA guide. Every view comes from the same underlying reporting system.

Swipe to browse all ten tracker views →

Prototype 02 · Private evidence-first news desk

Clean the data. Preserve the evidence. Let a human decide.

I built a private monitoring desk that watches public records on a schedule, cleans and connects messy filings, detects meaningful change and preserves the original receipt for every claim. It separates collection, analysis, editorial approval and publication; drafting can be assisted, but nothing becomes a publishable story without named human review. The screenshots show the workflow and its stop conditions without exposing private source configuration or thresholds. Across the system, 10,500+ candidate signals have passed through dual-model review workflows designed to challenge findings before they reach a human editorial gate.

01 · Collect

Scheduled source collectors retain raw records, receipts and separate freshness clocks.

02 · Clean + link

Normalize fields, deduplicate stable IDs, geocode defensible records and join exact parcel/entity evidence.

03 · Nominate

Deterministic detectors create reason-coded candidates and sealed evidence packets, not conclusions.

04 · Decide

A journalist checks significance, claims, unknowns and context. No narrative auto-publishes.

The integration layer

A product only counts when the parts work together.

Supabase

Postgres, row-level security, scheduled functions, migrations, exact-match views and a bounded public mirror.

DigitalOcean

Hosted collectors, systemd schedules, APIs, source-health checks, durable data and recovery procedures.

GitHub

Private repositories, versioned architecture, automated tests, browser checks, deploy gates and monitoring.

Mailchimp

Consent-aware subscriber workflows and human-approved newsletter artifacts, separated from the research system.

Browser + Mac automation

Resilient source collection with retries, checkpoint state, login-aware recovery and explicit stop conditions.

Public-source APIs

Permits, property, meetings, environmental, infrastructure and official geographic layers with provenance intact.

Sources first · Editor-led

Keep the judgment human. Let the tools accelerate the work.

Sources, standards and editorial judgment stay human. Inside those guardrails, I use Claude, Codex, ChatGPT, Grok and Gemini as scoped, auditable collaborators to speed research, implementation and review while I build, test and challenge these products.

A stronger next review

Every correction should make the next review stronger.

Reviewed outcomes become test cases. The system can flag a possible improvement and test it against the evidence; a human decides whether the change belongs in the workflow. That is how the desk learns without surrendering editorial control.

The system should make the journalist more powerful, not make the journalist disappear.

The NewsroomNextThe Miami stream →