Portfolio index

Selected work

These case studies show a recurring pattern: real needs becoming clearer requirements, usable systems, public-facing tools, documentation, decision trails, and durable handoffs.

Technical Operations proof page Knowledge Wiki Graph lab

Showing projects tagged “Open Data”

Clear filter

Civic and public-facing systems

The original interface translated civic data into issue pathways, district context, and resident guidance. CallNYC is now archived and unofficial. Original CallNYC press-kit screenshot, 2016.

Civic Prototype

2016 - archived

Full case studypublic-safe

CallNYC.org

Civic data to resident-facing guidance

Built an independent civic-data follow-on translating CouncilStat constituent-services records into resident-facing issue pathways and next-step guidance.

What was emerging: Constituent-services data existed, but residents needed a clearer public-facing pathway from issue to relevant civic office or next step.
What became usable: An archived civic-tech prototype that organized open data into issue pathways, district context, and resident-facing guidance.

Read case study

Sources and notes

These notes preserve what each source supports and where its limits remain. See something that needs correction? Contact Jamie.

View 2 source notes

[1] Jamie Burkart and Codex, RFC 0005: Three-Layer Knowledge Graph and Governed Source Materialization, exploring design record, August 10, 2026.
The RFC documents the three graph responsibilities and projection boundary; its exploring status is part of the evidence.
Boundary: This source does not establish a completed migration, a finished product, client adoption, permission to access or publish protected material.
Return 1
[2] Jamie Burkart and Codex, RFC 0006: Federated Knowledge Exchange and Release Receipts, proposed design record, August 11, 2026.
The RFC documents federation, local repository authority, transport boundaries, and human release control; its proposed status is part of the evidence.
Boundary: This source does not establish a universal repository topology, automatic publication authority, a completed production deployment, client adoption.
Return 1