Sisyphus/Sisyphus
4
0
Fork 0
Code Issues 74 Pull Requests 11 Actions 3 Packages Projects Releases Activity

docs: describe event-driven daemon updates accurately #419

New Issue
Closed
opened 2026-10-18 01:52:01 +00:00 by excho0 · 0 comments
excho0 commented 2026-10-18 01:52:01 +00:00
Owner
Copy Link
Copy Source

Both README statements now describe the event-driven behavior accurately:

  • Document startup and event-triggered node-record publication, retry timing, and renewal timing.
  • Document store-pin change notifications and the periodic cluster anti-entropy check.
  • Verify both descriptions against daemon code, the record tests, and docs/timers.md / docs/development.md.
  • Merge PR #420: #420
Both README statements now describe the event-driven behavior accurately: - [x] Document startup and event-triggered node-record publication, retry timing, and renewal timing. - [x] Document store-pin change notifications and the periodic cluster anti-entropy check. - [x] Verify both descriptions against daemon code, the record tests, and `docs/timers.md` / `docs/development.md`. - [x] Merge PR #420: https://git.echelonts.net/Sisyphus/Sisyphus/pulls/420
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
Barrier affecting people with disabilities
 all-platforms
Run every platform's packaging and checks on this pull request, not only the three main ones
 area:agents
MCP server, skill, and thinking on the pool
 area:ai
Planner and model providers
 area:chain
Blockchain, SISY, verification
 area:ci
Continuous integration and build workflows
 area:client
Desktop and web clients
 area:daemon
sisyphusd coordinator, worker, scheduler
 area:p2p
libp2p hosts, relays, discovery, connections between nodes
 area:project
Project planning, roadmap, and governance
 area:protocol
Protobuf schemas and RPC contracts
 area:runtime
Workload execution and environments
 area:storage
Content-addressed storage, IPFS, Kubo, Cluster, S3, names, pinning
 bug
Something isn't working
 chore
community
Repository health, templates, Discussions, contributor experience
 dependencies
Updates to actions, Go modules or npm packages
 discussion
Migrated from GitHub Discussions
 discussion/Announcements
GitHub Discussions category: Announcements
 discussion/General
GitHub Discussions category: General
 discussion/Ideas
GitHub Discussions category: Ideas
 discussion/Q&A
GitHub Discussions category: Q&A
 discussion/Show and tell
GitHub Discussions category: Show and tell
 discussion/answered
Q&A discussion with an accepted answer
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 i18n
Translations and right-to-left layouts
 infra
Build, CI, releases
 invalid
This doesn't seem right
 needs:decision
Waits on a decision from both owners
 needs:hardware
Waits on a machine we do not have yet
 paired
Built together by both maintainers, with co-authored commits
 question
Further information is requested
 research
Needs investigation or a design decision
 security
Sealing, keys, access control, tokens, the security model
 status:in-review
Built and in an open pull request; closes when it merges
 test
testing
Tests, test harnesses and the rehearsal
 tracking
Roadmap and meta issues
 wontfix
This will not be worked on
type
Feature
A request, idea, or new functionality (GitHub issue type)
type
Task
A specific piece of work (GitHub issue type)
No labels area:daemon area:storage documentation
Milestone
No items
No Milestone V0: prove the loop
Projects
Clear projects
No projects
Sisyphus roadmap
Done
Assignees
Clear assignees
excho0 (Excho) rvnminers-A-and-N (Austin L.) sisyphus-bot (Sisyphus CI bot)
No Assignees excho0
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Sisyphus/Sisyphus#419