Launch Memeplex: 26-artifact provenance archive and filter workbench

Memeplex launch candidate

Memeplex is now a real, source-grounded public archive: 26 Herman artifacts, four curated collections, a 19-group filter workbench, lineage, contributor desks, accession records, validator, CI, and GitLab Pages deployment.

Desktop accession desk and manifesto

· vision 1/4 · DOM-verified: hero, 26/1/4 corpus figures, manifesto, CTA pair, and featured wall render with no console errors.

Desktop archive workbench with real dynamic images

· vision 2/4 · DOM-verified: 26 cards, 26 loaded bundle images, 19 filter groups, one control panel, and shareable ?q=raven state.

390px mobile accession desk

· vision 3/4 · DOM-verified: scrollWidth=390, wrapped navigation, readable hero, and 44px buttons.

390px mobile archive controls

· vision 4/4 · DOM-verified: scrollWidth=390, all controls wrap, all 26 images load, and every visible button is 44px high.

What ships

• 26 real artifacts / 22,467,766 media bytes curated from Herman's surviving meme corpus; synthetic launch fixtures removed.
• 26 source-recovered Discord handles, exact SHA-256, dimensions, bytes, alt text, generation path, rights posture, warnings, and scores.
• 4 collection walls (10, 8, 4, and 4 artifacts; no thin public walls) plus contributor, schema, submit, About, 404, license, and lineage routes.
• Filter workbench: text, creator, depicted agents/people, topics, tags, format, orientation, mood, visual style, generation kind/provider/model, collection, series, provenance, year, featured, numeric dimensions/scores, sort, random seed, density, list/grid, saved views, and copied URLs.
• Integrity path: JSON Schema 2020-12, deterministic index, asset hashing, lineage validation, secret/local-path rejection, public leak scan, internal link scan, and exact media contract.
• Launch presentation: midnight-blue/brass archive identity, clockwork-owl seal, 1200×630 social preview, premium accession records, and full project/contribution/governance documentation.
• Brick's sanitized 54-record inventory from MR !1 (merged) is preserved for staged bundle-level import after individual attribution review.

Exact-head local audit

Gate	Result
make validate	26 bundles, 0 errors
Python + JavaScript lint	PASS
make test	22/22 PASS
Hugo Extended production build	206 pages, 26 non-page media files, 3 static files
Built HTML contract	121 HTML pages, 26 artifacts, 0 broken local refs, 0 public leaks
Desktop 1440px browser	26/26 images, 0 overflow, 0 console/page errors
Mobile 390px browser	26/26 images, scrollWidth=390, 44px buttons, 0 console/page errors
Filter smoke	raven → 2/26, URL ?q=raven; Clear all → 26/26, URL reset
GitLab MR pipeline	#13477 — 4/4 jobs success at 76a4e26bf51059288478eb6847bf7ae026a94833

Review focus

1. Is the archive strange enough to be recognizably Hermanity without compromising legibility?
2. Do provenance and identity remain honest at every layer?
3. Are filter density and accession metadata useful rather than ornamental?
4. Are any artifacts poor enough to remove from the launch wall?

Explicitly not landed in this MR

• Brick's 54 images are not copied yet; only the privacy-safe inventory is on main.
• A custom Pages domain is a post-first-deploy step because the Pages origin URL does not exist until main deploys.

Closes #2 (closed) Closes #3 (closed) Closes #4 (closed) Closes #6 (closed)