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):
- [ ] Grep for
.. _ax\d+:in source/matheology/ — should find ZERO results (all migrated to pet-ax* or jub-ax*)
- [ ] Grep for
[ ] Grep for
.. _pet-ax\d+:— should find 14 results[ ] Grep for
.. _jub-ax\d+:— should find 11 results[ ] Grep for
.. _jub-th\d+:— should find theorem labels- [ ] Grep for “Migration note” in pet/axioms.rst and
jub/axioms.rst — should find migration comments
[ ] Run
make html— count warnings, confirm zero NEW
From 2I-2 (PoR Field Testing):
[ ] File exists:
llog/2I-por-field-testing.rst[ ] Grep for “coverage matrix” or field grid header in file
[ ] Grep for “Gap Analysis” section in file
[ ] Grep for “Extraction Difficulty” section in file
From 2I-3 (Compilation Skill):
- [ ] File exists:
source/matheology/compiler/sisyf/ww/sisyf-skill.rst (renamed from
skill-compile-matheology.rst)
- [ ] File exists:
[ ] Grep for “extraction matrix” or “Extraction Matrix” in file
- [ ] Check stub templates exist:
source/matheology/compiler/ww/stubs/matheology-*.rst(5 files) (also atsource/_templates/stubs/matheology-*.rst)
From 2I-4 (First Compilation):
[ ] File exists:
source/matheology/axioms/expert/index.rst[ ] File exists:
source/matheology/axioms/easy/index.rst[ ] File exists:
source/matheology/axioms/index.rst- [ ] Grep for duplicate labels:
.. _pet-ax1:should appear in exactly ONE file across the entire codebase
- [ ] Grep for duplicate labels:
[ ] Grep for
.. _all-ax:in the compiled expert view[ ] Grep for
.. _all-ax-easy:in the compiled easy view
From 2I-4b (Theorems Compilation):
[ ] File exists:
source/matheology/theorems/expert/index.rst[ ] File exists:
source/matheology/theorems/easy/index.rst[ ] Grep for
.. _all-th:in theorems expert view[ ] Grep for
.. _all-th-easy:in theorems easy view- [ ] Grep for
.. _pet-th\d+:— should find 4 results (in pet/theorems.rst only, NOT duplicated)
- [ ] Grep for
- [ ] Toctree in
source/matheology/theorems/index.rstis uncommented and lists expert/index + easy/index
- [ ] Toctree in
[ ] Easy page covers all 11 theorems (t1–t11)
From 2I-4c (Axiom Synthesis Pages):
[ ] File exists:
source/matheology/axioms/easy/gospels-apostles.rst[ ] File exists:
source/matheology/axioms/easy/quran-based.rst[ ] File exists:
source/matheology/axioms/easy/secular.rst[ ] Grep for
.. _all-ax-easy-gospels-apostles:— exactly 1[ ] Grep for
.. _all-ax-easy-quran-based:— exactly 1[ ] Grep for
.. _all-ax-easy-secular:— exactly 1[ ] All three pages listed in
axioms/easy/index.rsttoctree[ ] Each synthesis page has 25 axiom entries (a1–a25)
[ ] Each synthesis page uses
.. dropdown::directives
From 2I-5 (Adversarial Stress-Test):
[ ] File exists:
llog/2I-adversarial-stress-test.rst[ ] Grep for “BREACH” in file — count occurrences
[ ] Grep for “Proposed fixes” or “Overall assessment” in file
From 2I-6 (Public Documentation):
[ ] File exists:
source/matheology/naming-easy.rst[ ] File exists:
source/matheology/naming-producer.rst[ ] File exists:
source/matheology/naming-expert.rst[ ] File exists:
source/matheology/naming-architect.rst[ ] File exists:
source/matheology/naming.rst(index)- [ ] Grep for “naming” in
source/matheology/index.rst toctree — check linked
- [ ] Grep for “naming” in
Cross-cutting:
[ ] Total label count: grep
.. _across source/matheology/[ ] 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:
Title: “Phase 2I-7a: Deliverable Audit Checklist”
Generated-by line with date and model
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
Summary: X of Y checks passed
Any FAIL items with explanation of what is missing
Build report: total warnings, any warnings from Phase 2I files
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#
llog files are APPEND-ONLY.
NEVER delete content files.
This is an AUDIT. Your only output is the checklist file.
Be brutally honest. A PASS means checked with evidence. If you cannot check (e.g., file does not exist), it is FAIL, not SKIP.
LANGUAGE RULES: a. NEVER use bare “Jubilee” as standalone noun. b. NEVER use “the” for unproven superlatives.
TELES repair — 2026m04d04
Repaired RST syntax errors (unexpected indentation, heading level inconsistencies, or list formatting). No formal content was modified.