Rule registry · AG-001

Orphaned action

Checked by the Agentforce scan. Severity low.

AG-001LowGrounding Integrity

What it requires. An agent action that is defined but attached to no topic, so no agent can ever reach it.

Why it matters. An orphaned action is configuration that looks like capability. It appears in the action list, it is counted when someone asks how much the agent can do, and it never runs. The planner routes through topics, so an action outside every topic is unreachable by construction rather than by accident.

How to fix it. Attach the action to the topic that should own it, or delete it. Leaving it in place makes the agent look more capable than it is.

Source. Agentforce planner model: actions are reached through topics

Is this rule worth checking?

Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.

Every rule we check, every source, and every one we turned down