# eXplore presentation and integration

The public MCP reads avatar metadata and prepares billboard content. Native UI editing and a fresh consuming view are still needed for scene placement, visual avatar evaluation, billboard creation and sharing. No arbitrary scene-save endpoint is exposed here.

Choose avatars by the work represented: engineering definition, electrical/FPGA work, manufacturing, verification, operational execution or sustainment. A computer beside an aircraft may depict flight test and is not a generic engineering icon. Inspect the library image and name, test its actual 3D appearance, and check the target process. Reuse native industry aircraft scenes for thread backdrops and project images when appropriate; verify card framing after saving.

Subway Maps can coexist in the native Digital Threads map list. Separate capability navigation from phased implementation navigation, retain the default intentionally, and verify the map opened by the actual share/startup link. Do not promise a universal eXplore map switcher: the supported runtime picker/startup contract has not been established by this package.

Native broad domains are Design, Realize and Optimize; individual catalogs can define additional display areas. Assign each stage by meaning. Realize can map to Manufacturing or Execution, verification to Test, and Optimize to Sustain. Keep WIP threads visually consistent, for example one shared gray for thread and all path segments, with monotonic stages across the correct domains. Gray is a visual signal, not a native validation status.

## Layout persistence discovery

An exercised web-client integration uses POST /IntegrationAPI/api/integration/explore/getExploreData with objectId, objectType string Project or Catalog, dataKey subway and authoringMode. Project authoring data and user overrides can differ. storeExploreData accepts the corresponding data and lastModified. A successful response is insufficient: independently read the applicable source/override and reopen the consuming view. Use exact baseline/timestamp guards and preserve unrelated scene data. These are observed private web endpoints, not a supported API guarantee or an exposed MCP tool.

The scene data can be base64 Odin binary (Explore.L0Platform+DB), with shared references and unknown metadata. Do not deserialize arbitrary runtime types or replace the scene with a guessed JSON object. A future typed layout tool needs a safe primitive parser, bounded synthetic fixtures, preservation checks and measured native readback. This release deliberately excludes task-specific binary scene editors.

## Billboards

Establish native Trend -> Challenge -> Possibility relationships. solutionlink_prepare_billboard expands those relationships into a local content blueprint. In native eXplore use Dynamic Tools > Value Map Billboards > Create a New Billboard, name it and Add Trend. Verify that linked Challenges/Possibilities appear. Reopen it in a fresh launch to verify persistence. Same-profile persistence does not prove cross-device or global sharing. Upload to all Users is a separate publication action and needs task authorization. Badges are not asserted to represent ROI.

## Embedding

The vendor external/share button supplies a starting link, but authenticated iframe startup can fail on session expiry, identity-provider framing or host-specific sign-in. This release does not solve that contract. Ask the vendor for supported origins, frame policy, external launch parameters, session refresh and identity flow. Never proxy another user's authentication or publish signed startup credentials. A separately hosted 2D BPMN XML viewer is a useful snapshot alternative, with explicit refresh/provenance and appropriate customer-data access controls.


## Production S2CD embedding follow-up, November9,2026

Read the [Saber production embedding results and project-only durable access request](https://explore.xcelerator.us/saber-embedding) and [technical requirements](https://explore.xcelerator.us/docs/saber-embedding.md). Actual production-origin share routes failed at framed sign-in; direct eXplore loaded its shell and reported session expiry. No supported authenticated embed or persistent project grant is enabled. This is a supplemental site report, not a change to the MCP0.4.0 ZIP.