Context
ADR-013 describes runtime feed subscriptions (feeds.subscribe(...)) allowing agents to dynamically subscribe to feeds at runtime rather than only through static pod declarations.
What's needed
- Define subscription API surface in cllama or claw-api
- Handle dynamic feed registration with TTL and scope validation
- Ensure subscribed feeds go through the same injection path as static feeds
References
- ADR:
docs/decisions/013-context-feeds.md
- Feed client:
cllama/internal/feeds/feeds.go
Design note (added 2026-04-03)
This is explicitly Future Milestone 13 in ADR-013 — deferred because it conflicts with Compilation Principle #1: all wiring is resolved at claw up time. An agent dynamically subscribing to a new feed at runtime is self-registration, which the manifesto explicitly rejects.
Before this can be Ready, the architectural tension needs to be resolved. The most compatible path is probably an operator-side claw discover command that introspects a running pod, finds available feeds from service descriptors, and updates the compiled manifest — keeping the subscribe act in the operator layer rather than the agent layer. That preserves compile-time guarantees while enabling feed discovery.
This is not a capability wave item. It warrants its own ADR or ADR-013 amendment before implementation begins.
Context
ADR-013 describes runtime feed subscriptions (
feeds.subscribe(...)) allowing agents to dynamically subscribe to feeds at runtime rather than only through static pod declarations.What's needed
References
docs/decisions/013-context-feeds.mdcllama/internal/feeds/feeds.goDesign note (added 2026-04-03)
This is explicitly Future Milestone 13 in ADR-013 — deferred because it conflicts with Compilation Principle #1: all wiring is resolved at
claw uptime. An agent dynamically subscribing to a new feed at runtime is self-registration, which the manifesto explicitly rejects.Before this can be Ready, the architectural tension needs to be resolved. The most compatible path is probably an operator-side
claw discovercommand that introspects a running pod, finds available feeds from service descriptors, and updates the compiled manifest — keeping the subscribe act in the operator layer rather than the agent layer. That preserves compile-time guarantees while enabling feed discovery.This is not a capability wave item. It warrants its own ADR or ADR-013 amendment before implementation begins.