285474a552dbee9c9287d2b3b412a33f8352c5bb
RULES.md says not to turn a requested outcome into extra product features and to keep inferences open until the maintainer or repository evidence settles them. The first draft broke that: a reviewer found that a record replaced in place lets a process that applied a version and then died keep reading as current, and I answered it by adding a periodic re-stamp, a recurring write in three processes that neither the tracking issue nor runtime-control-plane.md asks for. The hazard is real, so it stays in the document as an open question with three options and a recommendation, for Sam to settle. The re-stamp and the instance identity come out of the design. Also the sentence pass RULES.md requires before approval, which had not been done: the staleness rule was stated in three sections, and rationale stood where a requirement belongs. Relates to archie-core-pskb.
feat(messaging): Messaging Service operator surface, chat report rendering, and the diff-cap config fix (#899)
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
132 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%