Your Coding Agent Changed an ACL in 26 Seconds. What Are the Consequences? The Intelligence Layer for ServiceNow

Your coding agent changed an ACL in 26 seconds. The pull request shows two lines. What it doesn't show: which roles gained access, which records now depend on that change, and what else moved underneath.

A ServiceNow app isn't just code. It's roles, ACLs, business rules, tables and the relationships between them. As agents like Build Agent, Claude and Codex write more of our apps, we need an intelligence layer: a live understanding of what the app is and what every change does. Agents use it before they write, and people use it to verify before anything ships.

In this session I'll walk coding agent's change through the full layer, live on a real Fluent app:

Blast radius: see everything a change can reach, direct and transitive, hop by hop
Agent context: give the agent the exact facts it needs before it edits, over the command line
Validate: catch broken references, conflicting execution order and unsafe deletions while you're still working
Review and verify: see the consequences of the change (access, behavior, reach) before it's approved
Gate: enforce your team's rules in CI

Not on Fluent yet? This is the strongest reason to move: code-first ServiceNow can make every consequence visible before commit.

Built with Fluent-Graph, free and MIT-licensed, and the lessons from a year of building it.