[Verse 1]
When deadlines matter and time runs short
Recovery time objectives need support
Real-time requirements with SLA demands
ACE can't capture what timing commands
Sequential steps in incident response
Need procedural flow with clear pronouns
[Chorus]
Know when not to use it, save yourself the pain
Temporal and procedural, deontic domain
Must and may and shall not, obligations clear
ACE breaks down completely when these needs appear
Know your limitations, choose the right design
Some problems need solutions of a different kind
[Verse 2]
Deontic logic separates the three
Permission, obligation, what's prohibited, you see
When reasoning depends on modal distinction
ACE provides no helpful jurisdiction
Must versus may versus cannot do
These subtle differences ACE can't pursue
[Chorus]
Know when not to use it, save yourself the pain
Temporal and procedural, deontic domain
Must and may and shall not, obligations clear
ACE breaks down completely when these needs appear
Know your limitations, choose the right design
Some problems need solutions of a different kind
[Bridge]
Non-technical stakeholders need to read
Plain language policies fulfill their need
Training overhead becomes too high
When executives just want to understand why
Business readability trumps formal precision
Choose your tool to match your mission
[Verse 3]
Step-by-step procedures can't be expressed
In ACE notation, you'll be stressed
Workflow sequences need different grammar
Time-based controls require planning's hammer
Recognition saves you wasted hours
Know your formal language's powers
[Chorus]
Know when not to use it, save yourself the pain
Temporal and procedural, deontic domain
Must and may and shall not, obligations clear
ACE breaks down completely when these needs appear
Know your limitations, choose the right design
Some problems need solutions of a different kind
[Outro]
Match the tool to problem space
Wrong choice puts you out of place
ACE has limits, understand
Choose wisely for the task at hand