Memory #83 CURRENT
Catalog documents in D:/GitHub, not Downloads
Drafts and finished documents live in the relevant project's docs/ subdirectory on the D: drive Git library, not in C:/Users/mark/Downloads/
Catalog all Tribernachi / GCD working documents (drafts, memos, training guides, reports, specs) under `D:/GitHub//docs/` on the D: drive Git library, not under `C:/Users/mark/Downloads/`.
Convention observed across the workspace: every project has a `docs/` subdir (e.g., `conductor/docs`, `super-streamer-solo/docs`, `ttem-platform/docs`, `tribernachi-trust/docs`). Filenames follow the `GCD____V_` pattern (example: `GCD_TRN_SUPERSTREAMER_001_V1_0.docx` in `super-streamer-solo/docs/`).
**Why:** Downloads is ephemeral and un-indexed. The D:/GitHub/ library is version-controlled, searchable by project, and is where the team expects to find reference material.
**How to apply:**
- Pick the project directory whose code or scope the document is about (e.g., a Signal Engine doc → `D:/GitHub/signal-engine/docs/`, a Conductor doc → `D:/GitHub/conductor/docs/`).
- If the target project has no `docs/` dir yet, create it — that matches every other project's convention.
- If the doc spans multiple projects, pick the primary one and mention the location to Mark; do not default to Downloads.
- Received documents (e.g., Joseph's `C:/Users/mark/Downloads/TTEM_Overlay_Anatomy_Explained.20260417.docx`) can stay in Downloads until cataloged; I do not move inbound files without being asked.
- When writing new drafts, save directly to the catalog location from the first Write call — do not stage through Downloads.
— [feedback_document_catalog.md]
| Composite | E08617146AE57E10F |
| Project prime | 13 |
| Domain prime | 4F |
| 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 |