It is still a bit of a mess but sharing if you are interested. I still have more work to clean up the interfaces, and what has to be exported out of the engine, etc.
https://github.com/c-ferrier/lore-protocol
I'll actually break apart the engine and lore into two separate repos. (i had a need to store other types of data in git trailers... hence the need) Lore just serves as a reference implementation wrapper, but lore isn't actually required. one can use the "atom" executable as long as it has a protocol defined. (Either in code or toml) The wrapper is primarily for user experience compatibility.
I'd be interested in hearing your thoughts.
(All the docs need work, ignore them)
It is still a bit of a mess but sharing if you are interested. I still have more work to clean up the interfaces, and what has to be exported out of the engine, etc.
https://github.com/c-ferrier/lore-protocol
I'll actually break apart the engine and lore into two separate repos. (i had a need to store other types of data in git trailers... hence the need) Lore just serves as a reference implementation wrapper, but lore isn't actually required. one can use the "atom" executable as long as it has a protocol defined. (Either in code or toml) The wrapper is primarily for user experience compatibility.
I'd be interested in hearing your thoughts.
(All the docs need work, ignore them)