Jubilee System Example: Naming Convention Coordination#

Origin#

Date: 2026m04d04

Context: During the b14 post-flight cleanup session (see VV-to-HELL Migration — Execution LLog), LLoL identified the PET/JUB axiom renaming as a concrete worked example of why Jubilee System coordination (ax25 — Jubilee Recalibration) is necessary for certain classes of systemic transitions. This llog records that example for future JUB model refinement.

The Example: Why Axiom Naming Cannot Be Changed Gradually#

The PET and JUB axiom systems were developed in the order that research insights arose. The earliest sessions (2026m03d11 onward) used uppercase labels A1 through A25 for axioms and T1 through T11 for theorems. These labels appear extensively throughout dozens of llogs.

However, these labels are not in their final form. The current numbering reflects the historical order of discovery, not the order that would be most natural for a reader encountering the system for the first time. Once sufficient research clarifies the logical dependencies and pedagogical flow, the axioms and theorems should be reordered and given final names that make the system as clear and elegant as possible.

This creates a namespace collision problem:

  • The uppercase A# and T# forms must be reserved for the future final names.

  • But the current transient names (in the same uppercase form) already saturate the historical record.

  • If both the old and new systems use A1, then a reader encountering A1 in a document cannot tell which system it belongs to without checking the date.

The solution adopted on 2026m04d03 was to migrate all historical occurrences to compound form (ax1_A1, th8_T8), where lowercase ax# / th# marks the current transient name and the underscore-linked _A# / _T# suffix preserves the legacy label for traceability. Forward-facing pages use only the brief ax# form. The final A# namespace remains clean for future assignment. See DD b12 for the full design decision.

Why This Is a Jubilee Problem#

Naming conventions are coordination problems. They share a critical property with other systemic standards: they cannot be changed gradually.

Consider driving on the left or right side of the road. A country cannot transition from left-driving to right-driving by having some roads switch first and others later. The transition must happen everywhere at once, or the resulting inconsistency is more dangerous than either system alone.

Naming conventions in a formal system have the same structure:

  • A partial transition — where some documents use old names and others use new names — is worse than either the old system or the new system, because it forces every reader to check which system each document uses before they can interpret any symbol.

  • The transition point must be coordinated: everyone switches at the same time, or nobody does.

  • The old system must remain accessible (in archives) for those who need provenance, but it must not interfere with the new system for those who are learning fresh.

This is precisely the kind of problem that Jubilee System coordination (ax25 — Jubilee Recalibration) is designed to handle:

  1. A clear transition point. The Jubilee provides a socially agreed moment when the old system is cut off and the new system begins.

  2. A bounded commitment. The new names are authoritative for one Jubilee cycle (approximately 50 years). If a ground-breaking discovery during that period reveals a better naming system, the next Jubilee can adopt it without breaking the current generation’s work.

  3. Clean separation for learners. Future generations learn the streamlined system without needing to know the historical idiosyncrasies of how those names arose, why the axioms are in this particular order, or why certain theorems have numbers that seem arbitrary. The legacy forms remain in the historical record for scholars.

  4. Prevention of BABL drift. Without Jubilee-style coordination, a naming system accumulates layers of partial transitions, abbreviations, and exceptions. Each layer forces every new participant to learn the history before they can learn the content. This is a concrete instance of BABL: agents talking past each other because the same symbols mean different things in different contexts.

Generalization#

The axiom naming case is small (25 axioms, 11 theorems), but the pattern scales. Any system that depends on shared conventions — measurement units, calendar systems, legal terminology, software APIs, accounting standards, diplomatic protocols — faces the same coordination problem when the convention needs to change.

Non-Jubilee approaches to this problem include:

  • Gradual deprecation (mark old names as deprecated, hope everyone migrates). This creates an indefinite transition period during which both systems coexist, precisely the ambiguity that makes the old system problematic.

  • Versioning (old-v1, new-v2). This works for software but creates cognitive overhead for humans, who must remember which version context they are in.

  • Ad-hoc switching (change when convenient). This is the BABL default: no coordination, maximum confusion.

A Jubilee-coordinated transition avoids all three failure modes by providing a fixed, socially agreed switching point with clean separation between generations.

Action Items#