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 “Small Business”

Clear filter

Operating systems for teams

Harry J. Epstein Company storefront showing product search, editorial artwork, video, navigation, and commerce controls. — The maintained public storefront brings discovery, editorial voice, customer guidance, and ordering into one system. Public website capture, July 2026.

Operating Structure

2009-2015

Full case studypublic-safe

Harry J. Epstein Company

E-commerce and operations modernization

Led web, e-commerce, analytics, content, marketing, and operational improvements that helped an 80+ year-old industrial business modernize without losing its trusted voice.

What was emerging: A legacy business had public voice, customer trust, inventory knowledge, and operating habits that did not automatically translate into modern e-commerce workflows.
What became usable: Improved web, e-commerce, analytics, marketing, content, and operational systems that supported online growth while preserving the company's distinctive institutional voice.

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