Skip to content
FSS Knowledge Base

Ongoing Projects — Dept Projects/ Folder Convention

Section titled “Ongoing Projects — Dept Projects/ Folder Convention”

Date: 2026-07-07 Project/Task: Ongoing-Projects-Folder-Convention (Processes dept) Status: ✅ Complete

Summary

Section titled “Summary”

Gave the 6 registered Ongoing Projects a Core/<Dept>/Projects/ home, parallel to Core/<Dept>/Tasks/ — the folder-level symmetry Talbot wanted for finite vs ongoing work. Also settled a related, broader question raised mid-task: whether the vault should standardize on DASHBOARD.md hubs everywhere or keep the existing Folder Notes (Waypoint) convention — decided combination, not universal, with the boundary now documented.

Decisions

Section titled “Decisions”
  • Repo-backed projects → flat portal note at Core/<Dept>/Projects/<name>.md (state stays in the repo). KB-native projects → full folder moves under Core/<Dept>/Projects/<name>/ (only KB-OS today — it holds real multi-file state, unlike the repo projects’ portal-only folders).
  • Naming: identity over role. Flat notes are named after their own project/repo (ai-config.md, monorepo.md, web-deploy.md, my_backup.md, my_OpenClaw.md) rather than a uniform DASHBOARD.md — this sidesteps the shared-folder naming collision that blocked a prior uniform-naming attempt (KB-OS-portal-rename.md, 2026-07-06), with no further decision needed. My_Backup System.md renamed to my_backup.md for consistency with the others.
  • Folder Note vs DASHBOARD.md — keep both, don’t go universal. Ordinary content folders keep Folder Notes (Waypoint auto-MOC, cheap, ~22 in use vault-wide). DASHBOARD.md is reserved for elevated hubs: vault root, business roots, Ongoing-Project homes, purpose-built dept indexes (e.g. Core/AI/Skills/DASHBOARD.md). Where a folder is both (KB-OS), DASHBOARD.md wins and serves double duty — no separate Folder Note is created. Documented in Folder Notes.md and KB-OS-Usage.md.

Changes

Section titled “Changes”

KB repo (commits 5bfd422, 9cd40db, plus this session’s final doc round):

  • Moved all 6 portals to their new Core/<Dept>/Projects/ homes (git mv, history preserved for 5 tracked files; my_OpenClaw.md was untracked, plain mv + git add)
  • Fixed every inbound reference: SMTM_System.md, Ongoing-Projects.md registry (now at Core/Processes/Projects/KB-OS/Ongoing-Projects.md), JOB_DESCRIPTION.md ×3 (AI/IT/Processes), IT-Director.md, AI.md, Processes.md, Focus-Pages.md, _active.md, plus self-references inside the moved KB-OS folder (STATUS.md, LESSONS.md, Folder Notes.md)
  • Fixed .obsidian/plugins/templater-obsidian/data.json — 6 hardcoded references to the old template path, which would have silently broken “New File” task creation in every dept Tasks/ folder
  • Folder Notes.md — added “Folder Note vs DASHBOARD.md” boundary-rule section; fixed 2 stale references to a non-existent Create Folder Note template name (actual file: Folder Note.md)
  • KB-OS-Usage.md — added the same boundary clarification after “Navigation Entry Points”; fixed a stale Conventions-table line that flatly claimed “Folder Notes + Waypoint removed” (contradicted by 22 live Folder Notes vault-wide; the line predated the current dept-first structure and was never updated)
  • Core/Processes/Projects/KB-OS/DASHBOARD.md — added a one-line cross-reference to the boundary rule
  • Core/Processes/Projects/KB-OS/LESSONS.md — 3 lessons added (git mv staging gotcha, flat-naming pattern, Templater corruption open item)

External repos (4 separate commits, one line each):

  • ai-config/README.md, monorepo/AGENTS.md, web-deploy/AGENTS.md, my_backup/AGENTS.md — KB Note portal path updated

Global rules SSOT:

  • ~/ai-config/AGENTS.md (Skills Quality Standard) — extended the restructure-audit rule to explicitly cover .obsidian/ plugin configs, not just skills/commands

Gotchas

Section titled “Gotchas”
  • git mv doesn’t stage content edits made after the move — several files got moved then had their content fixed; those edits sat unstaged until a follow-up git status sweep caught them. Always re-check git status after a git mv + edit sequence, don’t assume the rename staged everything.
  • Templater corruption (unresolved root cause): Templates/Folder Note.md and Templates/SMTM Task.md were found with their placeholders replaced by literal rendered values, restored via git checkout. Not reproduced — flagged in KB-OS LESSONS.md in case it recurs.
  • Historical dated logs and closed task-conversation history were deliberately left with old path references during the reference sweep — they’re point-in-time records, not live navigation.

Next Steps

Section titled “Next Steps”

None — task closed. Watch for the Templater corruption recurring (see KB-OS LESSONS.md).