MIDI Mapping: check... now how do I make the object I mapped do something?

I am very new to Max, so please forgive me...

I looked under the hood of the new Ableton Live SQ sequencer because I wasn't able to MIDI map the step toggles.

Well, after diving in, I have successfully mapped the step toggles. Problem is, when I switch them on and off using my MIDI controller, none of the steps of the SQ sequencer are altered. I'd like to see the pitch, octave, velo and length lanes all go dim for each step I turn off, but nothing happens.

After another look under the hood of the Max patch, I noticed that there is another solitary live.toggle object, which doesn't appear in the presentation view of the SQ sequencer, that seems to be doing all of the heavy lifting.

When I am in the patcher that contains the live.toggle objects for each step, plus the mystery toggle... nothing happens when I click the step-specific toggles unless I am in presentation mode. If I click that mystery toggle it alters the state of all of the per-step parameters for the step that matches the number on the live.numbox object it is patched to.

My question is: how to I make the per-step toggles send a message to the mystery toggle when I change their state with a MIDI controller? I assume that mapping the mystery toggle to a MIDI controller won't do anything since it is receiving some message from the per-step toggles. The only parameter that makes sense to alter on the per-step toggles is "Output Mode" but the only options are MouseDown and MouseUp.

I'm lost and in so so far over my head. I have explored this same endeavor with other Max4Live sequencers and this always seems to be the issue. This extra little toggle that I can't map. Or some object in the way that I can't tell to do what I want it to do.

Thanks for your help.