704a5ee642653011060cd68638b2f3b3b745bd37
Closes archie-core-1786637499161-356-e424e40d.1. setupMemory's own doc comment claimed external providers are added via RegisterExternal when cfg.Memory.Provider is set -- no such call existed. Investigated wiring it for real: there is no external MemoryProvider implementation anywhere in the repo to construct and register (only internal/memory/builtin.Provider exists), so there is nothing to route memory.provider's value to yet. Wiring the call would be dead plumbing to nothing, not a fix. The actual defect is that setting memory.provider has always silently done nothing -- an operator who set it reasonably believed they configured something. validateMemory now rejects it outright with a clear reason, turning a silent no-op into a loud one at config load, same failure-loudly posture as every other unimplemented-value check in this file. Drop the rejection once a real external provider (or the new domain/memory engine family's Honcho proof, archie-core-1786637492031) gives the field an effect again. Updated setupMemory's doc comment and config.example.toml to match -- the provider_config example is removed too, since it has nothing left to configure.
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.8%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%