The only piece of information recorded is preset-keys, which is not a logseq reference.
Project - move the sections of the Microfreak user guide in the UG subnamespace
When I requested that AI import the Logseq/Entity/Book/Sections for the microfreak user guide, it was one of the first times I prototyped that section, and I instructed AI to put it inside of Microfreak, for example, Microfreak/08 LFO was a direct child of the parent namespace. Placing guide sections directly under Microfreak made the user guide difficult to reference in the abstract. I changed this in Launchpad/UG, where UG stood for User Guide. The section is now Microfreak/UG/08 LFO.
define a Logseq/Entity/Book/User Guide entity that describes a particular type of book which is a user guide. By convention, this type of book should appear in a <Item>/UG logseq namespace, with Logseq/Entity/Book/Section entities underneath it.
convert Microfreak user guide book sections so they are nested under Microfreak/UG
ensure that information is not duplicated. This means that the preset name should only appear once in the file, and once in the filename.
it's important to me that preset pages don't contain useless AI slop. This means that they should not contain tautological information. For example, a preset Microfreak/Preset/397 Imit should not contain an obviously derivative description like, "A MicroFreak preset stored in slot 397, in the Keys category."
preset pages should point to their data definition
all frontmatter in the page that represents a categorical variable must be an auto-complete-able logseq entity. If preset-category is Keys, then I need to be able to autocomplete a logseq namespace and find the sibling categories. One place this could happen would be Logseq/Preset/Category/Keys, with sibling namespaces. Ensure that links to the relevant parts of the logseq user guide are included.
TODO I want each Logseq/Entity/Preset/Synth/Microfreak page - and indeed, each Logseq/Entity/Preset/Synth page - to have its frontmatter represent a lossless digital twin of as many of the preset's primary parameters as I can, along with documented links to the data dictionaries that describe them, while allowing me to add my private notes in the body of the document and have those preserved over time. If this is likely to be problematic due to the need to regularly sync items over, then maybe we can come up with some convention for adding commentary, such as <preset path>/Log/YY/MM/DD WWW. Do some research to determine what's reasonable here. Convert 1-2 of pages to an enhanced format. The goal here is that I want to be able to ask my AI questions about my presets or have my AI be able to annotate my podcast episodes with human-oriented descriptions of the signal chains used in the podcast.
in logseq, one can click on a frontmatter item and be taken to a page. For example, preset-on-device is literally the page preset-on-device. I want to develop or work towards a convention that when frontmatter is defined in a logseq entity, then the frontmatter defined and requested by that entity should be related to the entity, for provenance and data definition reasons, and the page for the custom frontmatter attribute must be filled in with its definition - and that definition should be of type Logseq/Entity/Frontmatter/Definition. There's a design tension here. If we click on a certain property, say, preset-on-device, we are taken to a page that is not a subnamespace of Logseq/Entity/Preset/Synth the way that definition page describes. One way around this would be to create Logseq/Entity/Preset/Frontamtter/preset-on-device with an alias of preset-on-device, so that clicking on preset-on-device would take it to the appropriate location in the garden. I think we need to further stipulate that prefixes should have a certain type of namespacing. For example, in the entity system, Logseq/Entity/X/Y/Z/Frontmatter/Fruit should likely lead to frontmatter key x-y-z-fruit. We don't need to do this everywhere just yet, but in this synth preset space, I'd like to do this.
link the sync task and implementation from the entity definition, and document the source of category names such as Bass, Brass, and Keys.
move the scripts from <root>/scripts into mise-tasks and remove the old directory. My/Pref/Dev/mise/Tasks describes this expectation.