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 “Community Systems”

Clear filter

Community and cultural infrastructure

WOW List landing page over a photograph of people gathered around a table, with the words being there changes everything. — WOW List's current threshold pairs its returning interface with a photographic scene of people gathering. Public website capture, August 13, 2026.

Community Platform

2010s; public return in progress, 2026

Short proof pagepublic-safe

WOWList.org

Natural-language community infrastructure for arts and music organizers

Co-founded, co-built, and operated a natural-language community-calendar platform across 35 city ecosystems, supporting local organizers who used WOW List to run calendars, websites, and email lists for their own scenes.

What was emerging: DIY organizers needed lightweight ways to distribute events and maintain community visibility across scenes without relying on one centralized editorial calendar.
What became usable: A natural-language, collaboratively editable event system that turned community vocabulary into followable keyword calendars and organizer-facing distribution workflows.

Read case study

A person stands at a crowded dinner table, raising one hand and holding up a sheet of paper as others laugh beside a hand-drawn map. — A Sunday Dinner gathering with a hand-drawn map and shared table, January 6, 2013. Photo courtesy of Sunday Dinner NYC.

Participation Infrastructure

2010s-present

Short proof pagesummary-only

196 Artists Residency / Sunday Dinner

Hosting, onboarding, facilitation, and continuity systems

Created repeatable hosting, onboarding, facilitation, documentation, and continuity systems across 300+ gatherings and 20+ resident artists.

What was emerging: A recurring cultural space needed trust-building routines, invitations, hospitality, artist support, and continuity without turning private community records into public spectacle.
What became usable: Repeatable participation infrastructure for gatherings, resident artists, onboarding, facilitation, and handoffs.

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