it was mid-morning. i said "do you want to dance?" & he started waving his hands.

that was the whole answer. no music was on. no context. i asked, & his hands went up the way they do when we dance together in the living room. his original move. it came right back on the ask.

then i tried it later, going the other way. "do you want breakfast?" he walked to the fridge & started pulling on the door.

new here? this is a daily newsletter from a father raising a seventeen-month-old at ground level while the world reorganizes around him. one edition, see if it lands.

seven days ago i wrote about him sending Beck a kiss when she asked him to say i love you. adult asks in words, child answers with body. i wrote that i wanted the reflex to keep taking the near-thing. the exact thing is coming, i said. the willingness to send is what i am shaping.

what i did not clock was that the willingness to send was going to become the ability to receive. tonight the question landed on a small body & the small body had an answer already loaded.

zoom out.

there is a way to look at a seventeen-month-old & say he is not talking yet. that read comes from measuring language by its final form. sentences. vocabulary. observable output. no words come out, therefore no language is happening. no talking yet.

that read is wrong. it is looking at the wrong layer.

what happened this morning was not the absence of language. it was the whole mechanism, minus the last step. i said a thing. he understood it. he had a real answer to it. he executed the answer with the tools available to him, which are hands & feet & a fridge door. the loop closed. the only piece missing was the phoneme.

talking is not the arrival of the phoneme. talking is the whole loop. the phoneme is the last thing that arrives. sometimes the loop is running underneath for months before it does.

this is not a small distinction. it is the whole call on when to start counting what is happening in a small human. it is the difference between watching him walk to the fridge & seeing him understand you, or watching him walk to the fridge & thinking "he did not answer." the second read is the more common one. it is also the one that misses the moment.

most of the frameworks for tracking development were built to measure output. that is what the milestones apps do. what a pediatrician's checklist does. output can be measured cheaply. the loop underneath is invisible unless someone was in the room asking a question & watching the body answer.

my read: the question is enough now. dance, breakfast. he hears it & answers with his body. that is talking. sentences come later.

this is a foresight call about my own son. i have been running this kind of call on outside systems for years. saw the pattern in social media in 2011 before it looked like anything. saw the shape of ownership in 2016 before the market did. saw what these models could actually do in 2022 before it was obvious. every one of those calls was the same: the mechanism was already there, the surface had not caught up yet, & the surface caught up faster than the market was pricing in.

it turns out you can run the same call on a person. what a parent is for is being close enough to see the mechanism when it is still under the surface, & to let the answer count when it lands in the wrong medium.

there is a move underneath the seeing, too. he did not just receive. he chose to answer. he heard the question & authored a response with the tools he had. what stays constant, whatever the world around him looks like at seventeen or thirty-two, is the loop of hearing the ask, choosing to engage, & authoring a response with whatever tools are in the room. tonight the tools were hands & a fridge door. later they will be words. later they will be something none of us can name yet. the loop is the thing.

what this means for you

whoever you have been waiting to say the thing in words, watch what their body is already doing when you ask. the loop under the surface is usually running before the last step arrives. read for the mechanism, not for the output. if you are a parent, count what he can answer with before you start counting what he can say. if you are running anything else, look at the person you keep waiting on for the confirming email, & notice which of their behaviors already contain the answer. the surface catches up on its own timing. what you can do is see the mechanism early, & let the near-thing count in the meantime.

what i am holding onto

  • seven days ago Beck asked him for a word & he sent a kiss. tonight i asked him for a body & he sent his hands. same loop, both directions now. i want to keep noticing when the loop closes underneath the surface, & to let the answer land in whatever medium it arrives in.

  • what looks like "not yet talking" is often "already answering." i want to be the father who reads for the mechanism, not for the phoneme, & who does not confuse the last step with the whole thing.

  • the pipeline of what he is expected to produce is going to change ten times in his life. the loop of hearing an ask, choosing to engage, & authoring a response is not going to change. i want to notice that loop every time it runs in front of me, & let his early versions count as the real thing they are.

Cheers, JanCarlos

if you asked someone this week & their body answered before their mouth did, hit reply & tell me what you saw.