Expanding module collision detection
Privatizing command constants

I don't want these bleeding beyond their boundaries; Yes I can step
around this, but its a major inconvenience to direct access the
command. Its a bit of vinegar to discourage an developer from breaking
the boundary (of which I'm already doint that).
Adding rudimentary documentation

This is to appease rubocop now that many of the constants are
private.