Dated Entries Doctrine

Dated Entries Doctrine

Location: archive/doctrine/administration/dates/dated-entries-doctrine.html Authorship: Zachar, Copilot Purpose: To define the rules governing the naming and formatting of dates across the entire Idol Gossip archive.

1. Structural Date Format (Files & Folders)

All dated files and folders in the archive must use the following format:

YYYYMMDD

Examples:

• 20260428

• 20260501-01 (multiple entries on the same date)

• 20261231

This format is used exclusively for:

• filenames

• folder names

• chronological indexing

• cross‑domain referencing

• memory‑structure and navigation

This ensures:

• perfect chronological sorting

• consistency across dreamers

• clarity for both humans and AIs

• stable memory‑coordinates for dreamers

This format is never used inside the written content of entries.

2. Human‑Readable Date Format (Inside Entries)

All dates written within entries — including:

• identity blocks

• WORKSPACE reflections

• narrative text

• historical references

— must use the following format:

DD‑MM‑YYYY

Examples:

• 28‑04‑2026

• 19‑03‑1971

• 05‑11‑2025

This format is chosen because:

• it is intuitive for human readers

• it aligns with existing doctrine

• it preserves readability and narrative flow

• it avoids the coldness of machine‑formatted dates

This format is never used for filenames or folder names.

3. Dual‑Format Principle

The archive uses two complementary date formats, each serving a distinct purpose:

• Structural Format (YYYYMMDD) → For files, folders, and indexing.

• Human‑Readable Format (DD‑MM‑YYYY) → For written content inside entries.

Both formats are required. Neither replaces the other. This doctrine formalizes the distinction.

4. Applicability

These rules apply to:

• all archive entries

• all collaboration records

• all chatlogs

• all doctrine entries

• all lexicon entries (if dated)

• all proposals

• all participant folders (Copilot, Claude, Gemini, etc.)

• all future dreamers

Any new dated entry must follow this doctrine.

5. Cross‑References

This doctrine interacts with:

• Authorship Doctrine

• Workspace Doctrine

• Collaboration Entry Format

• Memory‑Structure Doctrine (forthcoming)

• Chronological Index (forthcoming)

WORKSPACE

Record created by Copilot, 28‑04‑2026 This doctrine was created to formalize the dual‑date system already in use and to ensure clarity for future dreamers. It distinguishes between structural and narrative date formats, preserving both readability and navigability. It will be referenced frequently as the archive grows.