Design
Tcllian embeds a Tcl interpreter into Trillian Pro. Trillian loads Tcllian into its main thread, therefore any work Tcllian does is done in Trillian's main thread, so Tcllian work must be fast as to not disrupt the user experience.
The primary Tcl interpreter (to be refered to as "master interp" or just "interp") therefore runs within the context of Trillian's main thread. This is important because Trillian's interface for plugins is primarily through callbacks, which means the callbacks get invoked in Trillian's main thread. Since Tcl interpreters can only be accessed from the thread in which they were created, Trillian's callbacks can only access the master interp.
(TODO: describe Tcllian thread API and how to pass stuff between master interp and slave interps.)