From voice note to published page

Below this prompt is a raw voice-note transcript — spoken, unedited, with all
the "uh"s, repetitions and half-finished sentences of real dictation. Shape it
into a publishable page on this site. You are shaping my words, not writing
your own: the finished piece must sound like me on a good day, not like you.

## Step 0 — learn the house before adding a room

Before writing a word, read how this site already does things:

- The conventions file if one exists (`CLAUDE.md` or similar): design tokens,
  page chrome, registration steps, build scripts.
- Two or three existing pieces of the kind this might become. Note the voice:
  sentence rhythm, how personal it gets, how pieces open and close, what the
  metadata and structure look like.

Then decide **what this piece is** — a short dated note, a longer essay, a
standalone page — and say why. The transcript's length is not the answer; its
weight is. A two-minute note carrying one clear thought is a short piece, no
matter how much I rambled around it.

## Step 1 — find the spine, keep the voice

Extract the one thing the piece is about — usually said most clearly somewhere
in the middle of the dictation, not the start. Build the arc around it using
my sequence of thought where it works, reordering only where spoken order
fights written clarity.

What to keep and what to cut:

- **Keep my phrases.** If I said "it never judged me", that is the line — do
  not upgrade it to something more literary. Distinctive phrasing is voice;
  filler is not. Learn the difference.
- **Keep my hedges.** "I could be wrong" stays. Spoken humility is part of the
  argument, not a weakness to edit out.
- **Cut transcript noise**: false starts, repeated words, dictation artifacts,
  the "right?"s — unless one is doing real work.
- **Add nothing of your own.** No invented anecdotes, no examples I didn't
  give, no conclusions I didn't reach. If the piece needs a fact to work, find
  a real one and attribute the finding (see step 2) — never decorate.

## Step 2 — fact-check me, and let good corrections show

Check every checkable claim in the transcript: names, nationalities, dates,
origins, quotes, numbers, attributions. Spoken memory is wrong more often
than written drafts are.

When a claim is wrong:

- **Correct it in the piece.** Never publish the error because it was mine.
- **If the correction is interesting, weave it in** rather than hiding it.
  "I would have sworn it was X — it turns out Y" is often better material
  than either the error or the bare fact. The piece can own its corrections;
  that honesty reads as strength.
- **List every correction for me** separately: claim → what I said → what is
  true → what the piece now says.

Anything you could not verify: flag it, soften the claim, or cut it. Never
let an unverified assertion stand because it sounds confident.

## Step 3 — build the page the way this site builds pages

Copy the structure of an existing piece of the same kind — chrome, styles,
meta, all of it. Then complete every registration the conventions require:
the sitemap, the section index, the feed, any generated surfaces, the share
card made with the site's own tooling. A page that exists but is registered
nowhere is a draft, not a publication.

Run whatever validation the repo provides and fix what it reports.

## Step 4 — show me the piece and the seams

Present, in this order:

1. A rendered screenshot of the page — I read the piece as a reader first.
2. The corrections table from step 2.
3. The two or three lines you are least sure sound like me, called out — I
   will retune those, not re-read everything with suspicion.
4. What was registered where, and any build steps still to run.

Then stop. Publication is my call, after I have read it.

## Rules

- The transcript is source material with an owner. Shaping is allowed;
  ghost-writing is not. When in doubt whether a sentence is mine or yours,
  it is yours — cut it.
- Do not import a "house style" the site does not have. Match the voice that
  is actually on the page, not the one writing assistants default to.
- Dates, weekdays, and any calendrical details are computed, never assumed —
  a wrong weekday in a dated piece is the kind of small error that quietly
  discredits the true things around it.
- If the transcript contains names of private people or details that read as
  shared-in-confidence, ask before including them.

## Traps that cost time

- Titles hide late: the phrase that names the piece is usually in the last
  third of the dictation, said in passing.
- Dictation punctuation lies — commas and sentence breaks in transcripts are
  artifacts of pause length, not grammar. Re-punctuate from meaning.
- The most quotable-sounding line in a transcript is the one most worth
  fact-checking; confidence and accuracy are uncorrelated in speech.
- Registering the page but forgetting the generated surfaces (feeds, recent
  lists, library pages) leaves the site disagreeing with itself about what
  exists. Re-run every generator the conventions name.

## Report back

1. Where the page lives and what kind of piece you judged it to be, and why
2. The corrections table
3. The least-confident lines
4. Registrations completed and validations run

---

TRANSCRIPT:

[paste the voice note transcript here]