[#5,site/notes][xs]: small addition explaining that Obsidian closed s…

…ource.

site/content/notes/obsidian-database-research.md

@@ -4,7 +4,9 @@ title: Obsidian Database Research
 
 Research on the details of the internal Obsidian "database" i.e. its cache of files and their metadata, links etc which in turn power functionality like network graph, page links, plugins etc.
 
-Links to Flowershow's need to have its own metadata database to power things like a network graph, links etc (tracking issue: https://github.com/flowershow/flowershow/issues/5)
+Relates to Flowershow's need to have its own metadata database to power things like a network graph, links etc (tracking issue: https://github.com/flowershow/flowershow/issues/5)
+
+Note:  Obsidian is closed source so we don't know the internal code implementation. However, we have some insight into the cache itself both by inspecting it on disk and by examining the API exposed to plugins.
 
 # Motivating questions
 
@@ -84,4 +86,4 @@ lengthy comment from Dec 2021 explaining there are 2 caches a persistent and eph
 > -   A link resolver orchestrator: `MetadataCache.linkResolver()`
 > -   A link resolver worker: `MetadataCache.resolveLinks(srcFilePath)`
 > 
-> On app startup, all markdown files within the vault are passed into the `linkResolverQueue` and the results are stored in the resolved and unresolved link cache.
+> On app startup, all markdown files within the vault are passed into the `linkResolverQueue` and the results are stored in the resolved and unresolved link cache.