================================================================================
COLLABTUNES_OUTPUT_NAMING_RULES_PERMANENT_5_12_26.txt
CollabORhythm / Collabtunes — Operational Infrastructure
Status: ACTIVE_CANON — applies to ALL future Claude sessions on this project
================================================================================

RULE: EVERY output file and ZIP must follow these standards.
This is infrastructure, not preference. Non-negotiable.

================================================================================
SECTION 1 — FILE NAMING FORMULA
================================================================================

FORMAT:
[FILE_COUNT]_[FILE_TYPE]_[PROJECT]_[CATEGORY]_[PURPOSE]_[DATE].ext

REQUIRED ELEMENTS:
1. FILE COUNT     — number of files in ZIP (e.g. 4_TXT_FILES, 11_TXT_FILES)
2. FILE TYPE      — TXT, HTML, ZIP, PDF, MD, MIXED
3. PROJECT        — COLLABTUNES (always include)
4. CATEGORY       — see approved category list below
5. PURPOSE        — brief description of what's inside (2-5 words)
6. DATE           — M_DD_YY or M_DD_26 format

GOOD EXAMPLES:
  4_TXT_FILES_COLLABTUNES_NAV_STABILIZATION_CROSS_REF_URL_REGISTRY_CHAPTER_DRIFT_20_TOM_DECISIONS_5_12_26.zip
  11_TXT_FILES_COLLABTUNES_RATINGS_CANON_BLOCKERS_SUMMARIES_VOL1_VOL2_VOL3_5_12_26.zip
  3_HTML_FILES_COLLABTUNES_FIXED_COLOR_BOUNCER_AIO_GENERATOR_DEMO_5_11_26.zip
  1_TXT_FILE_COLLABTUNES_RATINGS_MASTER_INDEX_VOL4_5_13_26.txt

BAD EXAMPLES (never use):
  final.zip
  final2.zip
  newfinal.zip
  fixed_v2.zip
  realfinalFINAL.zip
  output.txt
  untitled.zip
  export.zip
  copy.zip

================================================================================
SECTION 2 — APPROVED CATEGORY CODES
================================================================================

Use one or more of these in every filename:

LIVE_CAPTURE     = pages/data pulled directly from collabtunes.com
CANON            = source-of-truth content, confirmed and locked
QA               = quality assurance, conflict registries, risk audits
HTML             = HTML prototype or production files
REGISTRY         = master lists, indexes, inventories
DEPLOYMENT       = deploy-ready files or deploy status trackers
BACKUP           = safety copies, rollback files
PLACEHOLDERS     = coming-soon or future pages tracking
RATINGS          = content rating indexes and system files
URL_MAPS         = URL registries, link maps, navigation maps
BLOCKERS         = deploy blockers, issue trackers
NAV_STABILIZATION= navigation cross-reference and cleanup work
TOM_DECISIONS    = items requiring Tom arbitration
MASTER_DUMPS     = session memory / operational handoff docs
GENERATOR        = template files, generator inputs, generator outputs

================================================================================
SECTION 3 — VERSION CONTROL RULES
================================================================================

1. NEVER overwrite a previous version.
   Create a new file with VOL2, VOL3, or a new date instead.

2. ALWAYS increment VOL number when updating a recurring document:
   MASTER_CONTENT_RATINGS_INDEX_VOL1 → VOL2 → VOL3 (never replace VOL1)

3. ALWAYS add date to filename.
   If two files have the same date, add _AM or _PM or a sequence number.

4. ARCHIVE old versions — do not delete.
   Label them clearly: _ARCHIVE or _SUPERSEDED if no longer authoritative.

================================================================================
SECTION 4 — MANIFEST / README REQUIREMENT
================================================================================

EVERY ZIP must include a MANIFEST file that states:

  ZIP NAME          (exact filename)
  PHASE             (which stabilization or build phase)
  CATEGORY          (from approved list above)
  AUTHORITATIVE?    (yes/no + scope)
  CONTAINS          (numbered list of every file + 1-line description each)
  WHAT THIS RESOLVES
  WHAT REMAINS UNRESOLVED
  PRIOR PACKAGES THIS BUILDS ON
  DO NOT OVERWRITE warning

MANIFEST naming:
  MANIFEST_[same name as ZIP without .zip]_5_12_26.txt

================================================================================
SECTION 5 — OUTPUT CATEGORIES FOR THIS PROJECT
================================================================================

When creating outputs, sort them into these buckets:

BUCKET              | CONTENTS
--------------------|-----------------------------------------------------------
LIVE_CAPTURE        | Raw captures from collabtunes.com (HTML, text, link lists)
RATINGS             | Content rating indexes (VOL1, VOL2, VOL3...)
CANON               | Canon source notes, locks, conflict registries
BLOCKERS            | Deploy blockers, issue registries
REGISTRY            | URL maps, page inventories, master lists
NAV_STABILIZATION   | Chapter drift, cross-reference, navigation cleanup
TOM_DECISIONS       | Decision queues, arbitration items
HTML_PROTOTYPES     | Fixed-color HTML files, generator demos, AIO templates
QA                  | QA reports, risk audits, handoff documents
SUMMARIES           | Short findings summaries (one per session)
MANIFESTS           | README / manifest files for each ZIP

================================================================================
SECTION 6 — THIS RULE APPLIES TO ALL FUTURE SESSIONS
================================================================================

When handing off to a new Claude session, include this file in the package.
The new Claude reads it before creating any output.

This file is: ACTIVE_CANON
Do not deprecate. Update with a new VOL number if rules change.
================================================================================
END COLLABTUNES_OUTPUT_NAMING_RULES_PERMANENT_5_12_26.txt
================================================================================
