Chisle
The coding-agent plugin that bills 52% of a bare model across 20 live tasks. Terse persona + tool-output compressor + context diet.
The Ant-Colony-Based Routing Algorithm: reactive ants, data that reinforces its own path.
Developer toolsGitHub @swarm-routingOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Repository information has not been collected yet.
No updates detected yet. GitHub releases will appear here.
ARA, the Ant-Colony-Based Routing Algorithm (Güneş, Sorges & Bouazizi, 2002), as a standalone swarm routing protocol for MANETs: planned as a simulator-agnostic C++ core and an ns-3 contrib module on swarm-core, with a paper-fidelity sheet.
Translation pending
Loading the full README.
Read the full README ↗ARA, the Ant-Colony-Based Routing Algorithm (Güneş, Sorges & Bouazizi, 2002),
as a standalone protocol: a simulator-agnostic core/ and the ns-3 contrib
module ara on
swarm-core. Status:
the org's Phase 3; the three slices of core/ (route discovery, route
maintenance by data, duplicate errors with route-failure backtracking) run in
ns-3 as the module ara (header codec, adapter, helper, example,
test.py -s ara, and the ara arm of ns3-tools' routing-compare). The
anchor (#5) misses: ARA's
routing load is below AODV's, its delivery is not above it, and the written
infeasibility verdict is docs/benchmarks/v0.2.0-anchor.md.
Release status: the first release, v0.1.0, comes before the comparator gates (maintainer decision 2026-11-10): it has not cleared them (org golden rule 6: fidelity sheet, per-PR delivery smoke, anchor). No number from v0.1.0 counts as a benchmark result. v0.2.0 (2026-11-13, Zenodo version DOI 10.5281/zenodo.24202635) is the release with the gates run: the anchor missed, and it ships with the written infeasibility verdict (docs/benchmarks/v0.2.0-anchor.md), so ARA's delivery against AODV is not presented as a reproduction of the paper. Releases are cut by release.yml and listed under Releases.
How to work here, for people and AI agents alike: AGENTS.md has the rules and how to build and verify; the org conventions are in CONTRIBUTING.md.
Versions follow SemVer (CHANGELOG.md). Each release is listed under Releases, built by the org's release workflow and archived on Zenodo with its own DOI.
To cite this repository, use the “Cite this repository” button (from CITATION.cff):
| DOI | resolves to |
|---|---|
10.5281/zenodo.24125198 | concept DOI: always the latest release. This is the badge above, and the right citation when you mean this project. |
Each release also has its own version DOI, listed on its Zenodo record: cite that one when you reproduce a number measured at that release.
Please also cite the work it builds on:
What this implementation reproduces from its sources, and every deliberate deviation, is in docs/fidelity.md.
Using it in your work? Contributions are welcome, and citing the DOI helps just as much.
What is planned and in progress here: the issues labelled epic. An epic's open sub-issues carry a priority:* and a model:* label, so a contributor or an AI agent can pick one up (how issues work). The whole org's plan: the roadmap.
| Epic | Status | Sub-issues closed |
|---|---|---|
| #3 ARA as a standalone hexagonal protocol (Phase 3) | In progress | 2 / 3 |
See LICENSING.md.