Naming and Versioning

Read-only generated mirror. Source: Cold Deep-Ethics Testing of Default A.I.s at commit bce75876e53c. This rendered copy does not replace the archived source record.

Back to the Cold Deep-Ethics Testing of Default A.I.s portal

---

Naming and Versioning

PDF filenames

Use:

YYYY-MM-DD_provider_model_session-state_short-title_vNN.pdf

Example:

2026-09-16_google_gemini_cold-default_deep-ethical-reasoning_v01.pdf

Use lowercase ASCII characters, numbers, hyphens, and underscores. Keep the filename descriptive enough to recognize outside GitHub.

Companion metadata

Give the metadata file the same basename:

2026-09-16_google_gemini_cold-default_deep-ethical-reasoning_v01.md

Corrections

Do not overwrite a published PDF when its contents change materially. Publish v02, retain v01, and create or update a record in CORRECTIONS/ stating:

• what changed;
• why it changed;
• who identified the issue;
• whether the earlier interpretation remains historically useful;
• which version should normally be read first.

Metadata-only corrections that do not alter the PDF may update the companion Markdown file through ordinary Git history.