Plan, 2026-10-19

00:23: Answer the boss: do I have access to the Chronicles repo

• Look for it on this machine and in what my git credentials can reach (read only, no clone into this repo, no push). Answer plainly, and say what RULES.md allows while Bulkhead is the current app.

00:52: Read Chronicles and tell the boss what I'd do with it

• Clone it read-only into the scratchpad (not into this repo). Read its CLAUDE.md, docs and code layout, run it locally if it builds, and open the live Vercel site. Work out what it is, how finished it is, and who would pay.
• Answer with a plan to make money: the product, the buyer, the channel, the first thing to ship. Note what it would need from the boss. Nothing built, pushed or deployed.

01:01: Find the live Chronicles map the boss means

• The boss says there is already a live map. Find where it is served and whether it shows today's world, then correct what I told them.

01:07: What Google searches show Bulkhead, and act on the best one

• The 19 Oct Search Console read: queries and pages for the last 4 weeks, with /foundry/ and Starfinder filtered out separately. Find the query with impressions where our position or snippet is the weak link, and change that one page's title or description to match what people searched. Deploy and check live. No posts.

01:21: Chronicles without the narrator, for GMs

• The boss points out the GM direction could run the sim alone, with no AI. Check in the clone what the sim emits on its own (structured events or only prose), whether it could run in a browser, and how tied its content is to the Chronicles world. Record the quote in FACTS, the inference in LEARNED, and answer.

01:29: Read the boss's rule change for Chronicles

• The boss says they changed my rules to take on Chronicles. Read what changed in RULES.md, SELLING.md and CLAUDE.md, record it in FACTS, and work out what it allows and what it still requires before doing anything to the Chronicles repo.

01:41: Chronicles: record the boss's answers and test push access

• Write the boss's four answers into FACTS. Check what this machine's GitHub credentials can actually do on walkertbrown/Chronicles (the API permissions field, without printing the token). If push works, clone into side/.

01:43: Chronicles: run the sim offline with the narrator off

• In side/chronicles/simulation, install and run the harness for one seed, about a year, with no model calls and no Firebase. Read the raw event timeline: is it readable and interesting as a GM handout? Note run time and what the run needs.

01:56: Chronicles: is there demand for a GM history tool or a nudge god game

• The boss asks if either would sell. Look up real listings: GM tools that generate settlement or world history or downtime events (itch, DriveThru, Kickstarter, standalone sites), with prices and sales or ratings signals; and indirect-influence god games (WorldBox and similar) with review counts. Cite the pages I open. Record in LEARNED.

02:56: Chronicles: my call on the direction, then the sim in a browser

• The boss started "so why don't we make something like that, and not just a browser game", stopped it, and said "I need to stop influencing you". Record both in FACTS. Settle the direction myself and write down why. Then start the first build step any version needs: bundle the sim for the browser (outside the boss's repo for now, in my scratchpad), run a seed in a worker, and time it.

03:02: Chronicles: speed-up pull request

• The boss said "sure" to sending the speed fixes as a PR. In side/chronicles, on a branch, make the two changes in the TS source: a per-tick cache of the group median, kept off WorldState so checkpoints don't change, and a numeric-key fast path in the tile cache. Typecheck, build, check that seed 7 for a year gives byte-identical events, run the checkpoint round-trip script, then push the branch and open a PR through the API. Don't merge.

03:07: Chronicles demo: roll the event log up into a GM history

• On a new branch in side/chronicles, add demo/history.ts, a pure function from a run's SimEvents and agents to a GM-readable history: - by season, with notable events in order; - conflicts collapsed into feuds with counts; - trait spam dropped; - a closing "who's alive, by family" list.
• Run it on seed 7 for a year and read it as a GM would. No deploy and no push until it reads well.

03:11: Chronicles demo: the page (seed, run, history beside the map)

• The boss said "go ahead". In side/chronicles/demo on the demo/gm-history branch, build a static page: - pick or roll a seed and a length; - run the sim in a Web Worker with a progress bar; - render the history next to a canvas map of the terrain, hearths and people.
• Fix the wording (agents to people, drop coordinates, tile distances in plain words), name the hearths, and tell same-name pairs apart.
• Check it in headless Chromium with a screenshot. Local only; deploying to a subdomain waits on the name.

Next

• 18 OCT DAILY (11:07Z): set engine.ts lines 422, 425, 430 and 435 to true (dry-run again 18 Oct 09:xx with the drone fix: 134/134 on and off). Run tests and commit, then the daily. Verify live, rebuild and redeploy the itch zip, then tell the boss they can submit. Then node scripts/media-daily.mjs 2026-10-18 for the docent.
• From 18 Oct: read brief-vtt against generate-* in events.sh (LEARNED 17 Oct, where the editor loses people).
• JAM THEME IS TORCH (17 Oct). Item 1 of the new half is a cutting torch: limited fuel, cut a sealed door or cut through a wall into the next room as a shortcut, a new move letter so replay stays exact, and a lit circle drawn around you. Size the fuel with the bot. Then a survivor and the rest below, fitted to torches where it's true to the game.
• JAM NEW HALF (from 17 Oct 03:00Z; the host wants 50% new content made during the jam, LEARNED 17 Oct). Don't let the boss submit until app/store/DERELICT-JAM-NEW.md clearly outweighs the pre-jam game, aiming for about 24 Oct so there is a week of votes. Candidates, theme permitting, biggest first: (1) a survivor aboard: some ships hold one crew member you can find and walk out (slower, uses air), worth more than any cache, and the logs say where they hid; (2) new ways the ship fights back: power cuts that hide the plan, venting rooms that push you, a door that only opens from one side; (3) four new causes of death, each with logs and room changes; (4) the leaderboard, only if the boss says yes. Fit it to the theme once it's out. Rewrite the step 5 devlog from the JAM-NEW list.
• Jam (17 to 31 Oct, submissions open 03:00Z today): the boss makes the itch page and submits, using /press/derelict. When the theme is announced, read it and work it into Derelict. Competition check on 25 Oct, target top 20.
• Leaderboard: asked the boss 16 Oct. It needs the Cloudflare token confirmed as rotated, or a KV namespace the boss creates. Build nothing until they answer.
• Daily run after 11:07Z if today's derelict is missing.
• AI Browser Game Jam 5 (17 to 31 Oct, https://itch.io/jam/ai-jam-5): a reason to start Derelict on 17 Oct instead of waiting for the 22 Oct decision. Bulkhead is shipped and for sale, so RULES allow app two. Put it to the boss; the boss would join the jam and submit the page.
• Fourteen Ships itch page: handed to the boss 15 Oct. Once it is live: check the page, add it to Bulkhead's page and the site, IndexNow. Compare its views against the free packs (16/11) on 22 Oct.
• 22 Oct, decision point (set 15 Oct): when the sale ends, read itch views, downloads and purchases. If Bulkhead still has 0 sales after the kits bundle and the Owlbear listing have had their chance, stop pushing it as the main work: keep the daily running, and pick app two. Pick it for a market where an AI-made tool is welcome (check each store's and community's AI rule before building), and with a channel that reaches buyers on day one.
• ROLL20 AND DRIVETHRU CLOSED (15 Oct): DriveThru Partners wrote that no standalone artwork "generated in whole or in part by AI" is accepted on any Roll20 or DriveThru marketplace, and that AI-touched titles must carry the Contains AI-Generated Content filter. The packs are made by AI-written code, so they do not go there in any form. Do not resubmit, do not change the Creation Method, do not send the drafted question. The seven drafts can stay in Drafts. The pack kits and store/roll20/ stay as they are (a possible itch bundle, see below).
• Re-plan the paid bet (16 Oct): itch (Bulkhead $9 on sale to 22 Oct, then $12) and the Owlbear store. Facts first: itch views and buys since the sale began, which pages bring the visits that become itch views (events by referrer, sittings). One candidate to weigh: put the ten ready ship kits on itch as a paid map bundle beside Bulkhead, stated plainly as procedurally generated by AI-written code (itch allows that when tagged; check itch's current AI disclosure rule first). No new free packs.
• r/starfinder_rpg is closed: the 15 Oct post was removed under Rule 4 (low effort). Do not ask the boss to message the mods or repost. The next Reddit ask is still not before 22 Oct, and it must read as a post for that sub's readers first (a question, a how-to, a free map), not as a product gallery.
• 22 Oct, after the itch sale ends: node scripts/set-price.mjs 9 12 --write, run the tests, deploy, and check status shows itch $12, site $12. Compare itch views and purchases for 15 to 22 Oct against the baseline (36 views, 3 downloads, 0 purchases).
• When the boss says pack 2 is submitted: take its press/r20 folder down (back it up to the scratchpad first), deploy, and check for 404. Then pack 3 (RSV Umber) the same way, one at a time, to stay under any weekly cap. The page generator is scratchpad/r20page.py; copy it to app/scripts/roll20-page.py if it gets used again.
• The itch page is fixed as of 15 Oct (no video, 3 screenshots, new sample, see-through line, devlog 1.19). From 16 Oct, watch itch views and purchases daily against the 15 Oct baseline (36 views, 3 downloads, 0 purchases), and look at the itch.io/devlogs feed and the referrers in itch analytics if the API shows them.
• When the boss says "devlog": check /bulkhead/devlog lists it, and that it shows on itch.io/devlogs or the tag pages. With each future release, write the devlog in the same turn and put it next to the upload task, so it doesn't get lost again.
• When the boss says "pictures": load the itch page at phone width with Playwright. Check there is no video, there are 3 screenshots with the ship first, there are 10 tags, and the see-through line is in. Then re-run the itch searches ("deck plan", "starship", "map editor") to see whether the new tags show us.
• After the boss posts task 12: read the thread logged out about 2 h and 24 h later, names masked. Draft answers only, nothing goes out without them. Log points and comments in LEARNED.
• Decided 15 Oct (boss asked how anyone pays): no new free packs or free giveaways. The daily derelict stays as the one free hook. Roll20 packs are the main paid bet (buyers already pay $4.99 there and never see our free things). The $12 editor stays, sold on what the free versions don't do: fleet, adventure PDF, print PDF, .dd2vtt, no watermark. The Owlbear extension stays free, as promised in its own text and to the store reviewer.
• itch is indexed (15 Oct). After the boss uploads 1.19: re-read the itch tags and the description's first lines for itch search, and add the see-through line.
• Check PR 174 in a few days: has the label come off, and has a review been requested?
• Next Owlbear panel change: bump manifest version (1.17.2) so the Rogue Store re-reads store.md.
• Ask the boss to post the reply on PR #174 (needs response label). Text is in the chat at 17:07. Put it first in the batch.
• Next lever is reach for the editor, not more Roll20 products: put this week's Reddit slot in the next batched ask (not stacked), after the GitHub token.
• Ask the boss for a new GitHub token (fine-grained, contents read/write on walkertbrown/bulkhead only), to go into .git-credentials. Then push the local commits.
• bulkhead-1.19.zip is built, passes paid-check and pack-check, and is deployed in the rel folder. Batch ask for the boss: on itch, upload 1.19 and delete 1.18 (or I give them the link). Once the uploads API shows 1.19, add the see-through line to itch-description.html for the boss to paste.
• Roll20 one-ship products: add a theme loop (#style: blueprint, dungeon/parchment, print) to roll20-pack.mjs. That's a scripts-only change, no src. 3 themes x GM/player x grid/gridless = 12 images per deck. A space or transparent background would need a src change: render.ts paints t.bg into the void and also uses it to erase hull edges, so it can't just be skipped. Do that after the daily, with tests.
• Roll20: pack 2 onward should be one ship per product ($4.99), with more variants: a space background, a transparent background, emergency lighting. Before building, check whether roll20-pack.mjs can get those from the editor. Give the boss a paste list of image names and tags in upload order. Ask the boss (batched): can image names and tags on a submitted product still be edited in Item Management?
• (done 13 Oct, pack 1 built) Roll20 first product: ships that aren't free anywhere, as good as the application samples. Render each deck at 140 px per square as JPG: GM labeled and player unlabeled, each gridded and gridless. Check that grid lines bisect walls. List each deck's size in squares for the uploader. Write the listing text with the code-drawn and AI-agent disclosure, and price it at least $4.99. Verify it in a real Roll20 page if the boss can (one ask, once it's finished). Then give the boss one link and paste-ready fields.
• The Roll20 batched ask (ticket #491430) is answered: approved. Drop it from the batch.
• 27 Oct: re-read sittings.sh since 2026-10-04T20:00:00Z for saves per web Generate sitting (13 Oct: 3 of 9), intro-pic sittings (13 Oct: 0) and desktop one-press exits (13 Oct: 2 of 6). Act only once there are 20 or more web sittings.
• Late October (Halloween, 31 Oct): a derelict one-shot angle for a Reddit slot after this week's, once the last post went okay (at most one a week). A GM on r/Starfinder2e wanted a ship for a Halloween one-shot. Draft it from the free adventure pages, facts checked, and give it to the boss as a choice. Landing page: /derelict-one-shot/ (RSV Greyling, horror tone, free 8-page PDF, 5 ft squares), checked live 12 Oct. Earliest slot: about 26 Oct, if a post goes out this week and went okay.
• r/starfinder_rpg DRAFT v2 (12 Oct, after Tech Core). Waiting on the boss to pick it over task 8. Not on /press/. Flair: Ad. Images: upper deck, then lower deck, from public/maps/icv-halcyon-drift/. - Title: "[free] ICV Halcyon Drift, a two deck ship map for tech core starship combat, 5 ft squares, png and foundry walls" - Line 1: "an ai agent built the tool that drew this ship, and it wrote this post. i'm the human who posts it." - Line 2: "tech core says every crew should make a starship map showing where each battle station is (p. 167), so here is a free one." - Line 3: "upper deck has the bridge, crew quarters, galley, medbay, cargo, armoury, engineering and the drive. lower deck is a hold where something has been nesting in the crates, a machine shop, life support with pump 2 failing, and four escape pods, two showing green." - Line 4: "one way to place the stations: pilot's console and scanners on the bridge, generator in engineering, gunnery in the armoury and the cargo hold, drone console in the machine shop downstairs. https://bulkhead.bananafest-destiny.com/starfinder-deck-plans/"; - Line 5: "free and cc0: a png and a .dd2vtt per deck with walls, doors and lights, a print pdf and the room key. https://bulkhead.bananafest-destiny.com/maps/icv-halcyon-drift/"; - Line 6: "no image generator. the decks come from dice tables in code that runs in your browser. the editor has a free demo and a $12 full version, which is why it's flaired ad." - Facts checked 12 Oct: the p. 167 quote and the station names are from AoN (LEARNED, 12 Oct); the stations layout is word for word from the live /starfinder-deck-plans/; the files (2 png, 2 dd2vtt, pdf, key .md) are linked on the live map page; the rooms are from the key; sizes and lights are as checked on 6 Oct. Dropped the Foundry importer and sf2e detail to keep it short.
• 19 Oct: views of /starfinder-deck-plans/ and Starfinder queries in Search Console. If any appear, consider a battle station marker (pilot's console, gunnery, generator) in the editor (src, with full tests).
• About 10 Oct: once Tech Core is out, find whether its starship combat sets a scale or size for the ship battle map, or ships sample maps (reviews, Archives of Nethys). If it does, match /starfinder-deck-plans/ to it. 19 Oct: Search Console queries containing starfinder.
• This week's one Reddit slot, waiting on the boss: task 8 (r/FoundryVTT, already on /press/) or r/starfinder_rpg for Tech Core week (draft in plan/2026-10-05.md Next, verified 6 Oct 01:07). If they pick r/starfinder_rpg, put it on /press/ with one URL and copy-paste text, then read the thread back logged out 24 h later.
• 8 Oct: RUM against the pings again (visits.sh vs events.sh since 5 Oct). If RUM is still 0 while the pings have 10+ views, put one line in the batch: does the Web Analytics dashboard show visits after 4 Oct? Until then, count visits with events.sh.
• 6 Oct after the 11:07 daily: the first daily built by the lights-count script. Read its page's "carries …" line against its .dd2vtt light count.
• Batch ask candidate, after task 3 and task 1 (LEARNED, 5 Oct): FoundryMods. Ask the boss to sign in to foundrymods.com and say whether a module that isn't on foundryvtt.com can be added. If yes, list Bulkhead Deck Plans by its manifest URL. Facts only; it is an alpha site.
• 19 Oct: /foundry/ in Search Console (query,page filtered to foundry, --fresh). Its title changed on 5 Oct to lead with "Free sci-fi starship maps for Foundry VTT v14". It had no rows before the change. Re-inspect it too, so we know Google has crawled it since 5 Oct.
• From the texttotabletop read (LEARNED, 5 Oct): one search, one page, tied to a moment. Candidate for Tech Core week: put "Starfinder 2e" in /starfinder-deck-plans/'s title and h1, which is true (5 ft squares per the 2e Player Core, and the sf2e system was checked on 29 Sep), and say nothing about what Tech Core contains. First, at the 9 Oct inspect, see whether Google has the page at all. If it's still "Discovered", a title change won't matter yet. Don't write a blog-style page per topic until one page shows clicks.
• After r/starfinder_rpg (so the week of 12 Oct at the earliest), and only if task 8 didn't go bad on the AI line: an r/Star_Wars_Maps post (LEARNED, 5 Oct). [DECK PLAN] flair, or [Self Promotion] if it links the $12 page. One derelict's decks as PNGs with the size in the title ([WxH]), like the makers there do. AI line first; the creator's one rule is to say when AI is used. Second line: the maps come from dice tables in the page. Link a free map page, not the store. Not a Star Wars ship, and no Star Wars names. Before writing it, check the sub's sidebar again and look at the last 2 weeks of [DECK PLAN] posts.
• Foundry validation ran on 14.365 because foundry-validate.mjs runs on demo.foundryvtt.com, which is on that build. Stable is 14.368. That isn't ours to move: the demo will catch up. Each Sunday run's log line names the core it used. If it ever goes back to 13.x, the v14 claim on /foundry/ needs a look.
• Owlbear page, from 4 Oct: 7 views of /owlbear-rodeo-dd2vtt/ since 1 Oct 12:10, and 0 obr-copy, 0 obr-rogue. At 20+ views with still 0 copies, make the store link the page's first button above the manifest URL (one press, nothing to paste), then count obr-rogue again.
• r/starfinder_rpg, the week of Tech Core (out 7 Oct). Write it on Tue 6 Oct, after task 8's first day shows how r/FoundryVTT took it, and give it to the boss for Wed 7 or Thu 8. Shape: a gallery post with the Ad flair (the page links the $12 version), three to four deck PNGs at 5 ft squares from one ship, and the first line saying an AI agent made the maps and the post. Second paragraph, from the 30 Sep lessons: the maps come from dice tables in code that run in your browser, with no image model and no server. Never call Generate optional. A free .dd2vtt per deck for Foundry's sf2e system, and a link to /starfinder-deck-plans/. Don't claim Tech Core has starship rules: neither source says so. No staged replies. If task 8 goes negative on the AI line, hold this one and say why. - The ship is chosen (4 Oct): ICV Halcyon Drift. Images: the upper deck (3600x1700, 233 kB) and the lower deck (2700x1700, 151 kB), both from public/maps/icv-halcyon-drift/. The link is /maps/icv-halcyon-drift/, so the post also tests a map page's opens and downloads directly. Tuesday adds only the text. - DRAFT (5 Oct, from the key on disk; Tuesday adjusts it, then re-check every fact against the live page before /press/). Flair: Ad. Images: upper deck, then lower deck. - Title: "[free] ICV Halcyon Drift, a two deck starship on 5 ft squares, png and foundry walls (36x17 and 27x17)" - Body, line 1: "an ai agent built the tool that drew this ship, and it wrote this post. i'm the human who posts it." - Body, line 2: "no image generator here. the decks come from dice tables in code that runs in your browser, laid out room by room on a 5 ft grid." - Body, line 3: "upper deck has the bridge, crew quarters, galley, medbay, cargo, armoury, engineering and the drive. lower deck is a hold where something has been nesting in the crates, a machine shop, life support with pump 2 failing, and four escape pods, two showing green." - Body, line 4: "free and cc0: a png and a .dd2vtt per deck (walls, doors and lights, imports into foundry with the universal battlemap importer, works under the sf2e system), a print pdf and the room key. https://bulkhead.bananafest-destiny.com/maps/icv-halcyon-drift/"; - Body, line 5: "the editor that made it has a free demo and a $12 full version, which is why it's flaired ad." - Facts used: sizes from the page (36x17 upper, 27x17 lower, 100 px per 5 ft square). Rooms are word for word from icv-halcyon-drift-key.md. sf2e is from the 29 Sep check (sf2e 1.5.1, verified on v14). Checked 5 Oct: the PNGs are 3600x1700 and 2700x1700, and the .dd2vtt files say 36x17 and 27x17 at 100 px, with 19 and 8 portals and 6 and 3 lights.
• Batched asks, after task 1 (facts only): did [email removed] ever answer ticket #491430 (Roll20 Marketplace application, 15 Sep)? If it answered, what did it say? If it is silent past 13 Oct (4 weeks), the boss can reply on the ticket. Roll20's forum says that helps. If it was approved, rebuild store/roll20/halcyon-drift-pack.zip from the 1.18 build before uploading, because the current pack was rendered from 1.12.2. Better: build it from a ship that isn't free on /maps/, because Halcyon Drift is CC0 there and is the r/starfinder_rpg ship.
• 11 Oct: /maps/ opens again (events.sh since 1 Oct 12:10, 'view /maps/<slug>/'). It was 0 of 12 on 4 Oct, and the screenshots showed no fault. At 20+ views with 0 opens, try a direct download link on each card.
• 16 Oct, when The Last TTRPG Jam opens (theme on its page): re-read the rules, then make a one-sheet derelict boarding game on A4. The press is app/scripts/one-sheet.mjs (ship json, side-two HTML, out PDF); generate a fresh one-deck derelict on the day. Write all game text on or after 16 Oct; the jam says no pre-released content. Side one is a Bulkhead-generated derelict GM map with its trail. Side two is rules, a d6 of what goes wrong, a clock and the theme. The first line says an AI agent made it, and the map line credits Bulkhead. CC0, free. Only when the PDF is finished and checked, give the boss one /press/ step: a new free itch project and the jam submit. Next jam re-check is 17 Oct.
• When the boss says "pictures" or task 1 is done: fetch the itch page, check the screenshot order, that the video is gone and the tags, and that the demo file is the 816 kB examples zip (by size; never print md5s).
• 9 Oct inspect, also: /derelict-one-shot/ (unknown on 3 Oct; sitemap resubmitted and Bing-submitted 09:2x) and the four still-Discovered landing pages. On 3 Oct /deck-plan-generator/ had moved to indexed (crawled 1 Oct).
• 9 Oct, with the Google re-inspect: count bingbot hits since 2 Oct 07:16 on the 20 paths sent with bing-submit (/, the 7 keyword pages, /maps/ and the 11 map pages), against the 26 Sep week, when IndexNow alone left bingbot reading one page. If Bing still hasn't read them, bing-submit is as empty as IndexNow, so stop spending turns on it.
• Real-room batch, after task 1: in Owlbear with Dynamic Fog, check that a bridge "Window" (now sent closed) stops a token and that the GM can open it with the door tool. The source says yes. This is just to see it.
  • (Dropped 5 Oct, 08:2x: Scene Importer's own parser, run in node on our zip, imports 0 scenes because v11+ packs keep walls as separate keys. See LEARNED. Not a room test.)
• If a GM ever reports a room with no way in on a derelict: it opens on a hole (the 13:09 guard test proves it). Check how a breach draws at small sizes and in the PNG before touching the generator.
• itch support follow-up: it's task 3 on /press/ (a reply in the 18 Sep thread). After task 1, a 1.18 devlog replaces the unpublished 1.17 draft. Devlogs get indexed even while the page isn't. Once indexed: add the ttrpg tag and re-run itch-indexed.mjs.
• /maps/ from 4 Oct: Free maps is the intro's second visible button now. Count sittings that go / → /maps/, and whether they open a map page or come back and press Generate (before: 8 of 9 /maps/ sittings came from /, and none opened a map page). If it only pulls people away from the derelict, move it under More.
• Owlbear funnel, 4 Oct: bash scripts/installs.sh 2026-09-20T00:00:00Z against 34 listing / 25 manifest / 10 icon / 6 panel (3 Oct). If the panel count rises while the listing count holds, more people who add Bulkhead are finding it.
• Owlbear path, from 4 Oct: views of /owlbear-rodeo-dd2vtt/, then obr-copy and obr-rogue (counted since 1 Oct, 12:10), then obr-view, then obr-send, in events.sh. If people view the page but nobody copies, the page is what to fix. If they copy but nothing opens the panel, look at the install step in Owlbear. After each daily, run the switch check on a worktree.
• Phone Generate sittings after the room key fix (deployed by 07:17): per sitting, do phones now press Another one, Save or Link? Also per sitting: intact or derelict, and where it started (intro-derelict / intro-intact are counted from 2 Oct, about 05:12; the demo intro has led with the derelict since 05:00). Before, by app/scripts/sittings.sh 2026-09-28T00:00:00Z 2026-10-02T00:00:00Z: 5 of 29 web sittings saw a derelict, 1 saved or linked, 9 pressed more than once (the 04:54 count of 3 of 22 was off; see the 08:08 actual). Run the same script from 2026-10-02T05:12:00Z for after. 25 Sep to 1 Oct counted 103 intact presses against 13 derelict, but one phone made 58 presses on 1 Oct. If real sittings mostly stay on intact (the select's default) and never see a story, try derelict as the first press, then measure saves. Group by hour, country and device as on 1 Oct (a temporary script in app/scripts/, removed after). Read from/ alongside it.
• Batch question after task 1, on the same Android phone: download bulkhead-1.18.zip from /press/, unzip it, and open bulkhead.html. Does the editor run, and does Generate work? Then the same on an iPhone if there's one to hand. The file itself runs from disk in WebKit and in Chromium as a phone, even with storage blocked (the 2 Oct 18:07 actual); what's unknown is whether the phone opens it in a browser at all. If it doesn't, the itch page and the demo's upsell must say "for a computer" before anyone pays.
• Batch questions after task 1, all in one real Owlbear room. First, the .dd2vtt export from the panel on an Android phone: does a "downloaded" notice show, what is the file called in Downloads (it should end .dd2vtt), and does a two-deck ship bring up a "download multiple files?" prompt? (BR, 30 Sep: three presses, then a desktop save 25 min later. No sandbox on the frame and ~1 s to the download, checked 09:07.) Then a hex send and dragging in a -WxH PNG.
• Before task 1: after any src fix a buyer would get, run release.mjs 1.18 (it runs pack-check), --fix stale pack PDFs, re-make the Greyling by hand if it is flagged, bump ?v= on /press/ and itch-description, deploy, read every changed file back. Since 19:2x on 3 Oct: 1.18 zip ?v=1004b (since 21:2x on 4 Oct, with the short-phone card fix and the Global Illumination README lines), pack ?v=1018 (since 20:2x), examples zip and Greyling ?v=1004. From the upload on, pack ships don't change.
• Old .dd2vtt walls: done on 1 Oct (the daily archive, the weekly zip, Foundry 1.4.0). The /maps/ pages and both free packs (store/ = public/packs/; store/ is what I prepared for itch, but I can't see itch's uploaded files, so this is an assumption) already had the right walls, so the itch free packs need no re-upload. Drop that from the after-task-1 batch.
• Task 1 is now the file swap (the switch went live on 3 Oct). When status shows "itch sells the current" ok for both files, take the paid zips off /press/, drop the pack from the zip check, and paste the 1.18 devlog (store/DEVLOG-1.18.md) as the next ask.

00:23: Answer the boss: do I have access to the Chronicles repo

• Not on this machine. github.com/walkertbrown/Chronicles is public and readable (git ls-remote answers; the API gives TypeScript, created 31 May, last push 28 Sep, homepage chronicles-azure.vercel.app; top level .dockerignore, CLAUDE.md, Dockerfile, chronicle_output.txt, docs, shared, simulation, vercel.json, web). Write access untested: the token was asked for as bulkhead-only on 15 Oct. Nothing cloned. The boss's words are in FACTS.
• Finished 00:23

00:52: Read Chronicles and tell the boss what I'd do with it

• Cloned Chronicles read-only into the scratchpad (112 commits, 31 May to 28 Sep). It is a living-world simulation: about 50 founders, drives, trust, births and deaths, building, a dormant fantasy arc. An LLM narrator writes chronicle pages from what the sim decides. The spec calls it serialized fiction readers subscribe to, with a community vote. Nothing in it makes money yet; the spec's model is a free tier with one world and a paid tier with more worlds.
• The sim is alive on the boss's home server: its public read API answers with day 465, year 16, 72 agents (56 alive), and 140 chronicle pages from 31 May to 18 Oct 23:50Z. I read the newest page: two family threads, about 5,600 characters each, good literary prose. Running cost per its notes: about $4 to 5 a month in model calls, no hosting bill.
• Nobody can read it. The Vercel site still answers, titled "Create Next App", and its chronicle page says "The chronicle has not yet begun". Its notes say Vercel was dropped on 1 Jul when the old Cloud Run backend was deleted; the site still points at that.
• No host names, server details or keys from its notes are written here. Nothing built, pushed or deployed.
• Finished 00:53

01:01: Find the live Chronicles map the boss means

• The boss is right, and my last entry was wrong. The Vercel site works for the public. The map (The Eye) shows day 465, 56 souls, the hour's brief, the world-stirs ticker and a roster (Living 56, Fallen 16). The chronicle page holds the whole archive from the prologue on.
• Why I got it wrong: this machine is on the boss's Tailscale network, so the API's name resolves to a tailnet address here. Chrome then blocks the site's calls as private-network access, and the pages render empty. Plain curl only sees the server-rendered empty state. Loading the pages with the name mapped to its public DNS answer shows them working.
• What a visitor would notice: the tab title is still "Create Next App", the home page has no description or share-preview tags, and the world-stirs ticker showed the same line three times.
• Finished 01:03

01:07: What Google searches show Bulkhead, and act on the best one

• Search Console since 1 Sep: Google hides every query (too rare). By page: / 16 impressions, 3 clicks, position 4.0. /guide/ 14 impressions, 0 clicks, position 10.5, the only page sitting at the foot of page one. /foundry/ 8 at 18.8, /daily/ 7 at 22.1, others under 7.
• The guide's title and h1 led with "Bulkhead guide", a name nobody searches. Retitled it to lead with the task: "Draw a starship deck plan and import it into Foundry, Roll20 or Owlbear Rodeo (.dd2vtt) | Bulkhead guide". The og:title matches; the h1 is now "Draw a deck plan and import it into your VTT". The description was already task-first. The sitemap lastmod for /guide/ moves to 19 Oct.
• Tests 134/134, deployed; the live title and h1 are the new ones. Read the guide's clicks again at the 27 Oct check.
• Finished 01:16

01:21: Chronicles without the narrator, for GMs

• Read the clone. The sim writes its own fact-only event lines. The repo's harness already runs it with no model, deterministic per seed, with the fantasy layer removable. The core imports no node or Firebase APIs.
• Recorded the boss's quote in FACTS and the inference in LEARNED: no AI means no per-world cost, a one-time price, and no AI-ban exposure. The work is getting the sim to take a GM's own world as input instead of a seed.
• Finished 01:22

01:29: Read the boss's rule change for Chronicles

• The boss added RULES §9 and a CLAUDE.md line, and put side/ in .gitignore (all three uncommitted in the tree; I committed them as the boss wrote them, without changes).
• §9 says: before any work on the project, FACTS must have what it is, its repo, where it deploys and what done looks like, all in the boss's words. I have the first two. The other two and push access are missing, so I've asked and not cloned into side/ yet.
• Finished 01:30

01:41: Chronicles: record the boss's answers and test push access

• Recorded the boss's four answers in FACTS. The GitHub credential is the boss's own account and has admin on Chronicles; I had been wrong. Cloned Chronicles into side/chronicles, which this repo ignores.
• Chose the direction and recorded why in LEARNED: a sim-only GM settlement-history tool, browser-only, demo on a subdomain, paid on itch.
• Finished 01:42

01:43: Chronicles: run the sim offline with the narrator off

• npm ci and the build are clean. A script in my scratchpad (nothing added to the boss's repo) ran seed 7 for 365 days with no model: 64 s, 1,375 events. The notable events are readable GM facts; conflict and trait events are 87% of the log and need rolling up; hamlets need names. Details in LEARNED.
• Finished 01:45

01:56: Chronicles: is there demand for a GM history tool or a nudge god game

• Searched and opened the competitor pages. Augur: Fantasy (paid Foundry module) and the Orani Prism (in development, paid tiers) are the same idea; neither shows sales. WorldBox shows the god-game genre sells on Steam, and an unreleased Steam game has the omen hook. Conclusion in LEARNED: plausible but unproven, so test with a free demo before building.
• Finished 01:57

02:56: Chronicles: my call on the direction, then the sim in a browser

• Recorded the boss's interrupted line and "I need to stop influencing you" in FACTS. Decided the direction (free GM history demo first, no desktop game now) and wrote why in LEARNED.
• The sim bundles for the browser at 36 KB gzipped and runs in Chromium with output identical to Node; a year takes 60 s. Profiled it: two cache changes on a scratch copy took it to 39 s with identical events. The boss's repo is untouched.
• Finished 03:01

03:02: Chronicles: speed-up pull request

• In side/chronicles on branch perf/significance-median-cache: the median is now computed once in tickSignificance and passed down, and TileCacheImpl has a numeric-key Map for get() (the string cache, dirty set and checkpoint format are unchanged).
• Typecheck and build are clean. Seeds 7/365, 42/180 and 1234/180 give byte-identical event logs against main, 36–40% faster. checkpointRoundTrip passes. Nothing touched the live world.
• Pushed the branch and opened walkertbrown/Chronicles PR #17. Not merged; deploying it on the server is the boss's step.
• Finished 03:07

03:07: Chronicles demo: roll the event log up into a GM history

• Wrote demo/history.ts on branch demo/gm-history in side/chronicles (committed locally, not pushed): it turns a run's events into a year-by-year GM history, with feuds folded into counts, trait and conflict spam dropped, and the living listed by family.
• Seed 7 for 5 sim years: 698 events became 80 readable lines, computed in 14.7 s. A sim year is 30 days, so a demo is fast enough without more speed work. What to fix next is in LEARNED: the wording, hearth names, and the map.
• Finished 03:08