NEXT SPRINT / shrine-bell-crawl-sprint
Shrine Bell Crawl Sprint
Ship a 24-stop shrine crawl where every visit has a distinct background direction, a bell-ringing option, a route to visit next, and a Midjourney-ready prompt for the shrine visual pass.
WHY THIS SPRINT
Make shrine visits feel like a crawl, not a gallery.
The previous shrine work gave PointCast a strong unfurl language. This sprint turns that language into a playable chain: ring the bell, collect the prompt, visit the next room, and keep the route ritual moving.
LANES
Five workstreams, one board.
Codex Shrine Concepts
24 distinct stops with a reason to exist
- Name each shrine so it feels like a room, not a generic card.
- Pair every shrine with an existing PointCast route that works as the next visit.
- Keep the crawl loop coherent enough to run in one sitting.
Codex + Mike Backgrounds
Midjourney-ready recipes for every shrine
- Write one prompt per shrine with subject, materials, mood, and no-text constraints.
- Use the existing shrine background art as the temporary v1 surface.
- Keep prompts seedable so a later Midjourney pass can generate a stable set.
Codex Bells
four ring patterns that make repeat clicks feel different
- Reuse the shared Noun voice chime helpers instead of adding another audio path.
- Give each shrine a noun id and a single, chord, cascade, or drone mode.
- Track rung and visited state locally without making it a permission system.
Codex Visit Chain
one-button next shrine progression
- Add a rail with all 24 stops and an obvious current shrine.
- Make Visit Next advance the crawl while keeping route links visible.
- Keep the page functional on narrow screens without text collisions.
Mike + PointCast Polish
a crawl worth revisiting after the image pass
- Run the crawl on desktop and mobile and tighten any long labels.
- Pick the strongest prompts for the first Midjourney generation batch.
- Publish a short recap that names the best shrine visit and the next v3 idea.
SPRINT SHAPE
Four checkpoints before the next ritual.
- Hour 0 Rotate the board
/next-sprint and /next-sprint.json point at the shrine bell crawl.
- Hour 6 Ship the 24-stop crawl
/shrine-crawl renders every shrine with bells, tasks, routes, and prompts.
- Hour 12 Generate the image pass
Use the Midjourney prompt queue to make the first 24 shrine background candidates.
- Hour 24 Promote the winners
The best backgrounds become permanent shrine assets and the rest become v3 notes.
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 blocks access to a real page; this stays playful, not permissioned.
- No completion state depends on a server write.
- No shrine ships without a working route href and a next-visit action.
- No Midjourney prompt asks for readable text, logos, or watermark-like marks.
- No new sound path bypasses the existing shared chime helpers.
