G01-BA: No
Rationale
Both BATMAN_IV and BATMAN_V create per-originator entries in orig_hash from originator announcements. The common unicast forwarding path looks up the destination originator and its next-hop route; missing state causes a drop rather than a recursive global lookup. Thus reachability to arbitrary originators in the connected native mesh depends on mesh-wide originator reachability state, although nodes need not store a complete link-topology map. Keeping only next hops per destination is not eliminating the destination table. Attached-client translation adds another mapping layer and does not remove this requirement. The declared native Ethernet stack adds no hierarchical inter-mesh routing system that partitions this global namespace. This supports No for G01 under either algorithm; it is not a measured capacity ceiling, nor a claim that every endpoint application stores the mesh table. Loss, expiry or scoped announcements can make tables incomplete, but that does not establish arbitrary global reachability without them.
Assessment method
Linux v6.12 source inspection across BATMAN_IV and BATMAN_V; no scale test
Source context
bat_iv_ogm.c and bat_v_ogm.c originator creation; routing.c unicast destination lookup