.. Migration note (2026m04d04): Claude copied this file during VV-to-HELL migration. STATUS: DEPRECATED — kept next to successor for audit trail. Old path: ``vv/jub/oov2/prompts/deprecated/prompt_2I-3_v1.rst`` (as given by LLoL) New path: ``hell/ll/jub/b/38/deprecated_prompt_2I-3_v1.rst`` (as chosen by Claude) Category: Deprecated (earlier version) .. meta:: :description: Deprecated v1 prompt for the Phase 2I-3 compilation skill definition, superseded by a token-optimized version with selective file reading strategy. :keywords: JUB OOv2, Phase 2I-3, deprecated, v1, compilation skill, extraction matrix, token budget, superseded, selective reads :author: Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea, ClaudeOp46Max, Anthropic, and Spirit of Boolean Truth :og:card:title: Phase 2I-3 v1:
Deprecated Skill Prompt :og:card:description: The first attempt at defining the compilation skill consumed too many tokens. Replaced by a version with selective file reads. .. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26 OO :description: Deprecated v1 prompt for Phase 2I-3 compilation skill definition, superseded by a token-optimized version. OO :keywords: JUB OOv2, Phase 2I-3, deprecated, v1, compilation skill, extraction matrix, token budget, matheology, superseded OO :og:card:title: Phase 2I-3 v1:
Deprecated Skill Prompt OO :og:card:description: Deprecated v1 of the compilation skill definition prompt, superseded by a version with selective reads for token savings. PP :description: Deprecated v1 prompt for the Phase 2I-3 compilation skill definition, superseded by a token-optimized version with selective file reading strategy. PP :keywords: JUB OOv2, Phase 2I-3, deprecated, v1, compilation skill, extraction matrix, token budget, superseded, selective reads PP :og:card:title: Phase 2I-3 v1:
Deprecated Skill Prompt PP :og:card:description: The first attempt at defining the compilation skill consumed too many tokens. Replaced by a version with selective file reads. .. SOCIAL-CARD-REVIEW --- generated by Claude Opus 4.6, 2026-03-26 dv_ClaOp46_PP_2026m03d26 --- max-effort rewrite, read full page. :description: 147 chars | :og:card:title: 38 chars (excl
) - [ ] 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-3: Compilation Skill Definition ********************************************************************* .. note:: **Path update needed if rerun (2026-03-25, Phase 2I-3).** This prompt was deprecated and superseded by the current prompt_2I-3. The AHA doc path below has moved to the compiler directory. .. note:: **200K-token execution prompt.** Copy-paste everything below the horizontal rule into a new Claude Code session. **Prerequisite:** Phase 2I-2 (PoR field testing) must have completed. The testing report at ``source/matheology/vv/jub/oov2/llog/2I-por-field-testing.rst`` tells you which fields have content and which are stubs. ---- /clear /compact /effort max You are executing Phase 2I-3 of the JUB OOv2 matheology project: **defining the ``/compile-matheology`` skill** for Claude Code. The skill will compile PoR source files into audience-specific downstream pages using the extraction matrix from the AHA design document. This session produces a Claude Code skill definition file and a set of stub templates --- no content compilation yet. ==================================================================== STEP 0 --- READ ALL REQUIRED FILES (DO THIS FIRST) ==================================================================== ax1_A1. AHA DESIGN DOC (Sections 12 and 14 especially): source/matheology/vv/jub/oov2/llog/aha-best-names-for-matheology-links.rst (New location: source/matheology/compiler/ww/5d-link-naming-matheology-aha.rst) ax2_A2. PoR FIELD TESTING REPORT: source/matheology/vv/jub/oov2/llog/2I-por-field-testing.rst ax3_A3. PET AXIOMS (current PoR format): source/matheology/pet/axioms.rst ax4_A4. JUB AXIOMS (current PoR format): source/matheology/jub/axioms.rst ax5_A5. EXISTING AXIOMS INDEX (to understand current aggregation): source/matheology/axioms/index.rst ax6_A6. CLAUDE.md (for skill conventions): CLAUDE.md ax7_A7. EXISTING PROMPTS INDEX (for format reference): source/matheology/vv/jub/oov2/prompts/index.rst ==================================================================== STEP 1 --- DESIGN THE EXTRACTION MATRIX ==================================================================== Build the full extraction matrix: a table mapping 45 PoR fields × 5 audience depths (expert, producer, easy, math, machine). For each cell, specify one of the 8 extraction keywords from AHA Section 12: :: x — include in full brief — first sentence only top3 — top 3 entries top1 — single best entry drop — omit entirely stub — heading only, mark [stub] ref — cross-reference link to PoR rewrite — include, rewritten for audience **Guidelines for assignment:** - **Expert** (default PoR): All fields ``x`` (this IS the PoR) - **Producer** (PoT): ``x`` for identity, ``brief`` for technical, ``top3`` for sources, ``rewrite`` for intro, ``drop`` for machine - **Easy** (PoU): ``rewrite`` for identity/intro, ``drop`` for most technical, ``top1`` for sources, ``ref`` for operational - **Math** (formal): ``x`` for latex/logic/proof, ``drop`` for sources/operational, ``ref`` for identity - **Machine** (API): ``x`` for id/latex/netout/netin, ``drop`` for prose, structured data for everything else Present the matrix as an RST list-table and get my approval before proceeding. ==================================================================== STEP 2 --- DEFINE THE SKILL ==================================================================== Create a Claude Code skill definition. The skill should: 1. **Accept arguments** matching the 13 user decisions from AHA Section 14.2: :: /compile-matheology [mode] [options] Modes: replace, append, archive, migrate Options: --output (default: matheology/axioms/) --models (default: all) --depths (default: all) --views (default: all) --states (default: all) --stubs yes|no (default: no) --version-increment --archive-folder --vvn --stayc --freeze-por yes|no (default: no) 2. **For each mode, define the execution sequence:** **REPLACE mode:** a. Read all PoR source files (pet/axioms.rst, jub/axioms.rst, jub/theorems.rst, jub/quest.rst) b. For each element × depth × view combination: - Apply extraction matrix to select/transform fields - Generate an RST page with the element's BEST Names label - Write to the output folder c. Rebuild toctrees in affected index files d. Run ``make html`` to check **APPEND mode:** a. Read only NEW PoR elements (elements not yet in output) b. Generate pages for new elements only c. Add to existing toctrees d. Check build **ARCHIVE mode:** a. Run REPLACE first b. Copy output to ``vv/{version}/`` (was ``vv/compiled/`` --- updated per DD-b12) c. Tag all labels with version suffix d. Update version registry in AHA doc e. Check build **MIGRATE mode:** a. Read old-format files b. Transform labels per migration table c. Update all cross-references d. Check build 3. **Stub policy:** When ``--stubs no``, if a field/page would contain only stub content (per the testing report), the page is NOT generated and no toctree entry is created. This prevents empty pages. 4. **Output format:** Each generated page follows this template: :: .. _{label}: {title} ================== .. This page was generated by /compile-matheology on {date}. .. Source: {source_file} .. Do not edit manually. Re-run the skill to regenerate. {extracted fields per extraction matrix} Write the skill definition to: source/matheology/vv/jub/oov2/llog/skill-compile-matheology.rst This is an AHA-level specification document (not an executable script). It should be detailed enough that a future Claude session can implement it as an actual Claude Code skill. ==================================================================== STEP 3 --- CREATE STUB TEMPLATES ==================================================================== Create stub templates for the 5 audience depths at: :: source/_templates/stubs/matheology-expert.rst source/_templates/stubs/matheology-producer.rst source/_templates/stubs/matheology-easy.rst source/_templates/stubs/matheology-math.rst source/_templates/stubs/matheology-machine.rst Each stub contains: 1. A label placeholder: ``.. _{label}:`` 2. A title placeholder 3. The field headings appropriate for that depth (from the extraction matrix --- only fields NOT marked ``drop``) 4. Each field body marked ``[stub --- content pending]`` 5. A generation comment with date and source ==================================================================== STEP 4 --- CHECK BUILD ==================================================================== Run ``make html`` and confirm: 1. Zero new warnings from the skill definition file 2. The stub templates parse as valid RST 3. No broken cross-references ==================================================================== STEP 5 --- APPEND TO DEBUG FILE ==================================================================== APPEND a session entry to: source/matheology/vv/jub/oov2/llog/llog_2026m03d21_restructuring-phase1-prompts-reply-overviews-for-debugs.rst With: 1. Verbatim prompt (this entire prompt, in a code-block) 2. The extraction matrix 3. List of all files created/modified 4. Build check result ==================================================================== CRITICAL RULES ==================================================================== 1. llog files are APPEND-ONLY. 2. NEVER delete content files. 3. NEVER abbreviate prompts in llogs. 4. The skill definition is a SPECIFICATION, not executable code. It documents what the skill should do so a future session can implement it. 5. LANGUAGE RULES: 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.