Matheology Compilers#

The matheology project uses four compilers. Each is named with an acronym that describes what it does, and a metaphor that reflects its safety profile and character.

The Compiler Pipeline#

Compiler

Does what

Input

Output

Status

FORGE

Explores and develops new models from scratch through structured sessions (IGNITE/HEAT/STRIKE/TEMPER/QUENCH/BANK/EMBER)

Mission context + formal math reference sheets

Raw model content in llogs (axioms, theorems, proofs, tests)

Working

PROMY

Compiles raw materials from FORGE rounds of review into fully integrated, cleaned-up models ready for SISYF to present

FORGE llogs + HELL evidence

Clean model source files (axioms.rst, theorems.rst, symbols.rst, overview.rst, aa.rst, llog.rst, etc.)

Implicit

SISYF

Assembles audience-depth views across models for different readers (expert, easy, producer, math, machine)

Clean model source files

Downstream audience-specific pages

Working

TELES

Fixes RST formatting errors in LLogs without touching content (headings, indentation, directives, blank lines)

LLog files with RST errors

Same files with formatting fixed + error report appended

Designed

Note

PROMY has been partially formalized. The SEED/FEED/GROW/REAP pipeline is drafted and SEED has been tested on e7He (2026-03-29). FEED, GROW, and REAP are untested. Full formal specification is tracked in AA-PROMY-Build-a1. Remove this note once all four stages have prompt templates and have been tested on at least one model.

Compiler Descriptions#

  • FORGE (Formally Organized Research Growing Extensibly) — the background knowledge compiler. Like a forge where raw material is heated, shaped, and tempered into something strong, FORGE compiles mission-critical reference material from formal mathematics into concise, applied sheets that equip the model developer before new theory is written. FORGE feeds the forge sessions where models are developed, which then enter HELL for critique, PROMY for repair, and SISYF for presentation. Read-only — produces reference sheets, does not modify model content.

  • PROMY (Purifying Rewriting Orchestrating Matheological Yields) — the intra-model reasoning compiler, named after Prometheus. Like Prometheus, whose liver is torn out by the eagle and regrows overnight, PROMY purifies and rewrites flaws exposed by HELL evidence — and the cycle repeats as the model grows. Read-write with respect to source data. See PROMY design doc for the pipeline specification.

  • SISYF (Systems Integrating System Yielding Formalisms) — the cross-model compiler, named after Sisyphus. Like Sisyphus, who pushes his boulder up the hill again and again but never changes it, SISYF assembles PoR sources into audience-depth views repeatedly and faithfully. Read-only with respect to source data.

All compilers operate across the 5-dimensional link names label space defined by (Model, ElementTypes, Version, Depth, View).

Getting Started#

New to the system? Start here:

  • Introduction to 5D Link Naming — a plain-English walkthrough of how labels work and what the five dimensions are.

  • SISYF Guide — quickstart examples, option reference, stub templates, and troubleshooting for the cross-model compiler.

  • PROMY Guide — user guide for the intra-model reasoning compiler (placeholder).

  • FORGE Guide — background knowledge compiler: reference sheets, pre-forge prompts, forge session prompts, and the 12-sheet formal toolkit.

For the full technical specifications, see the SISYF Skill Spec and the 5D Link Naming Architecture.

Compilers

5D Space

StayVS (Versioning & Maturity)

POST (Shared Infrastructure)