# Original published marker caches

Research image: pinned `6891f70a021fa9f3a0e00458c284f48d1226e68ae7fc02ad48081aed47857e93`, `artifacts/ship-model-reference/client-copy/EliteDangerous64.exe`. Research outputs are in `artifacts/galaxy-query-research/published-markers/`. Current adapter guards use independently verified ED5A profile values; old and current images are not interchanged.

## Community goal systems

The original map constructor `3AC8AC0` binds registered type ID global `5FA10F0` at map object `+88`. The original map marker producer `3AFF080` tests setting 16 (`CommunityGoalMarkers`), calls this interface's slot `+18`, then enumerates the returned container's count at `+10` and vector at `+18`. Each original 64-bit system address is passed to `3B8C0C0` with marker type 7. The original marker name table identifies that type as `CommunityGoalMarker`.

Type getter `3A4C090` belongs to vtable `5527840`. The shared manager constructor `3A0E740` installs that interface at manager `+60`, together with its main vtable `55276E8` and owner at `+10`. This is the same original manager that publishes the Thargoid panel, through a separate interface. The community-goal getter `11D3BF0` is exactly `lea rax,[rcx+1B8];ret`. Consequently, its published container is manager `+218`, with capacity `+218`, count `+228`, and address vector `+230`. The constructor clears these four words; the destructor `3A12FF0` frees the vector at `+230`.

`thargoid-account-sources/compatibility.json` and `cg-shared-interface-compatibility.json` independently close the ED5A equivalents: interface `5527810`, main `55276B8`, secondary `55276E8`, type getter `3A4BFF0` reading the same `5FA10F0`, and list getter `11D3B50` with all eight instruction bytes identical.

`Navigation.GalaxyAccountCommunityGoals.cs` copies only this original published list on the game owning thread. It verifies registered source, vtables, owner, bounded header and row bytes before and after copying. It invokes no original method and never fills the list from historical journal records. Original ordering and duplicates are retained. It does not infer goal names, goal IDs, subscription status, expiry or rewards from a system-only container.

The result explicitly has `complete=false`: a readable empty container is not proven to be a complete current community-goal board or current account subscription answer. Current-game live freshness has not been verified. `XFENavigationGalaxyAccountCommunityGoalsSelfTest` expects 255 and passed in the isolated production-source fixture, including precision above 2^53, empty-list semantics, source/owner guards, malformed headers, invalid IDs, no native writes and independent copied buffers.

## Mission source, subsequent closure

The same marker producer's setting 15 branch resolves current player context through map `+C0` and type global `5F53244`, then uses that mission interface's `+70` and `+100` accessors. `+70` is `1F28D0`, exactly `lea rax,[rcx+40];ret`, returning a vector of original mission pointers. Each mission is tested through `+D8/+E0`; selected missions return their system address vector through `+78`, and the producer marks those systems with type 45. The aggregate `+100` systems are marked with type 4. Original registration `20E9C00` binds manager `+58`; interface vtable is `525EF78`, and constructor is `208CD90`.

The subsequent bounded reader closes manager ownership, the normal/failed derived tables, the selectable-list producer, complete ordered address extraction and the complementary marker4/45 predicates. Current details and limits are recorded in [fleet and mission evidence](galaxy-original-fleet-mission-evidence.md). The adapter copies only the current published manager source and reports `complete=false`; current-game freshness and the whole translated visible list remain unconfirmed. It has been built and tested in an isolated fixture, without installation or original game calls.

The original icon leaf `3A4E940` and its actual table at `3A4EB28` select `GM_DisplayOptions_Missions` for4 and `GM_Marker_MissionComplete` for45. Both original resources are available. Runtime UI styles retain these two codes independently from the common mission filter/display key, including two mission types at the same system. No Journal status is used to invent the original completed-marker type.