E05-BA: Yes

Rationale

Freifunk Stuttgart's operator report of 11 June 2015 describes eleven radio-meshed routers serving a residential shelter, with 40–50 simultaneous client devices and paths of up to five hops. Its 22 January 2016 operational incident report explicitly identifies batman-adv carrying mesh packets in the same community network, 225 days later. The operator's Gluon repository identifies batman-adv and direct WLAN mesh links. Together these primary records support sustained real-user operation of the native L2 mesh service by a local community operator rather than a research-only demonstration.

Assessment method

Selected-composition primary documentary review; no runtime experiment

Source context

Dated Freifunk Stuttgart operator reports and nostr.wine operator documentation

Outstanding qualification

Historical role-level documentary evidence, using the same adoption scope as the AX and Tor decisions. The dates and component mapping are complementary records, not synchronized traces of every installation. Credit the local radio/Ethernet-style batman-adv L2 mesh service; gateway VPNs and user IP applications are outside that boundary. The evidence does not establish six months on Linux 6.12, uninterrupted uptime, optional bonding or every study-specific setting. Community participation in Freifunk is disclosed; this credits an operational community deployment, not a second independent implementation or an organizational audit of every contributor. No live network test performed. E05 uses the owner-approved adoption rule from revision 6.40. Deployment differences are disclosed rather than imported into the technical column. Independence is assessed from public operator attribution and role, not a private affiliation audit. No runtime, security, uptime or full-profile certification is implied.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.

round573.html
round573-sources.json