Council hall · Org commons · swarm-routing/.github
Org commons
The rules every repository shares: licence gate, reusable workflows, labels, templates and agent skills.
Under construction: no release, 9 epics in progress, 10 planned Computed from its 20 epics, as they stood on .
What it does
swarm-routing/.github holds the org-wide defaults: the profile page, issue forms and PR template, the label taxonomy (labels.json), the C++ style, and the reusable workflows other repositories call (reusable-ns3-ci.yml, reusable-licence-check.yml, reusable-python-ci.yml, reusable-pr-title.yml, sync-labels.yml). Callers pin @main, so those inputs are a public contract.
tools/org-sync renders templates/ into each repository (AGENTS/CLAUDE org sections, badges, SECURITY, licence files, ADR template, Makefile targets) and checks drift in CI. The swarm-routing/skills marketplace ships the org-repo Claude Code plugin that drives it, script first.
Diagrams
Package structure
The repository's layout, its licence per directory (LICENSING.md) and what exists today.
| Path | What | Licence | State |
|---|---|---|---|
.github/workflows/ | reusable-ns3-ci, reusable-python-ci, reusable-pr-title, reusable-licence-check, reusable-org-sync-check, sync-labels | MIT OR GPL-2.0-only | present |
tools/checks/check-headers.py | the licence-header gate | MIT OR GPL-2.0-only | present |
tools/org-sync/ | applies templates/ to a repo and checks drift | MIT OR GPL-2.0-only | present |
templates/ | what org-sync renders | MIT OR GPL-2.0-only | present |
ISSUE_TEMPLATE/, labels.json | issue forms and the label taxonomy | MIT OR GPL-2.0-only | present |
ROADMAP.md, CONTRIBUTING.md | the phases and the org invariants | GPL-2.0-only | present |
Where it sits in the colony
Quests
The repository's epics and their sub-issues, as the issues stood on 2026-11-13: 55 of 153 sub-issues closed.
- #6 org repo template — security policy, README badges and community files, applied and kept in sync by a tool and a skill
In progress · 15 / 28 sub-issues closed - #14 Repository hardening for every org repo: Scorecard, rulesets, merge policy, CI hygiene
In progress · 5 / 18 sub-issues closed - #50 One repository per swarm protocol: create the missing ones (Termite, HOPNET)
In progress · 2 / 3 sub-issues closed - #107 ns-3 images: every protocol release and campaign builds on ns3-containers
In progress · 6 / 7 sub-issues closed - #141 AI files stay correct: automated review of AGENTS.md and CLAUDE.md in every repo
In progress · 1 / 11 sub-issues closed - #150 CI time: every job under its budget
In progress · 1 / 4 sub-issues closed - #156 benchmarks: each protocol repo benchmarks its changes, swarm-routing/benchmarks records every release
In progress · 6 / 16 sub-issues closed - #251 Roadmap by tracks (protocols on ns-3, portable runtime, research, infrastructure) and the ticket clean-up that goes with it
In progress · 1 / 8 sub-issues closed - #370 Container images: official `<name>`, development `<name>-dev`, a 2-day retention for development images
In progress · 2 / 11 sub-issues closed - #35 code quality across the org — order of work and maintainer decisions
Planned · no sub-issues - #48 Other simulators: container and tooling repos for OMNeT++/INET, Veins and CORE/EMANE (deferred; ns-3 first)
Planned · no sub-issues - #216 every public repository releases and is archived on zenodo: ns3-containers, benchmarks, skills, the site and .github too
Planned · 0 / 5 sub-issues closed - #250 Portable runtime: one host contract, a discrete-event host and a Linux daemon, then real computers, tested on the same scenes at every step
Planned · 0 / 10 sub-issues closed - #252 A swarm protocol of our own, designed from what the five implementations measured
Planned · 0 / 4 sub-issues closed - #272 Routing security: one threat model, shared adversaries, default-off defences per protocol, secure comparators
Planned · 0 / 4 sub-issues closed - #322 Standalone discrete-event host: every core run without ns-3, deterministic, on the same scenes
Planned · 0 / 3 sub-issues closed - #323 Linux daemon host: every core over real sockets, packaged for amd64 and arm64
Planned · 0 / 4 sub-issues closed - #324 Emulation: the daemons on CORE/EMANE, real stacks over emulated radio links
Planned · no sub-issues - #325 Raspberry Pi testbed: the protocols on real boards, run and judged by one command
Planned · 0 / 1 sub-issues closed
Closed: 1 epic
- #307 docs/references.bib in every repository, DOI links first, sections generated and checked
Done, closed 2026-11-13 · 16 / 16 sub-issues closed
Sources
The status and the quests come from the repository's issues and releases (2026-11-13); the other
facts on this page are kept by hand from its AGENTS.md (as of 2026-11-08).