Vault Organisation - Hustle Thoughts

Core Idea

How to keep the Hustle Thoughts vault clean, navigable, and honest as it grows — covering folder structure, inactive project handling, changelog management, and template standardisation.

State of Thinking

The vault has grown to a point where some structural decisions need to be made. The main tension is between keeping things where they were created versus moving them to where they actually belong as thinking matures.

Implementation snapshot question (resolved): When development starts on a project, the question arose of whether to copy and date the current node as a frozen snapshot. The versioning system already handles this — the version: frontmatter and Last updated date together serve as the snapshot. No separate copy needed. Bump the version when the model shifts; the date records when. The AI changelog may need to be split — either by month or every 10 entries — to stay within AI context limits. No decision made yet but worth monitoring as the vault grows.

Inactive projects: A set of projects are not actively being worked on and feel misplaced in the Projects folder:

  • Projects/Games/AI Interactive Story Experience.md
  • Projects/Games/Neopets Successor.md
  • Projects/Websites/Food Recommender.md
  • Projects/Websites/GroundNews Local.md
  • Projects/Websites/Property Analysis Tool.md

The question is where they should live. Resources/Inspiration was suggested but feels slightly off — inspiration is pre-concept, and these files are past concept stage. Moving them may also require restructuring their content to match a new context.

Teacher Dashboard for Games: Projects/Games/Teacher Dashboard for Games.md is unclear as a project — it groups multiple different projects under a shared dashboard concept, but those projects have different needs and presentations. The instinct is to dissolve it and redistribute any still-relevant ideas back into their respective project files.

Files that need review for relevance:

  • Meta/Home - Hustle Thoughts Index.md — needs updating to reflect current state
  • Meta/Idea Evaluation Framework.md — needs reviewing for whether it is still being used
  • Resources/Research/Youth Gaming Trends 2025.md — unclear how relevant this still is
  • Resources/Inspiration/Inspirations.md — unclear what this file actually does

Templates: No boilerplate templates exist yet for projects, inspirations, or other note types. These should live in the Templates folder but have not been created.

Thinking Trace

  • The vault has grown organically and some decisions made early no longer feel right
  • The inactive project question is uncomfortable — these are real ideas but not active work, and Projects feels like the wrong folder for them
  • Teacher Dashboard for Games never felt like a real unified project — it was more of a grouping convenience that has outlived its usefulness
  • The changelog splitting worry comes from a practical concern about AI context windows, not about organisation per se
  • Templates have been missing from the start — every note has been created ad hoc

What changed?

— skip, v1 —

Why it changed?

— skip, v1 —

Evidence / Signals

  • The discomfort with the current structure is itself a signal — when the vault feels messy it stops being used

Open Questions

  • What is the right tier for ideas that are past concept but not actively in development — between Inspiration and Projects?
  • Should the changelog be split by time (monthly) or by volume (every N entries)?
  • What content should a project boilerplate template contain?
  • Is Meta/Idea Evaluation Framework.md still being used or has it been superseded by how triage actually works?
  • What does Resources/Inspiration/Inspirations.md actually contain and is it still needed?
  • After moving inactive projects, do their internal structures need to change to reflect their new context?

Connections


Changelog

  • v1 — Initial node