Skip to content

First run — no prior report to trend against.

CheckVerdictWorst findingSince last audit
Routing integrity🟢 GREEN—first run
Wikilinks🟡 YELLOW (was 🔴)2 active-impact links fixed same-day — stub files created, content still needs Talbot’s confirmfirst run
Ambiguous filenames🟡 YELLOW34 basenames exist in 2+ locations, all with bare (non-path-prefixed) links somewherefirst run
Tasks/Logs hygiene🟡 YELLOW1 orphaned status: complete task file not archivedfirst run
Folder notes🟢 GREENnone — JOB_DESCRIPTION.md confirmed as the valid folder-note substitute for business deptsfirst run
Root hygiene🟡 YELLOW1 loose file at vault rootfirst run
.obsidian config🟢 GREENnonefirst run
Section titled “Wikilinks — 🟡 YELLOW, was 🔴 RED (2 active-impact fixed same-day, ~55 historical remain)”

Active-impact — fixed 2026-07-27: Core/_WorkingOn/Tasks/_active.md listed these as currently open work, but the task files didn’t exist anywhere in the vault. Both links now resolve — recreated as stub task files (Core/_WorkingOn/Tasks/) seeding in the one line of known content from _active.md, since neither file had any recoverable history (mBR-brand-text-tweak never existed on disk per git log; web-deploy-issues existed and was closed 2026-06-26, but that closure’s content doesn’t cleanly match the current _active.md description — flagged as ambiguous rather than guessed). Real content is still missing — both stubs ask Talbot to confirm/fill in.

LinkReferenced inIssue
[mBR-brand-text-tweak](/core/_workingon/tasks/mbr-brand-text-tweak/)_active.md line 8”plan written; awaiting Talbot approval” — file missing
[web-deploy-issues](/core/_workingon/tasks/web-deploy-issues/)_active.md line 9”all three issues fixed; awaiting Talbot’s deploy” — file missing

Either the task files were deleted/renamed without updating _active.md, or work described there was never captured as a file. Following _active.md today, /task-continue would fail to locate both.

Historical dangling links (low severity — closed work, informational): ~10 links to task files that were intentionally deleted on completion (SMTM’s “remove” disposition per /task-complete) but left a dangling reference behind in a log/STATUS.md that predates the deletion: KB-OS-resume-rate-limit, ai-config-rules-upgrade, graphify-fullvault-rerun, idea-capture-workflow, Maximizer-Twenty-CRM-Migration, my_backup-kopia-cache-relocation, SMTM-v5.2-Ongoing-Projects. Not urgent — the linking documents are themselves historical logs.

Legacy file Core/_WorkingOn/Tasks/Tasks.md: a pre-SMTM master task index, source of ~15 of the remaining broken links (Business-OS-Architecture*, Tasks-Template, Template-changes, monorepo-project-mess, monorepo-review, KB-OS-Architecture, my_backup-Issues, web-deploy-issues, _DASHBOARD, Focus-BrandText, Focus-Tooltip). Looks superseded by the current _active.md/DASHBOARD.md system — worth confirming it’s safe to archive rather than fixing each link individually.

Template placeholder text (not real findings): Core/Processes/Projects/KB-OS/Templates/Folder Note.md and similar templates contain literal placeholder bracket text (Page, link, Most important file in this folder, etc.) that the wikilink scan naturally flags — these are template scaffolding, not broken links. Excluded from the count above; the check should skip Templates/ going forward (noted for the skill itself, not fixed this run).

Full missing-target list (57 lines) available in scratch if needed — not reproduced here in full to keep the report readable; ask if you want it.

34 basenames exist in 2+ vault locations (mostly expected: every dept/project has its own STATUS.md, ROADMAP.md, Strategy.md, etc.), and all 34 have at least one bare name link somewhere pointing at them — the same “first-occurrence-wins” resolution risk already known for Focus.md (documented in Memory, already fixed at point of use with path-prefixing). This is systemic rather than a single bug: too many instances to triage individually this run. Recommend a future pass (or a /skills-dashboard-style batch tool) that path-prefixes every bare link to a duplicate basename, rather than fixing one at a time.

FileIssue
Core/_WorkingOn/Tasks/2026-05-14_Monorepo-Review-Report.mdstatus: complete frontmatter, still sitting in a live Tasks/ folder (not archive/)

The other 4 grep hits (DASHBOARD.md ×2, Tasks.md, _active.md) are false positives — those are index/tracker files whose frontmatter happens to include status: complete for unrelated reasons, not orphaned SMTM tasks. Worth tightening this check’s grep to exclude known index filenames next run.

FileIssue
HST-Process.mdLoose .md file at vault root — not in any <Biz>/<Dept>/ structure

Folder notes, Routing integrity, .obsidian config — 🟢 GREEN

Section titled “Folder notes, Routing integrity, .obsidian config — 🟢 GREEN”
  • All 10 concrete paths referenced by CLAUDE.md/AGENTS.md resolve (JOB_DESCRIPTION.md ×5, CONSTITUTION.md, KB-OS-Context.md, both Focus.md files, templater data.json).
  • Every active business dept without a literal DASHBOARD.md (Core/IT, MBR/IT, MBR/Mktg, MBR/Risks) has JOB_DESCRIPTION.md at its root instead — confirmed as the intentional convention, not a gap.
  • Single live .obsidian/ config at vault root; no stale duplicate reappeared.

None — this run didn’t touch any skill files.

  • Batch A: Resolve mBR-brand-text-tweak and web-deploy-issues — ✅ done 2026-07-27, both recreated as stub task files pending Talbot’s content confirmation.
  • Batch B: Archive or delete Core/_WorkingOn/Tasks/2026-05-14_Monorepo-Review-Report.md (it’s a completed report, not an open task). Decide Core/_WorkingOn/Tasks/Tasks.md’s fate (archive vs. keep) — it’s the source of most historical broken links. Give HST-Process.md a real home.
  • Batch C (durability): Tighten this skill itself next run: exclude Templates/ from the wikilink scan, exclude known index files from the Tasks/Logs hygiene grep, and accept JOB_DESCRIPTION.md explicitly as a folder-note substitute in Step 5’s wording (currently passes only because of my manual read, not the documented check logic).