Under the Hood: The Patch Archive

I collect the stories behind military patches — soldier-made art, worn as identity. I wanted a home for them that treated the work the way an archive should. Here's how the build actually went, because the process is the part people ask about.

The Patch Archive home screen, dark background with the headline Thread, worn as identity — The archive opens on one line and a filter row. No search box, no grid of thumbnails competing for attention.

The brief

I didn't ask for a website. I asked for a collection with standards: every patch entry needed provenance, sources, and era context, and the design had to feel like a gallery, not a database. Dark, minimal, mobile-first — you should be able to browse it from a couch.

The AI's first move wasn't design. It was structure: a content schema, a research-sources file, and a research queue — before a single pixel. That ordering matters. When the structure exists first, the design has something true to express.

Each patch gets a full screen rather than a slot in a grid, and every record can open to show its blazon, its unit history, and the sources behind both.

An expanded record for the First Special Service Force showing the patch description, unit history, and a sources list — Open a record and you get the blazon, the unit's history, and — at the bottom — the sources. Provenance is part of the design, not a footnote.

The iteration that earned my trust

The first pass shipped three seed entries — Merrill's Marauders, the First Special Service Force, VMF-214. Looked great. Then we ran a deep-research verification pass against live institutional sources, and it got humbling:

The Black Sheep squadron's designation was four years stale — VMA-214 became VMFA-214 in a 2022 redesignation, and half the internet hasn't noticed.
The Marauders entry gained the official blazon and correct combat-team colors.
A "victory stars" claim I liked got removed entirely — we couldn't source it.

That last one is the whole method. The archive is smaller than it could be and right about what it keeps.

The Merrill's Marauders record — shield quartered blue and green with white sun, star, and red lightning bolt — One of the three seed entries. The blazon, the unit history, and the sources all live on the record itself.

What stuck as process

Two standing rules came out of it, written into the project so future sessions inherit them: current-designation claims are the highest-rot facts in this domain — live-check them at verification time, and artwork ships only with public-domain provenance recorded per entry (Commons CC0, Army Quartermaster Museum scans, official USMC vectors — each documented).

Same pattern as everything else in my OS: taste and the ask are mine, the machine drafts fast, and a verification gate decides what survives. The iteration loop isn't "make it prettier" — it's "prove it or cut it."

Where it stands

Twenty-four records so far, spanning WWII through today — the 101st and 82nd Airborne, Merrill's Marauders, the Tuskegee Airmen's 99th Fighter Squadron, MACV-SOG, the Borinqueneers, the Night Stalkers, SAC, Space Delta 9.

The MACV-SOG record — a white skull in a green beret on a red shield — MACV-SOG — the archive's purest example of forbidden art: made by the men themselves, for a unit that officially did not exist. Its provenance note says the artwork isn't final until a cleaner scan exists — that honesty is the schema working.

The 160th SOAR Night Stalkers record — The Night Stalkers. Every era from WWII to the present renders from the same record schema.

The 99th Fighter Squadron record — the Tuskegee Airmen — The 99th Fighter Squadron — the Tuskegee Airmen's first combat unit.

Contact sheet of all twenty-four patches in the archive, from WWII through the modern era — All twenty-four records as of this writing. Every piece of artwork ships with public-domain provenance recorded per entry.

The site itself isn't public yet — it's coming soon. Everything above is work in progress. The records are real and the pipeline runs, but I'm still building the thing people will actually browse, and I'd rather show where it's at than sit on it until it's finished. When it's ready, it'll go up here first.