It could be as simple as a utility seed that does it (possibly using fetch). Ideally we'll need to figure out read/write access control to memories.
Memories are controlled by the user, but they also want ways to make sure that seeds they run don't read from (or espcially write to) memories that they don't intend them to. How to do that?
The engine could check the namespace matches the remote location of the memory (and let local ones read/write any ones they want)?
Seed_type import. When called, the harness shows "system" UI allowing the user to select which file to import (for example the CLI might use inquirer to list files in the data folder). Then the harness loads the file and returns it as a string. You could use a json extract to parse the content.
In web contexts, the UI would be to show a <input type='file'> and then load up the file and pass to the engine.
[ ] Stub out profile.import()
[ ] ProfileFilesystem.import()
[ ] seed_type import + documentation
[ ] In the web implementation, add an implementaion for import that uses <input type='file'>
The above I think is obsolete because we can just use fetch with a local file.
[x] A cache of embeddings in profile (#25)
[x] Make import-polymath process each bit and do a title\n\nbody
[x] When memorizing something skip if already memorized
[x] Add a memorize-items (meta-seed pattern)
[x] Add a import-polymath
[x] Document how to import a polymath instance
[x] Add logging on progress for import
[ ] Why does the return value of import-polymath have all undefined?
[x] Add a suggest-titles which selects titles and then asks for new ones
[x] Fix the extract used in suggest-titles
[ ] remove-numbers should handle empty lines at the end (needs a #46 filter)
[x] Update remove-numbers to be a split/join loop with an individual remove-number
[ ] Add a draft-content given a title from suggest titles
[ ] suggest-titles should stop relying on polymath-import memory name and have some other way of detecting which memory to use (perhaps enumerating current memory names?)
[ ] (Add a list seed, which can have a type of memories or stores)
[x] Make a thing to store a memory (ask for a name)
It could be as simple as a utility seed that does it (possibly using fetch). Ideally we'll need to figure out read/write access control to memories.
Memories are controlled by the user, but they also want ways to make sure that seeds they run don't read from (or espcially write to) memories that they don't intend them to. How to do that?
The engine could check the namespace matches the remote location of the memory (and let local ones read/write any ones they want)?
Seed_type
import. When called, the harness shows "system" UI allowing the user to select which file to import (for example the CLI might useinquirerto list files in thedatafolder). Then the harness loads the file and returns it as a string. You could use a json extract to parse the content.In web contexts, the UI would be to show a
<input type='file'>and then load up the file and pass to the engine.importthat uses<input type='file'>The above I think is obsolete because we can just use
fetchwith a local file.memorize-items(meta-seed pattern)import-polymathimport-polymathhave all undefined?suggest-titleswhich selects titles and then asks for new onesremove-numbersshould handle empty lines at the end (needs a #46 filter)remove-numbersto be a split/join loop with an individualremove-numberdraft-contentgiven a title from suggest titlespolymath-importmemory name and have some other way of detecting which memory to use (perhaps enumerating current memory names?)listseed, which can have a type ofmemoriesorstores)