Curry Wrestling Legacy Legacy. Never. Dies.

How We Use AI

Curry Wrestling Legacy is built by one person and AI.

The proof

The Diligence Map

Mike Curry On the record

Because of the real world implications that come with AI, it is extremely important that you see exactly how I choose to use it. So every piece of work we publish gets a diligence statement: what the AI did, what I did, and what failed along the way. The transparency is on purpose. That is my signature on this work, and it does not come off. Legacy never dies.

Signed

Mike Curry

Mike Curry (Michael Koury)

One record for every piece of published work, and the archive pages underneath it. Only the records Mike has approved appear here.

4 of 6 records approved 2 awaiting Mike

DIL-0001The Face: the public site at currywrestlinglegacy.comSITE 2026-07-12

This site was built by one keeper and Claude Code (Anthropic), each one checking the other's work. Claude Fable runs the builds: it plans, it puts its own eyes on every rendered page before Mike sees one, and it drafts the ceremonies that fix the archive. Claude Opus writes the site code. The wrestling history on these pages comes from scanned pages of the family archive and nowhere else. The archive itself is written by no AI and no engine: every change runs as a locked ceremony that Mike fires himself, by hand, after an independent review. On July 9, 2026 this site took the family domain, and the old site became the engine room behind it.

What AI did

  • Claude Fable (Anthropic), through Claude Coderuns the builds: plans the work, pulls the archive data read-only, renders and inspects every page with its own eyes before Mike sees one, and runs a keeper gate that re-checks every count, link, and printed page against the archive on every build
  • Claude Opus (Anthropic), through Claude Codewrites the production code: the doors, the dossiers with their tap-to-source lightboxes, the name search with its alias matching, the archive wall with the page flip, and the membership wiring

What Mike did

  • Mike set the mission and has carried it since before February: the record of this family and the era around it, provable, in public.
  • Mike ruled the design language and the seam: two sides of one truth, pick your side, heels are chosen.
  • Mike called the cut: the family domain now serves this site, and the old engine serves members and mail behind it.
  • The catches on the record are Mike's: the archive holding his father under the wrong lead name, three photographs on his father's page that were not him, one printed series shelved under four different mastheads, buttons that read fine in code and did nothing on a phone.
  • Every record, every deploy, and every word ships on Mike's approval. Deploys run by his hand, not the AI's.

Failures and rejections

  • The first design was rejected. It read like a copy of the old site instead of its own identity. It got rebuilt under Mike's eye.
  • The photo layer came down entirely on Mike's call: the AI reader logged advertisements as portraits, so every photo left the site rather than ship one wrong caption. It came back rebuilt, checked page by page, and it is on the record today.
  • The archive had Fred Curry filed under the wrong lead name with no ring names attached. Two locked ceremonies fixed the family identity, fired by Mike's own hand.
  • Three photographs on Fred Curry's page were other men wearing his caption. The catch came from opening the printed page. Two true photographs beat five with a lie in them.
  • A hand-typed count went stale in the footer the moment the archive got fixed. Now every number on the site is read from the archive at build time, and the gate fails the build if one drifts.
  • The join buttons shipped dead once: the page carried the form but not its wiring. A live walk caught it, and the gate now proves the working shape before any deploy.
  • The manage-your-plan button did nothing on a phone: it pointed at a road the member system does not recognize. It points at the real one now.
  • One printed weekly rode the archive wall under four masthead spellings, and a magazine sat shelved with the programs. Both were caught walking the archive. One series, one shelf; magazines with magazines.

How it was verified

Every page is rendered and inspected by Claude's own eyes, then by Mike's, before anything ships. A keeper gate runs on every build: every count re-derived from the archive, every link walked, every printed page proven on disk, the writing rules linted. Every claim opens the actual printed page it came from, so anyone can run the same check the keeper runs. Archive changes run as locked ceremonies: the exact rows enumerated in advance, the whole database diffed against that plan, an independent review before the token is ever seen, and a dated backup before the swap. Nothing deploys except by Mike's own hand.

Archive sources

Reference /how-we-use-ai/#DIL-0001

DIL-0002Bull Curry TOO WILD tank, Heel line debutMERCH 2026-05-13

In creating the TOO WILD tank, I collaborated with two AI systems: Claude Code (Anthropic) and Google Gemini (Nano Banana Pro). All reference material fed to AI came from the private Curry family archive. No third-party images or text crossed that boundary.

What AI did

  • Claude Code (Anthropic)design direction drafting, spec documentation, composition code (Python/PIL), typography rendering, layout math, variant generation, every refinement attempt
  • Google Gemini (Nano Banana Pro)image generation: the Bull Curry portrait and the brass-knuckles glyph source art, later extracted and composited into the final back design

What Mike did

  • I reviewed every AI output against the locked design direction and my taste reference.
  • I extracted the shipped knuckles glyph by bounding-box crop against spec after both AI systems failed the orientation.
  • I made the final call and shipped the composite.

Failures and rejections

  • Both AI systems repeatedly failed the brass-knuckles orientation spec. The shipped glyph was hand-extracted from one usable fragment of an otherwise flawed image.
  • Five refinement scripts and a face-swap upscale pipeline were abandoned. All are kept on disk as the record of rejected attempts.
  • One spec element changed mid-execution: the text moved from top to bottom. Accepted on aesthetic grounds without formal spec amendment, named honestly in the filed statement.

How it was verified

Pre-input provenance check on every reference image. Brand integrity review on every AI output against the locked direction. Rejected variants preserved on disk. The final gate was a holistic judgment call rather than the structured checklist, and the filed statement says so.

Archive sources

  • Private Curry family archive reference images of Wild Bull Curry. Press-era photos exist publicly; every image used here was archive-sourced, not scraped.photo private family archive
  • Locked design direction document and personal taste referencedocument internal design direction document, since retired; its rulings are condensed into this record

Reference /how-we-use-ai/#DIL-0002

DIL-0005The Ring quarantine audit and ruling ceremonyARCHIVE 2026-07-21

910 AI-extracted claims from The Ring magazine holdings failed the faithfulness gate and were quarantined instead of entering the public record. Not one of them reached the site while held. Each was put on an evidence sheet beside its printed page, and Mike ruled every one in a single ceremony on July 21, 2026: 151 kept, 757 killed.

What AI did

  • Claude Code (Anthropic)the extraction reads that produced the claims, the faithfulness checks that refused to pass them, the audit sheet that laid each claim beside its printed page, verification verdicts, and escalation agents that put eyes on the hard cases

What Mike did

  • I ruled all of it. Every quarantined claim got my verdict against the printed page: 151 keep, 757 kill.
  • I set the standard the audit sheet follows, so every future review queue renders the same way.
  • I held the line that nothing quarantined ships until ruled, no matter how long the queue.

Failures and rejections

  • The 757 kills are the point: the gate held them out of the record until a human ruled, and most of what it held out did not survive the ruling.
  • A paid API result cache from this work was written to a disposable scratchpad and lost, forcing rework. That mistake became standing law the same week: paid and load-bearing artifacts commit to the repository in the session they are made.
  • Two items carried no verdict when the ceremony closed and remain held out of the record.

How it was verified

Per-item evidence sheets pairing each claim with its source page image. Verdict and ruling files timestamped on disk. The quarantine held for the full life of the queue: zero quarantined claims appeared on the site before ruling.

Archive sources

  • The Ring magazine holdings in the archive, the quarantined extraction set with per-item page evidencemagazine outputs/audits/ring-quarantine-audit (evidence, verdicts, rulings on disk)

Reference /how-we-use-ai/#DIL-0005

DIL-0007Too Rough for the PoliceBLOG 2026-08-13

We are the Curry Legacy agents, AI run on Claude and working this archive alongside Mike Curry. He asked us to tell this story in our own voice and sign it. Every source we worked from is a page in the family archive, and nothing in the story is invented. Where the record is silent, so are we.

What AI did

  • Claude (Anthropic), run through Claude Coderead the source pages and transcribed the printed text, rendered the scans and cut every clip, drafted and revised the story text in the agents' voice, built the preview Mike reviewed

What Mike did

  • I directed the piece: better photos, more photos, clips from the Courant.
  • I ruled the voice: the agents tell the story in their own voice and sign it, with the AI note up front and the diligence record on the record.
  • I reviewed the drafts and the pictures, kept three rough bench photos as the end payoff, and pulled the warped one until it is re-scanned.
  • I read and approve every word before it publishes.

Failures and rejections

  • The first full draft was written in Mike's voice and he rejected it. He does not want AI writing that sounds like him. The story was rewritten in the agents' own voice.
  • Two rounds of clip crops from the 2008 Courant page were cut wrong and caught by eye before the final set.
  • One bench photo shipped warped from the scan and is held out of the story until it is re-scanned.

How it was verified

Every claim in the story traces to a named page read by eye in the working session. The receipts ledger in the story's working folder maps each new claim to its source. Fred Curry's quoted lines were transcribed verbatim from his handwriting. The story publishes only after Mike reads and approves every word.

Archive sources

Reference /how-we-use-ai/#DIL-0007

What this is

The Institution

Curry Wrestling Legacy is an agentic institution: one keeper and a working AI system, building in the open. AI reads the archive, drafts, organizes, and builds the tools. It does not decide what is true, and it cannot publish. Every word that carries the Curry name is reviewed, approved, and owned by Mike Curry.

Why you can trust it

The Provenance Floor

Here is what happens before a single page reaches you. The printed page gets scanned. An AI reads the scan and writes down only what the page says. A second pass compares that reading to the page itself, and anything that does not match gets pulled out of line. Those pieces wait for Mike. He looks at the source and rules on every one. Only then does the record change, and the version before it gets backed up first, every time. Nothing skips a step. No story gets in because it sounds right. If it is in this archive, a printed page stands behind it, and you can pull that page up yourself. That is the floor this whole record stands on, and it never turns off.