tgss-mem

Memory #123 CURRENT

Niagara confidentiality sweep — vocabulary patterns Workspace-wide Niagara-reference scrub completed 2026-05-01; canonical replacement phrases for future use; SQLite re-seed pending; what was acceptable to leave **Sweep completed 2026-05-01** following Niagara Development workspace creation. All Niagara identifiers genericized in cross-cutting business files outside `D:/GitHub/niagara-development/`. Documented in detail in `D:/GitHub/niagara-development/OPEN_ITEMS.md` items 8–11. **Why:** The user's directive was "clean up the Niagara reference in our other business files it is not a public project yet." Combined with the README's confidentiality posture (workspace not in public release; only docs inside the project may name the site, Owner, or counterparties), this required scrubbing every cross-cutting document that named Niagara — including LOCAL_ONLY internal docs that could be exported, pasted into outreach, or shared. **How to apply — canonical replacement vocabulary:** - "Niagara pattern" / "Niagara entity-substitution" → **"depositor-engagement pattern"** or **"GCD/GCE entity-substitution pattern"** - `GCD.AGMT.NIAGARA-PHASE1-001` → **`GCD.AGMT.-PHASE1-001`** (doc-code shape) or `GCD.AGMT.[CONFIDENTIAL]-PHASE1-001` - "Niagara Summit" (project name) → **"Flagship Summit"** (in CRM/dossier contexts) or **"flagship North American AI data center"** (in narrative) - "Niagara campus" / "Niagara MicroCity" → **"flagship campus"** / **"North American flagship MicroCity"** - `NIAGARA_SUMMIT` (workstream tag) → **`FLAGSHIP_SUMMIT`** - "GCE.RPT.NIAGARA-SUMMIT-001" (doc-code reference) → **"GCE.RPT.[CONFIDENTIAL]-SUMMIT-001"** (in catalogs) **Acceptable Niagara mentions left alone:** - `D:/GitHub/CLAUDE.md` project menu `[15] niagara` — workspace dispatcher, local-only by design - `microcity/projects/niagara/MOVED.md` — forwarding stub at the old location - `microcity/.git/*` — git internals; resolves on next commit - `microcity/reference/research/Tesla*.md` and `microcity/reference/treaties/*.pdf` — historical references (Tesla's 1897 Niagara Falls speech, Iroquois treaty); different Niagara - `personal-history/*` + `SESSION_CONTINUITY_2026_04_20.md` — Mark's personal Niagara Falls border crossing (Canadian PR Thread 2 evidence); PROTECTED A scope, different Niagara - `lydian-node-specs/CONTINUITY_2026-05-01.md` — one-line session note mentioning the project name itself - `tribernachi-skills/web/extracted/*` — gitignored web extracts per repo CLAUDE.md - `.claude/settings.local.json` — local permission entries **Open follow-up:** - `pria-relate/data/milken-2026/milken_speakers_2026.db` — SQLite preview DB built from `seed_sqlite.py`; the script is now clean but the DB binary still has 89 Niagara strings inside. Re-run the seed script to regenerate. **Surprising finding worth noting:** OPEN_ITEMS.md's original guess at sweep targets (`lydian-currency`, `lydian-framework`, `business-ops`) was wrong — those skills had zero Niagara mentions. The actual surface was the GCD/GCE disambiguation files using `GCD.AGMT.NIAGARA-PHASE1-001` as the canonical example, plus public-bound documents (Lydian Space whitepaper) and the entire Milken outreach prep corpus in pria-relate. Lesson: grep before writing speculative sweep targets. — [project_niagara_confidentiality_sweep.md]

Outgoing Edges

No outgoing edges.

Link to Another Memory