Reference
File Naming Convention
A standardised naming pattern for AI disclosure materials and evidence documents. Consistent naming makes files easy to identify, sort, and verify.
This reference guide is for process documentation only. It does not constitute legal advice.
Loading PDF preview...
Template Content Preview
Below is the full text of the template for quick reference. Use the PDF above for the formatted version.
Preview — File Naming Convention Reference
File Naming Convention
AI Evidence Disclosure Standard v1 — Reference Guide
Pattern
[type]-[description]-[YYYY-MM-DD]-[version].[ext]
Components
| Component | Description | Allowed Values |
|---|---|---|
| type | Document category | disclosure, log, source, output, checklist |
| description | Brief, hyphenated content description | Lowercase, no spaces or underscores |
| YYYY-MM-DD | Date (ISO 8601) | e.g., 2025-03-15 |
| version | Revision number | v1, v2, v3 ... |
| ext | File extension | pdf, csv, txt, docx, png |
Examples
disclosure-statement-2025-03-15-v1.pdfFirst version of disclosure statement
log-evidence-interactions-2025-03-15-v1.csvEvidence interaction log
source-medical-report-original-2025-03-10-v1.pdfOriginal medical report
output-chatgpt-claim-summary-2025-03-14-v1.txtRaw ChatGPT output
checklist-integrity-2025-03-15-v1.pdfCompleted integrity checklist
output-claude-chronology-draft-2025-03-13-v2.txtSecond revision of Claude output
Rules
- Use lowercase for all file names — no capitals.
- Use hyphens to separate words — no spaces or underscores.
- Always include the date in YYYY-MM-DD format.
- Always include a version number, even for the first version (v1).
- Use standard file extensions (.pdf, .csv, .txt, .docx, .png).
- Keep descriptions brief but specific — enough to identify content without opening the file.
- Never rename files after submission — create a new version instead.
What this reference covers
- Standardised naming pattern for all disclosure files
- Component breakdown (type, description, date, version)
- Allowed file type prefixes and extensions
- Real-world naming examples for common documents
- Rules for versioning and preventing file name conflicts
How to use
- Apply the naming pattern to every file in your disclosure pack
- Use the correct type prefix (disclosure, log, source, output, checklist)
- Always include the date in YYYY-MM-DD format
- Start every file at version v1 and increment for revisions
- Never rename files after submission — create new versions instead
Get the full standard
This naming convention is part of the AI Evidence Disclosure Standard v1. View the complete standard or request a disclosure pack.
This platform provides process documentation tools only. It does not provide legal advice, is not a substitute for professional legal counsel, and does not certify the truth or accuracy of any information disclosed. All outputs are for documentation purposes only.