PROMY — Purifying Rewriting Orchestrating Matheological Yields#
Status: Partially formalized. SEED/FEED/GROW/REAP pipeline drafted. SEED tested on e7He (2026-03-29). See DD: PROMY Pipeline Specification (Draft).
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 FORGE Session Documentation Protocol.