Entry Naming Doctrine

1. Purpose

The Entry Naming Doctrine defines how slugs are formed for all entries in the Archive. Slugs appear in filenames, folder names, and cross-references. This doctrine ensures consistency, clarity, and long-term navigability across all domains.

This doctrine governs the naming portion of filenames. Structural dates are governed separately by the Structural Dates Doctrine.

2. Slug format

All slugs must follow these rules:

• Lowercase only: no capital letters.
• Hyphenated words: multi-word subjects must use hyphens (e.g., snatching-frame).
• No spaces: spaces are never permitted.
• No underscores: underscores are reserved exclusively for separating the date from the slug.
• Descriptive: the slug must reflect the content of the entry.
• Stable: once chosen, a slug should not change unless the entry is renamed.

3. Multi-word subjects

Multi-word concepts must be hyphenated:

• concept-incubator
• excision-plate
• dreaming-archive

Hyphens create a single semantic unit and ensure compatibility with all indexing systems.

4. Disambiguation

When two entries would otherwise share the same slug:

• Add a clarifying term (e.g., snatching-frame-design vs snatching-frame-analysis).
• Or use optional numbering only when the entries are part of a series.

Disambiguation must be semantic, not arbitrary.

5. Numbering rules

Numbering is used only when multiple entries share:

• the same date, and
• the same slug.

Numbering begins at -02:

20260502_entry-name-02.html
20260502_entry-name-03.html

Numbering is never used for conceptual disambiguation; only for multiple entries created on the same day.

6. Prohibitions

• No capital letters.
• No spaces.
• No underscores inside slugs.
• No camelCase or PascalCase.
• No punctuation other than hyphens.
• No emojis or symbolic characters.

7. Rationale

The slug system exists to:

• Ensure consistency across all domains.
• Support long-term indexing and searchability.
• Prevent naming drift as the Archive expands.
• Maintain clarity in cross-references.
• Enable predictable filenames for both humans and AIs.

8. Cross-references

This doctrine works in tandem with:

• Structural Dates Doctrine (date prefix rules).
• File Naming Doctrine (full filename structure).
• Authorship Doctrine (identity block consistency).
• Concept Entry Doctrine (concept naming conventions).

Workspace

Record created by: Copilot

Date: 02-05-2026

This doctrine formalizes the slug and naming rules that were previously implicit or scattered across earlier entries. It pairs with the Structural Dates Doctrine to form the complete filename system. No prior doctrine is retired by this document.

12-05-2025
Zachar Laskewicz
Use:

YYYYMMDD_01_conceptA
YYYYMMDD_02_conceptB

Example:
20260305_01_dudit
20260305_02_perfeck
Case B — Unrelated Concepts (same date, different clusters)

Use:

YYYYMMDD_conceptA_01
YYYYMMDD_conceptB_02

Example:
20260305_calculator-poltergeist_01
20260305_tentacle-doctrine_02