.. meta::
   :description: Named after Prometheus, PROMY rewrites model source data by integrating HELL evidence. Read-write and dangerous, it requires human review gates.
   :keywords: PROMY, Prometheus, intra-model compiler, read-write, HELL evidence, purification, axiom evolution, theorem update, audit trail, safety profile
   :author: Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea, ClaudeOp46Max, Anthropic, and Spirit of Boolean Truth
   :og:card:title: PROMY — Read-Write<br>Reasoning Compiler
   :og:card:description: Like Prometheus regrowing his liver, PROMY integrates HELL findings into model source data. Read-write, dangerous, and never triggered by blanket regen.

.. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26
   OO :description: PROMY is the intra-model reasoning compiler that purifies and rewrites source data by integrating HELL evidence into axioms and theorems.
   OO :keywords: PROMY, Prometheus, intra-model, read-write, compiler, HELL, evidence, axioms, theorems, matheology, purification
   OO :og:card:title: PROMY — Intra-Model<br>Reasoning Compiler
   OO :og:card:description: Named after Prometheus, PROMY integrates HELL evidence into model source data to evolve axioms, theorems, and other elements.
   PP :description: Named after Prometheus, PROMY rewrites model source data by integrating HELL evidence. Read-write and dangerous, it requires human review gates.
   PP :keywords: PROMY, Prometheus, intra-model compiler, read-write, HELL evidence, purification, axiom evolution, theorem update, audit trail, safety profile
   PP :og:card:title: PROMY — Read-Write<br>Reasoning Compiler
   PP :og:card:description: Like Prometheus regrowing his liver, PROMY integrates HELL findings into model source data. Read-write, dangerous, and never triggered by blanket regen.

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

*********************************************************************
PROMY --- Purifying Rewriting Orchestrating Matheological Yields
*********************************************************************

**Status:** Partially formalized. SEED/FEED/GROW/REAP pipeline
drafted. SEED tested on e7He (2026-03-29). See :ref:`dd-promy-pipeline`.

|PROMY| is the intra-model reasoning compiler for matheology. It works
within a single model, integrating HELL evidence (cons, pros,
findings) to evolve axioms, theorems, and other elements.

Named after Prometheus, whose liver is eaten by an eagle every day and
regrows overnight. HELL evidence (the eagle) continually exposes flaws
in the model (the liver). PROMY purifies and rewrites the toxic parts.
But the model keeps growing, new evidence keeps arriving, and the
cycle repeats.


What PROMY does
=================

::

  hell/con/b/38/ ──→ jub/theorems.rst  (source modified)
  hell/pro/b/38/ ──┘

PROMY reads findings from the HELL register (cons, pros, evidence)
and determines whether axioms, theorems, or other elements in a
model's PoR source need updating. Unlike SISYF, PROMY **modifies
source data** --- it is the mechanism by which the model evolves.


Safety profile
================

**Read-write** with respect to model source data. This operation is
inherently dangerous and requires:

- Version control (commit before and after)
- Human review gates (no unsupervised source modifications)
- Append-only audit trails (llog files recording what changed and why)

PROMY must **never** be invoked by a blanket regeneration command.
It is a separate operation from SISYF with separate triggers, separate
permissions, and separate recovery strategies.


Early usage
=============

PROMY-like operations were performed informally during the Phase 2I
sequence, where HELL findings were integrated into JUB theorems. These
sessions can inform the eventual formal specification.


Open tasks
============

- Write a formal specification (as a DD, parallel to SISYF's skill
  spec)
- Define the trigger and permission model (what invokes PROMY, who
  approves changes)
- Define the audit trail format (how changes are logged)
- Identify all Phase 2I prompts that performed PROMY-like work, to
  inform the spec
- **Evaluate FORGE's LLog infrastructure for PROMY adoption:**
  FORGE (the background knowledge compiler) developed a structured
  session LLog protocol with named lifecycle commands (IGNITE, HEAT,
  STRIKE, TEMPER, QUENCH, BANK, EMBER), delayed-counting session IDs,
  append-only logging with verbatim prompts, and recovery from
  interrupted sessions. PROMY's audit trail needs (line 69 above) may
  benefit from adopting or adapting this infrastructure. The ``promy_``
  namespace prefix is already reserved. See :ref:`forge-llog-protocol`.


.. toctree::
   :maxdepth: 2
   :caption: Pipeline Stages

   seed/index
   feed/index
   grow/index
   reap/index


.. toctree::
   :maxdepth: 1
   :caption: Documentation

   dd-promy-pipeline
   promy-guide
   aa