outreach: draft Move #49 (swarm / multi-robot / alternative-framework wave)#423
Merged
Conversation
… wave) Lane A of the 2026-06-13 second candidate slate. Seven Outreach RFCs (0542-0548) proposing how URML v0.1 relates to swarm/aggregate-computing language peers, a multi-agent simulator, and non-ROS frameworks. No spec change is proposed in any of them. Three framings, no single thesis: - Language-to-language PEER (no manifest ask): Buzz (anchor, 0542), ScaFi (0543), Protelis (0544) express swarm/aggregate collective behavior; URML validates the per-robot intent and addresses many via the fleet roster (RFC-0286/0291). - Multi-agent runtime -> URML fleet: SCRIMMAGE scenario (0545), LSTS Neptus fleet C2 (0546). - Alternate non-ROS substrate: LSTS DUNE onboard runtime (0546), OpenRTM-aist OMG RTC middleware (0547), RoboComp (0548). LSTS DUNE + Neptus folded into one org-anchor RFC/row (0546). No license-ask anywhere; GPL/LGPL/EUPL-NC targets are cross-citation only, no code reuse. VIBE.md disclosure up front. Post titles carry no em-dash. Drafted, not posted: examples/lighthouses/outreach-move49.yaml carries empty sent_at/posted_url and response: none until the founder authorizes posting; bodies staged in posts-move49.md. README index rows added. Funnel 532 -> 539 on posting. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Ido Yahalomi <greenvh@gmail.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.
What
Drafts Move #49, the swarm / multi-robot / alternative-framework wave (Lane A of the 2026-06-13 second candidate slate). Seven Outreach RFCs (0542-0548), the ledger, the post bodies, and the README index rows. Drafted, not posted.
No spec change is proposed in any RFC.
Targets and framing
Three framings, no single thesis:
buzz-lang/Buzz(anchor)scafi/scafiProtelis/Protelisgtri/scrimmageLSTS/dune(+LSTS/neptus, folded)OpenRTM/OpenRTM-aistrobocomp/robocompLSTS DUNE + Neptus are one org-anchor RFC/row (post on DUNE, referencing Neptus).
Discipline
origin/mainwas 0541 at commit time; 0542-0548 are clean.How tested
grep "—"onposts-move49.md→ clean.origin/main→ 0541 max, no overlap.Posting (held for founder go)
outreach-move49.yamlcarries emptysent_at/posted_urlandresponse: noneuntil authorized. On "post": extract the seven bodies fromposts-move49.md, post under idoco2003 as GitHub Issues, setsent_at/posted_url/last_touch, flipclaude_directivesto done, refreshoutreach.db. Funnel 532 → 539 on posting.Rollback
Pure additive (new RFC docs + one ledger + one posts file + README rows). Revert the merge commit; nothing else references these files until posting.
🤖 Generated with Claude Code