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.

Pinky Local Resilient Snapshots

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.

Pinky Shim Boundary

The Pinky Shim Boundary is the edge of the framework that connects to the local host. Pinky watches host facts and turns them into approved data. It shows approved views and does safe operations on the host. Pinky cannot make plugin rules or change Brain state directly. Pinky cannot turn host info into official identity.