Phase 2I-2b: PoR Field Testing — Operational, Network, Analytical#

Note

Path update needed if rerun (2026-03-25, Phase 2I-3). This prompt was executed before the compiler directory was created. If this script is ever rerun, update the AHA doc path below.

Note

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

Prerequisite: Phase 2I-2a must have completed and written its partial report to source/matheology/vv/jub/oov2/llog/2I-por-field-testing-part-a.rst

Token budget: ~100K. Reads the stress-test and critique files (which contain the operational/analytical evidence) plus the Part A report. Does NOT re-read the full PoR source files.

/clear /compact /effort max

You are executing Phase 2I-2b of the JUB OOv2 matheology project: PoR field testing, Part B. This session tests fields 19–45 (Operational State, Network & Versioning, Analytical) against the stress-test output, critique integration, and quest structure.

This session does NO migration or code changes. It reads, analyses, and produces the COMBINED final testing report.

STEP 0 — READ ALL REQUIRED FILES (DO THIS FIRST)#

ax1_A1. AHA DESIGN DOC (field definitions, Section 11) — READ IN FULL: 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. PART A REPORT (fields 1–18 already tested) — READ IN FULL: source/matheology/vv/jub/oov2/llog/2I-por-field-testing-part-a.rst

ax3_A3. STRESS-TEST MATH — READ IN FULL: source/matheology/vv/jub/oov2/llog/2G-stress-test-math.rst

ax4_A4. STRESS-TEST FEASIBILITY — READ IN FULL: source/matheology/vv/jub/oov2/llog/2G-stress-test-feasibility.rst

ax5_A5. STRESS-TEST DISPOSITIONS — READ IN FULL: source/matheology/vv/jub/oov2/llog/2G-stress-test-dispositions.rst

ax6_A6. CRITIQUE INTEGRATION (C3.1–C3.7) — READ IN FULL: source/matheology/vv/jub/oov2/llog/llog_2026m03d22_restructuring-2F-critique3-c3-1-c3-7.rst

ax7_A7. JUB QUEST (for con/pro references and network) — SELECTIVE: source/matheology/jub/quest.rst Use grep to find all .. _con- and .. _pro- labels and any :ref: cross-references between elements. Read 5-line context around each. Do NOT read the full file (~48K tokens).

ax8_A8. 2G-2H SUMMARY (for StayVS assessments) — READ IN FULL: source/matheology/vv/jub/oov2/llog/llog_2026m03d22_restructuring-2G-2H-stress-tests-summary-freeze.rst

STEP 1 — BUILD COVERAGE MATRIX: FIELDS 19–45#

For EACH axiom (ax1_A1–ax25_A25) and EACH theorem (th5_T5–th11_T11), assess coverage for fields 19–45:

Group 4: Operational State (fields 19–29)

  1. limit — known limitations, assumptions

  2. jj — current blocker for this element

  3. aa — next steps, tasks

  4. kk — identified trap and avoidance

  5. ff — collected feedback to process

  6. cc — background reading from others

  7. dd — architectural decision for this element

  8. gg — promising draft not yet integrated

  9. hh — recently deprecated content

  10. ww — what would break if this changed

  11. yy — test case for reliability checking

Group 5: Network & Versioning (fields 30–40)

  1. netout — upstream dependencies (builds on)

  2. netin — downstream dependents (used by)

  3. stayc — StayVS maturity code

  4. mento — stage-appropriate learning guidance

  5. diff — what changed from prior versions

  6. ll — links to relevant llog sessions

  7. con — objection addressing this element

  8. pro — response defending this element

  9. vv — all VVNs for this element

  10. vvnow — pointer to latest version

  11. model — which model(s) use this element

Group 6: Analytical (fields 41–45)

  1. conv — where traditions agree/diverge

  2. bib — academic references

  3. pol — known active policy discussions

  4. his — historical analysis

  5. doi — permanent stable identifier

Use the same scoring: F/P/S/N.

STEP 2 — NETWORK GRAPH EXTRACTION#

For fields 30–31 (netout/netin), build the actual dependency graph by reading the PoR content and stress-test analysis:

  1. For each axiom, list which other axioms it depends on (netout) and which theorems/axioms depend on it (netin).

  2. Every edge must be justified with a specific reason (e.g., “th1_T1 depends on ax5_A5 because the proof invokes ax5_A5’s containment property”).

  3. List any edges that are uncertain or disputed.

  4. Note any missing edges (elements that appear isolated but probably should not be).

STEP 3 — COMBINED GAP ANALYSIS#

Merge the Part A findings with your Part B findings:

  1. Critical gaps: Fields rated “Stub” for >50% of elements (across all 45 fields)

  2. Quick wins: Fields rated “Partial” that could become “Full” with targeted work

  3. Source-text gaps by tradition (from Part A)

  4. Network completeness (from Step 2)

  5. StayVS coverage: Do the 2G-2H assessments cover all 36 elements?

  6. Operational field patterns: Are the POST fields (jj, aa, kk, etc.) populated from the stress-test outputs, or are they systemically empty?

STEP 4 — EXTRACTION DIFFICULTY (ALL 45 FIELDS)#

Combine Part A’s difficulty ratings (fields 1–18) with your ratings for fields 19–45. Present the full 45-row table: field, difficulty, source files, notes.

STEP 5 — WRITE COMBINED FINAL REPORT#

Create the FINAL combined report at: source/matheology/vv/jub/oov2/llog/2I-por-field-testing.rst

Contents:

  1. Title: “Phase 2I-2: PoR Field Testing Report”

  2. Generated-by line (note: produced in two sessions, 2I-2a + 2I-2b)

  3. Complete coverage matrix (all 36 elements × all 45 fields) — merge Part A’s fields 1–18 with your fields 19–45

  4. Gap analysis (6 sections from Step 3)

  5. Network dependency graph (from Step 2)

  6. Complete extraction difficulty table (all 45 fields)

  7. Recommendations for Phase 3 priority ordering

  8. Any proposed changes to the 45-field structure

Then REMOVE the partial Part A file: Rename 2I-por-field-testing-part-a.rst to deprecated/2I-por-field-testing-part-a.rst (do not delete).

STEP 6 — UPDATE LLOG INDEX#

Add the final report to the toctree in: source/matheology/vv/jub/oov2/llog/index.rst

Under the “Phase 2I: Post-Processing” section.

CRITICAL RULES#

  1. llog files are APPEND-ONLY.

  2. NEVER delete content files. Move to deprecated/ instead.

  3. This session READS and ANALYSES only. The files you CREATE are the final report (and deprecated move of Part A).

  4. The combined report must be ONE file containing the complete matrix. Do not leave it split across two files.

  5. NEVER abbreviate prompts in llogs.

  6. LANGUAGE RULES: a. NEVER use bare “Jubilee” as standalone noun. b. NEVER use “the” for unproven superlatives.

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 TELES Axiom/Theorem Compound Naming — Execution Prompt for the complete mapping table and DD b12 — Legacy Naming for PET/JUB Axioms and Theorems for the permanent reference.