be03844df8a19248c3984aed61284a4bfdf59496
Part of archie-core-1786637490043 (config surface for memory engine selection and settings). config.MemoryConfig gets an Engine field selecting among the domain/memory engine family, plus toml tags on every field -- Provider, ProviderConfig, and SessionTTL had none before, yaml/json only, which didn't match repo convention. Engine and Provider are kept as two separate fields rather than one: they select between two different mechanisms (the new engine family vs. the legacy external-provider path, archie-core-1786637499161-356-e424e40d.1), and conflating them would mean a value meant for one silently getting read by the other once both are wired. applyMemoryDefaults resolves an absent engine to "builtin" so unconfigured and explicitly-builtin are the same state everywhere after defaulting. validateMemory rejects an unrecognised engine name in the same style as forge.type's existing validation -- named constant list, "%w: field %q (want %s)" shape, wired into the same validate() chain. config.example.toml documents the new field. Not yet wired to anything: nothing reads cfg.Memory.Engine at daemon boot yet to actually select and start an engine through domain/memory.Registry. That's bootstrap wiring, tracked as the remaining half of archie-core-1786637499480 (ship the builtin store as the default engine).
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%