Remove skym-notify - #15
Merged
Merged
Conversation
skym tells no one by itself: what is worth a message is left to its readers, agents with the skill, which call the API and decide. This reverts #14 and says so in the failure model: a reader that cannot reach the server reports it, and pings a dead man's switch after each run so its own silence is noticed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts #14. Notifications are left to agents reading the API with the skill: they decide what is worth telling, instead of fixed rules pushing messages. The failure model in docs/architecture.md now says how the server's own death is noticed (its readers) and that a reader should ping a dead man's switch after each run. Workspace builds and tests pass.