renamed some files

This commit is contained in:
Richard Kranendonk 2026-06-01 22:40:30 +02:00
parent 5906aa163f
commit 01ed8705ce
6 changed files with 7 additions and 6 deletions

View file

@ -17,7 +17,7 @@ See [PROJECT - Five Agents](PROJECT%20-%20Five%20Agents.md) for role description
- Create a single short Corpus Index Note with a list of all overview notes, with a one-line description of what they cover. - Create a single short Corpus Index Note with a list of all overview notes, with a one-line description of what they cover.
- Upload the Corpus Index Note and all Overview Notes to each agent Project. Claude will read the ones it needs and ignore the rest. - Upload the Corpus Index Note and all Overview Notes to each agent Project. Claude will read the ones it needs and ignore the rest.
See [Corpus overview notes](../metadata/Corpus%20overview%20notes.md). See [creating-corpus-overview-notes](../metadata/creating-corpus-overview-notes.md).
**3. Prepare and maintain a log** **3. Prepare and maintain a log**

View file

@ -1,7 +1,7 @@
# Corpus Metadata # Corpus Metadata
- All notes in this Obsidian vault need metadata. - All notes in this Obsidian vault need metadata.
- These metadata need to follow the [Obsidian Front Matter Syntax](Obsidian%20Front%20Matter%20Syntax.md). - These metadata need to follow the [obsidian-front-matter-syntax](obsidian-front-matter-syntax.md).
- Obsidian calls metadata variables 'Properties' - Obsidian calls metadata variables 'Properties'
- In this Corpus we use General properties (every note should have them) and Specific properties (depending on the kind of note, can be inferred from other properties) - In this Corpus we use General properties (every note should have them) and Specific properties (depending on the kind of note, can be inferred from other properties)
@ -33,5 +33,5 @@ For example, a note that needs to be linked to ISO 27001 clause 5.2 Policy, will
- These notes are tagged with “sourcetext”. - These notes are tagged with “sourcetext”.
- The body of these notes must never be changed! - The body of these notes must never be changed!
- Specific properties for ISO 27002 OST notes are deduced from chapter 4 of the standard ("Themes and Attributes"). They are: `theme`, `control_type`, `information_security_properties`, `cybersecurity_concepts`, `operational_capabilities`, and `security_domains`. - Specific properties for ISO 27002 OST notes are deduced from chapter 4 of the standard ("Themes and Attributes"). They are: `theme`, `control_type`, `information_security_properties`, `cybersecurity_concepts`, `operational_capabilities`, and `security_domains`.
- For the possible values of these properties, see [Metadata - ISO 27002 Themes and Attributes](Metadata%20-%20ISO%2027002%20Themes%20and%20Attributes.md). - For the possible values of these properties, see [themes-and-attributes-in-iso-27002](themes-and-attributes-in-iso-27002.md).

View file

@ -1,4 +1,5 @@
# Create corpus overview notes # Creating corpus overview notes
Here's a prompt you can use. Run it once per note or cluster of notes, feeding Claude the content each time. Here's a prompt you can use. Run it once per note or cluster of notes, feeding Claude the content each time.
--- ---

View file

@ -1,4 +1,4 @@
# Front matter for marketing posts # Front matter for publications
From [claude chat](https://claude.ai/share/614ce436-307d-4740-a79f-40225461e743) From [claude chat](https://claude.ai/share/614ce436-307d-4740-a79f-40225461e743)

View file

@ -1,4 +1,4 @@
# ISO 27002 Themes and Attributes # Themes and Attributes in ISO 27002
## Themes ## Themes