Execution policy
Execution policy controls the handling of calls outside missions and links to change-approval and signature policy. Each section edits real township configuration.
- Console address
/townships/ :townshipId/ governance/ execution-policy - Console section
- Township · Governance
- Reviewed
- 14 October 2026
Controls and behaviour
Legacy preserves outside-mission behaviour. Observe records calls that enforcement would refuse. Enforce refuses unbound external calls. Saving changes the township's outside-mission posture.
Access and limits
Calls already bound to a mission are always screened. Enforce can refuse scheduled, webhook and action-step external calls because those tasks are not automatically bound. Change-approval and signature rules are separate controls, not another name for mission authority.
Related API endpoints
Console addresses and API addresses are different. These endpoints use authenticated console access and server-side authorisation.
/api/profiles/{profileId}/governance/postureCurrent posture.
/api/profiles/{profileId}/governance/postureBody contains posture: legacy, observe or enforce. Requires governance.write.
Related pages
Need more help?
Open Mysaria from the console header to ask about the page you're on, or send work to an agent in your township.