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

.. meta::
   :description: Execution prompt for auditing all Phase 2I deliverables against the original design specification before writing the permanent closing record.
   :keywords: JUB OOv2, Phase 2I-7a, deliverable audit, closing, quality check, BEST Names, compilation, PoR fields, design specification
   :author: Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea, ClaudeOp46Max, Anthropic, and Spirit of Boolean Truth
   :og:card:title: Phase 2I-7a: Deliverable<br>Audit Prompt
   :og:card:description: Before closing, check the work. This prompt audits every Phase 2I deliverable against the original design specification for completeness.

.. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26
   OO :description: Prompt for Phase 2I-7a deliverable audit, reviewing all Phase 2I outputs before writing the closing llog record.
   OO :keywords: JUB OOv2, Phase 2I-7a, deliverable audit, closing, llog, matheology, BEST Names, compilation, PoR fields, quality check
   OO :og:card:title: Phase 2I-7a: Deliverable<br>Audit Prompt
   OO :og:card:description: Prompt for auditing all Phase 2I deliverables before writing the permanent closing record for the JUB OOv2 project.
   PP :description: Execution prompt for auditing all Phase 2I deliverables against the original design specification before writing the permanent closing record.
   PP :keywords: JUB OOv2, Phase 2I-7a, deliverable audit, closing, quality check, BEST Names, compilation, PoR fields, design specification
   PP :og:card:title: Phase 2I-7a: Deliverable<br>Audit Prompt
   PP :og:card:description: Before closing, check the work. This prompt audits every Phase 2I deliverable against the original design specification for completeness.

.. 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: 36 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 2I-7a: Phase 2I Closing --- Deliverable Audit
*********************************************************************

.. note::

   **200K-token execution prompt.** Copy-paste everything below the
   horizontal rule into a new Claude Code session.

   **Prerequisite:** All Phase 2I prompts (2I-1 through 2I-6, plus
   2I-4b and 2I-4c) must have completed. This is the first of two
   closing sessions.

   **Split note:** The original 2I-7 was split into 2I-7a (this
   session: audit all deliverables) and 2I-7b (write closing llog)
   to fit the 200K-token context window. The audit reads many files
   but only shallowly; the closing llog reads fewer files but writes
   the permanent record.

   **Token budget:** ~110K. Reads each deliverable selectively
   (title + key sections) rather than in full. Does NOT read prompt
   scripts or the debug file.

----

/clear
/compact
/effort max

You are executing Phase 2I-7a of the JUB OOv2 matheology project:
**auditing all Phase 2I deliverables.** Your output is a structured
audit checklist that Phase 2I-7b will use to write the closing llog.

This session READS and CHECKS. It does not write the closing
llog (that is 2I-7b).


====================================================================
STEP 0 --- AUDIT STRATEGY
====================================================================

You must check ~35 deliverables across ~20 files. To stay within
budget:

- For each file: read the FIRST 50 lines (to confirm title,
  structure, generated-by line) and LAST 30 lines (to confirm
  completeness).
- For specific content checks (e.g., "does the coverage matrix
  exist?"), use grep to find section headers.
- Do NOT read entire files unless they are small (<100 lines).
- Do NOT read prompt script files (their existence is sufficient).
- Do NOT read the debug file.


====================================================================
STEP 1 --- AUDIT ALL DELIVERABLES
====================================================================

**From 2I-1 (Migration):**

1. [ ] Grep for ``.. _ax\d+:`` in source/matheology/ --- should
       find ZERO results (all migrated to pet-ax* or jub-ax*)
2. [ ] Grep for ``.. _pet-ax\d+:`` --- should find 14 results
3. [ ] Grep for ``.. _jub-ax\d+:`` --- should find 11 results
4. [ ] Grep for ``.. _jub-th\d+:`` --- should find theorem labels
5. [ ] Grep for "Migration note" in pet/axioms.rst and
       jub/axioms.rst --- should find migration comments
6. [ ] Run ``make html`` --- count warnings, confirm zero NEW

**From 2I-2 (PoR Field Testing):**

7. [ ] File exists: ``llog/2I-por-field-testing.rst``
8. [ ] Grep for "coverage matrix" or field grid header in file
9. [ ] Grep for "Gap Analysis" section in file
10. [ ] Grep for "Extraction Difficulty" section in file

**From 2I-3 (Compilation Skill):**

11. [ ] File exists: ``source/matheology/compiler/sisyf/ww/sisyf-skill.rst``
        (renamed from ``skill-compile-matheology.rst``)
12. [ ] Grep for "extraction matrix" or "Extraction Matrix" in file
13. [ ] Check stub templates exist:
        ``source/matheology/compiler/ww/stubs/matheology-*.rst`` (5 files)
        (also at ``source/_templates/stubs/matheology-*.rst``)

**From 2I-4 (First Compilation):**

14. [ ] File exists: ``source/matheology/axioms/expert/index.rst``
15. [ ] File exists: ``source/matheology/axioms/easy/index.rst``
16. [ ] File exists: ``source/matheology/axioms/index.rst``
17. [ ] Grep for duplicate labels: ``.. _pet-ax1:`` should appear
        in exactly ONE file across the entire codebase
18. [ ] Grep for ``.. _all-ax:`` in the compiled expert view
19. [ ] Grep for ``.. _all-ax-easy:`` in the compiled easy view

**From 2I-4b (Theorems Compilation):**

20. [ ] File exists: ``source/matheology/theorems/expert/index.rst``
21. [ ] File exists: ``source/matheology/theorems/easy/index.rst``
22. [ ] Grep for ``.. _all-th:`` in theorems expert view
23. [ ] Grep for ``.. _all-th-easy:`` in theorems easy view
24. [ ] Grep for ``.. _pet-th\d+:`` --- should find 4 results
        (in pet/theorems.rst only, NOT duplicated)
25. [ ] Toctree in ``source/matheology/theorems/index.rst`` is
        uncommented and lists expert/index + easy/index
26. [ ] Easy page covers all 11 theorems (t1--t11)

**From 2I-4c (Axiom Synthesis Pages):**

27. [ ] File exists: ``source/matheology/axioms/easy/gospels-apostles.rst``
28. [ ] File exists: ``source/matheology/axioms/easy/quran-based.rst``
29. [ ] File exists: ``source/matheology/axioms/easy/secular.rst``
30. [ ] Grep for ``.. _all-ax-easy-gospels-apostles:`` --- exactly 1
31. [ ] Grep for ``.. _all-ax-easy-quran-based:`` --- exactly 1
32. [ ] Grep for ``.. _all-ax-easy-secular:`` --- exactly 1
33. [ ] All three pages listed in ``axioms/easy/index.rst`` toctree
34. [ ] Each synthesis page has 25 axiom entries (a1--a25)
35. [ ] Each synthesis page uses ``.. dropdown::`` directives

**From 2I-5 (Adversarial Stress-Test):**

36. [ ] File exists: ``llog/2I-adversarial-stress-test.rst``
37. [ ] Grep for "BREACH" in file --- count occurrences
38. [ ] Grep for "Proposed fixes" or "Overall assessment" in file

**From 2I-6 (Public Documentation):**

39. [ ] File exists: ``source/matheology/naming-easy.rst``
40. [ ] File exists: ``source/matheology/naming-producer.rst``
41. [ ] File exists: ``source/matheology/naming-expert.rst``
42. [ ] File exists: ``source/matheology/naming-architect.rst``
43. [ ] File exists: ``source/matheology/naming.rst`` (index)
44. [ ] Grep for "naming" in ``source/matheology/index.rst``
        toctree --- check linked

**Cross-cutting:**

45. [ ] Total label count: grep ``.. _`` across source/matheology/
46. [ ] Run ``make clean && make html`` --- record exact warning count


====================================================================
STEP 2 --- WRITE AUDIT RESULTS
====================================================================

Create:
source/matheology/vv/jub/oov2/llog/2I-audit-checklist.rst

Contents:

1. Title: "Phase 2I-7a: Deliverable Audit Checklist"
2. Generated-by line with date and model
3. For each of the 46 checks above:
   - Check number and description
   - Result: PASS / FAIL / INCOMPLETE / SKIP (with reason)
   - Evidence: the grep output, file size, or warning count
4. Summary: X of Y checks passed
5. Any FAIL items with explanation of what is missing
6. Build report: total warnings, any warnings from Phase 2I files
7. Label statistics: total definitions, total references


====================================================================
STEP 3 --- NOTE FOR 2I-7b
====================================================================

At the end of the audit file, add a section:

"Inputs for Phase 2I-7b Closing Llog"

Listing:

- Number of deliverables complete vs. incomplete
- Any critical FAILs that must be noted in the closing
- The build warning count
- The label statistics
- The StayVS maturity assessment recommendation (based on what
  you found --- but 2I-7b will write the formal assessment)


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

1. llog files are APPEND-ONLY.
2. NEVER delete content files.
3. This is an AUDIT. Your only output is the checklist file.
4. Be brutally honest. A PASS means checked with evidence. If
   you cannot check (e.g., file does not exist), it is FAIL,
   not SKIP.
5. LANGUAGE RULES:
   a. NEVER use bare "Jubilee" as standalone noun.
   b. NEVER use "the" for unproven superlatives.


.. admonition:: TELES repair — 2026m04d04

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