.. _forge-aa:

****************************************************
FORGE --- Any Aims (AA)
****************************************************

Open tasks for the FORGE compiler.


Operational Aims
==================

.. list-table::
   :header-rows: 1
   :widths: 28 52 10

   * - Item
     - Description
     - Priority
   * - AA-FORGE-LLogLocation-a1
     - **Update Session Directory Structure in protocol.rst.** The
       protocol currently specifies ``forge/llog/`` as the session
       directory root. The agreed future location is
       ``hell/llog/forge/`` (see AA-LLogMigration-a1 in
       ``model/e7day/anyaims.rst``). The protocol must be updated
       to reflect the new location **before** running further FORGE
       sessions, so new sessions are created in the right place from
       the start. Existing sessions (sa1--sa3) will be migrated
       separately. Update: ``llog/protocol.rst`` lines 99--108,
       and any forge prompt templates that reference the old path.
     - high
   * - AA-FORGE-HeadingHierarchy-a1
     - Cross-reference to AA-HeadingHierarchy-a1. FORGE-generated
       llog content introduces heading underlines that conflict with
       the document's established hierarchy, causing CRITICAL Sphinx
       warnings. Fix must be applied in FORGE prompts to enforce a
       consistent heading convention.
     - medium
   * - AA-FORGE-KeepSyntax-a1
     - Cross-reference to AA-KeepDirective-a1. FORGE prompts should
       use ``.. keep --`` (valid RST comment) not ``.. keep::``
       (unknown directive). Update all FORGE prompt templates.
     - low


   * - AA-FORGE-ModelChangeMarker-a1
     - **Grep-friendly change markers in llogs.** During PROMY:GROW,
       the operator must scan the entire FORGE llog to find all
       changes to formal statements. This is error-prone for large
       llogs (the Sa3 session was 8700+ lines). **Proposal:** every
       time FORGE modifies, creates, or proposes a change to a formal
       statement (axiom, theorem, structural property, predicate, or
       symbol), it emits a standardized marker::

         MODEL_CHANGE: <claim-id> | <type> | <target-file>

       where ``<type>`` is one of: ``repair``, ``new``, ``rename``,
       ``strengthen``, ``weaken``, ``predicate-spec``. The marker
       appears on a single line, grep-able. PROMY:GROW can then
       ``grep MODEL_CHANGE llog.rst`` to generate the repair
       inventory automatically. **Implementation:** update FORGE
       prompt templates (STRIKE, TEMPER, QUENCH) to emit the marker
       as part of their standard output protocol.
     - high


Adversarial Aims
==================

*(None currently open.)*