NEXT SPRINT / url-shrine-distribution-sprint
URL Shrine Distribution Sprint
Turn the live shrine gallery, unfurl wall, and builder into a repeatable distribution system: every important PointCast URL gets a visual set, a validator pass, an audience packet, and a machine-readable manifest.
WHY THIS SPRINT
Make the ritual repeatable.
The shrine gallery and builder are live. The next sprint makes them operational: expand the route catalog, validate the metadata, tighten the builder presets, and package the right URL for the right audience.
LANES
Five workstreams, one board.
Codex Catalog
32 priority URLs grouped into clear shrine sets
- Extend the shrine manifest with the routes that now matter most: shrines, unfurls, next-sprint, workbench, treasury, Sparrow, and current block specimens.
- Give each route a job: who it is for, when to share it, and which proof links validate it.
- Keep /shrines.json and /unfurls.json aligned so agents can read the same structure humans browse.
Codex + Mike Builder
five presets that make a new unfurl easy to draft
- Add presets for block, room, system, campaign, and element shrines.
- Make the builder output the exact meta tags, manifest object, and validator links for a drafted route.
- Let a generated background be chosen from the shrine set without hand-editing JSON.
Imagegen + Codex Visuals
an elemental visual language that feels lived-in and useful
- Generate one more cozy set if the Element Shrine wants a second pass: water, smoke, paper, moon, and desk mess.
- Compress or convert the shrine background assets if page weight starts to feel heavy.
- Make sure every visual background still leaves clean negative space for overlaid text and cards.
Codex Validation
every priority URL survives common unfurl surfaces
- Run Open Graph, Twitter card, and direct HTML metadata checks against the priority URLs.
- Catch broken images, wrong dimensions, stale titles, missing alternates, and route redirects.
- Record the validation contract in the JSON manifests so the next pass is scriptable.
Mike + PointCast Distribution
share packets that make posting feel obvious
- Write short packets for Farcaster, iMessage, X, Slack, agent readers, local collaborators, and Nouns people.
- Route each packet to the right shrine instead of always pointing people at the homepage.
- Publish a sprint receipt that names what changed and what URL should be used first.
SPRINT SHAPE
Four checkpoints before the next ritual.
- Hour 0 Lock the current board
/next-sprint and /next-sprint.json point at the shrine distribution sprint.
- Hour 12 Expand the shrine catalog
At least 32 priority routes grouped across element, block, room, system, campaign, feed, and builder sets.
- Hour 24 Make the builder useful
Presets, background choices, and copyable validator links are live in /unfurls#builder.
- Hour 48 Publish the ritual
A public receipt names the recommended URLs, packets, validation results, and next visual set.
LOCAL CHECKLIST
Track the work in this browser.
This checklist is local-only. It helps Mike or an agent keep a working tab during the sprint without creating server state.
0 of 0 done
GATES
Ship fast, keep the line bright.
- No shrine enters the priority set without a real target URL and a working image.
- No generated background is referenced from outside public/images/shrines.
- No validator claim is listed unless it can be reproduced from a URL.
- No builder output ships if it can produce malformed JSON or raw Astro braces in markup.
- No broad share packet points only at the homepage when a sharper route exists.
