.. meta:: :description: Complete reference for the 5D BEST Names system: model, element, version, depth, and view dimensions that give every axiom a stable unique label. :keywords: BEST Names, 5D label grammar, D1 model, D2 element, D3 version, D4 depth, D5 view, PoR fields, extraction matrix, link stability, knowledge pipeline :author: Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea, ClaudeOp46Max, Anthropic, and Spirit of Boolean Truth :og:card:title: BEST Names Reference
— 5D Label System :og:card:description: Every axiom, theorem, and objection gets a stable, parseable, globally unique label built from five orthogonal dimensions. Full registry included. .. SOCIAL-CARD-QUALITY-COMPARE --- OO (default effort) vs PP (max effort), 2026-03-26 OO :description: Full reference for the BEST Names system that assigns every axiom, theorem, and objection a stable, parseable, globally unique label. OO :keywords: matheology, BEST Names, naming architecture, label system, expert reference, axiom labels, theorem labels, parseable, globally unique, knowledge pipeline OO :og:card:title: BEST Names Reference
Expert Label System OO :og:card:description: How every axiom, theorem, and objection gets a Brief, Explicit, Summarizing, Title label that is stable and globally unique. PP :description: Complete reference for the 5D BEST Names system: model, element, version, depth, and view dimensions that give every axiom a stable unique label. PP :keywords: BEST Names, 5D label grammar, D1 model, D2 element, D3 version, D4 depth, D5 view, PoR fields, extraction matrix, link stability, knowledge pipeline PP :og:card:title: BEST Names Reference
— 5D Label System PP :og:card:description: Every axiom, theorem, and objection gets a stable, parseable, globally unique label built from five orthogonal dimensions. Full registry included. .. 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
) - [ ] 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 .. include:: /_templates/include-file/page-prefix.rst .. _naming-expert: ***************************************************** BEST Names Architecture --- Expert Reference ***************************************************** This page is a reference for researchers, mathematicians, and theologians who work directly with the formal content of mathematical theology. It documents the naming system that assigns every axiom, theorem, objection, and response a stable, parseable, globally unique label. BEST stands for **B**\ rief, **E**\ xplicit, **S**\ ummarizing, **T**\ itle --- four naming layers, from the compact label code (``pet-ax5``) to the full display title (ax5 --- Containment). For the beginner version, see :ref:`naming-easy`. For the technical design decisions behind this architecture, see :ref:`naming-architect`. .. contents:: On this page :depth: 2 :local: ---- 1. The knowledge pipeline ============================ Knowledge flows through five stages from raw evidence to end-user consumption. Each stage has a "Place of" designation: .. list-table:: :header-rows: 1 :widths: 8 22 35 35 * - Stage - Name - What it contains - Example files * - **PoE** - Place of Evidence - Interactive sessions, raw exchanges, reviewer input - Claude conversations, reviewer notes * - **PoC** - Place of Chronicling - Organized evidence: llogs, quest files, analyses - ``quest.rst``, ``llog_*.rst`` * - **PoR** - Place of Reasoning - Synthesized axioms, theorems, analyses (40+ fields per element) - ``pet/axioms.rst``, ``jub/theorems.rst`` * - **PoT** - Place of Translating - Producer-depth materials for teaching and communication - ``axioms/producer.rst`` * - **PoU** - Place of Using - Consumer-depth, beginner-friendly content - ``axioms/easy.rst`` The PoR is the single source of truth. All downstream views (PoT, PoU) are compiled from it. Every formal element has ONE canonical label pointing to its PoR page. ---- 2. The 5 orthogonal dimensions ================================= Every page can be located by coordinates in a 5-dimensional space. Not every combination exists, but the naming system accommodates any valid combination without collisions. .. list-table:: :header-rows: 1 :widths: 4 12 20 30 12 22 * - D - Dimension - Answers - Values - Label segment - Combinable with * - **D1** - Model - Which axiom system? - ``pet``, ``jub``, ``4be`` (see registry) - prefix: ``pet-`` - all * - **D2** - Element - What element, and what about it? - Flat type ID registry; chainable - ``ax5``, ``ax5-logic`` - all * - **D3** - Version - Which frozen snapshot? - ``oov1``, ``oov2``, ``ppv1`` - ``-oov2`` - all * - **D4** - Depth - For which audience? - (default=expert), ``prod``, ``easy``, ``math``, ``hu``, ``ma`` - ``-easy`` - all * - **D5** - View / Source / Language - Which worldview, source text, or cultural lens? - ``v*`` views, ``s*`` sources, ``l*`` languages - ``-vjud``, ``-stor``, ``-lde`` - all ---- 3. The label grammar ====================== :: {model}-{typeID}[{N}][-{typeID}[{N}]]*[-{version}][-{depth}][-{view}] **Rules:** 1. D1 (model) + at least one D2 type ID are always required. 2. Omitted dimensions default to: latest version, expert depth, all views, English. 3. The bare label ``{model}-{typeID}`` is the canonical PoR --- globally unique, never duplicated. 4. **All lowercase.** RST/Sphinx labels are case-insensitive; case cannot encode information. 5. **Hyphen is the sole separator.** No underscores. No exceptions. 6. Bare codes without digits (``pet-ax``) denote collection or landing pages. Codes with digits (``pet-ax5``) denote specific items. 7. The parser reads D2 type IDs greedily until it encounters a token matching D3, D4, or D5 --- at which point it transitions out of D2. **Examples:** .. list-table:: :header-rows: 1 :widths: 40 60 * - Label - Meaning * - ``pet-ax5`` - Pet Axiom 5, canonical PoR (latest, expert, English) * - ``pet-ax5-oov2`` - Pet ax5, frozen at OOv2 * - ``pet-ax5-easy`` - Pet ax5, beginner view * - ``pet-ax5-oov2-easy`` - Pet ax5, OOv2, beginner * - ``pet-ax5-prod-vjud`` - Pet ax5, producer depth, Jewish perspective * - ``pet-ax5-logic`` - Pet ax5, logic field (D2 chain of 2 type IDs) * - ``pet-ax-net`` - Pet axiom dependency network (collection) * - ``jub-th8-stayc`` - Jub th8 maturity status * - ``all-ax-conv`` - Cross-model axiom convergence matrix * - ``pet-ax-ff`` - Pet axioms feedback collection ---- 4. D1 --- Model registry ============================ .. list-table:: :header-rows: 1 :widths: 12 12 50 26 * - Prose form - Label code - Full name - Status * - Pet - ``pet`` - Pan-En-Theistic foundation (ax1--ax14) - Active * - Jub - ``jub`` - Jubilee-System extension (ax15--ax25) - Active * - 4Be - ``4be`` - (future) - Reserved * - (all) - ``all`` - Cross-model compilation (reserved keyword) - System **In prose:** TitleCase (Pet, Jub, 4Be). **In labels:** all lowercase. ---- 5. D2 --- Type ID registry ============================== All D2 codes live in a single flat registry. Any registered type ID may appear at any position in a D2 chain. The groupings below are organizational, not grammatical. 5.1 Formal elements ^^^^^^^^^^^^^^^^^^^^^^ .. list-table:: :header-rows: 1 :widths: 8 16 52 24 * - Code - Name - Definition - Standard in * - ``ax`` - Axiom - Statement assumed true without proof - Logic, mathematics * - ``th`` - Theorem - Statement proven from axioms/lemmas - Mathematics * - ``lm`` - Lemma - Proven stepping stone toward a theorem - Mathematics * - ``cr`` - Corollary - Statement following directly from a theorem - Mathematics * - ``cj`` - Conjecture - Statement believed true, not yet proven - Mathematics * - ``df`` - Definition - Precise meaning of a term - Logic * - ``sy`` - Symbol - Formal notation - All formal systems * - ``con`` - Contra - Objection in quest/disputatio structure - Scholastic method * - ``pro`` - Reply/Pro - Response to an objection - Scholastic method * - ``proof`` - Proof - Formal proof object - Mathematics 5.2 Structural fields ^^^^^^^^^^^^^^^^^^^^^^^ These chain after any other type ID: ``pet-ax5-logic``, ``jub-th8-needs``, ``pet-ax-ff``. .. list-table:: :header-rows: 1 :widths: 10 18 52 20 * - Code - Name - Purpose - Example * - ``logic`` - Logic - Which logical framework; what it preserves/discards - ``jub-ax13-logic`` * - ``limit`` - Constraint - Known limitations, boundary conditions - ``pet-ax5-limit`` * - ``needs`` - NeedsFeed - Upstream dependencies - ``pet-ax5-needs`` * - ``feeds`` - FeedsNeed - Downstream dependents - ``pet-ax5-feeds`` * - ``net`` - Network - Dependency graph - ``pet-ax-net`` 5.3 POST operational fields (doubled-letter codes) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Pattern: ``^([a-z])\1$`` --- exactly 2 identical lowercase letters. .. list-table:: :header-rows: 1 :widths: 8 22 50 20 * - Code - Name - Purpose - Example * - ``aa`` - AnyAim - Tasks, next steps, priorities - ``pet-ax5-aa`` * - ``cc`` - CollectedContent - Background reading, references from others - ``pet-ax5-cc`` * - ``dd`` - DesignDoc - Architectural decisions and rationale - ``pet-ax5-dd`` * - ``ff`` - FeedbackFlow - Collected feedback to be processed - ``pet-ax-ff`` * - ``kk`` - KnownKiller - Identified traps with avoidance strategies - ``pet-ax5-kk`` * - ``ll`` - LabLog - Session log landing page - ``pet-ax5-ll`` * - ``vv`` - VersionedVariant - Overview of all versions - ``pet-ax5-vv`` * - ``ww`` - WorkingWheel - What would break if this changed - ``pet-ax5-ww`` 5.4 Analytical fields (3+ letter codes) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. list-table:: :header-rows: 1 :widths: 8 22 50 20 * - Code - Name - Purpose - Example * - ``diff`` - VersioningHistory - What changed between versions - ``pet-ax5-diff`` * - ``stayc`` - StabilityCode - StayVS maturity status - ``jub-th8-stayc`` * - ``conv`` - Convergence - Worldview agreement/divergence matrix - ``all-ax-conv`` * - ``bib`` - Bibliography - Academic references - ``pet-ax5-bib`` * - ``his`` - History - Historical analysis, development timeline - ``pet-ax5-his`` **Design rule:** All D2 codes must contain only lowercase letters (``[a-z]``), never digits. The parser identifies the item-number boundary by detecting the first digit: ``ax5`` parses as type ``ax``, item ``5``. ---- 6. D3 --- Version registry ============================== .. list-table:: :header-rows: 1 :widths: 15 50 35 * - Code - Meaning - Status * - ``oov1`` - Original Objections Version 1 - Archived * - ``oov2`` - Original Objections Version 2 - Current freeze * - ``ppv1`` - Poster Phase Version 1 - Archived ---- 7. D4 --- Depth (audience) ============================ .. list-table:: :header-rows: 1 :widths: 10 14 40 36 * - Code - Name - Pipeline stage - Audience * - (default) - Expert - PoR (full synthesis) - Researchers, theologians * - ``prod`` - Producer - PoT (translation) - Teachers, preachers, communicators * - ``easy`` - Easy - PoU (point of use) - Beginners, general public * - ``math`` - Math - Formal extraction - Mathematicians, theorem provers * - ``hu`` - HumanHub - Human disambiguation - Human visitors ("Which view?") * - ``ma`` - MachineHub - Machine disambiguation - AI agents, APIs ---- 8. D5 --- View, source, and language ======================================= Three prefixes partition this dimension: - ``v`` + 3 letters = **View** (broad tradition synthesis) - ``s`` + 3 letters = **Source** (narrow upstream source text) - ``l`` + 2 letters = **Language** (language-specific cultural insight) 8.1 Views ^^^^^^^^^^^ .. list-table:: :header-rows: 1 :widths: 8 18 74 * - Code - Name - Scope * - ``vjud`` - Judaism - Torah, Prophets, Writings, Talmud, Kabbalah, modern * - ``vchr`` - Christianity - Gospels, Apostolic, Church fathers, councils, modern theology * - ``visl`` - Islam - Quran, Hadith, Sunni/Shia, Sufi, modern * - ``vhin`` - Hinduism - Vedas, Upanishads, Bhagavad Gita, Vedanta, modern * - ``vsec`` - Secular - Philosophy, empiricism, humanism, naturalism * - ``vbud`` - Buddhism - All Buddhist traditions * - ``vbah`` - Baha'i - Baha'i sources * - ``vzor`` - Zoroastrian - Avestan/Zoroastrian sources 8.2 Sources ^^^^^^^^^^^^^ .. list-table:: :header-rows: 1 :widths: 8 18 54 20 * - Code - Name - Scope - Related views * - ``stor`` - Torah - Five Books of Moses (Genesis--Deuteronomy) - vjud, vchr, visl * - ``sheb`` - Hebrew Bible - Prophets + Writings (non-Torah Tanakh) - vjud, vchr * - ``sgos`` - Gospels - Matthew, Mark, Luke, John - vchr, visl * - ``sapo`` - Apostolic - NT beyond Gospels + earliest Church - vchr * - ``squr`` - Quran - The Quran only - visl * - ``ssan`` - Sanskrit texts - Vedas, Upanishads, Bhagavad Gita - vhin Source-view relationships are many-to-many. The Torah (``stor``) is primary for Judaism but also cited by Christianity and claimed by Islam. 8.3 Language-specific cultural content ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ``l`` + ISO 639-1 code: ``lde`` (German), ``lar`` (Arabic), ``lhe`` (Hebrew), ``lzh`` (Chinese). These are for content that is structurally different because the language itself contributes something untranslatable --- not for straight translations, which use Sphinx i18n (``.po`` files). ---- 9. The PoR fields ==================== Each formal element at the PoR level has 40+ fields. A selection: **Identity and display:** .. list-table:: :header-rows: 1 :widths: 8 22 70 * - # - Field - What it contains * - 1 - ``id`` (BriefName) - Canonical identifier, e.g. ``pet-ax5`` * - 2 - ``title`` (Title) - Full display title, e.g. "ax5 --- Containment" * - 4 - ``sum`` (SummarizingName) - Plain-English statement * - 5 - ``intro`` (ExplanationIntro) - Accessible explanation for general readers * - 6 - ``latex`` (FormalMathLatex) - LaTeX notation, e.g. :math:`W \leq G` **Technical and structural:** Logic used (``logic``), reasoning chain (``twhy``), known limitations (``limit``), upstream dependencies (``needs``), downstream dependents (``feeds``), StayVS maturity code (``stayc``), versioning history (``diff``). **Independent support (per worldview/source):** Each ``v*`` and ``s*`` code from D5 can appear as a PoR field. ``stor`` contains Torah citations with glosses explaining relevance. ``vjud`` synthesizes all Jewish sources into a coherent perspective. **POST operational:** AnyAims (``aa``), FeedbackFlow (``ff``), DesignDoc (``dd``), KnownKillers (``kk``), LabLog (``ll``), VersionedVariant (``vv``), WorkingWheel (``ww``). ---- 10. The extraction matrix ============================ The extraction matrix controls which PoR fields appear at each audience depth and *how* they appear. Keywords: - ``full`` --- field copied verbatim - ``brief`` --- first sentence only - ``top3`` / ``top1`` --- top entries from lists - ``rewrite`` --- rephrased for the audience - ``ref`` --- cross-reference link only - ``stub`` --- heading only, marked ``[stub]`` At ``easy`` depth, a reader sees the identifier, the plain-English summary, and one representative tradition quote. Technical context and operational fields are omitted. At expert depth, all technical fields and all citations appear. At ``dump`` depth, everything appears including operational POST fields. ---- 11. Link stability policy ============================ **Internal links:** RST ``:ref:`` labels are permanent identifiers. They survive file moves. If an element is deprecated, the label stays as a signpost pointing to where the content moved --- like an HTTP 301 redirect. **Deprecated elements:** Content moves to a HistoryHeap page (``pet-ax5-hh``). The original label stays and says "this moved." Deprecated numbers are retired, not recycled. **External links:** For academic papers and permanent references, cite the versioned URL path (``/matheology/vv/oov2/...``). The ``/matheology/`` prefix and model directories (``/matheology/pet/``, ``/matheology/jub/``) are committed as permanent paths. **Periodic recompilation:** At intervals, the entire site is recompiled to ensure all internal links resolve. This is a technical argument for periodic global reconciliation --- accumulated link debt requires periodic reconciliation, just as accumulated economic concentration requires periodic recalibration (ax25). ---- 12. Prose reference convention ================================ .. list-table:: :header-rows: 1 :widths: 12 28 22 38 * - BEST - Context - Format - Example * - Brief - First mention - Model-element - Pet-ax5, Jub-th8 * - Brief - Subsequent - Element only - ax5, th8 * - Explicit - Formal heading - Full with title - Pet-ax5 --- Containment * - Explicit - RST cross-reference - ``:ref:`` - ``:ref:`pet-ax5``` * - Brief - Code/label context - All lowercase - ``pet-ax5`` ---- Cross-references ================== - :ref:`AHA design document (full) ` --- the authoritative technical specification - :ref:`Adversarial stress-test ` --- 29 attacks, 17 HELD, 12 BREACH, known limitations documented - :ref:`Easy overview ` --- if this page has too much detail - :ref:`Technical design ` --- the "why" behind each design decision