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

.. meta::
   :description: Agent prompt for tracking which PoR fields get populated during the OOv1-to-OOv2 migration, informing Phase 3 field set right-sizing decisions.
   :keywords: JUB OOv2, PoR fields, census, migration, OOv1, field usage, data collection, agent prompt, right-sizing, empirical
   :author: Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea, ClaudeOp46Max, Anthropic, and Spirit of Boolean Truth
   :og:card:title: PoR Field Usage Census<br>Agent Prompt
   :og:card:description: Which fields actually get populated? This agent prompt tracks real usage during migration to right-size the PoR field set for Phase 3.

.. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26
   OO :description: Agent prompt for tracking PoR field population during OOv1 to OOv2 migration to assess field set right-sizing.
   OO :keywords: JUB OOv2, PoR fields, census, migration, OOv1, field usage, data collection, agent prompt, matheology, empirical test
   OO :og:card:title: PoR Field Usage Census<br>Agent Prompt
   OO :og:card:description: Agent prompt for tracking which PoR fields get populated during migration to inform Phase 3 field set decisions.
   PP :description: Agent prompt for tracking which PoR fields get populated during the OOv1-to-OOv2 migration, informing Phase 3 field set right-sizing decisions.
   PP :keywords: JUB OOv2, PoR fields, census, migration, OOv1, field usage, data collection, agent prompt, right-sizing, empirical
   PP :og:card:title: PoR Field Usage Census<br>Agent Prompt
   PP :og:card:description: Which fields actually get populated? This agent prompt tracks real usage during migration to right-size the PoR field set for Phase 3.

.. SOCIAL-CARD-REVIEW --- generated by Claude Opus 4.6, 2026-03-26
   dv_ClaOp46_PP_2026m03d26 --- max-effort rewrite, read full page.
   :description: 143 chars | :og:card:title: 38 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

:orphan:

*********************************************************************
PoR Field Usage Census --- Agent Prompt for Migration
*********************************************************************

.. note::

   **Secondary task prompt for migration agents.** Embed this prompt's
   instructions when an agent is migrating content from OOv1 to OOv2.
   The agent performs its primary migration task AND simultaneously
   tracks which PoR fields get populated, which stay empty, and which
   content wants a field that does not exist.

   **Prerequisite:** The agent must have read CLAUDE.md and the AHA doc
   (at minimum Sections 1--16, especially Section 9: PoR Fields).

   **Safety:** This prompt asks the agent to APPEND findings to a data
   collection file. It does not ask the agent to modify the PoR registry
   or resolve design questions.

   **Context:** The PoR registry (AHA Section 9) defines 40+ fields per
   element. These were designed analytically --- before any real content
   was migrated into the structure. The OOv1→OOv2 migration is the
   first empirical test of whether the field set is right-sized. The
   data collected here will inform Phase 3 decisions about which fields
   to keep, merge, drop, or add.

----

/clear
/compact

You are performing content migration for the matheology project. Read
CLAUDE.md first. Obey all rules (especially: append-only llogs, no
"validate/verify" language, use HELD/BREACH not PASS/FAIL).

Read the AHA doc Sections 1--16:
``source/matheology/compiler/ww/5d-link-naming-matheology-aha.rst``

Your primary task is [INSERT SPECIFIC MIGRATION TASK HERE].

While doing that primary task, you have a secondary task: **track PoR
field usage for every element you migrate.** You are the one touching
every piece of content. You are in the best position to see which fields
fill naturally and which remain empty.

**For each element you migrate, ask yourself these questions:**

1. **Which PoR fields does this element's existing content naturally
   populate?** Look at the current OOv1 source (axioms.rst, theorems.rst,
   quest.rst). For each field in the PoR registry (Section 9), does the
   existing content contain material that maps to this field? If yes,
   status is ``Y``.

2. **Which fields require invention?** The content exists in some form
   but needs restructuring, inference, or expert judgment to fit the
   field definition. For example: a logic formula buried in prose that
   needs extraction into FormalNotation. Status is ``I``.

3. **Which fields are empty stubs?** No content exists and none can
   reasonably be inferred. Status is ``E``.

4. **Which fields are not applicable?** The field definition does not
   make sense for this element type. For example: SourceCitation may
   not apply to a Symbol. Status is ``N/A``.

5. **Does the content want a field that does not exist?** This is the
   most important observation. If you encounter content that clearly
   belongs in the PoR but does not fit any existing field, record it
   in the "Proposed New Fields" table. Describe what the content is
   and why no existing field covers it.

**Where to report findings:**

Append rows to:
``source/matheology/compiler/ee/por-field-usage-census.rst``

Use the format documented in that file. One row per field per element.
You do not need to record every field for every element --- focus on
the interesting cases:

- Fields that are ``Y`` (confirm the design works)
- Fields that are ``I`` (reveal hidden content)
- Fields that are ``E`` consistently across elements (candidates for
  dropping or merging)
- Fields that are ``N/A`` for entire element types (misfit between
  field and type)
- Any proposed new fields (most valuable observation)

**Sampling strategy:** For the first 3--5 elements you migrate, record
ALL fields (complete census). After that, focus on surprises ---
fields whose status differs from the pattern you saw in the first batch.

**At the end of your migration session,** write a brief summary
(3--5 sentences) at the bottom of the census file, noting: how many
elements sampled, how many fields recorded, any patterns (e.g., "all
POST fields are consistently empty", "SourceCitation is Y for axioms
but E for theorems"), any proposed new fields, any surprises.

**Do not modify the PoR registry.** Your job is to collect evidence,
not to change the architecture. If you have a strong opinion about a
field, state it in the Note column.