280c97de7c06860889d79a47c8b751c3d30230df
Status moves to Decided. Six amendments, all found by measuring the draft against the tree and against what PR #859 produced from it: - Sequencing gains the reaction stream as step 1. The parent decision already requires ARCHIE_REACTIONS under LimitsPolicy and 7d5u.2 parameterised Retention for it, but no stream exists, so every publish to archie.reaction.* fails against no matching stream. - The owned-task guard becomes its own step. The (owner, repo, pr_number) lookup it depends on does not exist: pr_number is written and never read in a WHERE clause, so it needs a store method, a StateStoreService RPC and an index. - The producers move to the end. A producer built before its consumer and its guard publishes into nothing, and becomes an unguarded intake the moment a stream appears. - Idempotency keys gain the reaction kind. Review IDs and review-comment IDs are independent forge sequences, so the bare id let the two collide. - A review is the unit of remediation, never a comment. One review with eight inline comments would otherwise mean eight builder runs, eight gates and eight pushes to answer one review. Runs also serialise per task regardless of allow_concurrent. - Only archie's own comments are excluded, not all bots'. The external review bot is the main source of findings on an archie-opened PR. Because that makes bot comments actionable, the exchange can run away between two bots with no human involved, so remediation rounds are capped by max_retries. Withdraws the RepliesAfter citation: no such mechanism exists in the tree.
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%