Skip to content
SDC Knowledge Base

sdc-strategy-duplicate-pairs-reconcile

SDC/MBR 20 Duplicate-Name Strategy Pairs — Reconcile

Section titled “SDC/MBR 20 Duplicate-Name Strategy Pairs — Reconcile”

Background

Section titled “Background”

Spun out from sdc-dept-scaffold-mbr-absorb Phase 4 (2026-08-28) so the parent dept-scaffold task can close without this open-ended, Talbot-only judgement work blocking it. MBR/Strategy/ and SDC/Strategy/ hold 20 files with identical names — one home per pair is the goal (SSOT: one home, zero duplicates), decided by Talbot, not Claude.

Full context and the checklist: Core/Processes/Projects/KB-OS/Tasks/KB-OS-re-focus-sdc.md §4b.

Tasks

Section titled “Tasks”

For each pair below, decide: SDC’s version wins, MBR’s wins, or the two merge. Several are yours alone to call (Strategic Plan, Mission, Vision, the whole Internal View/ set — largely personal, not business-specific).

  • Core Value Propositions.md
  • Ideal Client Profile.md
  • Key Success Factors.md
  • Strategic Plan.md — name collision resolved 2026-09-06 by Brainstorm-upgrade-CC: SDC’s is now SDC/Strategy/Strategic-Plan.md (v2.0, rewritten), MBR’s keeps MBR/Strategy/Strategic Plan.md. Two distinct filenames, so no ambiguous-wikilink risk remains. Still open for Talbot: whether the two documents should also be merged in content, or stay as separate per-business plans (the rename settled the filename, not the content question).
  • Strategy.md
  • Unique Selling Proposition.md
  • ROADMAP.md
  • Opportunities/Opportunities.md
  • Identity/01_Identity.md
  • Identity/Mission.md
  • Identity/Vision.md
  • Identity/Internal View/* (8 files)

Progress Acceleration.md is already done — Claude owned that one pair per the parent task; not part of this checklist.

Success Criteria

Section titled “Success Criteria”
  • Every one of the 20 pairs has exactly one home (SSOT).
  • Every bare FileName-style wikilink to a resolved pair is path-prefixed or otherwise unambiguous — run the wikilink-sweep step from sdc-dept-scaffold-mbr-absorb Phase 3 over whatever changes.

Notes

Section titled “Notes”
  • No rush — do this “when an appropriate priority/rock” (Talbot, 2026-08-28). focus: 3_later reflects that; re-prioritize freely.

Context (Auto-Prepared) — 2026-08-28

Section titled “Context (Auto-Prepared) — 2026-08-28”

Resolved File Paths

Section titled “Resolved File Paths”
  • Core/Processes/Projects/KB-OS/Tasks/KB-OS-re-focus-sdc.md → /mnt/d/FSS/KB/Core/Processes/Projects/KB-OS/Tasks/KB-OS-re-focus-sdc.md (verified: exists — §4b has the full pair list + rationale)
  • MBR/Strategy/ and SDC/Strategy/ → both verified: exist, each holding one file per pair

KB Context

Section titled “KB Context”
  • The 20 pairs (from KB-OS-re-focus-sdc.md §4b, quoted in full in this task’s Tasks section): Core Value Propositions.md, Ideal Client Profile.md, Key Success Factors.md, Strategic Plan.md, Strategy.md, Unique Selling Proposition.md, Progress Acceleration.md (done, excluded), ROADMAP.md, Opportunities/Opportunities.md, Identity/{01_Identity, Mission, Vision}.md, all 8 of Identity/Internal View/*.
  • Why this is Talbot’s call, not Claude’s: several pairs (Strategic Plan, Mission, Vision, Internal View/*) mix personal and business content in ways only Talbot can judge — this was the explicit reasoning in the parent task (sdc-dept-scaffold-mbr-absorb) for not delegating them.
  • Wikilink risk, not optional: per global AGENTS.md, wikilink resolution is “first occurrence wins” by filesystem walk — every bare [Key Success Factors](/strategy/key-success-factors/)-style link currently resolves non-deterministically across these 20 pairs. Resolving a pair without then sweeping its bare links leaves the ambiguity in place even after the content decision is made.
  • sdc-dept-scaffold-mbr-absorb’s Phase 3 already demonstrates the sweep pattern for 3 other pairs (CEO.md, Filter+Focus.md, Progress Acceleration.md) — same mechanism applies here: grep -rn "\[\[<FileName>\]\]" across the vault, path-prefix each hit to whichever home won.

Dependencies

Section titled “Dependencies”
  • Prerequisite status: all clear (none listed)
  • External systems needed: none
  • Files that must exist before execution: none beyond the 20 pairs themselves (all verified present)

Execution Notes

Section titled “Execution Notes”
  • Model recommendation: none needed — this is Talbot’s own manual review/decision work, not agent-executed. If Talbot later hands the mechanical part (the wikilink sweep after his decisions) to an agent, Sonnet is sufficient — matches the pattern used for the parent task’s own sweep.
  • Assignee: talbot
  • Key constraints: SSOT rule (AGENTS.md) — one home, zero duplicates, no exceptions. Never merge/delete a pair without Talbot’s explicit decision recorded first.