.. meta::
   :description: Census of 45 PoR fields across ax1-ax5, with surprises for ax6-ax25 and th5-th11. Theorems lack source fields; two new fields proposed for type and scope.
   :keywords: PoR field census, 45 fields, ax1-ax5, extraction matrix, field applicability, ElementType, DomainScope, theorems, source fields, Phase 2I-4
   :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>45 Fields Across 32 Elements
   :og:card:description: Full census of ax1-ax5 field coverage reveals systematic gaps in operational fields and proposes two new fields: type and scope.

.. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26
   OO :description: Full census of PoR field usage for axioms ax1-ax5 from the Phase 2I-4 first compilation run, with surprises noted for ax6-ax25 and th5-th11.
   OO :keywords: PoR field, usage census, ax1, ax2, ax3, ax4, ax5, compilation, compiler, evidence, SISYF, extraction matrix
   OO :og:card:title: PoR Field Usage Census —<br>Phase 2I-4 Compilation
   OO :og:card:description: Full census for ax1-ax5 field coverage and notable surprises across ax6-ax25 and th5-th11 from the first compilation run.
   PP :description: Census of 45 PoR fields across ax1-ax5, with surprises for ax6-ax25 and th5-th11. Theorems lack source fields; two new fields proposed for type and scope.
   PP :keywords: PoR field census, 45 fields, ax1-ax5, extraction matrix, field applicability, ElementType, DomainScope, theorems, source fields, Phase 2I-4
   PP :og:card:title: PoR Field Usage Census —<br>45 Fields Across 32 Elements
   PP :og:card:description: Full census of ax1-ax5 field coverage reveals systematic gaps in operational fields and proposes two new fields: type and scope.

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

.. _compiler-ee-census:

*********************************************************************
PoR Field Usage Census --- Phase 2I-4 First Compilation
*********************************************************************

Evidence collected during Phase 2I-4 first compilation run (2026-03-25).

**Sampling:** Full census for first 5 elements (ax1--ax5); surprises only
for ax6--ax25 and th5--th11.


Full Census: ax1--ax5
======================

**Legend:** Y = content exists and maps / I = exists but needs
restructuring / E = empty stub / N/A = not applicable

.. list-table::
   :header-rows: 1
   :widths: 4 8 6 6 6 6 6

   * - #
     - Field
     - ax1
     - ax2
     - ax3
     - ax4
     - ax5
   * - 1
     - id
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 2
     - title
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 3
     - name
     - I
     - I
     - I
     - I
     - I
   * - 4
     - sum
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 5
     - intro
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 6
     - latex
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 7
     - tctx
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 8
     - tcnt
     - I
     - I
     - I
     - I
     - I
   * - 9
     - logic
     - I
     - I
     - I
     - I
     - I
   * - 10
     - twhy
     - I
     - I
     - I
     - I
     - I
   * - 11
     - tinf
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 12
     - stor
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 13
     - sheb
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 14
     - sgos
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 15
     - sapo
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 16
     - squr
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 17
     - ssan
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 18
     - vsec
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 19
     - limit
     - I
     - I
     - I
     - I
     - I
   * - 20
     - jj
     - E
     - E
     - E
     - E
     - E
   * - 21
     - aa
     - E
     - E
     - E
     - E
     - E
   * - 22
     - kk
     - I
     - I
     - I
     - I
     - E
   * - 23
     - ff
     - E
     - E
     - E
     - E
     - E
   * - 24
     - cc
     - I
     - I
     - I
     - I
     - I
   * - 25
     - dd
     - E
     - E
     - E
     - E
     - E
   * - 26
     - gg
     - E
     - E
     - E
     - E
     - E
   * - 27
     - hh
     - E
     - E
     - E
     - E
     - E
   * - 28
     - ww
     - I
     - E
     - E
     - E
     - E
   * - 29
     - yy
     - E
     - E
     - E
     - E
     - E
   * - 30
     - needs
     - I
     - I
     - I
     - I
     - I
   * - 31
     - feeds
     - I
     - I
     - I
     - I
     - I
   * - 32
     - stayc
     - I
     - I
     - I
     - I
     - I
   * - 33
     - mento
     - E
     - E
     - E
     - E
     - E
   * - 34
     - diff
     - E
     - E
     - E
     - E
     - E
   * - 35
     - ll
     - I
     - I
     - I
     - I
     - I
   * - 36
     - con
     - I
     - I
     - I
     - I
     - E
   * - 37
     - pro
     - I
     - I
     - I
     - I
     - E
   * - 38
     - vv
     - I
     - I
     - I
     - I
     - I
   * - 39
     - vvnow
     - I
     - I
     - I
     - I
     - I
   * - 40
     - model
     - Y
     - Y
     - Y
     - Y
     - Y
   * - 41
     - conv
     - I
     - I
     - I
     - I
     - I
   * - 42
     - bib
     - I
     - I
     - I
     - I
     - I
   * - 43
     - pol
     - E
     - E
     - E
     - E
     - E
   * - 44
     - his
     - I
     - E
     - E
     - E
     - E
   * - 45
     - doi
     - E
     - E
     - E
     - E
     - E


Surprises (ax6--ax25, th5--th11)
================================

**Field 3 (name / ExplicitName):** Consistently status I across all
elements. The PoR does not have a separate "ExplicitName" field --- the
information is *implied* by the title + summary but never stated as a
standalone field. This is the most uniform gap.

**Field 8 (tcnt / TechExplanationContentAll):** Status I for most
elements. The PoR merges technical content with the "Explanation" section
(field 7/tctx). Separating tcnt from tctx requires editorial judgment.

**Field 9 (logic / LogicsUsed):** Consistently I for PET (mereology +
S5 always applies but is stated only once in the Formal Framework
section, not per-axiom) and mostly E for JUB (predicate logic used but
not explicitly labeled).

**Field 22 (kk / KnownKiller):** Status I for ax1--ax4 and ax15--ax25 (the
content exists in the "Explanation" and "Note" sections as implicit
acknowledgments of threats) but E for ax5--ax14 (Group II--V axioms
generally lack explicit threat identification).

**ax25 is the richest element:** 3 formal notes (Arrow, commons-tragedy,
cross-traditional qualification), capitalist and communist stream
annotations, multiple quest references. ax25 naturally populates more
fields than any other axiom.

**Theorems th5--th11:** Source fields (12--18) are systematically E. This
is expected --- theorems are derived, not independently supported by
scripture. The PoR field structure may need a mechanism for marking
fields as "not applicable by type" rather than "empty stub."


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

**Field proposal 1: ``type`` (ElementType)**
The PoR registry distinguishes axioms, theorems, quest entries, etc.
but this distinction is not a numbered field. Adding ``type`` as a
field would make the axiom/theorem/quest distinction extractable.
Currently, the compiler infers type from the D2 code (``ax``, ``th``),
but an explicit field would be more robust.

**Field proposal 2: ``scope`` (DomainScope)**
Several JUB axioms are explicitly scoped to specific domains (D_f,
D_free, D_inno). The scoping is stated in the intro/tctx but is not
a separate extractable field. A ``scope`` field would make domain
restrictions machine-readable.


Summary
=========

The compilation confirmed the Phase 2I-2 field testing report's findings.
The core content fields (identity, technical, sources) are well-populated.
Operational fields (20--29) are systematically empty. Network fields
(30--40) exist at status I (inferrable but not explicitly stated).
The most valuable observation is that theorems do not naturally populate
source fields (12--18), suggesting a field-applicability mechanism is
needed. Two new fields are proposed: ``type`` (element type) and
``scope`` (domain scope).