Receipt · a near-miss log

What the system almost got wrong

A real session's chaos report, lightly cleaned. One item is redacted in the open.

Every session keeps a log of its own near-misses — the traps it caught, the risks it surfaced, the wrong turns it corrected. A receipt that names its own mistakes proves honesty better than any polished claim. This is one, exactly as written, with a single item cut where the cut is the point.

Traps caught (byte-truth over the handoff)

1.corpus.html is GENERATED, not static. The doc-index lived only in a hand-edit — the first deploy would have silently wiped the whole Documents hub. Fixed by baking the doc-index into the builder. Highest-severity catch of the session.

2.Deploy is air-gapped GitHub Pages, not an app server. An inherited note described an app-server deploy pattern that was byte-wrong for the website. Real path: the static deploy to the public Pages repo.

3.creed.html leaked an internal provenance path (dev-comment) that refused the whole-tree predeploy gate — pre-existing, unrelated to the hub, but blocked deploy. Scrubbed.

4.rsync not installed — the deploy failed (exit 127) until it was installed. Not persistent across container resets.

5.No git identity on the public clone — commit failed until name/email set on the deploy clone.

6.Dark-tab favicon regression (self-introduced): the new ink loop vanishes on dark browser tabs on a transparent favicon. Fixed with a paper chip.

■ one item redacted — guard G2

████████████████████████████████████████ ██████████████████████████████

Here the session surfaced a real, honest open risk for the operator — a note about the credential and air-gap setup. It's a genuine near-miss, flagged twice, not auto-actioned. But its shape is exactly the kind of thing the receipts never publish, so the whole item is cut, not paraphrased. The cut is the receipt.

Decisions

· Operator pick C on the two standalone HTML docs (strip content, rebuild) — carded, lints PASS, resolved.

· Choice A on deploy (push from this env) — carded with the honest air-gap trade-off; operator chose A twice.

· Logo split (loop=ink / bit=persimmon) — executed per the site's own scheme; flip offered.

The traps are verbatim. The one cut item is removed in full because publishing the shape of that risk would itself be the leak — the honest way to show a near-miss log is to keep every operational trap and black out the one whose shape is sensitive.

← back to the receipts