Skip to content

Drift between _WorkingOn/CLAUDE.md and Talbot’s actual SMTM conventions has caused misunderstandings more than once. This task corrects the doc so future AI sessions see Talbot’s real conventions, not the stale ones.

Discovered during the 2026-05-03 cycle of Business-OS-Architecture.md. Talbot explicitly approved fixing this in a separate task.

Fix the following drifts in D:\FSS\KB\Business\_WorkingOn\CLAUDE.md:

  1. Task naming convention — current doc says substantive tasks use Tasks/YYYY-MM-DD_Task-Name.md. Talbot’s actual convention is no date prefix (Tasks/Task-Name.md). The Tasks-Template.md SSoT already says “no date prefix” (line 8) — CLAUDE.md should match.

  2. _tmp.md description — current doc treats _tmp.md as a quick-task funnel. Talbot’s clarification: _tmp.md is for temporary tasks not important enough to get a name — i.e., low-priority scratch work, not a primary funnel. Adjust language so the role is clear.

  3. Frontmatter on Tasks-Template.md — the template file’s own frontmatter currently has title: Tasks-Template. Any task copied from this template inherits that title field, which then needs manual fixing (this exact bug occurred on Business-OS-Architecture.md). Either:

    • Use a placeholder title: [Task Name] in the template’s outer frontmatter (matching the inner-fenced example), or
    • Add a one-line note above the fenced template reminding users to update title after copy.
  4. Cross-check — read D:\FSS\KB\Business\03_Processes\Simple Markdown Task Management\SMTM_System.md for any other date-prefix references; reconcile.

  5. Same checks for the MBR vaultD:\FSS\KB\MBR\_WorkingOn\CLAUDE.md likely has the same drift; fix if present.

  • After this task, a fresh Claude session reading either CLAUDE.md will not produce date-prefixed task names by default.
  • Tasks-Template.md frontmatter no longer carries a misleading title: Tasks-Template value into copies.
  • No _tmp.md confusion: a fresh session understands it as low-priority scratch, not a primary funnel.