59ffcdf229483c684b13c9c66bfb1efec4447bb2
The landing page still opened with "archied is a resident daemon that polls a forge", which is wrong twice over. A deployment is a set of contracted services, not one process, and a forge is one event source among several: signed webhooks from any sender and chat-channel messages reach the same playbook routing that a GitHub or Gitea issue does. GitHub/Gitea was the first case, not the shape of the product. The intro now leads with the event path (event -> playbook -> workflow in an isolated worktree) and says outright that sources, their fields, and the workflows they reach are configuration rather than code. "What runs where" names the actual services and which contract each owns. The stray "Work arrives as events." line went with it, since the intro now states that. Claims are held to what ships: module actions load and type-check but are not dispatched yet, so the page promises one outcome per event, not a fan-out.
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%