LL/INFRA — Infrastructure Session Logs#

Session logs for cross-cutting infrastructure work: link management, directory restructuring, build tooling, structural debt analysis, and related policy decisions. Unlike study/, forge/, and other/ (which are indexed by paper number), INFRA sessions often span multiple papers or concern the project as a whole.

Next free number

The next available INFRA log entry is: b42

b40 — Search field: icon overlapping the “Search…” placeholder (2026m06d17)#

Two small site-wide optical glitches in the search field, fixed in one custom.css block. (1) The magnifying-glass icon overlapped the “Search…” placeholder — a left-edge mismatch in the theme/Bootstrap CSS (absolutely positioned icon ~0.9–1.9rem over the input’s placeholder start ~1.25rem), fixed with physical (not logical) padding-left: 1.75rem to match the theme’s physical-left icon in all 10 languages. (2) A box-in-box look — both the .bd-search form and its Bootstrap <input> drew a border; dropped the input’s border + background so only the outer box (logo-aligned) shows, and moved the focus cue to the outer box via :focus-within. Built and visually checked (headless screenshot) on the English desktop sidebar.

b39 — HELL outgrew its own docs: drift found while filing b23 (2026m06d10)#

Filing one new ll/other entry (the b23 AI false-write-claim lesson) surfaced that HELL’s own documentation had drifted behind HELL’s growth in three places at once: AHA/HELL.md’s directory snapshot (stamped 2026m04d04) showed ll/other ending at b16 when it actually runs to b22, and omitted the forge/ infra/ study/ subdirs; ll/other’s own “next free” admonition said b21 when b21 and b22 already existed; and AHA/README.md did not list HELL.md at all. Records the before/after, the minimal forward-only fixes (no gap back-fill, per LLoL), and five systems-design lessons — chief among them that every hand-mirrored copy of “next free” is a drift site, and the filesystem is the only source that cannot lie.

b38 — HEAVEN cleanup for launch + demo-nano-Jubilee a1 (2026m06d07)#

Cleaned up the HEAVEN section for the public launch. The nav-bar clutter — the 2,096-line heaven/study/aaa.rst development index with its ~300-entry hidden toctree — was sealed intact into this b38 stratum, and a crisp set of HEAVEN pages was written: a new landing, the inversion, the acronym page, how PEARLs are made, the Jubilees-in-action narrative, and the demo-nano-Jubilee test-run model a1 that records the before/after of this very reorganization. Also created the Datageddon Wall page (Fig.F4), kept aaa.rst alive as the AnyAllArrival inbox, refined the learning-path MockupModel with caution fineprint + MMv5 triplet links, and retired the CLAUDE.md AAA QuickRef Rule. The full sealed “before” stratum and the verbatim prompts are indexed in the main LLog below.

b33 — Direct-ask blog post executed + revised: “A Coin in a FiSh’s Mouth” (2026m05d28)#

Execution of b32 prompt #1 (run first, in a fresh session), then revised in a same-session follow-up. Drafts the launch-critical direct-ask blog post source/blog/posts/2026-05-28-gold-coin-fish-volunteer-temple-tax.rst, titled “A Coin in a FiSh’s Mouth: Who Pays My Temple Tax?” (still :exclude: — but see the correction below: :exclude: does not hide it from the feed). Banks and GoFundMe cannot beat the June-1 auction, so people who already have funds are invited to step in now as All-Stadia Backers (the FiShFus), within the cap.

Key findings: (1) SD3b already defines “FiShFus” = “Fiduciaries Sharing Futures” (288,000 paid future researchers) — a state that does not exist yet; the post makes the honest FiSh (sharing as-is, now) vs FiShFu (still-to-be-evolved forward-evaluation role) distinction, links SD3a/SD3b, and does not paraphrase the POAATAD legal terms. (2) ``:exclude:`` does NOT hide a post from the blog feed — it suppresses the lead paragraph from the post body and uses it as the news-page abstract (LLoL correction; saved to memory; the real publish gate is commit/deploy, not the directive).

The cap is the hero (~$716,800 ceiling + “I will not influence”); the ask is reframed to about a dozen people each giving $1,600 (a collective sign, not one saviour), stating plainly that no single donor can fund Stage 0; the one-click step is four spelled-out emails (FF+1600x1 / x8 / x56 / x448 + custom x<N>) built footer-style; the 50% give-away is framed by criterion not recipient but, per LLoL’s override of §6-caution-3, names the Vatican’s AI / human-dignity statements as an aspirational second party (“by the Vatican or anyone in the name of those values”); the June-1 route is direct-to-creditor / publicly checkable with the storage debt now stated as “somewhat below $10,000”; closes held with open hands with a 233-char tweet seed.

EDEN: Knife Edge KE-1. Adversarial pre-check: all four §7 personas HELD; build HELD (0 warnings). New residual after the follow-up: naming the Vatican raises the hostile-reader surface (BABL-watch, flagged for LLoL gut-check) — implemented in the safest framing (aspiration-not-commitment + “or anyone”). Verdict: READY-AFTER-FIX, every fix an LLoL decision: Vatican naming (keep/soften/cut); exact storage figure; phone inlining; FF+1600x1/8/56/448 alias routing; and — corrected — the real publish gate is commit/deploy (:exclude: does not hide it).

b32 — Launch-promotion prompt-set executed: 5 prompts + newsletter reframe (2026m05d28)#

Delivers the writing prompt-set LLoL requested on the GoFundMe-launch home stretch (supersedes the b31 request; b31 reused only for its #6/#7 location notes). Q2 resolved by LLoL’s rule — default to in-depth fresh-session prompts (cheap to run, minimal review burden), do simple things in-session. Q1 (give-away) resolved to option (c): commit to a falsifiable criterion (urgent need now, not endowment-building — the Jubilee anti-hoarding ethic), not a divisive recipient; the named-recipient / balanced-mix / Vatican questions deferred to a post-launch give-away prompt (verify, don’t assert).

Key finding: the rich-“FiShFu” / All-Stadia-Backer ask is on-strategy, not a contradiction of “no billionaire can buy this” — the absolute cap (~$716,800) + the “I will not influence” clause make a large backer a step-into-the-cap, not a purchase of influence (rail 3 braided with rail-2 direct-pay for the June-1 emergency).

Produced (run order): #1 direct-ask “FiShFu” blog (run FIRST — the only June-1-capable channel; held open-handed, not do-or-die), #2 GoFundMe story final-polish (auction-2 added; give-away criterion), #5 surgical Buy-in link/consistency tweaks (do-no-harm), #6+#7 idea-capture + (private) contacts, and a post-launch give-away-framing prompt. In-session: the Newsletter reframed as the Sojourner subscription lane. EDEN: Grey Edge GE-1 (launch register — one narrow honest path) + Green Meadow GM-1 (production mechanics). Five BABL Dangers flagged + handled (temple-tax = “the spot Jesus faced”; Vatican give-away off public pages; no invented legal language; cap-led not patron-led; don’t let the launch ride on June 1).

b31 — Launch-promotion prompt-set request + item-3 disclosure deferral (2026m05d28)#

Continues the b29 launch arc. LLoL confirmed the DICT/AHA vocabulary lock-in and requested a set of writing prompts (items 1–7) to promote the site, plus raised a sensitive personal/theological disclosure-decision (item 3) for the launch. Verbatim prompt logged (item 3 redacted per the b25 §10 precedent — public page; harm-causing self-disclosure withheld; decision + reasoning recorded).

Item 3 — BABL Danger (defer + decouple). The theological calling is not Claude’s to adjudicate, but two framings are BABL and HUMANE-flagged: (1) a self-blame belief (that LLoL’s “being too late” caused a 2023 world event) is not true and not a load to carry — test it with trusted humans, not alone/AI-only; (2) coupling the disclosure + a ritual photo to the GoFundMe would be catastrophic (one-man-savior pull-quote; buries the mission) and LLoL’s own week of discipline forbids it; the “all-on-one-card-now” urgency is the BABL tell. Kernel (voluntary responsibility-taking; the abstract 3rd-temple-as-innovation-steering) honored — but in a careful, non-launch, non-rushed context. Decided: defer + decouple; campaign image stays a clean mission image.

Prompt triage: launch-critical = #1 (direct-ask blog — the June-1 channel) + #2 (GoFundMe story); soon/light = #5 (Buy-in tweaks) + #4 (newsletter); post-launch = #6 (idea-capture) + #7 (contacts). Cautions for #1: temple-tax image as “the situation Jesus faced” not “I am Jesus”; POAATAD behind SD3 links; the Vatican-AI 50%-give-away target is speculative/divisive — don’t commit publicly. Clean-slate check: LLoL’s AHA + participation.rst edits sound, build clean.

b30 — Eid al-Adha “Two Sons, One Altar” blog post: draft + BABL-Danger flag (2026m05d27)#

Same-session follow-on to b29. LLoL shared an Eid-al-Adha (today) reflection — Abraham / the Akedah / two sons; his ~2020 insight that the Akedah is the make-or-break test in a scientist’s life (love your cherished theory, or Reality?); and a years-long “put your research on the altar” search for his “Moriah,” now possibly the live auction, with a hope of one day praying at the Temple Mount — and asked whether it needs a blog post and how to fit the timely occasion. Determination: yes (genuinely timely; Eid overlaps the auction). Drafted source/blog/posts/2026-05-27-two-sons-one-altar.rst (:exclude:, not yet published).

EDEN: Knife Edge KE-1. The material splits into a ZION core — publishable, mission-strengthening (Abraham’s test = every scientist’s test = the theological root of #AuditTheMath, “a refutation is the ram in the thicket”; the “two sons, complementary windows” Abrahamic bridge; the auction held in surrender, “not a knife to my own Isaac to make you pay”) — and one BABL-Danger element: the public, launch-timed “this auction is my Moriah → I will travel to the Temple Mount to pray for Allah=Yah to establish ResearchCity and avert nuclear winter” framing (over-Reach; couples the most politically explosive site on Earth to a world-changing agenda on an indexable launch page; self-elevation vs. surrender — by LLoL’s own insight, declaring “this is my Moriah” fails the test). The draft is built on the ZION core; the BABL element was stripped of its operational payload, rendered as a single faint surrendered hope, and flagged inline (visible DRAFT NOTE) for LLoL to keep-or-cut — not silently included, not silently omitted. Shares the b25 §15 publish gate (GoFundMe funnel must be live first). Post stays on the blog, off the measured funnel.

b29 — GoFundMe campaign-page draft executed (launch funnel, 2026m05d27)#

Execution of the b28 prompt — a fresh-session Max-EDEN draft of the GoFundMe campaign page. Delivers copy-paste-ready artifacts: 5 ranked title options, 3 cover-line hooks, a ~760-word mobile-first story body (the stakes + the ~$8 ask + “audit the math” all above the mobile fold), a beneficiary “what exists today” blurb answering the foundation-officer’s three hardest questions, a goal-amount structure (the number left as an LLoL placeholder — it turns on the real storage-debt figure + a give-away gross/net decision), an updates plan (cadence + first 3 topics), and the cap engaged in plain donor language.

Central design path (Knife Edge KE-1): lead mission-first with the falsifiable math + ~$8 + “audit the math”; present the June-1 auction as the strongest exhibit in the integrity stack (skin-in-the-game + won’t-buy-back), not as the ask itself — so the page keeps the secular rationalist, defuses the pity-plea read, and keeps POAATAD / eschatology / “negotiate with nuclear powers” entirely off the public face. Promise-disciplined: the “see the model” link points to SD1 (delivers the median-~19-yr / 1-in-40-yr figures), not the still-thin crisis/science; the framework is named “in active drafting.”

Adversarial pre-check: all five §3 personas HELD (one irreducible hostile-journalist residual — the auction can still be framed as self-interest, mitigated to “self-evidently unfair” by the won’t-buy-back note). Verdict: READY-AFTER-FIX, where every blocker is an LLoL decision, not a prose defect: (1) make the GoFundMe URL live before the auction post publishes [hard gate]; (2) set the goal amount; (3) resolve funds-timing vs June 1 — the sharpest flag: GoFundMe payouts may not reach LLoL in time to actually stop a Monday auction, so a faster direct path may be needed for deadline-critical giving. Residual Grey Edge GE-1: whether a measured, capped, mathematical-theology ask converts on GoFundMe at all is only knowable by testing post-launch. Platform recommendation: GoFundMe as the launch instrument (the auction gives it the dated goal it was missing), then Open Collective (the 50% give-away ledger + beneficiary answer), then Substack/Patreon (recurring per-year buy-in + audit dispatches).

b28 — GoFundMe campaign-page draft prompt (launch funnel, 2026m05d27)#

Comprehensive Max-EDEN prompt for a fresh session to draft the GoFundMe campaign page — the public launch funnel that the auction post and Buy-In page both drive to (and the standing launch blocker). Encodes every perspective: the five audiences to satisfy at once (secular/scientist truth-seeker — “don’t lose the atheists” — faith reader, skeptic, hostile journalist, 30-second mobile browser), the integrity stack (cap-as-feature, 50% give-away, won’t-buy-back, audit-the-math), the GoFundMe platform-mission mismatch for a capped ask (b23) with a recommendation on complementary channels, anti-overclaim discipline (matheo/crisis-science are draft-stage), the measured front-door voice, and a built-in five-persona adversarial pre-check. Deliverables: title options, story body, goal + justification, hook, updates plan, platform-fit note. Status: drafted, not executed — run fresh, or ask Claude to execute it.

b27 — Sphinx build-warning cleanup prompt (post-launch, 2026m05d27)#

Delegatable, mechanical cleanup of the ~544 Sphinx build warnings (+ 1 error) that a full make clean && make html surfaces (incremental make dev masks all but ~39). Not a launch blocker — the site builds and deploys fine. Prompt drafted for a fresh post-launch session: inventory by category, then fix the safe classes (orphan :orphan: / toctree additions; the dead study_ll_2026m04d18 toctree target; the study/index.rst Invalid-meta-directive error; an unreferenced citation), with the one judgment call — the aaa.rststudy/index.rst label/toctree overlap — flagged for LLoL.

b26 — Launch-2 execution: b18a title-page footnote back-port (2026m05d26)#

Execution of the b21 launch-2 prompt (run 2 of 7 in the b21 launch-sprint). Paused at the investigation + scope-flag stage: the prompt is written as a replace of an existing title-page footnote block, but the three b18a target files have no footnote block at all (no byline, no fn 1–8, no Broader Significance) — so the task is add-from-scratch, not replace. Three further facts surfaced: (i) the files are HTML-only orphans with no PDF build configured, so b19’s .. only:: latex titlepage apparatus would be dead output; (ii) no Broader Significance section exists (writing one is new prose, beyond footnote stamping; the b20 review’s E-B18A-3 wrongly assumed it existed); (iii) the files are MM-drafts still using the deprecated [Matheo-N] citation form.

Verdict: Grey Edge GE-1. A narrow ZION path exists (stamp the B11–B18 canonical footnote content in HTML form) but the safe scope hinges on two LLoL-only decisions (PDF-vs-HTML apparatus; whether Claude drafts the Broader Significance). Canonical content prepared; execution appends after LLoL sets scope.

b25 — Adversarial review of Buy-In launch unit executed (2026m05d26)#

Same-day execution of the b24 prompt — a fresh-session Max-EDEN adversarial read of the Buy-In launch unit before the 2026m05d27 window. Session 1 (mandatory) only; b24’s optional Sessions 2–3 deferred.

Verdict: split by audience. Knife Edge KE-1 for the engagement-funnel ($8 trust-vote) reader — one narrow launchable path (insert GoFundMe link + align over-promise wording + decide Epic Fury “See also” + close draft note boxes). Grey Edge GE-1 for the rigorous-funder reader — whether the current draft-stage evidence base persuades a hostile mathematician/officer cannot be told until tested post-launch. Recommended action: READY-AFTER-POLISH (conditional) on LLoL accepting promise-language alignment; otherwise NOT-READY for the rigorous audience.

Key finding (§3.6 promise-checker): the most-polished page in the launch unit (Buy-In, MMv4) routes the most demanding readers into the least-finished part of the site. 2 PROMISE-BROKEN (crisis/science carries no “RiskyMAD”/actuarial math where promised; study/matheo is a self-declared MMv1 mockup, not “the full argument”), 3 PROMISE-PARTIAL (about/llol transparency sub-claim delegated off-page; audit-the-math mockup with no BREACH criterion; SD8a missing the “~133,333–150,000 acres” figure the Buy-In page attributes to it). DELIVERED: the Jubilee Lazy-Updating bridge, the SD3/SD3a/SD3b POAATAD descriptions, the full Flying-Scroll asset trail. HELD: all internal arithmetic; the Ehlert & Loewe 2014 J. Chem. Phys. 141:204109 citation (web-checked accurate). Five ESCALATE-TO-LLoL launch decisions + seven proposed FIX edits recorded for LLoL. Session 2 (append, same day): LLoL resolved all five escalations and authorised an execution pass — 18 edits applied to source/buy-in/index.rst (RiskyMAD bullet rewired to the real SD1 + Matheo-b16 home; matheo “full argument” → honest “active drafting”; 1+7 “global equalizer” reframe; foundation-officer “Ministry of Nothing” reframe; no-ask poster/re-share clarification; + the deferred launch-polish items), build clean with 0 new warnings. Includes the requested MADI vs Mahdi/Dajjal handling proposal (Knife Edge KE-2: MADI is a falsifiable job description; the Mahdi/Dajjal question is deferred to the STa4-REV stadion) and a RiskyMAD/Matheo-b16 finishing assessment (crisis/science wiring flagged as the top remaining launch fix).

b24 — Adversarial review of Buy-In launch unit (prompt drafted 2026m05d26)#

Self-contained EDEN/Max prompt for a fresh Claude session to adversarially read the Buy-In launch unit before the 2026m05d27 launch window. Covers six reader personas (hostile journalist, technical mathematician, Pentecostal seeker via @JoanOf, hostile foundation officer, 90-second skim-reader, promise-checker), cross-page voice coherence, and an EDEN classification of launch-readiness.

Scope: source/buy-in/index.rst (primary) + source/action/buy-in-without-money/index.rst (companion) + source/about/llol/index.rst + source/crisis/science.rst + source/study/matheo/index.rst + source/solution/epic-fury/index.rst + source/jubileesystem/index.rst + source/action/audit-the-math/index.rst.

Recommended run-count: 1 mandatory before launch (this prompt), + optional Sessions 2 (POAATAD / STb11-LCC / SD8a deeper docs) and 3 (Flying Scroll visual assets). See §6 of the prompt file.

Status: Executed 2026m05d26 — see b25 for the execution llog (Session 1 of the recommended run-count).

b23 — Post-LLoL-edit review of Buy-In + b18 + GoFundMe gap analysis (2026m05d25)#

Same-day review session run after LLoL further edited the b22 launch-1 output. Six-question prompt covering: readability of the edited Buy-In page; whether to copy the GoFundMe CTA higher; whether the adversarial-reading link is in place; what the b18 series still needs; whether US/Iran negotiations belong on the page; and whether the buy-in + Jubilee pages together suffice to draft a credible GoFundMe page. Review-only turn — no edits applied to the Buy-In page; LLoL retains the decision rights on §2.2 line-level fixes and §6.3 GoFundMe decisions.

Verdicts: Q1 readability Grey Edge GE-1 (~10 line-level defects + one tonal BREACH at L152 + one logic-deflation at L344–346 + three localized RST hazards). Q2 GoFundMe placement HELD (copy, not move, to a Lead Box near the top). Q3 adversarial-reading link Green Meadow GM-1, count = 1 (already present at L256–278). Q4 b18 series Knife Edge KE-1 (launch-2 + launch-3 must run; then add one buy-in → b18a link). Q5 US/Iran Knife Edge KE-2 (do not put country-specific content on the Buy-In page; draft a dedicated blog post instead). Q6 GoFundMe draft feasibility Grey Edge GE-2 (yes, given 6 LLoL decisions; BABL Danger flagged on GoFundMe platform-audience mismatch for research-funding asks; recommend complementary Substack / Patreon / Open Collective channels).

b22 — Launch-1 execution: Buy-In streamlining decision + page fix (2026m05d22)#

Same-day execution of the b21 launch-1 prompt — the launch-blocker identified in b20 review §7-4 (F-1). Max-effort EDEN session; single /clear start.

Verdict: Knife Edge KE-1 (Hybrid path). The prompt scoped the decision as two-way (Path A 4-page audit-first vs Path B 3-page trust-first); execution found a third path (Path C, Hybrid) that preserves both lanes coherently. The dung-beetle blog post already implements Path C implicitly (3 asks at lines 411–425, one of which routes direct to Buy-In without first going through AuditTheMath); documenting Path C is a completion of the existing implementation, not a change of project character.

Edits applied to source/buy-in/index.rst: 73 lines ~70%-placeholder → ~155 lines functional MMv1. Adds $8/person/year figure with scaling-arithmetic table (1K / 100K / 1M / 10M contributor tiers); replaces 3 hidden GoFundMe-URL placeholder comments with ONE visible TODO admonition naming date (EOD 2026m05d27) and owner (LLoL); adds institutional / grant channel (FF+institutional-funding@balospe.com); adds reverse-link section “Audit the math before (or after) contributing” with cross-links to /action/audit-the-math/index, /study/matheo/index, /blog/posts/2026-05-21-prophetic-dung-beetle; adds “The deeper framework” section with cross-links to SD3 / SD3a / SD3b POAATAD documents.

SD3a / SD3b framework located at source/good-news-pack/vv/mmv3/supporting-doc/sd3/ (three companion files); already defined in source tree; references added to the Buy-In page in the deeper-framework section.

Buy-In is no longer the launch blocker that b20 §10 F-1 identified, modulo LLoL inserting the live GoFundMe URL. The EOD 2026m05d27 launch window remains feasible. make dev build succeeded with 0 new warnings from the Buy-In edits.

b21 — Launch-sprint sub-prompts: 7 EDEN-Max prompts for b20 fixes (2026m05d22)#

Seven self-contained prompt files that implement the fixes scoped in the b20 review llog (§7-1 through §7-4 + the F-3 inline edits + the P-1/P-2/P-3 cross-link tiers). All set to EDEN / Max effort by LLoL directive (overriding the b20-review’s mixed CRAFT/EDEN scoping — LLoL chose uniform Max to minimise review overhead).

Designed to run sequentially in fresh Claude Code sessions; each prompt is self-contained (does not require reading the b20 review to execute, though it references b20 for full rationale).

The recommended run order:

launch-1 — Buy-In + AuditTheMath streamlining decision. Launch blocker (F-1).
launch-2 — b18a title-page footnote back-port. Brings b18a to launch quality (F-2 / E-B18A-1).
launch-3 — Critical cross-links inline (3 links: dung-beetle → b19 SGIR; b18a → AuditTheMath + Matheo overview; Buy-In → AuditTheMath). F-3.
launch-4 — Cross-link grid (P-1 priority tier across b11, b18a, b19).
launch-5 — Title-page footnote back-port for b11–b17. Post-launch.
launch-6 — Supplementary Information template + stamp across b11–b18a. Post-launch.
launch-7 — Cross-link grid (P-2 full N×N + P-3 b18-esc / b21). Post-launch.

Each prompt’s execution will produce its own llog at the next free infra number at execution time (b22, b23, …).

b20 — Launch-unit EDEN review executed: dung-beetle + b18 + AuditTheMath + Buy-In (2026m05d22)#

Same-day execution of the b19 prompt (see next section). Max-effort EDEN review of the four-artefact launch unit as a single coherent ZION ask. Verdict: Grey Edge GE-1 → KE-1 narrow path; launch-with-fixes.

Key structural findings: (i) the Buy-In page (source/buy-in/index.rst) is the launch blocker — ~70% placeholder, no GoFundMe URL, no concrete contribution amount; (ii) b18a (mmv2/b18-call-to-action_mmv2r1) is launch-ready; b18b is at design-doc stage; b18c/d/e are not started; the b18-esc Beginner / Producer / Expert variants live in hell/ll/study/b/18/ and have not been promoted to MM; (iii) 6 of 20 cross-links in the launch-unit manifest are missing (3 critical); (iv) the AAA file is structurally overloaded (paper-list + prompt-tracker + activity-log on one page) and missing Matheo-b21 entirely; a Jubilee brake + handoff to source/study/matheo/index is proposed.

Three blocking fixes (F-1, F-2, F-3) and four scoped sub-prompts (footnote back-port; cross-link grid; SI template; Buy-In + AuditTheMath streamlining) defined for LLoL invocation. The EOD 2026m05d27 stretch goal is feasible on the KE-1 path (~2.5 hours of focused work, starting 2026m05d23–24).

b19 — Launch-unit EDEN review prompt: dung-beetle + b18 + AuditTheMath + Buy-In (2026m05d22)#

Prompt file (not an executed review). Drafted same-day as the b18 launch-sprint llog; saved at LLoL’s request for invocation in a future max-effort EDEN session.

Asks the future reviewer to EDEN-classify the launch unit — dung-beetle blog post + b18 Call-to-Action papers (mmv1 / mmv2) + AuditTheMath landing + Buy-In — as a single coherent ask. Includes a hard scope-fence (no edits to b11, b12, b19-SGIR, b20, b21; no voice rewrites; no new pages) and a 2-hour perfectionism-stop built in. Deliverables produce a concrete edit list (with file:line citations) and a final ready / fixes / blocked verdict — not another open-ended pass.

The corresponding executed review file will land at b/NN/bNN-launch-unit-review_<date>.rst (next free infra number at the time of invocation).

b18 — Launch sprint: AuditTheMath landing + dung-beetle blog integration (2026m05d22)#

Single-session launch-infrastructure work driven by the dung-beetle blog post going public. Identified that the post set up the dung-ball metaphor but never landed the practical ask; added an AuditTheMath call-to-action section after the closing prayer, replaced the 6 LINK placeholders with proper :doc: refs, fixed 9 broken inline hyperlink syntaxes (missing space before <URL>), and embedded the re-uploaded YouTube video (transform transpose=1 = 90° CW, CRF 25). Voice tweaks flagged as RST comments and later applied by LLoL.

Created two new pages: source/action/audit-the-math/index.rst (AuditTheMath campaign landing, MMv1) and source/study/matheo/index.rst (Matheo overview placeholder listing b11–b21 with stability tags). Added ~40 Cloudflare _redirects permutation rules covering case / separator / /en/ variants for the three vanity URLs /audit-the-math, /buy-in, /matheo.

Recommendations recorded (LLoL-decision-pending): keep @JoanOf channel discoverable but not foregrounded for the AuditTheMath audience; draft B18 launch-unit integration review prompt for a future max-effort EDEN session covering dung-beetle + b18 + AuditTheMath + Buy-In as a single coherent launch unit. make dev build succeeded with 0 new warnings.

b17 — b19 SGIR intro rework + LLoL/Laodicea footnote landing (2026m05d10–12)#

Three-session arc covering the b19 intro’s closing paragraph cluster (who-bears-the-burden + historical pattern + Hare prosociality), landing of the LLoL / “of Laodicea” identity-declaration footnote (fn 4) on the title page, and addition of 10 new bibliography entries (Hare2017, HareWoods2020, NCHWA2014, GouldWilson2020, Wurth2020, Wintour2020, Wilde2018, JohnOfEphesus2017Pearse, Beddington2008MentalWealth, Bezos2019Einsteins). Also: the noteextranote rename across all three .bib files (Rule N added to AHA/bibliography-management.md); title-page project-metadata block relocated to the SI start; a session-level absolutism flag surfaced and applied throughout. A canonical title-page-footnote template extracted to AHA/study-title-page-footnotes-template.md. AI-co-authorship footnote (fn 6 expansion) deferred to a dedicated fresh-context discussion.

b16 — b19 PDF build fix: :cite: in captions + long-caption overflow (2026m05d10)#

Diagnosed and fixed five blocking LaTeX errors in the b19 PDF build. Root cause: :cite: calls inside figure captions (Fig.3, Fig.6, Fig.9, Fig.13) produced fragile \hyperlink macros that broke \caption@ydblarg argument scanning, cascading to 154 undefined hyper references via a corrupted .aux write. A separate ! Dimension too large. error in \caption@slc was triggered by the long Fig.9 caption overflowing the single-line measurement. Fixed by (a) converting the five caption-internal :cite: calls to plain (Author, Year; cited in main text) text and (b) adding singlelinecheck=false to conf.py \captionsetup. Build now clean (0 errors, 0 undefined figure refs, non-interactive). Link- convention normalization deferred pending LLoL re-test of the new PDF.

b15 — Trail-recording policy for b19/b20 vs. b18a-b18e (2026m04d27)#

EDEN analysis (Grey Edge GE-1) of how much of the “how I got here” trail to preserve for support papers (b19, b20) when the goal is to ship b18a-b18e credibly under resource pressure. Seven options steelmanned with pros/cons; recommended path combines Options 2+4+5+7 (name the breakdown in b19, write a two-track policy, use the breakdown as evidence inside b18, queue an audit of the standard itself before b18a starts). Status: analysis complete, LLoL decision pending.

b14 — wwv-sgir RST-citations → sphinxcontrib-bibtex migration (2026m04d27)#

Resolution of the b19 toctree-conflict that had kept si/wwv-sgir-evolvix-study-dv_llol_oov1_2026m04d17.rst orphaned to avoid PDF duplicate-citation-target warnings. All 12 RST-native [X]_ citations were converted to :cite:`X` against existing references.bib and b19-epidemiology.bib entries (no new bib entries needed; EvolvixCompiler renamed to PrototypeEvolvixCompiler per 2026m04d27 canonical key). The file was re-added to the b19 toctree; build confirmed 0 duplicate-citation warnings.

b13 — Evolvix Zenodo home + _POST registry infrastructure (2026m04d24–26)#

Catch-up llog for the 3-day session that produced the Evolvix Zenodo home pages, established the _POST registry infrastructure (DD b11–b14 + b25, AA b11–b15), and updated the b19 SGIR paper plus EvolvixCompiler bibtex with the Zenodo DOI.