Pinky Shim and Resilience
These notes describe the deliberately small part of Pinky that sits closest to the game engine. It translates bounded host data and approved operations without moving general plugin logic onto the game thread.
Pinky also keeps a last-known valid local snapshot for qualified operations. If Brain is briefly late or unavailable, the game can use an explicitly safe recent value or native fallback instead of freezing while it waits.
Keeping Data Ready for the Game
This service keeps a small, validated local copy of the current framework values that host callbacks need immediately. Readers see one complete generation, not a half-written update. If Brain is late or unavailable, every value follows its declared stale or fallback rule. Sensitive actions still require current authority.
What Pinky Connects to the Game
Pinky connects to the game and watches what happens there. It turns those facts into approved data and shows safe views. It can do operations on the host but cannot change plugin rules or Brain’s state directly. Pinky also cannot turn host information into official identity.