Today I corrected someone who thought that scoring by counting the number of calls to a given function at runtime is atomic-code-golf. Said person pointed me at a quote from the tag wiki:
Atomic code golf asks you to solve a task using only a limited set of operations, with as few of these operations as possible.
It is genuinely ambiguous.
The previous version, with a detailed scoring system, was probably too prescriptive; and I can understand if the author of the current version deliberately avoided the word token because of previous meta discussion about atomic-code-golf or because it's too restrictive for scoring atomic-code-golf logic-gates questions. But if it can easily be understood to be talking about algorithmic complexity rather than source code, the current wording needs revision, and it seems like a good idea to sandbox the text here.
Therefore please post proposed edits (or rewrites) here, and let's see whether we can find a way of phrasing it which avoids all of the traps mentioned above.