.. meta::
   :description: Open action items for e7Day OOv1: formalization tasks, new model dependencies, precision improvements, and FORGE protocol proposals from TEMPER QUENCH.
   :keywords: e7Day, AnyAims, action items, AA, TEMPER, QUENCH, formalization, e7He, e7Ch, open tasks
   :author: LLoL as Laurence Loewe of Laodicea and Claude Opus 4.6

*************************************************
e7Day --- AnyAims (Open Action Items)
*************************************************

.. vvnow dv_ClaOp46Max_OOv1_2026m03d27

Active action items from TEMPER QUENCH (Round a2). Completed and superseded
items are excluded. For the full AA history, see the session log
(``matheology/hell/ll/forge/b/12/llog.rst``).


New Model Dependencies
========================

.. list-table::
   :header-rows: 1
   :widths: 15 55 15

   * - ID
     - Description
     - Priority
   * - AA-e7He-a1
     - Specify e7He model (7-stage Hero Journey for scope-expansion
       commitment). Critical dependency for th7 Gate 5.
     - **high**
   * - AA-e7Ch-a1
     - Specify e7Ch model (7ChangeStages: 7 functional milestones for
       self-stabilizing innovation processes). Dependency for m7.ax3 defense.
     - medium
   * - AA-e7Tr-a1
     - Specify e7Tr model (tech adoption cycle traced through e7Ch stages).
     - low


Formalization Tasks
=====================

.. list-table::
   :header-rows: 1
   :widths: 15 55 15

   * - ID
     - Description
     - Priority
   * - AA-TEMPER-a2
     - Formalize "designed-to-resolve" predicate for m6.ax3.
     - medium
   * - AA-TEMPER-a8
     - Formalize proof of m2.th1 from m2.ax1 + m2.ax2.
     - medium
   * - AA-TEMPER-a10
     - Formalize derivation of m6.th1 from m6.ax3 + m6.ax4 (6-step chain).
     - medium
   * - AA-TEMPER-a11
     - Determine whether "continuous novelty generation" needs an explicit
       axiom or is derivable from existing axioms.
     - medium
   * - AA-TEMPER-a12
     - Formalize error-accumulation model for th5 (define error rate during
       work, consolidation rate during rest, threshold for BABL).
     - medium
   * - AA-ASON-a1
     - Formally define ASON (Ambiguous Semantics Of Nothing). Current status:
       concept introduced at th7, acronym stored, no formal definition.
     - low


Precision Improvements
========================

.. list-table::
   :header-rows: 1
   :widths: 15 55 15

   * - ID
     - Description
     - Priority
   * - AA-TEMPER-a13
     - Clarify "constructive" for VOID case (mc.ax1). Does VOID have a
       constructive witness?
     - medium
   * - AA-TEMPER-a14
     - Formalize "scope-creep-excluded" (mc.ax2).
     - medium
   * - AA-TEMPER-a15
     - Refine mc.ax4 cascade to DAG (m5 depends on m3 AND m4,
       multi-dependency rather than linear order).
     - low
   * - AA-TEMPER-a16
     - Resolve constructive-existence tension for VOID. Type-theoretic void
       vs. thermodynamic maximum entropy may need disentangling.
     - medium
   * - AA-TEMPER-a17
     - Justify Ocean → Trees → Ocean as the specific circulation pattern
       (vs. alternative patterns).
     - low
   * - AA-TEMPER-a18
     - Formalize "first-class" for time (m4.ax2). Needs sharper
       type-theoretic definition.
     - low
   * - AA-TEMPER-a19
     - Clarify "self-replicating" scope (m5.ax1): type-level replication
       vs. instance-level replication.
     - low
   * - AA-TEMPER-a20
     - Scope "recursively endowed" to within L (m6.ax2). Not claiming divine
       powers in D.
     - low
   * - AA-TEMPER-a21
     - Specify categorical duality for th6 (initial/terminal object duality?).
     - low


Cross-Model Issues
====================

.. list-table::
   :header-rows: 1
   :widths: 15 55 15

   * - ID
     - Description
     - Priority
   * - AA-th8-Metastable-a1
     - **th8 / e7He.th5 CTMC tension:** JUB th8 calls BABL an "attractor,"
       but e7He.th5 claims P(BABL self-destructs | t→∞) = 1. If BABL
       self-destructs almost surely, it is not a true absorbing state.
       Resolution: BABL is **metastable** --- absorbing on finite horizons,
       transient on infinite horizons (like a supercooled liquid or a
       metastable nuclear isomer). th8's language should be qualified:
       "BABL is a metastable attractor that self-destructs stochastically
       via the ISMR feedback loop." This affects th8 (JUB), th3 (e7Day),
       and th5 (e7He). Cross-model update needed.
       Source: FORGE Sa3 Round a2 TEMPER, Iron Maiden Test I on e7He.th5.
     - **high**


Open Investigations
=====================

.. list-table::
   :header-rows: 1
   :widths: 15 55 15

   * - ID
     - Description
     - Priority
   * - AA-TEMPER-a6
     - Investigate whether th7 Gate 5 partially derives th8 (Binary
       Attractors), potentially answering Con-11.
     - medium
   * - AA-TEMPER-a7
     - Attempt quantitative fracture-dynamics model to strengthen Gate 5 → th8
       derivation.
     - low


7e Hairball Construction
==========================

.. list-table::
   :header-rows: 1
   :widths: 15 55 15

   * - ID
     - Description
     - Priority
   * - AA-7eHairball-a1
     - Construct 2nd-intro files integrating StayC, MentO, and DOIS into
       the 7e cross-reference hairball alongside the existing e7He/e7Tr/e7Ch/BABL
       1st-intro files. The 1st-intro files cover 3 of the known 7e echo types;
       additional echo types (StayC stages, MentO mentoring codes, DOIS data
       architecture, and others) should be added in subsequent intro levels
       to progressively reveal the full hairball without overwhelming beginners.
     - medium
   * - AA-7eHairball-a2
     - Assess whether additional 7e echo types (beyond the ~6 known types)
       exist and whether the structural alignment is genuine (structural)
       or incidental (organizational convenience). Current status: OKO.
     - low
   * - AA-e7He-CardGame-a1
     - Design a card game for teaching the 7-stage hero journey to
       young audiences. Use journey segment definitions, BABL
       temptation patterns, Beatitude encouragements, and 7e echoes
       as card content. Goal: stimulate discussion of the hero journey
       while playing. Consider doing this in the same session where
       the FORGE context is already loaded.
     - medium
   * - AA-e7Ch-Rev23-a1
     - Draft an interpretation of Revelation 2-3 (letters to the
       seven churches) through the e7Ch lens. Write to
       ``model/e7ch/1st-ai-deex-rev.2-3.rst``. Caution: deep rabbit
       holes exist in this text; focus on main innovation-lifecycle
       parallels without getting sidetracked by eschatological detail.
     - low
   * - AA-KeepDirective-a1
     - Collect experiences with ``.. keep --`` content protection comment
       during FORGE sessions. After sufficient experience, evaluate whether
       gradation, expiration, StayC integration, or unification with SISYF
       ``.. compiler:protected`` is needed. Design doc at
       ``compiler/living-docs/dd/dd-keep-directive.rst``.
       **Syntax update (2026-03-29):** Changed from ``.. keep::`` (unknown
       directive, causes Sphinx ERROR) to ``.. keep --`` (valid RST comment).
       All compilers should use the ``.. keep --`` form going forward.
       Update references in design doc and all compiler instruction sets.
     - low
   * - AA-HeadingHierarchy-a1
     - Permanent fix for heading-level inconsistency in compiler-generated
       llog content. **Problem:** When compilers append sections to llogs,
       they introduce heading underlines (``===``, ``"""``, etc.) that
       conflict with the heading hierarchy established earlier in the
       document. Sphinx reports CRITICAL errors for every such section.
       **Analysis:** RST determines heading levels by order of first
       appearance --- the first underline style seen becomes level 1, etc.
       Compilers generate sections independently without knowing the
       existing heading stack. **Possible fixes:** (1) Define a fixed
       heading-level convention in the FORGE protocol (e.g., ``=`` for
       session, ``-`` for round, ``~`` for entry, ``"`` for sub-entry)
       and enforce it in all compiler prompts. (2) Add a post-processing
       step (``make lint-headings`` or similar) that detects violations.
       (3) Use RST ``rubric`` or ``topic`` directives instead of headings
       for compiler-generated sections, avoiding the hierarchy entirely.
       Option (1) is recommended as it is simplest and most durable.
     - medium
   * - .. _aa-promy-build-a1:

       AA-PROMY-Build-a1
     - Formally specify and build PROMY as an operational compiler.
       PROMY is currently used only informally --- the workflow exists
       implicitly in the gap between what FORGE produces and what SISYF
       needs. **Progress:** SEED stage tested on e7He (2026-03-29),
       generic SEED prompt template written. PROMY llog infrastructure
       created in ``hell/llog/promy/``. **Remaining:** (1) Finalize
       the SEED/FEED/GROW/REAP pipeline spec in
       ``compiler/promy/dd-promy-pipeline.rst``. (2) Run FEED/GROW/REAP
       on e7He to complete the test case. (3) Write prompt templates
       for FEED, GROW, REAP (as done for SEED). (4) Write the formal
       skill spec (parallel to SISYF's). (5) Remove the "implicit" note
       from the compiler index page.
       **See:** :ref:`dd-promy-pipeline` for the draft pipeline spec.
     - high
   * - AA-LLogMigration-a1
     - Migrate all llogs to ``hell/llog/`` with compiler prefixes
       (``forge_``, ``promy_``, ``vv_``). Currently llogs are scattered
       across ``compiler/forge/llog/``, ``vv/jub/oov2/llog/``, and
       model-local ``llog/`` directories. **Prerequisite:** Complete
       PROMY extraction of e7He/e7Ch/e7Tr first (reduces the number of
       content refs pointing into llogs). **Scope:** ~68 files, ~69k
       lines, ~481 path references across 46 files. Estimated effort:
       2--4 hours of careful refactoring plus full build check.
     - low
