353c1bb982110cc707973c3ddbec63bf7fc5811f
The rule as first written said release notes state what a reader gets and that withheld capabilities and failure modes belong in docs/architecture/. That is true but blunt enough to invite the wrong edit: applied mechanically it deletes a caveat a reader needs. Three cases, distinguished by whose experience the sentence describes. A capability that never existed leaves no expectation to correct, so a note about it reads as a feature. The implementation's journey is not the reader's experience either. A capability that shipped but is not yet wired is the reader's experience, and belongs as a caveat paired with the behaviour that compensates for it -- the release note is then the only place a reader learns they should not expect it to work yet. The last line says so outright, because the failure mode of this rule is someone applying it to a caveat. The gate ran and passed in the same conditional chain as this commit.
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%