cf6c5f42d5dac17530ff96a27becb40b0220739a
Third slice of docs/prds/eda-playbook-engine.md (t2db.11), completing open question 2: instead of a single playbook dir, the config gains a LIST of directories (playbook_dirs) of *.yaml/*.yml binding files, loaded at startup as an additional input to workflow_routing_file and workflow_labels_file, which remain supported unchanged. - LoadPlaybookDirs(dirs []string) reads every yaml file across the configured directories and merges kind + arbitrary-label bindings. - This is what finally exercises the design doc's drop-and-report collision rule: a single file cannot collide with itself, so the cross-source path (two files in one dir, two dirs, or a dir plus a single-file field) had never run in production. A binding key declared by more than one source is a reported load failure, not a silent pick-one by source order or version. - Router-level collision handling: MergeKindWorkflows/MergeLabelWorkflows fail on a key bound by both the single-file fields and the playbook dirs, applied at boot. - Config: PlaybookDirs []string, empty by default (no behavior change for existing configs). Repo-scoping (typing dirs to Config.Repos owner/name) is explicitly deferred to a separate later decision per ticket; org/tenant keying is out of scope. - PRD: records the list shape per Sam's correction (single dir would contradict multiple independently-maintained playbook sources).
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%