2.3 KiB
2.3 KiB
SCUM transitional ownership audit
This audit records the five transitional deliveries that placed SCUM behavior in the platform. They are migration input only; new writes must use the declared plugin bundle and Companion channel.
| Transitional platform area | Existing ownership | Plugin-owned replacement | Migration dependency |
|---|---|---|---|
api/game_player_handlers.go, service/game_players.go, domain/game_players.go |
SCUM player profiles, sessions, risk projections | features/players page data projected from declared scum.login/scum.logout semantic events |
Companion parser and event uploader |
api/game_map_trajectory_handlers.go, service/game_map_trajectories.go, domain/game_map_trajectories.go |
SCUM map conversion and trajectory projection | features/trajectories catalog and page projection |
A verified server-side source; otherwise the page remains unavailable |
api/game_gift_handlers.go, service/game_gifts.go, domain/game_gifts.go |
SCUM catalog and grant workflow | features/rewards contracts plus declared protected request handlers |
Available server-bound handler and approval |
api/game_player_handlers.go, service/game_player_state_patch.go, domain/game_player_state_patch.go |
SCUM field catalog and state-patch approval | features/state-patches declarative field catalog and protected request handler |
Runtime schema availability and approval |
components/ScumFileConfigWorkbench.tsx |
SCUM configuration workbench | SCUM page bundle configuration catalog | Companion config.read/config.patch availability |
components/GamePlayerIntelligencePanel.tsx, GameGiftCatalogPanel.tsx, ScumMapTrajectoryPanel.tsx |
SCUM panels imported by the host | SCUM page bundle module | Generic manifest bundle validation and plugin-page host |
contracts/scumOperations.ts, schemas/scumOperations.ts |
game.scum host branch |
manifest-driven bundle contract | Generic page-bundle registry |
The generic platform primitives retained by this change are server-scoped authorization, manifest validation, bundle identity/version validation, typed game-client command delivery, idempotent command completion, snapshot/event retention, audit linkage, and unavailable-feature responses. No transitional record is treated as proof that an executable SCUM capability is available.