docs: task-lifecycle spec (permanent-team orchestration)#17
Merged
Conversation
…am API) Petrus (2026-06-20): task lifecycle + lead/worker + monitor + completion summaries over the PERMANENT roster; no create-team API. Defines the Task object, statuses (open/in_progress/blocked/done/cancelled), daemon /tasks API (ether's lane), CodeWatch monitor + completion-summary surface (claudeMB), and the link to the control-plane action-system. Shared contract both lanes build to. Inspired by michelhelsdingen/ensemble, controlled via CodeWatch. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Petrus (2026-06-20): "implement the team lifecycle, lead worker, task monitor, completion summaries, but do we want create team api, we have a permanent team?"
Answer captured here: no create-team API (permanent roster). Instead, task lifecycle over the existing team.
docs/task-lifecycle.mddefines:open -> in_progress -> (blocked) -> done | cancelled/tasksAPI (registry/state/log/room-posting) — ether's lane/actions/requestreceipts attach to a task)Shared contract so both lanes build to the same shape. Inspired by
michelhelsdingen/ensemble, controlled through CodeWatch + backed by IAK typed actions/receipts.🤖 Generated with Claude Code