From 8e76ef0fa1ef817caa6e87b806650f7b675771aa Mon Sep 17 00:00:00 2001 From: Padreug Date: Sun, 24 May 2026 15:38:31 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20note=20ZeroClaw=20as=20alternate=20runt?= =?UTF-8?q?ime=20in=20spec=20=C2=A712?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The spec is runtime-agnostic — what matters is conformant events per §4 and community scoping per §5. Adopters who want a richer agent layer than a focused Matrix bot can satisfy the spec on top of ZeroClaw (Rust, Apache/MIT, ships Matrix + Nostr channels + Ollama provider). Renderers filter by community a-tag, not by client tag, so multi-runtime ecosystems work without coordination. Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/community-organizer-spec.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/community-organizer-spec.md b/docs/community-organizer-spec.md index 4cc1fe3..68f6d74 100644 --- a/docs/community-organizer-spec.md +++ b/docs/community-organizer-spec.md @@ -635,6 +635,19 @@ to drive a 13.3" panel in the community's shared foyer. Both serve as worked examples of the spec; neither is mandatory. +### Alternate runtimes + +Adopters who want a richer agent layer than a focused Matrix bot can +satisfy this spec on top of a general-purpose agent runtime such as +[ZeroClaw](https://github.com/zeroclaw-labs/zeroclaw) (Rust, Apache-2.0 +/ MIT, ships Matrix + Nostr channels and Ollama provider out of the +box). The spec is runtime-agnostic — what matters is that captured +input produces conformant events per §4 and respects the community +scoping in §5. A ZeroClaw-based implementation would carry the +`["client", "zeroclaw", ""]` tag (per §4.1) instead of +`["client", "maubot-tracker", "..."]`; renderers ignore the difference +since they filter by community `a`-tag. + --- ## Changelog