Mbr Cleanup

MBR Project-cleanup

Date: 2026AP05

Background

MyBetterRates has quickly gone from exploring a possible business idea into many rounds of brainstorming and scattered ideas forming the basis of a business development plan.
This entire knowledge base was created to manage this new business, sharing some structure with my initial business KB, focused on the $MART DEBT Coach Mission. See d:\FSS\KB\_shared\README.md
Multiple rounds of brainstorming have occurred in a partially organized way resulting in stale files, with no clear structure on single sources of truth, and no clear guidance on what tasks to focus on next.
- D:\FSS\KB\MBR\_WorkingOn\Brainstorming
- D:\FSS\KB\MBR\_WorkingOn\Tasks
- D:\FSS\KB\MBR\_WorkingOn\Projects
- see also D:\FSS\KB\MBR\_WorkingOn\Tasks\_active.md
To prevent making a bigger mess to unravel later, many more of my brainstorming ideas are in Dynalist (my ideas capture tool), not yet shared with CC for feedback and subsequent upgrades, and thus not in this KB at all.

Tasks

The short-term goal is to create a new SMTM project entitled MBR-Business-Dev to manage the development of this new business at all levels.
For that can happen, we need to clean up and organize the knowledge base structure to properly reflect all existing KB content, and update stale files, WITHOUT LOSING ANY IDEAS.
- Some ideas have undergone naming upgrades (eg. Promo Partner Program is now WealthCare50Alliance).
- Review all knowledge base content, noting the date and time stamps on each file, and create a cleaned up and structured content with a single source of truth for each file.
  - How can we do this in a way that allows confidence that no ideas are left behind, including a check of the current system versus new and cleaned up? One approach is to create a clone of this KB, so both Claude and Talbot will be able to compare more easily.

Claude Response — 2026-04-05

Summary

Audited all MBR KB content (24 files across Brainstorming/, Tasks/, Projects/, main KB)
Created Tasks/archive/ — moved 6 superseded concept docs
Created Brainstorming/archive/ — moved all 9 raw brainstorming files + Gemini.md
Filled 6 empty skeleton stubs in main KB (Mission, Vision, Core Value Propositions, Key Success Factors, USP, Ideal Client Profile) — all drawn from existing mature docs
Created Projects/MBR-Business-Dev/ with STATUS.md, PLAN.md, TASKS.md
Updated Tasks/_active.md — added MBR-Business-Dev project link

What Was Done

Archive approach (vs. clone): Git history provides the full safety net — every archived file is recoverable. Archive folders (not deletion) allow visual comparison directly in Obsidian.

Naming alignment: All new files use confirmed naming: WealthCare 50 Alliance, Cancer 50 Pledge, F.A.S.T., The Money Minute, Guaranteed Benefit. Legacy files in archive still use “Promo Partner Program” — acceptable since they’re archived reference material.

Main KB stubs filled from SSoT docs:

Mission + Vision ← Executive-Summary.md + Strategic Plan.md
Core Value Propositions ← Executive-Summary.md (five moats section)
Key Success Factors ← Filter+Focus.md + Strategic Plan.md
Unique Selling Proposition ← Brand_What_Why.md + Executive-Summary.md
Ideal Client Profile ← Strategic Plan.md + Executive-Summary.md

MBR-Business-Dev project seeded from:

STATUS.md: current phase + Phase B priority list
PLAN.md: A→B→Z framework with all phases
TASKS.md: prioritized checklist from Filter+Focus.md rocks + Rate-Scanner Phase B next steps

Next Steps for Talbot

Review TASKS.md in MBR-Business-Dev — correct priorities, add anything missing from Dynalist
1. Very good clean up. Now I need to carefully review everything to absorb, incubate, and ensure no good ideas are left behind (eg. I think that the first paid tier service is better named “No hassle, benefit guaranteed”, and I see that the “no hassle” part has been dropped.
Confirm three open naming decisions captured in TASKS.md (Education Tools name, WealthCare 50 final name, Dynalist review timing)
1. WealthCare 50 Alliance might be upgraded more. Dynalist ideas added soon.

Talbot Response

It appears you have created some of the scaffolding that is done with a project-start skill. Do we not need to initiate /project-start D:\FSS\KB\MBR\_WorkingOn\Projects\MBR-Business-Dev?
- I see no ROADMAP.md, which should be linked to in D:\FSS\KB\MBR\00_KB Home
Explicitly fine open naming tasks, as I am not clear on the third one.
- Additionally, which are compound names without spaces? eg. WealthCare50Alliance vs “WealthCare 50 Alliance”
- Should we address these in a separate task for clear separation of concerns?
I want to provide upgrades to the origin story which is foundational. Best to put this in a new separate task as well?

Claude Response — 2026-04-05

Summary

Created Projects/MBR-Business-Dev/ROADMAP.md (the missing scaffolding piece)
Updated 00_KB Home/ROADMAP.md — ticked completed items (Mission, Vision, ICP, USP, all stubs), added link to MBR-Business-Dev project, added Vision/Mission/Positioning content
Answered all questions from Talbot Response (see below)

Answers to Talbot’s Questions

On project-start scaffolding: The manual creation from the previous session was functionally equivalent to /project-start. The only missing piece was ROADMAP.md in the project folder — now created. The /project-start skill would also have created it; we just skipped that by doing it manually. No need to re-run project-start; the scaffold is now complete (STATUS.md, PLAN.md, TASKS.md, ROADMAP.md).

On naming format — spaces vs. compound: Per Filter+Focus.md naming decisions (confirmed 2026-04-02):

Text/prose: spaces — “WealthCare 50 Alliance”, “Cancer 50 Pledge”, “The Money Minute”, “Guaranteed Benefit”
Domains: no spaces, merged — Cancer50Pledge.ca, mybetterrates.com
Rule: ProperCase with spaces in text; merged (no spaces, no hyphens) only for domain names
“WealthCare50Alliance” (no spaces) would be the domain form; “WealthCare 50 Alliance” is the text form

On the three open naming decisions (clarified): The third one (“Dynalist ideas timing”) was misplaced as a “naming decision” — it’s a project management action. The actual open naming decisions are:

#	Decision	Current	Issue
1	Tier 2 service name	”Guaranteed Benefit” (in Filter+Focus.md)	Talbot prefers “No Hassle, Benefit Guaranteed” — note different word order from original “No Hassle, Guaranteed Benefit”
2	Education/Analysis Tools	No brand name yet	Needs a name for the wealth acceleration education component
3	WealthCare 50 Alliance	Confirmed in Filter+Focus.md 2026-04-02	Talbot notes it may be upgraded further

On separate tasks for naming + origin story: Yes — agreed. Separation of concerns applies here. Recommend:

Tasks/2026-04-05_MBR-Naming-Decisions.md — covers all three naming items above, in one focused session
Tasks/2026-04-05_MBR-Origin-Story.md — Talbot provides upgrades to the origin story; Claude refines and propagates to Executive-Summary.md and any other relevant files

On “No Hassle” being dropped: You’re right — in the process of drawing from Executive-Summary.md (which shortened it to “Guaranteed Benefit”), the “No Hassle” element was lost. This should be resolved in the naming task. In the meantime, the USP.md and other files I wrote use “Guaranteed Benefit” — the correct update will flow through once the naming decision is made.

Next Steps for Talbot

Confirm: create Tasks/2026-04-05_MBR-Naming-Decisions.md as a new task (Tier 2 name, Education Tools name, WealthCare 50 Alliance final form)? 1.
Confirm: create Tasks/2026-04-05_MBR-Origin-Story.md for origin story upgrades? 1.
Review Projects/MBR-Business-Dev/ROADMAP.md and 00_KB Home/ROADMAP.md — any corrections needed? 1.
When ready to close this cleanup task, run /task-complete mbr-cleanup 1.

Talbot Response

need to cleanup/finish
- D:\FSS\KB\MBR_WorkingOn\Tasks\MBR-Upgrades-CC.md