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 “Campaign Infrastructure”

Clear filter

Community and cultural infrastructure

KC Spaces Fund website showing its cultural-space support message, donation route, navigation, and support section. — The 2020 campaign surface brought its purpose, donation, application, sign-up, contact, and fundraising pathways into one coherent public system. KC Spaces Fund public website capture, August 20, 2026; historical campaign content.

Rapid Public Implementation

2020

Short proof pagepublic-safe

KC Spaces Fund

A finished campaign site for cultural-space mutual aid

Built and maintained the campaign's Ghost-based web stack, customized a reusable theme, and implemented donation, application, sign-up, and contact pathways plus a fundraising progress display for a collaborator-led 2020 mutual-aid campaign.

What was emerging: A fast-moving cultural-space mutual-aid campaign needed a coherent public identity and clear action paths across the website and collaborator-led social channels.
What became usable: A maintained Ghost site with a reusable campaign theme and visible routes to donate, apply, join, contact, and follow fundraising progress.

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