.. Migration note (2026m04d04): Claude copied this file during VV-to-HELL migration.
   Old path: ``vv/jub/oov2/prompts/prompt_2G-1.rst`` (as given by LLoL)
   New path: ``hell/ll/jub/b/44/prompt_2G-1.rst`` (as chosen by Claude)
   Category: JUB OOv2 prompt

.. meta::
   :description: Execution prompt for stress-testing mathematical rigor across all JUB OOv2 quest resolutions that claim logical or formal proof-level support.
   :keywords: JUB OOv2, Phase 2G-1, stress-test, mathematical rigor, Se1, logical chain, proof audit, adversarial review, skeptical
   :author: Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea, ClaudeOp46Max, Anthropic, and Spirit of Boolean Truth
   :og:card:title: Phase 2G-1: Math Rigor<br>Stress-Test Prompt
   :og:card:description: An independent reviewer audits every mathematical claim in the JUB OOv2 quest with skeptical rigor, looking for gaps in logical chains.

.. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26
   OO :description: Prompt for Phase 2G-1 stress-testing mathematical rigor of all JUB OOv2 quest resolutions claiming logical support.
   OO :keywords: JUB OOv2, stress-test, mathematical rigor, Se1, logical chain, Phase 2G-1, matheology, adversarial review, proof audit
   OO :og:card:title: Phase 2G-1: Mathematical<br>Rigor Stress-Test
   OO :og:card:description: Prompt for an independent reviewer to audit mathematical claims in the JUB OOv2 quest with skeptical rigor.
   PP :description: Execution prompt for stress-testing mathematical rigor across all JUB OOv2 quest resolutions that claim logical or formal proof-level support.
   PP :keywords: JUB OOv2, Phase 2G-1, stress-test, mathematical rigor, Se1, logical chain, proof audit, adversarial review, skeptical
   PP :og:card:title: Phase 2G-1: Math Rigor<br>Stress-Test Prompt
   PP :og:card:description: An independent reviewer audits every mathematical claim in the JUB OOv2 quest with skeptical rigor, looking for gaps in logical chains.

.. SOCIAL-CARD-REVIEW --- generated by Claude Opus 4.6, 2026-03-26
   dv_ClaOp46_PP_2026m03d26 --- max-effort rewrite, read full page.
   :description: 142 chars | :og:card:title: 40 chars (excl <br>)
   - [ ] PP title more compelling than OO title
   - [ ] PP description more accurate than OO description
   - [ ] Description hooks without misleading
   - [ ] Keywords specific to this page's actual content
   - [ ] No language rule violations
   - [ ] Character counts verified

*********************************************************************
Phase 2G-1: Stress-Test --- Mathematical Rigor
*********************************************************************

.. note::

   **200K-token execution prompt.** Copy-paste everything below the
   horizontal rule into a new Claude Code session. This is the first
   of 3 independent stress-test sessions (2G-1, 2G-2, 2G-3). They
   can run in any order. Their outputs feed into 2G-4 (Convergence).

----

/clear
/compact
/effort max

You are an independent mathematical reviewer conducting a stress-test
of the JUB OOv2 quest. This is Session 2G-1: examining the
mathematical rigor of all resolutions that claim mathematical or
logical support (Sphere Se1 objections).

CONTEXT: Phase 2F has integrated all 33 objections from 3 rounds of
adversarial review into quest.rst. Each objection has a Con entry
(the critique, steel-manned) and a Pro entry (the response). Many
Pro entries claim "fully resolved" status. Your job is to audit
those claims with the skepticism of an independent reviewer.

Your goal: identify the strongest remaining mathematical weakness
in the framework, AFTER considering the best available replies.

You are NOT looking for new objections. You are re-examining the
existing 33 objections, focusing on those in the Se1 (Mathematical
Proof) sphere, and asking: are the resolutions genuinely rigorous,
or do they rely on plausible narratives disguised as proofs?

Then express an opinion about how much effort should be spent on
looking for new objections: (a) AI effort (b) human effort.


====================================================================
STEP 0 --- READ ALL REQUIRED FILES (DO THIS FIRST)
====================================================================

  ax1_A1. QUEST FILE (all 33 Con/Pro entries, ScoreBoard, Round Summaries):
  source/matheology/jub/quest.rst

  ax2_A2. CRITIQUE ROUND 1 (C1--C14) --- original Se1 arguments:
  source/matheology/vv/jub/oov1/llog/llog_2026m03d18_opus-critique-1-of-jubilee-argument.rst

  ax3_A3. REPLY ROUND 1 --- original defenses:
  source/matheology/vv/jub/oov1/llog/llog_2026m03d18_opus-reply-1b-for-jubilee-argument.rst

  ax4_A4. CANONICAL JUB AXIOMS (ax15_A15--ax25_A25):
  source/matheology/jub/axioms.rst

  ax5_A5. CANONICAL JUB THEOREMS (th5_T5--th11_T11):
  source/matheology/jub/theorems.rst


====================================================================
STEP 1 --- ENUMERATE Se1 OBJECTIONS
====================================================================

List every objection that touches Se1 (Mathematical Proof), across
all three rounds. For each, record:

- ID, severity, title
- The resolution claimed in the Pro entry
- Whether the resolution relies on mathematical derivation, formal
  model, logical argument, empirical analogy, or narrative plausibility

The Se1 objections include (check against quest.rst) --
Round 1: C1, C2, C3, C5, C7, C8, C9 (and check C4, C13);
Round 2: C2.3, C2.4, C2.5, C2.8, C2.9, C2.11, C2.12;
Round 3: none (all Se2--Se6).

Also include non-Se1 objections whose resolutions make mathematical
claims (e.g., Pro-A.2.1's competitive-inhibitor CTMC model).


====================================================================
STEP 2 --- GRADE EACH RESOLUTION
====================================================================

For each Se1 objection, grade the resolution on this scale:

  P (Proven): A formal derivation or mathematical proof exists in the
    reply, with defined terms and valid logical steps.

  S (Semi-formal): The logical structure is clear and could be
    formalized, but key steps remain informal or appeal to analogy.

  L (Plausible): The argument is consistent with evidence and
    logically coherent, but is not derived --- it is asserted with
    supporting reasoning.

  A (Asserted): The claim is stated without adequate mathematical
    support, even if it sounds rigorous.

For each grade, cite the specific passage in the reply or Pro entry
that justifies your assessment. Be concrete: quote the key claim and
explain why it is or is not mathematically rigorous.


====================================================================
STEP 3 --- TRACE THE CORE LOGICAL CHAIN
====================================================================

The framework's core argument chain is:

  th8_T8 (binary attractors: civilization -> catastrophe or safety)
  -> ax24_A24 (life-trifecta: innovation requires specific conditions)
  -> ax25_A25 (Jubilee recalibration is necessary for the safe attractor)
  -> ResearchCity (institutional implementation)

For EACH link in this chain, assess:
1. Is the link proven, semi-formal, plausible, or asserted?
2. What is the strongest objection to this link?
3. How convincing is the reply to that objection?
4. What would a formal proof require that is currently missing?


====================================================================
STEP 4 --- IDENTIFY THE WEAKEST MATHEMATICAL LINK
====================================================================

Based on Steps 2--3, identify:

1. The single weakest link in the core logical chain. Explain WHY
   it is the weakest --- what specific mathematical gap makes it
   vulnerable?

2. The top 5 strongest remaining mathematical gaps across all Se1
   objections, ranked by consequence (if the gap cannot be closed,
   how much of the framework falls?).

3. For each of the top 5, state what would be needed to close the
   gap (what kind of proof, what data, what formalization).


====================================================================
STEP 5 --- WRITE OUTPUT
====================================================================

Write all findings to:
source/matheology/vv/jub/oov2/llog/2G-stress-test-math.rst

Structure --

1. Title: "Phase 2G-1: Mathematical Rigor Stress-Test"
2. Generated-by line with date and model
3. Enumeration table (Step 1 output)
4. Resolution grades (Step 2 output, as a table)
5. Core chain analysis (Step 3 output)
6. Weakest link and top-5 ranking (Step 4 output)
7. Overall assessment: what percentage of the mathematical claims
   are genuinely rigorous vs. plausible-but-unproven?

This file is a working document that feeds into Phase 2G-4
(Convergence). It does NOT modify quest.rst or any canonical file.


====================================================================
CRITICAL RULES
====================================================================

1. Do NOT modify quest.rst, axioms.rst, theorems.rst, or any
   existing file. This session produces ONE new file only.

2. Be genuinely adversarial. Do not give the benefit of the doubt.
   If a resolution claims mathematical rigor but relies on analogy
   or narrative, grade it accordingly.

3. Distinguish carefully between "this argument is wrong" and "this
   argument is plausible but not proven." The framework may be
   correct without being rigorously proven --- note the difference.

4. LANGUAGE RULES (apply to ALL new text):
   a. NEVER use bare "Jubilee" as standalone noun.
   b. NEVER use "the" for unproven superlatives.


.. admonition:: TELES migration report (2026m04d04)

   Mechanical identifier migration applied to this file.
   All axiom/theorem text references were migrated from short form
   (e.g., A15) to compound form (e.g., ax15_A15) as part of the
   matheology compound naming operation. Both forms refer to the
   same formal object. The old form survives as the suffix to
   ensure consistency with the oldest records; the new form adds
   a temporary-status prefix. Forward-facing pages use brief form
   (ax15) only. See
   :ref:`hell-ll-other-b15-teles-renaming-prompt` for the complete
   mapping table and :ref:`legacy-5d-link-names-table-for-pet-jub-model` for the permanent
   reference.


.. admonition:: TELES repair — 2026m04d04

   Repaired RST syntax errors (unexpected indentation, heading level inconsistencies,
   or list formatting). No formal content was modified.
