Loop MMT

Receipt · a redacted handoff

The letter the system hands the next session

A real session-close handoff, lightly cleaned so it can leave the private repo.

None of this was written for you. At every close, the system writes a letter to the session that comes next — what landed, what it verified, and the one thing it almost got wrong. It's honest about what it couldn't finish, because the next session has to trust it. Here's a real one.

Line: loopmmt-website — Documents hub built, whole site deployed live, logo mark re-colored

One line. Finished the loopmmt.com Documents hub (all 5 cleared corpus pages built, wired, gated), made it deploy-safe by catching that corpus.html is a generated file, cleared a pre-existing deploy blocker, deployed the whole site live to loopmmt.com, then split the logo mark's colors for contrast (loop→ink, ball→persimmon) and deployed that too — all verified by served bytes.

What landed

  • 5 corpus doc pages, all PUBLISH-OK + redact-clean + rendered clean
  • corpus.html — all 5 doc-index rows live, "joining shortly" retired; doc-index baked into the builder (see the catch below)
  • creed.html — scrubbed an internal provenance path from a dev-comment that was refusing the whole-tree predeploy gate
  • Logo mark split — loop→ink #221d16, bit→persimmon #bf4a20; favicons + og-image regenerated
  • Two live deploys to the public Pages repo

Verified (not asserted)

  • publish-gate PUBLISH OK ×5; air-gap gate exit 0 on every new page + SVG
  • whole-site smoke GATE PASS
  • Tier-1 render every new page: 0 console errors; nav + tokens + links clean
  • deploy dry-run CLEAN end-to-end; live curl = 200 with content checks

For my successor

the near-miss the diff won't show

corpus.html is GENERATED by the builder (a pure fold, run at build). The predecessor built the whole hub by hand-editing the generated file — so the first deploy would have silently wiped the entire Documents hub. I baked the doc-index into the builder. Never hand-edit corpus.html again — edit the builder.

Also: the website deploy is air-gapped GitHub Pages, nothing like the app-server deploy note (that was a different project).

Champollion questions (for the next instance)

1. (Semantic) Why can't you fix a wrong link in the corpus Documents index by editing site/corpus.html? — It's generated; the build regenerates it, so a hand-edit is wiped. Edit the builder.

2. (Compositional) Why did the two build-standard docs get content-extracted into Score pages while the two md docs just ran through the doc-page builder? — The build-standard docs were standalone HTML with their own design system; the operator's pick was to strip the content and rebuild it, so they needed an HTML→Score extractor, not a markdown converter.

3. (Experiential) Why does the favicon sit on a paper chip when the header wordmark doesn't? — After the split the loop is ink; an ink loop on a transparent favicon vanishes on dark browser tabs, so the favicon needs an opaque chip. The header wordmark is always on paper.

Ignition block

LG! Picking up loopmmt.com — the Documents hub is built and the whole site is LIVE, and the logo mark is re-colored (ink loop, persimmon ball). What's next? Handoff + mesh: repo (private) · this session's mesh folder Where we left it: doc-batch done + whole site LIVE. Next thread is operator's pick — air-gap hardening / og-image polish / new content. Critical: corpus.html is GENERATED — edit the builder, never the HTML.

Cleaned, not curated: session identifiers are normalized and a handful of internal file-pointers are generalized, and the one line that described the credential setup was cut entirely. Nothing about what the handoff is changed — only the parts that would point back through the air-gap.

← back to the receipts