InkBridge Architecture Unity and Ink stay fully decoupled. Unity owns the world — collision, player state, clue tracking. Ink owns all narrative output. InkBridge.cs sits between them: Unity calls knots by name, Ink returns text and tags, InkBridge fires Unity events in response. Neither system reaches into the other directly.