57d8d48279f4bc98847507d44dce211b0db6f7d8
The cron ticker engine had no path from operator input to runtime. Add the four settings its EngineConfig is built from, as a declared type rather than loose root fields: interval, max_parallel, job_timeout, events_sink Every field is optional and defaults independently, so an absent section is valid and resolves to the engine's own documented constants. Zero means "unset, give me the default", which is why a negative value is a startup error rather than a clamp -- it is the only way an operator can name an unusable value deliberately, and running something other than what was written is how a misconfiguration stays invisible. events_sink is a simple on/off, "bus" or "none": the engine's Sink contract is the bus's emitter shape and there is exactly one bus in the process, so a named-sink registry would be scaffolding with one entry. Absent resolves to "none", the same shape applyMemoryDefaults and applyNATSDefaults use, so a resolved config has one spelling for "not publishing" rather than two that happen to mean the same thing. config.example.toml documents the block in the house style, commented out like [[repos]] and [capture]: a live example would be a default the operator never chose.
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%