Worktree task mgmt plan - #46
Merged
Merged
Conversation
Design for managing CalDAV calendar + Obsidian task vault jointly with Hermes on 204-agent. Collapses the original four-piece sketch (caldav MCP tool + vault MCP tool + skill) onto existing repo patterns: the terminal toolset is the vault tool, CalDAV is HTTP so it's a skill over khal/vdirsyncer like the mimir-alerting skill. Net build: two packages, one sops secret, one Syncthing folder, two skills, one cron sync job -- no hermes-agent changes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Drop one-file-per-task and folder-scoping per user: sync the ENTIRE vault and keep ONE big backlog list. Solve concurrent-edit conflicts with a MERGING sync layer (git via Obsidian Git + Hermes git client) instead of splitting files -- plain S3/Syncthing replicate without merging and would conflict-file a shared list. Daily list becomes a Tasks-plugin query lens over the backlog (planning = set a scheduled date), not a copy. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Pivot: the conflict saga was a wrong-storage-model smell -- flat files + dumb sync faking a shared datastore. SilverBullet keeps note-adjacent markdown but has ONE authoritative on-disk space that phone/desktop/Hermes all talk to, so the entire merge-layer question disappears. Its task query engine makes one-big-list + daily-lens native. Colocate on 204-agent so Hermes edits the space files directly (no MCP/API/replica). services.silverbullet confirmed in our nixpkgs (2.6.1). Calendar half (khal/vdirsyncer) unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add the missing piece: in-flight nixconfig work is itself a task at every stage until live -- the done-means-deployed rule as task state. A cc-sync skill on its own cron projects three sources (plans/*.md Status, open PRs via gh, merged-but-undeployed via each host's rev) onto a dedicated Engineering page Hermes solely owns (no conflict), tagged #cc. Prereq: set system.configurationRevision (currently unset) and expose it as a Mimir metric so Hermes reads deployed revs without ssh. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Nail the invariant that makes 'dump tasks, agent plans days' safe: the daily view is a lens over open tasks scheduled on-or-before today, so a planned-but-unfinished task carries forward and stays open until I check it off -- planning only sets metadata, it never closes a task (Hermes may set/bump dates, never checks off to 'clear' a day). Morning plan flow is calendar-aware: Hermes reads khal events + open backlog and fits tasks into the gaps around real commitments. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new implementation plan describing how to co-manage tasks (via a SilverBullet space) and calendar (via existing CalDAV tooling) with Hermes, including host placement, access rules, and rollout steps.
Changes:
- Introduces a SilverBullet-based “note-adjacent tasks” approach with backlog + daily query pages and an Inbox triage flow.
- Defines a CalDAV workflow for Hermes using
vdirsyncer+khal, with constrained write semantics. - Outlines a
cc-syncprojection from plans/PRs/deploy state into anEngineeringpage, including a proposedsystem.configurationRevision+ metrics-based deployed-rev detection.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+127
to
+128
| Two skills, both installed via activation script like | ||
| `mimir-alerting`/`hermes-autofix`: |
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
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.
No description provided.