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 “Source-Backed Memory”

Clear filter

Civic and public-facing systems

Organizers, artists, and public officials hold a hand-painted Save NYC Spaces and NYC Artist Coalition banner in front of a packed Market Hotel room. — A collective Save NYC Spaces town hall at Market Hotel, October 11, 2017. Photo courtesy of NYC Artist Coalition.

Civic Systems

2017-Present

Full case studypublic-safe

NYC Artist Coalition / FairRentNYC

Cultural-space advocacy, coalition memory, and Commercial Rent Stabilization

As a founding member and organizer of NYC Artist Coalition, implemented and maintained campaign websites and helped build coalition memory, source maps, and coordination infrastructure for cultural-space advocacy, FairRentNYC, Commercial Rent Stabilization, and storefront stability.

What was emerging: The work involved many stakeholders, public/private source materials, legal and policy questions, city/state strategy lanes, shifting meetings, and sensitive coalition context that could easily become fragmented or overexposed.
What became usable: Recurring cultural-space meetings, public event pathways, practical safety and legal sessions, town halls, hearings, campaign actions, running minutes, action trackers, source maps, public campaign websites, and shared campaign memory.

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