Prompt 02 — PP (PathProbing) Max Effort#
This prompt is designed for the max-effort rewrite of social card metadata
across all ~245 RST files in source/matheology/. Unlike Prompt 01 (OO),
this prompt requires reading each full page before crafting metadata.
Quality designation: PP (PathProbing) — deeply informed by full page content, with strict character counting and quality bar.
Execution: 6 parallel agents at /effort max, each handling a thematic
batch. Each agent reads every page in full.
The Prompt#
You are REWRITING social card metadata for RST pages at MAXIMUM quality
(PP --- PathProbing). Each file already has an OO-quality (Operates Oddly,
default effort) meta block. You will:
1. Read the ENTIRE file from beginning to end --- every section, every argument
2. Craft superior PP-quality meta fields based on deep understanding
3. Make PP fields ACTIVE in the .. meta:: block
4. Preserve OO fields in a comparison comment for human review
PROCEDURE for each file:
Step 1: Read the entire file. Understand the page's core argument, structure,
and what makes it distinctive --- not just its opening paragraph.
Step 2: Extract the existing OO-quality fields from the current .. meta:: block:
- :description:
- :keywords:
- :og:card:title:
- :og:card:description:
Step 3: Craft 4 new PP-quality fields:
:description: --- EXACTLY 140-150 characters.
Must be a COMPLETE sentence ending at a natural boundary (period, question
mark, or complete clause). Must hook the reader --- make them want to click.
Must be accurate to the FULL page content, not just the opening.
COUNT characters. If not in range 140-150, REWRITE until it is.
This range ensures maximum use of the 155-char Google snippet space
without any risk of truncation.
:keywords: --- 8-12 terms.
Must reflect the actual content of the full page, not generic topic words.
Include specific names, concepts, frameworks mentioned in the page.
:og:card:title: --- Target 35-45 characters (excluding <br> tags).
Fill the space with meaningful context. A title seen on social media
must be self-explanatory without any description below it.
Use <br> for line breaks. Each line must stand alone as a complete
phrase that makes sense independently.
MUST end at a natural word boundary --- never truncate mid-word.
:og:card:description: --- Max 155 characters.
Must be a complete sentence. Must complement the title, not repeat it.
Should make someone want to click through to the full page.
Step 4: Replace the file's header with this exact structure:
.. meta::
:description: [PP description]
:keywords: [PP keywords]
:author: Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea,
ClaudeOp46Max, Anthropic, and Spirit of Boolean Truth
:og:card:title: [PP title]
:og:card:description: [PP card description]
.. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26
OO :description: [original OO description]
OO :keywords: [original OO keywords]
OO :og:card:title: [original OO title]
OO :og:card:description: [original OO card description]
PP :description: [new PP description]
PP :keywords: [new PP keywords]
PP :og:card:title: [new PP title]
PP :og:card:description: [new PP card description]
.. SOCIAL-CARD-REVIEW --- generated by Claude Opus 4.6, 2026-03-26
dv_ClaOp46_PP_2026m03d26 --- max-effort rewrite, read full page.
:description: [N] chars | :og:card:title: [N] 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
CRITICAL: Preserve ALL content after the SOCIAL-CARD-REVIEW comment block
unchanged. If the file has :seo:title: in the existing meta block,
keep it unchanged. If the file has :orphan: before the meta block,
keep it before the meta block.
LANGUAGE RULES (violations will cause social media backlash):
- NEVER use bare "Jubilee" as a standalone noun --- use "JUB" or qualified form
- NEVER use "validate/verify/validation/verification" --- use "test/check/assess"
- NEVER use "the" before unproven superlatives
- Use HELD/BREACH, not PASS/FAIL for adversarial results
AUTHOR STRING (copy verbatim, do not modify):
Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea, ClaudeOp46Max,
Anthropic, and Spirit of Boolean Truth
QUALITY BAR: You are writing ad copy for a site whose credibility depends
on precision. Every word must earn its place. Sloppy descriptions will
cause social media backlash. Read the full page. Think deeply. Then write.
Batch Assignments (Run 2)#
Batch 1: 45 public-facing pages (axioms, theorems, JUB, PET, naming, prior-art, heaven, symbols)
Batch 2: 33 con findings
Batch 3: 33 pro findings
Batch 4: 51 HELL misc + VV indexes + VV prompts
Batch 5: 53 VV audit logs
Batch 6: 30 compiler docs
File lists for each batch are at /tmp/batch1_files.txt through
/tmp/batch6_files.txt (generated by the orchestrator session).
Results#
After completion, comparison tables are generated at three detail levels:
Social Card Comparison — Beginner View — simple title and description comparison
Social Card Comparison — Producer View — adds keywords, character counts
Social Card Comparison — Expert View — full detail with all fields and quality flags
Flagged for Human Attention — pages needing human attention