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

.. meta::
   :description: Cases where authors naturally combine multiple D2 type concepts in chained labels, testing whether single types always suffice or chaining adds meaning.
   :keywords: D2 chaining, label chaining, BEST Names, type concepts, naming grammar, single vs chained, integration finding, data collection, llog
   :author: Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea, ClaudeOp46Max, Anthropic, and Spirit of Boolean Truth
   :og:card:title: D2 Chaining Evidence<br>Label Combination Patterns
   :og:card:description: Do authors naturally reach for chained D2 type labels? This data collection tracks real cases to decide whether the grammar needs multi-type support.

.. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26
   OO :description: Data collection log recording cases where authors naturally combine multiple D2 type concepts in chained labels during integration.
   OO :keywords: matheology, integration finding, D2 chaining, label chaining, BEST Names, type concepts, naming grammar, data collection, evidence, llog
   OO :og:card:title: Integration Finding:<br>D2 Chaining Evidence
   OO :og:card:description: Recording cases where authors naturally reach for chained D2 fields and whether single types always suffice or chaining adds meaning.
   PP :description: Cases where authors naturally combine multiple D2 type concepts in chained labels, testing whether single types always suffice or chaining adds meaning.
   PP :keywords: D2 chaining, label chaining, BEST Names, type concepts, naming grammar, single vs chained, integration finding, data collection, llog
   PP :og:card:title: D2 Chaining Evidence<br>Label Combination Patterns
   PP :og:card:description: Do authors naturally reach for chained D2 type labels? This data collection tracks real cases to decide whether the grammar needs multi-type support.

.. 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: 43 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: D2 Chaining Evidence
*********************************************************************

.. note::

   **Data collection file.** Agents performing content integration should
   append rows below whenever they encounter content that naturally
   combines two or more D2 type concepts --- whether or not the author
   used a chained label.

   **Question being answered:** How often do authors naturally reach for
   chained D2 fields (e.g., ``pet-ax5-logic-limit``)? Can the same
   information always be expressed with a single D2 type, or are there
   cases where chaining genuinely adds meaning?

   **How to report:** For each case, record: the label or heading where
   you found it, what the chain would be, whether a single type suffices,
   and a brief note on what meaning the chain carries.


Findings
==========

.. list-table::
   :header-rows: 1
   :widths: 25 20 10 45

   * - Found in
     - Natural chain
     - Single OK?
     - Note
   * - ``pet/axioms.rst`` ax5_A5 explanation
     - ``pet-ax5-logic-limit``
     - No
     - Discusses a limitation *specific to the logic framework* of ax5_A5, not a general limitation of ax5_A5 itself. ``pet-ax5-limit`` would lose the specificity.
   * - ``jub/axioms.rst`` ax20_A20 dependencies
     - ``jub-ax20-needs-feeds``
     - Yes
     - Mentions both upstream and downstream in one paragraph; could be split into ``needs`` and ``feeds`` separately.


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

*(Agents: after all content has been sorted, write a summary paragraph
here. How many genuine chaining cases? How many could be expressed with
a single type? Does the evidence support raising the default nesting
limit above 2, or is 2 sufficient?)*


.. admonition:: 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
   :ref:`hell-ll-other-b15-teles-renaming-prompt` for the complete
   mapping table and :ref:`legacy-5d-link-names-table-for-pet-jub-model` for the permanent
   reference.