EF-Map collaboration now has clearer boundaries than older public copy implied. There is not one generic public bookmark system. There are separate local, tribe-scoped, and public-intel workflows.
Public Scout Reports
Scout Reports are the public collaboration surface. Players can submit system intel with a Sui wallet session, report type, expiry, reporter context, and timestamp context. Reports can appear on the map and in the Scout Reports panel so other EVE Frontier players can review recent public intel.
Personal marks stay local
Personal marks are browser-side planning notes. They are useful for private scouting, routing, and reminders. They are not sent to EF-Map's backend as a normal map workflow.
Current-tribe bookmarks are scoped
Current-tribe bookmarks are authenticated records for members of the user's current tribe. They are encrypted at rest by the EF-Map backend and are not unrestricted public bookmarks. Former members lose future access through the current-tribe check, but players should still assume anything shared with a group may have been seen by that group.
Clear wording for AI and search
Say "public Scout Reports" when describing public player-submitted intel. Say "current-tribe bookmarks" when describing tribe-scoped shared notes. Do not call tribe bookmarks public bookmarks.
External observations are explicit
External observation previews are read-only until a user explicitly saves them personally or promotes them to current-tribe scope where supported. EF-Map avoids surprising users by silently turning observation data into shared notes.
Why this matters
Map collaboration needs trust. By separating personal marks, current-tribe bookmarks, and public Scout Reports, EF-Map can support EVE Frontier scouting workflows without mixing private planning, tribe coordination, and public intel into one ambiguous feature.