b21 launch-3 — Critical cross-links inline (3 launch-blockers)#
dv_ClaOp47Max) at LLoL’s
request on 2026m05d22.1. Context#
The b20 cross-link manifest (§9) catalogued 20 nodes between the launch-unit artefacts; 6 are missing and 3 are critical for the launch:
dung-beetle post → b19 SGIR paper. Concrete proof-of-work that the audit-the-math ask is non-trivial.
b18a body → AuditTheMath landing + Matheo overview. The reader of b18a needs the action ask + paper-list anchor.
Buy-In → AuditTheMath (reverse). The reader who lands on Buy-In first (e.g. via dung-beetle’s Buy-In CTA) needs the verification path.
This prompt is inline edits, not architectural decisions — but EDEN/Max because each link’s placement matters (good UX vs ugly graft). Run AFTER launch-1 (Buy-In streamlining) which may already add the Buy-In → AuditTheMath link.
2. Tasks#
2.1 dung-beetle → b19 SGIR#
File: source/blog/posts/2026-05-21-prophetic-dung-beetle.rst
Add one cross-link to the b19 SGIR paper. Suggested placement: in the AuditTheMath CTA section (lines 401–425), as part of ask #1 (Read and respond) — naming b19 as the example paper to start with for an interested mathematician.
Test:
Does the new link land smoothly in the existing prose? (If the only way to add it is awkwardly, flag and propose a different placement; do not force.)
Does the metaphor sustain across the link? (b19 is the pandemic paper; the cross-link should not break the dung-beetle frame.)
Alternative placement: line 425 (after the final dung-ball line), as the b20 review’s E-DB-4 suggested. Decide based on prose flow.
2.2 b18a body → AuditTheMath + Matheo overview#
File: source/matheology/hell/mm/b/18/mmv2/b18-call-to-action_mmv2r1_2026m04d16.rst
Add cross-links per b20 §5.4:
L-B18A-3 equivalent: §1 Introduction first paragraph → link to Matheo-b11 (PET) + Matheo-b19 (SGIR) on first mention.
L-B18A-4 equivalent: §1 closing paragraph → link to AuditTheMath landing.
L-B18A-10 equivalent: Conclusion → link to dung-beetle blog post (narrative companion) + AuditTheMath landing (action companion).
For each insertion, use the :doc: form for internal RST refs.
Verify after each insertion that the link text reads naturally in context. If it feels grafted, propose moving it rather than forcing it.
2.3 Buy-In → AuditTheMath (reverse link)#
File: source/buy-in/index.rst
Add a single :doc: link back to AuditTheMath. Suggested
placement: in the “What ‘Buy In’ means” section (currently lines
30–40 of the placeholder), as the reader’s “verify before you
contribute” path.
Coordination note: if launch-1 (Buy-In streamlining) has already been executed, this link may already exist — check before adding. If launch-1 has NOT been executed, this is the minimum-viable Buy-In → AuditTheMath link; the streamlining in launch-1 will replace / extend this when run.
3. Test (across all 3 edits)#
After all three files are edited:
Run
make devfrom the repo root.0 new warnings introduced.
HTML build of each of the 3 files renders the new links.
Click-through each new link in the local HTML build to test the target page exists and is reachable.
4. Out of scope#
Any other cross-links (the b20 §5.4 P-1 grid is launch-4’s job; P-2 / P-3 grids are launch-7’s).
Reordering content to make cross-links fit better (TELES-scope insertion only).
Adding cross-links to other files (e.g. AuditTheMath landing, Matheo overview — these are out of scope for critical links; the b20 manifest shows their existing links are already PRESENT).
5. Deliverables#
Produce a single new LLog file at
source/matheology/hell/ll/infra/b/NN/bNN-launch-3-execution_<date>.rst
containing:
For each of the 3 edits: file:line of insertion + before/after excerpt (3–5 lines of surrounding context).
Build test result.
Click-through test result.
Any placements that proved awkward + the chosen resolution.
Concluding summary: which critical links are now in place.
Also update the infra index.
6. Timing & BABL-resistance#
Target: 30–60 minutes.
The BABL trap: scope creep. The b20 manifest lists 20 nodes; this prompt covers only the 3 critical ones. If during execution you notice other missing links that “obviously should be added,” flag them in the llog for launch-4 / launch-7 — do not add them inline.