.. Migration note (2026m04d04): Claude copied this file during VV-to-HELL migration.
   Old path: ``vv/jub/oov2/llog/integration-findings/por-field-usage-census.rst`` (as given by LLoL)
   New path: ``hell/ll/jub/b/41/por-field-usage-census.rst`` (as chosen by Claude)
   Category: Integration finding (raw copy)

.. meta::
   :description: Census of 40+ PoR fields: which are naturally populated by existing content, which require expert invention, and which remain empty stubs in practice.
   :keywords: PoR field census, usage patterns, naturally populated, expert invention, empty stubs, right-sizing, migration, integration finding, llog
   :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>Real-World Coverage
   :og:card:description: Which PoR fields fill themselves from existing content and which remain empty? This census informs whether the 45-field spec is right-sized.

.. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26
   OO :description: Census tracking which of the 40+ PoR fields are naturally populated, require expert invention, or remain empty during migration.
   OO :keywords: matheology, integration finding, PoR field, usage census, field coverage, migration, OOv1, OOv2, data collection, right-sizing, llog
   OO :og:card:title: Integration Finding:<br>PoR Field Usage Census
   OO :og:card:description: Census of which PoR fields are naturally filled by existing content, which require expert invention, and which remain empty stubs.
   PP :description: Census of 40+ PoR fields: which are naturally populated by existing content, which require expert invention, and which remain empty stubs in practice.
   PP :keywords: PoR field census, usage patterns, naturally populated, expert invention, empty stubs, right-sizing, migration, integration finding, llog
   PP :og:card:title: PoR Field Usage Census<br>Real-World Coverage
   PP :og:card:description: Which PoR fields fill themselves from existing content and which remain empty? This census informs whether the 45-field spec is right-sized.

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

.. include:: /_templates/include-file/page-prefix.rst

*********************************************************************
Integration Finding: PoR Field Real-World Usage Census
*********************************************************************

.. note::

   **Data collection file.** Agents performing the OOv1→OOv2 migration
   should append rows below whenever they attempt to populate a PoR field
   for any element. This file answers: which of the 40+ PoR fields are
   actually used in practice?

   **Question being answered:** Is the PoR field set right-sized? Which
   fields are naturally filled by existing content, which require expert
   invention, and which remain empty stubs? Are there fields the PoR
   does NOT have but the content wants?

   **How to report:** For each element migrated, record one row per
   PoR field attempted. Use the status codes below.

   **Status codes:**

   - ``Y`` --- field naturally populated from existing OOv1 content
   - ``I`` --- field required expert invention (content exists but
     must be restructured or inferred)
   - ``E`` --- field remains an empty stub (no content available)
   - ``N/A`` --- field not applicable to this element type

   For proposed new fields, append to the second table below.


Field Usage
=============

.. list-table::
   :header-rows: 1
   :widths: 12 8 8 6 66

   * - Element
     - Field #
     - Field name
     - Status
     - Note
   * - ``pet-ax1``
     - 1
     - Title
     - Y
     - Already present in axioms.rst heading
   * - ``pet-ax1``
     - 7
     - FormalNotation
     - I
     - Logic formula exists in prose but needs extraction into field
   * - ``pet-ax1``
     - 14
     - SourceCitation
     - Y
     - Torah refs already inline
   * - ``pet-ax1``
     - 30
     - AlignmentClassID
     - E
     - No cross-model alignment data exists yet
   * - (element)
     - (field #)
     - (field name)
     - (Y/I/E/N/A)
     - (brief explanation)


Proposed New Fields
=====================

Fields not in the current PoR registry (Section 9) that the migration
suggests would be useful.

.. list-table::
   :header-rows: 1
   :widths: 15 20 65

   * - Proposed by
     - Proposed name
     - Why needed (what content wanted this field?)
   * - (agent/session)
     - (field name)
     - (describe the content that didn't fit any existing field)


Summary (to be written after migration completes)
====================================================

*(Agents: after the migration is complete, write a summary addressing:
How many fields are Y, I, E, N/A? Which fields are consistently empty
across all elements? Which fields required the most invention? Are there
clusters --- e.g., "all POST fields are empty" or "all identity fields
are Y"? How many new fields were proposed? Do any proposed fields overlap
with existing fields that were merely poorly named?)*