Store an integer on a kingdom; survived save/load and restart in the tested scope.
API Explorer
API Explorer
Section titled “API Explorer”You should not have to know the exact method name before opening the documentation.
API Explorer
Search by the job you want to do, not only by exact method names.
Store an integer for a party; restart and inactive lifecycle were tested.
Event Bus exact/wildcard dispatch, cleanup and exception isolation.
Registration and execution of political actions/conditions/effects in tested branches.
Public zero-arg read; the canonical live sample returned 76, stability=same.
Parameterized query using an ActorTrait from runtime Actor.traits[].
Public City read; sample=100, owner=CityManager.dict.
ID came from a City.buildings_dict_id dictionary key; result=1.
Public Kingdom read; sample=14468, stability=same.
Public Building→City reference read.
Public WorldTile height read; canonical sample=210.
Read-only tile occupancy helpers; sample true/false.
Zone ID 0 came from a real _zones_dict_id dictionary key.
Eight selected ActorData fields produced exact delta + exact restore with no residual/collateral fields.
Verified-Lifecycle: pinned manager/owner/registry cleanup plus 50/50 stale reads.
Verified-Lifecycle through CityManager F:dict and Kingdom F:cities.
The same Building remained in pinned manager+owner for 30 frames; no permanent-persistence claim.
After all remaining cities were destroyed, the Kingdom stayed registered with zero cities for 120 frames.
The Explorer now mixes two clearly scoped surfaces: the earlier runtime-tested PoliticalWorldAPI baseline through WBML-0005 and selected canonical WorldBox internals from WBML 0.3–0.6. Every item shows its own evidence scope; raw/internal WorldBox evidence is not presented as PoliticalWorldAPI.