KB-OS Portal Rename — DASHBOARD.md Convention

Date: 2026-07-06 Project/Task: KB-OS-portal-rename (KB-OS ongoing project) Status: ✅ Complete

Summary

Attempted to give all 6 registered Ongoing Projects a consistently-named DASHBOARD.md portal (replacing arbitrarily-named folder notes like KB-OS.md, Monorepo.md). Hit a real naming-collision blocker before executing broadly, resolved it with Talbot, and renamed only the 2 projects with dedicated single-project folders. The other 4 kept descriptive names — later fully solved by the Ongoing-Projects-Folder-Convention task (2026-07-07), which gave every project its own Core/<Dept>/Projects/ folder, removing the collision problem structurally rather than by exception.

Decisions

Rename only where the project has a dedicated single-project folder — web-deploy.md, My_Backup System.md, and my_OpenClaw.md shared Core/IT/Utils/Custom/ (can’t all be DASHBOARD.md), and AI-config.md shared Core/AI/ with the AI dept’s own portal AI.md. Renamed only KB-OS and monorepo, which each had their own folder at the time.
When replacing a stale scratch file, salvage before discarding — KB-OS.md (the old portal) was mostly stale Folder-Note-era content (lorem-ipsum callout demos, an empty “Printing Notes” stub, a broken Waypoint MOC comment), but its Obsidian Bases-plugin syntax gotchas table was genuinely useful and still is — migrated into KB-OS-Usage.md rather than lost in the rename.

Changes (at the time — see note below on later moves)

Core/Processes/KB-OS/KB-OS.md → Core/Processes/KB-OS/DASHBOARD.md — content rewritten, not just renamed
Core/IT/Monorepo/Monorepo.md → Core/IT/Monorepo/DASHBOARD.md — pure rename, content already current
Bases syntax gotchas table migrated from the old KB-OS.md into KB-OS-Usage.md
Fixed 7 inbound references to path-qualified links once DASHBOARD became a non-unique filename: Processes.md, KB-OS/LESSONS.md, IT/JOB_DESCRIPTION.md ×2, IT/Utils/Custom/Focus-Pages.md, Ongoing-Projects.md, _WorkingOn/Tasks/_active.md
Updated the external monorepo repo’s ~/projects/monorepo/AGENTS.md KB-portal path (separate git repo, edited only)
Updated Ongoing-Projects.md registry table + added a footnote explaining why the other 4 projects intentionally kept descriptive names
Verified via grep -rn across the vault + ~/.claude/skills/ + ~/.claude/commands/ — zero remaining bare KB-OS/[Monorepo](/core/it/projects/monorepo/) links

Superseded 2026-07-07: Ongoing-Projects-Folder-Convention moved both KB-OS/DASHBOARD.md and monorepo.md again, into Core/Processes/Projects/KB-OS/DASHBOARD.md and Core/IT/Projects/monorepo.md respectively, as part of giving every Ongoing Project a Core/<Dept>/Projects/ home — the naming-collision exception this task worked around no longer applies, since every project now gets its own folder. This log records the intermediate state, not the current one; see 2026-07-07_Ongoing-Projects-Folder-Convention.md for current paths.

Gotchas

Left web-deploy.md, My_Backup System.md, AI-config.md, and my_OpenClaw.md untouched by design (naming collisions) — my_OpenClaw.md specifically because it was untracked, actively in-progress content, not just a collision.
The naming-collision lesson from this task and the flat-naming resolution are already captured in KB-OS/LESSONS.md (“Flat, project-named notes sidestep naming-collision debates for free,” 2026-07-07) — no new lesson added here to avoid duplication.

Next Steps

None — task closed.