richardk/iso27diy-corp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
iso27diy-corp/Corpus/Sparks folder cleanup suggestions.md
Richard Kranendonk edf18ed518 Notes added
2026-05-11 23:57:58 +02:00

2.4 KiB
Raw Blame History

Sparks folder cleanup suggestions

The core problem

The Sparks folder is a landing zone that was never cleaned up. It has at least four distinct categories mixed together:

  1. ISO 27001/27002 content — notes that belong in the Corpus proper, tagged with isotags and a notetype
  2. Platform/product notes — ISO27DIY-specific stuff (blurbs, prompts, design docs, partner lists)
  3. Tooling/dev notes — Supabase, Rasa, LLM prompts, Bolt.new, Git, etc.
  4. Clutter/stubs — single-link notes, raw dumps, files that are clearly just placeholders

Several notes also have zero frontmatter at all.

Suggested steps

Step 1: Triage first, don't reorganize yet

Before moving anything, do a first pass and tag each note with a simple status value in the frontmatter. I'd suggest three values: promote (ready or near-ready to move into the Corpus), develop (has substance but needs work), and archive (not ISO content, or irrelevant). This can be done quickly because most notes make it obvious within 10 seconds which bucket they're in.

Step 2: Separate non-ISO content

Notes like Bolt.new prompt.md, Blurbs.md, Rules to get better code.md, SurveyJS.md, slot_config_schema.sql etc. have no place in an ISO 27001 corpus. Move them to a iso27diy-corp/Product or iso27diy-corp/Dev folder. Don't delete anything yet.

Step 3: Add frontmatter to promote candidates

For notes that are ready to move, add the required frontmatter: notetype, language, status: active, and isotags. The _Corpus-metadata.md gives you everything you need. Start with the most mature notes — Shadow IT risks, Ransomware, Risk management, Access Control are obvious candidates.

Step 4: Move promoted notes to the right Corpus location

Once frontmatter is in place, move them to the appropriate subfolder in Corpus (MoCs, Literature notes, etc. depending on notetype). Notes without a clear home yet stay in Sparks until you know where they belong.

Step 5: Deal with stubs last

Notes like Awareness.md (single wikilink, nothing else) and Governance.md (three links, no content) are either index notes waiting to grow, or orphans. Decide then: expand them or merge them into a MoC.

The subfolders About iso27diy, C4 model for software development, Context, Strategy, and Leadership, and ISMS probably need the same triage treatment — want me to check what's in those too before you start?