This is the step-by-step plan for reorganizing notion.octaviantocan.com into a Knowledge Base + Dashboard structure. Each phase is designed to be non-destructive — nothing gets deleted, only moved, converted, or linked.

Phase 1 · Inventory & Prep

Before moving anything, we need a full picture of what exists and what matters most.

• [x] Audit all pages under notion.octaviantocan.com and the Home wiki
• [x] Identify orphaned, duplicate, or near-duplicate pages (e.g. Plaud vs. Fireflies versions of the same meeting)
• [x] Flag any "do-not-touch" pages or dashboards you rely on daily
• [x] Agree on naming conventions (e.g. date format for meetings, title casing)
• [ ] Confirm scope — is the Home wiki in scope, or only notion.octaviantocan.com?

✅ Inventory complete → See Phase 1 — Full Inventory & Proposed Destinations

Output: A shared checklist of every page with its proposed destination.

Phase 2 · Build the Bug Database

Convert the flat TwinMind Known Issues page into a proper, filterable database.

• [ ] Create a Bug Tracker database with properties:
  • Title (issue name)
  • Status (select: Needs Investigation, Needs Fix, In Progress, Resolved)
  • Priority (select: Critical, High, Medium, Low)
  • Component (multi-select: Chat, Memory Page, Navbar, BottomSheet, Onboarding, Todo, Audio Player, etc.)
  • Platform (multi-select: Android, iOS, Safari, Mobile Web, Desktop)
  • Date Reported (date)
  • Reported By (person)
• [ ] Migrate each issue from the current page into database entries — preserving all details, attachments, and strikethrough for resolved items
• [ ] Mark resolved/struck-through issues with status "Resolved"
• [ ] Create views: Open Bugs by Component (board), All Bugs (table), Critical & High Priority (filtered table)
• [ ] Add a "Moved from …" note on the original issues page linking to the new database

Output: A fully-populated Bug Tracker database with multiple views.