.. meta::
   :description: POST organizes matheology compilers with double-letter codes for backlog, design discussions, and evidence. This page defines the authoritative registry.
   :keywords: POST, Project Organization Stabilizing Toolkit, POST registry, double-letter codes, ww, ee, dd, aa, compiler infrastructure, SISYF, PROMY
   :author: Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea, ClaudeOp46Max, Anthropic, and Spirit of Boolean Truth
   :og:card:title: POST Code Registry —<br>Compiler Infrastructure
   :og:card:description: The authoritative registry of POST double-letter codes that organize backlog, design decisions, and evidence across all matheology compilers.

.. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26
   OO :description: POST provides shared organizational infrastructure for all matheology compilers, including backlog, design discussions, and evidence.
   OO :keywords: POST, Project Organization, compiler, backlog, design discussion, evidence, infrastructure, matheology, SISYF, PROMY
   OO :og:card:title: POST — Organizational<br>Toolkit for Compilers
   OO :og:card:description: Shared infrastructure for all matheology compilers: backlog tracking, design discussions, experimental evidence, and the POST registry.
   PP :description: POST organizes matheology compilers with double-letter codes for backlog, design discussions, and evidence. This page defines the authoritative registry.
   PP :keywords: POST, Project Organization Stabilizing Toolkit, POST registry, double-letter codes, ww, ee, dd, aa, compiler infrastructure, SISYF, PROMY
   PP :og:card:title: POST Code Registry —<br>Compiler Infrastructure
   PP :og:card:description: The authoritative registry of POST double-letter codes that organize backlog, design decisions, and evidence across all matheology compilers.

.. 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

.. _compiler-post:

*********************************************************************
POST --- Project Organization Stabilizing Toolkit System
*********************************************************************

POST provides the shared organizational infrastructure for all
matheology compilers. It contains the backlog, design discussions,
experimental evidence, and the POST code registry itself.

POST is not a compiler (yet!)--- it is the scaffolding that keeps the
compilers organized. The double-letter subdirectory codes (``aa/``,
``dd/``, ``ee/``) follow the POST naming convention defined in the
:ref:`5D link naming architecture <compiler-5d-link-naming>`.

.. note::

   ``ww/`` (WorkingWheels) directories live inside each compiler
   (e.g., ``sisyf/ww/``), not here. POST holds only the shared
   infrastructure that crosses compiler boundaries.


Contents
==========

.. toctree::
   :maxdepth: 2

   aa/index
   dd/index
   ee/index


.. _compiler-post-registry:

POST Code Registry
====================

The ``compiler/`` directory uses POST (Project Organization Stabilizing
Toolkit System) double-letter codes as subdirectory names. This section
is the authoritative registry mapping codes to their purpose within
the compiler. For the full POST system definition, see
:ref:`5D link naming architecture <compiler-5d-link-naming>` Section 9.3.


Active Codes
^^^^^^^^^^^^^^

.. list-table::
   :header-rows: 1
   :widths: 8 22 70

   * - Code
     - Name
     - Purpose in ``compiler/``
   * - ``ww``
     - WorkingWheels
     - Operational files the compiler reads at build time: skill
       specification, 5D architecture doc, stub templates. These are
       the living working copies that evolve as the system grows.
   * - ``ee``
     - EnclosedEvidence
     - Experimental evidence collected under well-defined circumstances
       during compilation runs. Integration findings, field usage
       census, design question evidence. To be used under well-defined
       conditions for informing future compiler updates.
   * - ``dd``
     - DesignDiscussions
     - Architectural discussions and decisions specific to the compiler.
       Each decision is numbered using the b11 delayed counting default
       and stored in ``dd/llog/b/N/``. The ``dd/`` top level is kept
       clean for introductory and overview material.
   * - ``aha``
     - (not a POST code)
     - All Help Available. User guide, quickstart, troubleshooting.
       Uses the AHA acronym rather than a POST code because it serves
       a different purpose (help, not project organization).


Reserved Codes (not yet in use)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

These POST codes are defined in the AHA doc but do not yet have a
``compiler/`` subdirectory. They may be created as the compiler
evolves:

.. list-table::
   :header-rows: 1
   :widths: 8 22 70

   * - Code
     - Name
     - Potential use in ``compiler/``
   * - ``aa``
     - AnyAim
     - Next steps and task tracking for compiler development
   * - ``hh``
     - HistoryHeap
     - Deprecated compiler versions, superseded extraction matrices
   * - ``jj``
     - JammedJob
     - Known problems where hope of fixing exists, even though it is not
       known whether fixing is possible. A JJ can become a KK (documenting
       why exactly it fails with no workaround) or lead to the revival of
       any maturity stage that fell into NN. See :ref:`compiler-stayvs`.
   * - ``kk``
     - KnownKiller
     - The definitive graveyard: concise collection of what is known to
       fail, for whatever well-defined and understood reason. Unlike NN
       (which carries hope of rescue), KK is terminal with a clear
       explanation of *why* there is no fix. See :ref:`compiler-stayvs`.
   * - ``ll``
     - LabLog
     - Session logs specific to compiler work
   * - ``yy``
     - YesYet
     - Test cases for checking compiler output quality


Naming Convention
^^^^^^^^^^^^^^^^^^^

- POST double-letter codes are double-caps for humans (e.g. FF), but in web-links they are lowercase: ``ww/``, ``ee/``.

- On rare occasions the POST system also uses other descriptive names, such as AHA or ``aha/`` (for Any Help Available, brief for README).