6ecde5cc249b1732e58dbf807ca98f932856d159
schedulingConfig translated [scheduling] config into a domain EngineConfig but nothing ever called it in production: the whole scheduling/cron family (ticker engine, cronstore, crondelivery) was built and tested but reachable from no binary, so an operator setting scheduling.interval etc got a silently inert section. setupScheduling opens a cronstore.Store as the engine's JobSource, builds a crondelivery.Router with a workflow-kind runner backed by the same non-forge gateway.TaskCreator chat's /spawn already uses, and constructs the scheduling.Engine from schedulingConfig. startServices starts it alongside every other subsystem; Stop is registered via addCleanup on the same Background-timeout pattern as the curator runtime. No chat task creator configured leaves the engine unstarted rather than running with no reachable job kind -- the "chat" delivery kind stays unmapped for the same reason (no unified cross-channel outbound sender exists at this composition root yet).
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.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%