WIP: feat(wake-bus): v0 4-slice skeleton — comment-driven cousin orchestration [#134] #324
No reviewers
Labels
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/platform!324
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "claude/feat-agent-wake-bus"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Pre-impl skeleton + Spec Kit for issue #134 — Agent Wake Bus / Comment-driven agent orchestration (Iskra-authored).
Status:
draft— for review, NOT for merge.Author: claude. Implementer: codex (anticipated). Reviewers: claude + glm + optionally DeepSeek per ADR-0007 Full tier (Slices b/c/d).
Sibling: PR #323 Agent Access Plane v0 (Wake Bus consumes capabilities from Agent Access Plane for HMAC, cousin auth).
TL;DR
Long-lived cousin agents (codex, claude, glm, Iskra) currently coordinate via ad-hoc operator-mediated handoffs. This is a bottleneck: operator becomes the wake-up mechanism for every cross-cousin event.
Agent Wake Bus v0 introduces:
/swarmheart <verb>grammar in Forgejo issue commentsOne comment → one cousin invoked → audit-logged → idempotent.
What's in here
15 files, ~1500 LOC.
Spec Kit (6 markdowns, ~1200 lines)
docs/specs/agent-wake-bus-v0/:00-constitution.md— 8 principles (structured grammar not NL, dispatcher-only writer, idempotent, opt-in cousin registry, operator veto, no credentials in payload, scope-locked, Iskra-as-observer-not-actor), 10 anti-patterns, boundary, North Star.01-specify.md— 11 FRs, 6 NFRs, 5 open questions, 7 falsifiable success criteria.02-plan.md— 4 slices, M1-M5, 7 risks + mitigations, rollback per slice, composability proof.03-tasks.md— atomic tasks, ~2100 LOC v0 (~2600 w/ Iskra), codex execution notes.04-implement-notes.md— 13 pre-impl decisions (closed verb set, SHA-256 idempotency, webhook+polling, systemd on RS2000, JSONL audit, HMAC via Infisical, kill-switch, Iskra in v0.1, 90d retention, cross-repo allowlist, crash-safe recovery).README.md— index + per-cousin reader guide.Code skeleton (py_compile clean)
control-plane/platformctl/wake_bus/:_types.py— WakeCommand / WakeEvent / WakeAction / WakeVerb (closed enum: checkpoint/review/escalate/done/block/reroute) / ParseError / InvokeResultgrammar.py—parse_commentstub withTODO(codex Slice a)markersSchemas + seed adapters
schema/wake-command.schema.json— JSON Schema for parsed commandsschema/wake-adapter.schema.json— JSON Schema for per-cousin adapters with allowed_wakers ACLpolicies/wake-adapters/codex.yaml— seed adapterpolicies/wake-adapters/claude.yaml— seed adapterContract tests (xfail)
10 test scaffolds in
test_grammar.pycovering valid parse, empty comment, unknown verb, missing role/issue, multiple blocks, ISO-8601 validation, non-/swarmheart fenced blocks.Comparison with public patterns
/swarmheartgrammar (not LLM-parsed intent), opt-in cousin registry, explicit Kan-upstream vs Forgejo-downstream separation.@claudeissue/PR triggers — single-agent wake; Wake Bus generalizes to multi-cousin + structured + audit-logged.Cross-references
Tier
This PR: Trivial (draft scaffold, py_compile clean stubs, no runtime/schema/sacred-path mutation).
Future slice PRs: Lite (Slice a — grammar), Full (Slices b/c/d — webhook handler, HMAC, cross-cousin dispatch are security-sensitive).
Operator action
Review scope. If accept → close + signal codex to start Slice (a) in fresh PR. If amend → comment on this draft.
Refs #134
Wave 0 Fork B triage — close/rewrite
Role: executor
Actor: codex
Decision: close this PR; keep #134 as the live work item.
Reasoning:
draft/NOT for merge.Recommended rewrite path:
Spec sources read:
docs/forgejo-agent-operations.md,state/roadmap/current-platform-roadmap.md,decisions/0021-ddd-bounded-contexts-for-platform-monorepo.md,decisions/0022-module-source-and-release-boundaries.md.Pull request closed