Memory #85 CURRENT
Filename Convention — underscores on disk, dots in citations Specification files in lydian-node-specs/ (and new GCD/TTI/APP specs) use underscores in filenames, dots in document codes; rule codified in TTI.ARCH.LYDIAN-STACK-001 V2.2 §2.8 **Rule adopted 2026-04-23.** - **Document code** (used in citations, `Related:` refs, Appendix A spec catalogues, prose): `TTI.ARCH.LYDIAN-STACK-001-V2.2` — dot separators - **Filename on disk** (filesystem, git, builder scripts): `TTI_ARCH_LYDIAN-STACK-001_V2_2.md` — underscore separators; internal dashes within DOMAIN field retained **Why:** Dots in filenames collide with file extensions on many tools (shell completion, web servers, some archivers) and produce ambiguous parsing when combined with `.md` / `.docx` / `.pdf` extensions. Document codes read naturally in prose with dots. **How to apply:** - When generating new spec files, name them with underscores: `TTI_ARCH_NAME-NNN_V{M}_{m}.md`. - When citing specs inside documents, use dot form: `TTI.ARCH.NAME-NNN V{M}.{m}`. - When renaming a legacy dot-form file during revision, convert to underscore form at that point. - Formal rule + worked-example table is in umbrella V2.2 §2.8. - Delta subdirectory is `TTI_ARCH_LYDIAN-STACK-001_deltas/` (underscore), with files `V{x}_{y}.md` inside. **Scope:** Applies to `D:/GitHub/lydian-node-specs/` and to any new GCD/TTI/APP/TRIB spec files going forward. Legacy dot-form filenames in other repos remain until their next revision. — [feedback_filename_convention.md]
| Composite | FCF1CC3AA654CC2F3 |
| Project prime | 13 |
| Domain prime | 59 |
| Type prime | 61 |
| Importance | 1.000000 (CRITICAL) |
| Decay epoch | 0 |
| Created | 2026-05-04 15:46:49 |
| Valid from | (unset) |
| Valid to | NULL — still believed true |
Outgoing Edges
No outgoing edges.