@rogercooper
As a alternative to the Feudal Japan approach a custom game property RUS AI can be set manually if Russians are to be played by the AI.
<property name="RUS AI" value="true" editable="true"/>
"movementRestrictionTerritories" is a player "RulesAttachment", a trigger can overwrite the value.
<attachment name="rulesAttachment" attachTo="Russians" javaClass="RulesAttachment" type="player">
</attachment>
<attachment name="conditionAttachmentRus1" attachTo="Russians" javaClass="RulesAttachment" type="player">
<option name='gameProperty' value='RUS AI'/>
</attachment>
<attachment name="triggerAttachmentRus1" attachTo="Russians" javaClass="TriggerAttachment" type="player">
<option name="conditions" value="conditionAttachmentRus1"/>
<option name="when" value="before:russianPurchase"/>
<option name="playerAttachmentName" value="RulesAttachment" count="rulesAttachment"/>
<option name="playerProperty" value="movementRestrictionTerritories" count="India:15 Sea Zone"/>
<option name="playerProperty" value="movementRestrictionType" count="disallowed"/>
<option name='uses' value='1'/>
</attachment>
I'm only testing the trigger once based on "RUS AI". To apply/clear movementRestrictionTerritories based on the ownership of India, I think you would need 2 opposite triggers based on conditionAttachmentRus1.
If RUS_AI: trigger1 (set movementRestrictionTerritories)
else: trigger2 (clear movementRestrictionTerritories).