# Runtime Effect Kind-8 Late Bringup Note

This note extracts the current grounded late-bringup facts for the ordinary startup
runtime-effect lane, so the remaining recovery work does not have to keep jumping between the
queue, the large function map note, and the broader subgraph artifacts.

## Grounded Ordering

- `world_load_saved_runtime_state_bundle` `0x00446d40` directly reaches
  `scenario_event_collection_refresh_runtime_records_from_packed_state` `0x00433130`.
- The same loader does **not** directly reach
  `scenario_event_collection_service_runtime_effect_records_for_trigger_kind` `0x00432f40`.
- `world_entry_transition_and_runtime_bringup` `0x00443a50` is the owner above both restore and
  service.
- Current `function-map.csv` notes for `0x00443a50` already state that:
  - the tagged load phase reloads event runtime records through `0x00433130`
  - the one-shot kind-`8` service through `0x00432f40` only runs much later in the final
    reactivation tail
  - shell-profile latch `[0x006cec7c+0x97]` is cleared after that late kind-`8` service

## Late-Tail Candidate Branches

- The remaining unknown is therefore no longer abstract restore-vs-service ordering.
- The remaining unknown is:
  - which late bringup branch or retagger between `0x00433130` reload and final kind-`8`
    `0x00432f40` service materializes the live mutation-capable records

## Post-Load Scenario Fixup

- `shell_apply_scenario_name_specific_post_load_world_and_object_fixups` `0x00442c30`
  is called from `0x00443a50` at `0x00444b50`.
- This branch is currently **prose-first**, not graph-first:
  - a direct subgraph export on `0x00442c30` collapses to the seed node
  - the useful evidence lives in the grounded function-map note rather than note-reference edges
- The function-map note grounds several concrete mutations across collections rooted at:
  - `0x0062be18`
  - `0x0062bae0`
  - `0x006ada80`
  - `0x0062b268`

## Explicit Trigger-Kind Retags Already Grounded

- `SP - GOLD` branch at `0x00443526`
  - rewrites `[event+0x7ef]` from `1 -> 5`
  - live runtime-event id `1`
  - gated by `[world+0x66de]`
  - checked payload root kind `7` with subtype byte `5`
- `Labor` branch at `0x00443601`
  - rewrites `[event+0x7ef]` from `0 -> 2`
  - live runtime-event id `0x0d`
  - gated by `[world+0x66de]`
  - checked `0x3c -> 0x3d` child payload pair with the matched negative scalar sentinel

## Current Best Next Recovery Question

- Which late bringup branch between:
  - `0x00433130` reload
  - `0x00442c30` scenario-name post-load fixups
  - and final kind-`8` `0x00432f40`
- is responsible for the live kind-`8` records that already carry mutation-capable compact payloads
  in ordinary nondirect bundles.
