diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-09 17:16:08 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-09 17:16:08 -0500 |
| commit | c91bd0b1e8183814f248b0751d88a8e422a905e8 (patch) | |
| tree | f70abe516c47162f8e6538c2d9fa639aa9349d13 /scripts | |
| parent | 1f0900281b8262539137bc1aff3f01cc05745139 (diff) | |
| download | rulesets-c91bd0b1e8183814f248b0751d88a8e422a905e8.tar.gz rulesets-c91bd0b1e8183814f248b0751d88a8e422a905e8.zip | |
feat(workflows): generalize broadcast into announcement + situational modes
cross-project-broadcast handled tooling and rule announcements but had no shape for the situational case: a life or work event I want every project's agent to know, said once so none is missing context when I next talk to them. I renamed it to broadcast (helper and test alongside) and split it into two modes over the same fan-out plumbing. Announcement keeps the rigid capability template. Situational carries a general-not-comprehensive summary plus a fixed receiving-agent contract: record it in notes.org, hold it time-boxed or standing, apply on the project's own judgment, ask follow-ups at startup. The broadcasting agent does no per-project relevance analysis. Each receiving agent decides what the event means for its own work.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
