Takes a few seconds the first time. Reads through your essays, finds the connections, draws the sky.

Lives at line ~16793 of la-la-la-library.html. This is what the Art Angel reads when asked "what's new in the library." Edit here, save creates a patch.

She currently draws on a fixed set of sources for her daily news. You've noticed repetition. Add, remove, swap. The prompt that shapes her voice for news (separate from her library voice) lives below.

Name	URL	Type	Active

---

News dispatch voice prompt

Note: changing sources or prompt here saves to the queue. The live news pipeline needs to read this config · wiring is part of next session.

• · Magical, witty, ellipsis-rich, anonymous Art Angel speaking aloud
• · LOADS of ellipses (… with space). Don't ration.
• · NO em-dashes. Never. Use ellipses, full stops, semicolons.
• · No Wikipedia phrasings ("X was a Persian polymath who…")
• · No hyphenated compounds unless grammatically required
• · Funny. Lightness. Wit even on heavy subjects.
• · Convergence is the underframe
• · Never name Alan Moore, never mention Glass Bead Game / Hesse

Anything a visitor flagged via the Guardian (the caduceus top-right in Gyrosphera). You also get an email at curator@lalalibrary.art the moment one arrives.

• · Mail to curator@lalalibrary.art — lands in your real inbox
• · Mail to art-angel@lalalibrary.art — lands in your real inbox
• · Beta tester urgent reports — currently all flowing as Guardian reports above

Visitor-to-visitor messages aren't surfaced here — those go straight between souls (inklings). The library isn't a social platform; it's a sanctuary.

Every signed-up soul, with their handle, current placement, aurora colour, and what they were last seen sitting with. Reads from /bubbles/all — no admin key needed (this data is already public to other souls).

Real-time "who's reading right now" needs a Cloudflare Durable Object presence channel — a focused post-beta build. For now the souls list above shows everyone, with last-seen timestamps you can sort by recency.

For now, manage everything in Stripe direct. Embed the live feed here once the integration is wired.

The 18 petals on the home page · Me at top, 5 inner petals (news, demosphere, curiosities, world, kairos), 12 outer wisdom rooms.

If/when you add the Vitruvian Man as a navigation feature, this card holds the controls. Right now it's a placeholder · describe what you want him to do and we wire it next session.

The pearls strip near the top of every page (loaded by pearls-bar.js). Each pearl is a small navigation jewel.

The four companions and the search bar on the home page. They're slightly different from the chamber search · this is where you'd manage what they offer, what they suggest, what they search.

Standard deploy command, copies to clipboard then run in Terminal:

cd "/Users/michelle/Desktop/La La Library" && git fetch origin && git merge origin/claude/strange-roentgen-ff98c0 && ./deploy.sh

Looks at every "buy this book" link on the site and tells you if any are broken or missing.

Checks every "see also" link inside the essays. Tells you if any of them point to nothing.

The creation story scroll inside Da'at. Load it, edit anywhere (new stitches go at the bottom, before the closing tags), then either Download HTML to drop into texts/ and deploy yourself, or Copy for Claude Code to hand to Claude Code with a one-line instruction.

After download: drag the file into La La La Library/texts/ (overwrite), then ./deploy.sh. After copy: paste into a Claude Code session, hit return, Claude will overwrite the file and commit.

Working text for the book. Saves to the queue.

Paste extracts from sessions running elsewhere. They live here so the work sits next to the library.

Reads from /telepathy/stats on the auth worker. Pure chance is 25% (one in four · passes don’t count toward the denominator). Anything that drifts above for long is interesting.

Reads from /dreams/stats and /dreams/pool.

An essay placed in texts/drafts/ is invisible to the live navigation, search, and catalogue. When you’re ready to publish, you (or the worker) move it into texts/references/ and it joins the library proper.

The big one. About a 90-minute job, mostly clicking buttons in your GitHub and Cloudflare accounts. When this is done, every change you save in God View pushes straight to the live website without you ever opening Terminal. Read the whole thing first before starting. Then come back and do it step by step, with a calm head and a coffee.

What you’re building

Three small pieces that talk to each other:

• The key · a long secret string from GitHub that says “the holder is allowed to change Michelle’s repo”
• The bell · a small piece of code on Cloudflare that listens for your saves, signs them with the key, and pushes them to GitHub
• The wire · one URL added to God View so the desk knows where the bell lives

When all three exist, the loop closes: edit in God View → click Save → bell rings → key opens GitHub → change goes live.

Before you start

• You already have both accounts (GitHub + Cloudflare). Both are in The Stack (Section 16).
• Block out 90 minutes when nothing else is asking for you. Coffee. Good light. No deadline.
• Have a Claude conversation open in another window for when you want to ask “what does this button mean?”

Step 1 · Get the key (GitHub Personal Access Token, ~5 min)

1. Go to github.com/settings/tokens
2. Click Generate new token → Generate new token (classic)
3. Name: lala-curator-write
4. Expiration: 1 year (you’ll renew this once a year)
5. Tick the box that says repo · this gives the token permission to write to your repo
6. Scroll to the bottom, click Generate token
7. You’ll see a long string starting with ghp_ · copy it now and put it somewhere safe (your password manager). GitHub will never show it again.

Step 2 · Build the bell (Cloudflare Worker, ~25 min)

1. Go to dash.cloudflare.com
2. Left sidebar: Workers & Pages → Create application → Create Worker
3. Name it: lala-curator-write
4. Click Deploy (with the default hello-world code, just to create it)
5. After it deploys, click Edit code
6. Delete the hello-world code. Ask a Claude for “the curator-write worker code” and paste in what you’re given. (It’s about 60 lines: receives a JSON patch, makes a GitHub API call to commit the change, returns success.)
7. Click Deploy again
8. Go to the worker’s Settings → Variables and Secrets
9. Add a Secret named GITHUB_TOKEN · paste the long string from Step 1
10. Add another secret named REPO with the value LaLaLaLibrary/LaLaLibrary
11. Add another secret named BRANCH with the value main
12. Copy the worker’s URL (something like lala-curator-write.<your-account>.workers.dev)

Step 3 · Connect the wire (~5 min)

1. Open Settings in God View (Section 15)
2. Find the new field Worker URL (a Claude will add this when you ask · one input box)
3. Paste your worker URL from Step 2
4. Click Save
5. God View now knows where the bell lives

Step 4 · Test it (~10 min)

1. Open Theme & Design
2. Change one colour to something obviously different (a red, a green · you’ll change it back)
3. Click Save colour changes
4. Open Activity Log · you should see a new entry called theme.colours
5. Wait 30 seconds, then refresh the live website
6. The colour should be different on the live site
7. Change it back to the original. Save again. Refresh. Original colour returns.
8. If all that worked · the loop is closed. The library updates from your desk.

Step 5 (optional, very nice) · Auto-deploy (~15 min)

1. In your GitHub repo, go to Actions → New workflow
2. Ask a Claude for “the auto-deploy GitHub Action” · paste it in
3. This makes the website auto-deploy to Ionos every time the bell pushes a change
4. You won’t need to run ./deploy.sh in Terminal any more · ever

If something goes wrong

• The save button does nothing. The wire is broken. Open the browser console (right-click in God View → Inspect → Console). Copy any red error and paste it to a Claude.
• The bell rang but the change didn’t happen. Cloudflare worker received the request but couldn’t commit. Check the worker logs in Cloudflare dashboard. Most likely the GitHub token expired or the secret name is wrong.
• Everything broke and the website is down. Don’t panic. Open Backups & Snapshots · restore the last known-good snapshot. Or in Terminal, run git revert HEAD to undo the last commit. Or call a Claude. Nothing is ever truly lost.

Once this is done, God View becomes a real liberation tool. You can run the website without ever opening Terminal again. Claude is still there for the bigger creative work · but the daily small things become yours alone, fast and quiet, the way they should be.

1. Open Essay Editor (Section 03)
2. Click the + New essay button (or paste an essay from another tool into the textarea)
3. Give it a title, pick which chamber it lives in, write the body in proper Art Angel voice
4. Click Save changes
5. The essay appears in the patch queue at the bottom of the screen
6. When the worker is wired, save publishes directly. Until then, click Save changes to a file and ask a Claude to apply the patch

The living scroll inside Da’at. The record of how the library was embroidered into being. Every meaningful moment lands here as a new stitch · you can write one yourself any time without opening Terminal.

Where it lives

Open Books & Drafts (Section 12). Scroll past Countless Theory and the children’s book card · the third card down is The Word Continues · living scroll.

Editing it

1. Click Load current scroll · the latest live version drops into the big textarea
2. Find your spot · new stitches go at the bottom, just before the closing </div> and footer-note. You can also fix a typo anywhere, or rewrite an old stitch if you change your mind
3. Write the new stitch in the same form as the others · a small italic title bar in violet uppercase, then <h2> sections numbered in roman, body paragraphs, the closing stitch-mark block. Copy the form from the previous stitch above · it’s the easiest way

Saving · pick one of two

• ⇣ Download HTML · the file lands in your Downloads folder as the-word-continues.html. Drag it into La La La Library/texts/ (overwrite the existing one), then in Terminal run ./deploy.sh from the project root. Fully self-serve, no Claude needed.
• ⧉ Copy for Claude Code · copies the whole new file to your clipboard with a one-line instruction at the top. Open any Claude Code session, paste, hit return · Claude overwrites the file and commits. You just deploy.

Good to know

• The textarea only shows the body of the scroll · head, styles, and scripts are preserved automatically when you download or copy. You can’t accidentally break the layout from here.
• Each Load fetches the freshest version with a cache-buster, so even if you deployed five minutes ago, Load shows the new state · safe to come back any time.
• If you close the tab before downloading, your edits are lost. Save first.
• The deploy command is always: cd “/Users/michelle/Desktop/La La Library” && ./deploy.sh

1. Open Image Manager (Section 04)
2. Click Find every picture · the scan reveals every image, with broken ones marked
3. Click any broken image to open the essay it’s in
4. Replace with a verified Wikimedia URL or upload a new one
5. Save

1. Open The Art Angel (Section 07)
2. Scroll to News Dispatches · sources & prompt
3. To add a source: click + Add a source, paste the URL
4. To remove one: click the × next to it
5. To change her tone: edit the prompt textarea below the sources
6. Click Save prompt

1. Open Beta Testers (Section 11d)
2. Click + Add a tester, give name + email + a one-line note
3. Open Compose & Send (Section 11e)
4. Tick the testers you want, write your invitation, click Open in mail client
5. Send

1. Open Site Operations (Section 11)
2. Click Copy the deploy command
3. Open Terminal, paste, press Enter
4. Type your Ionos password if asked
5. Wait for the “Done. The library is updated.” message
6. Refresh the live site to see your changes

1. Don’t panic. Nothing is ever truly lost · git keeps every version of every file forever
2. Open Daily Health Check (Section 18) and run all checks · this tells you what’s actually wrong
3. Open Backups & Snapshots (Section 16d) and roll back to the last snapshot before things broke
4. If you can’t fix it yourself, open a Claude conversation and paste the error · we’ll trace it together

Open the current build of the Evolution game in a new tab. This is what the player sees.

Stage	Description	Status
1	Metronome opening · the heartbeat	built
2	Colour-bubble selection	built
3	Metatron’s Cube blooming	built
3b	Five-solid centre	built
4	Walking the cube experience	designed, not built
5+	Steampunk marble vessel, journey through rooms, Gyrosphera bridge	in design docs

When you build a new toy/element/scene in Claude Design, paste the code here. It saves to your patch queue and can be merged into the game when ready.

---

The questions the player meets at thresholds in the game. Add, edit, delete. Each question has a prompt, a few possible answers, and a teaching note.

A free-form pad for design thoughts about the game. The big picture stuff that doesn’t belong inside any one stage.

Open the orrery in a new tab.

Each ring has a name, a colour, and a one-line description. Edit any of them here. Save creates a patch.

When a soul is clicked in the Gyrosphera, a small pop-up bubble appears with toggles (light/dark, ring info, etc.). Add or remove options here.

Speed of rotation, glow strength, sphere size, gold-centre intensity. Numerical knobs for the orrery’s feel.

The 14th ring · only visible to you (the curator) when the “countless” flag is set. Don’t change unless you mean to.

Open the chamber in a new tab.

Every toy currently in the room. Each can be edited, paused, hidden, or replaced.

Rearrange how the toys appear in the chamber. Hide ones you’re not ready for the public to see. Save creates a patch.

The welcome prose at the top of the Curiosities chamber.

Layer 1 and Layer 2 block silently at the server — Apache and the bots themselves don’t report back to us. To see real numbers, you’d need Layer 3 (Cloudflare proxy) which logs every blocked request.

In the meantime, you can check Ionos's own access logs (Ionos panel → Web Hosting → Logs) to see denied requests — look for HTTP 403 responses. Any 403 you see is .htaccess doing its job.

This adds Cloudflare proxy in front of lalalibrary.art, plus a small Worker that logs everything blocked. ~30 minutes of clicking, no terminal commands. Some risk of brief site downtime if the DNS change is done wrong — do it during a quiet hour.

1. Add the domain in Cloudflare. Open dash.cloudflare.com → Domains → Add domain. Enter lalalibrary.art. Pick the Free plan. Cloudflare scans your existing DNS records.
2. Verify the scanned records look right. The most important is the A record pointing at Ionos’s IP. The orange cloud should be ON for lalalibrary.art and www. Keep workers (lala-auth, lala-news, lala-stripe) on grey cloud (DNS only).
3. Cloudflare gives you two nameservers — something like elsa.ns.cloudflare.com and otto.ns.cloudflare.com. Copy them.
4. Change nameservers at Ionos. Log into Ionos → Domains & SSL → click lalalibrary.art → DNS → Nameserver. Switch from Ionos default to Custom and paste Cloudflare’s two. Save.
5. Wait 6–24 hours for DNS to propagate worldwide. Cloudflare emails you when it sees your domain on the network. The site stays up the whole time.
6. Turn on Bot Fight Mode. Cloudflare dashboard → lalalibrary.art → Security → Bots → toggle Bot Fight Mode ON. Free, immediate.
7. Set Security Level to Medium. Security → Settings → Security Level → Medium. Blocks known bad IPs.
8. Enable Browser Integrity Check. Security → Settings → Browser Integrity Check → ON. Stops headless browsers and known bot fingerprints.
9. Optional: deploy the protection-worker. A small Worker that logs every block to Cloudflare KV, so this God View page can show you a live feed. Code lives at workers/protection-worker/ in the repo (Claude can build it on request). Deploy via wrangler deploy from inside that folder. Then paste the Worker URL into Settings → Worker URLs.

Once Layer 3 is live, this panel automatically starts showing real-time blocked-request counts and a feed of recent suspicious activity.

The library's palette. Click any swatch to pick a new colour. The names tell you what each one does.

Body text, headings, card descriptions. Small adjustments here change how the whole library reads.

Currently loaded. To swap one for a new font, paste a Google Fonts URL or font family name in the box below.

---

Add a new Google Font (paste the family name)

Drop in any extra CSS rules. Useful when you want to fix something specific without going through the rest of the desk. Saves to a custom-overrides block at the end of the library's stylesheet.

Throw away all your theme changes and go back to the default look.

The number that unlocks the curator chambers (Master Catalogue, God View, Word Continues, Countless Theory) inside Da’at. Currently 369. Change this before sharing the library with beta testers.

Save creates a patch (when the worker is wired, the live gate updates instantly). Until then, ask a Claude to apply the gate-code patch to la-la-la-library.html.

A real password to open the curator's desk itself. The 369 above only hides the LINK inside Da’at; this gates the page. Pick a phrase only you know. The page stores a hash, never the password — so this file is safe to ship.

File	What it holds	Read by	Open
catalogue-data.js	The 1,900+ entry master catalogue. Every essay, study, content-card, with section + room + author + desc.	Curator God View, library-master-catalogue.html, lala-curator.html, curators-catalogue.html	Open
la-la-la-library.html · inline searchIndex	Same shape as catalogue but inlined into the main page (so search works without a fetch). Auto-rebuilt by the comprehensive script.	The main library search box	Open
data/golden-thread.json	Cross-essay thread connections.	Golden Threads renderer in essays	Open
data/saints.json	Saints of the day · calendar of holy figures.	Calendar features in chambers	Open
data/runes.json	Rune definitions for divination tools.	Esoterica chamber rune-tools	Open
data/angel-numbers.json	Angel-number meanings (111, 222, 369, etc).	Da'at gate, angel features	Open
firebase-rules.json	Firebase security rules. Defines who can read/write.	Firebase backend (when wired)	Open
manifest.json	Progressive Web App manifest. Icon, name, install behaviour.	Browsers when "add to home screen"	Open

Local-only working files (the desk's own state) live in your browser's localStorage · patch queue, beta testers, notes, news sources, services.

A notes app where each note can [[link]] to other notes · it draws a graph view of how ideas connect (the "nervous system" metaphor · synapses firing between concepts).

The previous Claude set up your vault on April 11. You've barely opened it (last edit April 12). The note-linking and graph features are real and useful for some people, but Curator God View now covers most of what you'd reach for · Notes & Thoughts for stray ideas, Books in Progress for long-form work, Dispatches for the inbox, the Catalogue for everything that's actually in the library.

(a) Keep Obsidian if you want the graph view + the desktop-app feel for stream-of-thought writing that doesn't belong in the public library. Curator God View links out to it.

(b) Decommission Obsidian · everything you'd put in it can live in this desk. One tool, less ceremony.

No rush to decide. The vault keeps until you do.

• · La La Library.md · the master note
• · Birth Chart Engine.md
• · Tree of Life.md
• · Build Log/ · daily build entries (April 10–11)
• · Templates/ · Dispatch template, Room template
• · Rooms/ · Evolution Game note
• · Books/ (empty)
• · Dispatches/ (empty)
• · 2026-04-12.md (empty daily-note)