The AutSide Podcast

At the end of two converging series, the question changes: meaning does not overflow into language. Safety, stability, access, and meaning time allow a superpositional field to resolve. The word is only the trace.
This is the epilogue to What Has to Happen for Meaning to Become Language?—and it arrives as the simultaneous series on Sensual Residue is also reaching into questions of field, dimensionality, access, and what remains alive before resolution. I did not expect the two series to meet quite here. But at the end of this long journey through Stage 0, the Script Garden, Shakaman, cognition, concept, sign, and the extraordinary machinery hidden behind successful language, I think the original question has changed. Perhaps I have been looking for a pathway when what I needed was a geometry.
That became clearer when someone recently described my cognitive experience back to me as “parallel processing that cannot serialise”—a mind holding too much at once and therefore requiring an external container for the overflow. The description was thoughtful and sympathetic. It was also wrong. Parallel versus serial is still binary. I continually describe my experience as superpositional. There is no container becoming full. There is no overflow. It is all there—and some of what eventually becomes discrete enough to name may not yet exist as discrete things at all. Shakaman’s architecture can be written sequentially, but analytical sequence does not necessarily describe cognitive mechanism.
In my dimensional model, field resolution requires safety within the lower dimensions. Stability permits sustained access. Sustained access permits entry into meaning time. And the fifth dimension is where the question at the centre of this series becomes capable of resolution: the superpositional field can resolve sufficiently for meaning to become linguistically available. Technology has changed what I can do there because I now have machinery I can trust with portions of the processing—holding intermediate structures stable, recovering relationships, testing formulations, and giving me different doorways back into the same field. Nothing has been emptied from my mind. Nothing has become serial. More has become resolvable.
Sometimes that resolution becomes a sentence. Sometimes, after years, it becomes a book. And then I want people to take those books—teach them, build courses from them, disagree with them, and carry the ideas somewhere I never could. That delights me. That was the point. But the thing I eventually managed to make sayable is not the machinery by which I came to know it. A fluent sentence cannot tell you how it became possible, and a book cannot tell you the shape of the cognition that produced it. The word comes late. The trace is not the machinery. Language may be the lower-dimensional trace of a resolution that became possible elsewhere.
The AutSide is a reader-supported publication. To support my work, consider becoming a paid subscriber.



This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit autside.substack.com/subscribe

Pain, questions, medical trauma, a former name, and one effortless she. What happens when a hospital demands sequential answers from an autistic gestalt processor experiencing the whole field at once?
This was supposed to be another Sunday Mornings with Jaime & Cathy. Instead, I became quite ill, missed the timing for our conversation, and spent part of the week moving through urgent care and hospital. But somewhere between the pain scale, the laboratory, the ultrasound, the questions, and the accumulating uncertainty, I realised I was living the question I have spent this entire series trying to understand:
What has to happen for meaning to become language?
An autistic gestalt processor with a very visibly obvious medical problem goes to hospital—and almost immediately, she is asked to take the whole of it apart. Rate the pain from one to ten. Describe the onset of symptoms. Tell me what happened first. What changed next? Have you ever been known by another name? Each question asks for something small and sequential, but the experience from which the answer must be extracted is neither small nor necessarily sequential. Pain, memory, sensory information, medical history, uncertainty, social inference, institutional power, and the unfinished residue of every previous interaction can remain informationally alive at once.
The answer that finally emerges conceals that labour. A pain score becomes seven. An enormously complicated history becomes a neat chronology. A former name becomes an entry in a database. The hospital receives Stage 1—the language. I am living everything that has to happen to get there.
And then a nurse speaks to the doctor and effortlessly calls me she. Nothing happens. That is precisely the point. I do not have to correct her, assess whether correction is safe, recover from being misgendered, or reconstruct the sentence I was forming before the interruption. The medical problem simply remains the medical problem.
Sometimes support is not another thing added to the field. Sometimes support is what allows something to leave it.
So this Sunday morning is a little different. It is about pain, medical care, autistic processing, and what becomes visible when the demand for language arrives whilst the whole of experience is still alive.
Do not mistake the answer for the process that made the answer possible.
The AutSide is a reader-supported publication. To support my work, consider becoming a paid subscriber.



This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit autside.substack.com/subscribe

A new school year means new students, new relationships, and a Script Garden filling with meaning. But how does any of it become usable language? I’m starting with the question between Stage 0 and Stage 1.
It is the beginning of another school year, which means I am back in the Script Garden. New students on my caseload. New students in the Maths classes I support. New teachers, new classroom dynamics, new relationships, and an enormous amount of information arriving all at once. I am paying attention to all of it. Rather spectacularly so. But thinking about something and having usable language for it are not the same event for me.
At Stage 0, there is already a great deal there: scripts, patterns, memories, sensations, observations, language, relationships, notices, wonders, and things other people have said. It isn’t empty. There is something almost superpositional about it—multiple possibilities remaining simultaneously alive whilst new information keeps arriving. A student may understand. They may not. They may understand the mathematics but not its language. They may understand both and not yet trust me enough to show me. I don’t necessarily want to collapse those possibilities too early, because sometimes that is precisely how I get a student wrong. Meaning is forming. There just may not be a sentence yet.
But eventually I need one. I am an RSP teacher. I have students to support, teachers to collaborate with, IEPs, meetings, documentation, and decisions to make. At some point I have to step out of the Script Garden carrying a word. And that has left me with a wonderfully inconvenient question: How do I actually get from Stage 0 to Stage 1? What has to happen for meaning to become language? Sometimes I know the whole before I can find its parts. Sometimes I know that a sentence is wrong before I have any idea what the right sentence would be. What, exactly, is happening in between?
This is very deliberately N = 1. I am not speaking for all autistic people, all gestalt language processors, all RSP teachers, my colleagues, or my employer. I am following my own problem of practice. My ASD Level 2 diagnosis matters here because much of the support I need has to be constructed by me: externalising information, collecting it, parking it somewhere safe, returning to it, moving it around, letting patterns emerge, and eventually developing words and scripts stable enough to use when I need them. That is accommodation, but it is also simply part of how I make my work possible.
So this video is a prologue, not an answer. I don’t know where the question is going yet. I’m going to do what I tend to do on Substack: collect things, park them, play with them, and see what grows. Somewhere inside that rather overgrown Script Garden, I am hoping to understand a little more about what has to happen before all that meaning becomes something I can actually say—and, with any luck, come out the other side with enough usable words and scripts to remain employed for another year.
The AutSide is a reader-supported publication. To support my work, consider becoming a paid subscriber.



This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit autside.substack.com/subscribe

What if reducing workload is not about doing less? This episode explores Quantity, Concurrency, and Content—and how real support can give unfinished information somewhere else to wait.
I put yesterday’s AutSide piece into Gemini Notebook because I wanted to hear what happened when the argument was handed back to me in another form. The resulting conversation begins with the deceptively simple arithmetic of workload reduction: if twenty problems become ten, surely the work is now half as heavy. The hosts quickly discover the problem I was trying to name in the essay. Once we move from physical quantity into cognition, the arithmetic stops behaving so neatly. A single problem can carry directions, retrieval, intermediate results, formatting expectations, uncertainty, and unresolved information simultaneously. Cutting the page in half does not necessarily cut any of that in half.
What I particularly enjoyed hearing them work through was the distinction amongst Quantity, Concurrency, and Content. Quantity is what schools can easily count. Content is what I actually need a student to know or demonstrate. Concurrency is the less visible part between them: how much information must remain alive at once for the student to continue. The episode reaches for the image of fifty browser tabs—not fifty extraordinarily difficult things, simply fifty things that have not been permitted to close.
The discussion becomes most interesting to me when it turns from explanation towards practice. If retrieval is not the Content I am assessing, I can provide the formula. If an intermediate result needs to remain available, I can give it somewhere outside the student to wait. If several instructions are competing simultaneously, I can change their arrangement. The student still has to understand the mathematics, science, history, or language in front of her. I have not necessarily reduced the intellectual demand at all. I have changed where the unfinished information has to live. The episode puts this rather nicely: the human does the processing; the tool can do some of the maintaining.
And I was glad that the conversation followed that idea into special education itself. This is why the work cannot be reduced to sitting beside a student and keeping her “on task.” To reduce a workload without accidentally reducing the learning, I have to understand what is load-bearing in the assignment in the first place. The episode describes that as finding the load-bearing walls of the Content—knowing what can move, what can be externalised, and what must remain. That is specialised intellectual labour, performed across students, teachers, subjects, and an entire school day.
A style note here, because I know this will matter to some readers: yes, I know Gemini Notebook is AI. I have disclosed my use of it before, and I am disclosing it again here. This episode is another demonstration of why the tool has become valuable in my life. I put my article—my research, my argument, my thoughts, my writing—into Notebook, and it explains the whole back to me in another form. Sometimes I need that. When I have spent days working from inside an idea, hearing an automated system reconstruct the complete gestalt helps me check whether the whole I thought I had written is actually the whole that made it onto the page. It can expose a missing relationship, an ambiguity, or simply reassure me that the architecture holds together. The tool is not originating the thought for me; it is giving my thought back to me so that I can inspect it from outside. I can error-check that reconstruction against what I actually wrote, and then choose to share the result with subscribers and followers. For me, that is not an embarrassment to hide behind euphemisms about technology. It is support.
The AutSide is a reader-supported publication. To support my work, consider becoming a paid subscriber.



This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit autside.substack.com/subscribe

I do not use Gemini Notebook because I need it to think for me. I use it because too much thought remains alive at once. Essay, timeline, infographic, podcast—different doors into the same relational whole.
I keep returning to Gemini Notebook because it does something I genuinely need—not because I need it to think for me, but because I need support moving through the world of words once too many of them become alive at the same time. My difficulty is rarely the absence of thought. It is almost embarrassingly the opposite. Sukhareva is there. Peters is there. Prizant, Nelson, Kanner, Shaqaman, contemporary Chinese scholarship, developmental psycholinguistics, the Naysayers, my own nine essays, their citations, the disagreements amongst them, the historical changes in terminology—all of it remains available simultaneously. I know the shape before I know how to walk another person through it. As I wrote in the piece, the expensive part is often moving from that relational whole into the selective, sequential form through which somebody else can encounter it. That is where I require substantial support.
Notebook has become part of that support infrastructure because it gives me several different ways of moving through the same material. I can give it my own articles, research, arguments, and sources, then ask it to help me reorganise what is already there. An infographic lets relationships coexist spatially. A timeline lets chronology become the organising structure. A mind map lets me move amongst relationships without pretending they arrived sequentially. And now there is this podcast—a conversational rendering of the same informational field. None of these replaces the scholarship underneath them. They are different entrances into it. The original experiment was precisely this: could something that exists for me as a large relational whole be made available to somebody else without requiring them first to reproduce my entire journey through thousands of words?
And I rather love what the podcast notices about the actual argument. It begins with the absurdity at its centre: a century of researchers can repeatedly encounter recognisable patterns in autistic language, but those observations become remarkably easy to erase if we search backwards demanding contemporary vocabulary. Sukhareva did not need the term gestalt language processor for the children she observed to be there. Neither did Kanner, Peters, Nelson, or Prizant. Different researchers brought different questions, theories, disciplines, languages, and desired outcomes, but the humans did not vanish between those frameworks. The podcast compresses this beautifully: “The humans didn’t change, just the lexicons did.” That is very close to the historical gestalt I have been trying to make visible—the lexicographers change; we remain.
What becomes especially striking, though, is that the podcast itself eventually turns towards the reason I am using Notebook in the first place. It describes the problem as trying to take a vast web and force it into a single straight piece of string—the researchers, dates, clinical disagreements, frameworks, and relationships all informationally alive together, whilst academic prose demands that I select one thing, then another, then another, paragraph after paragraph. Notebook can hold some of that intermediate organisational labour for me. That matters. My support need does not disappear because I can eventually produce fluent prose. Successful language can conceal an extraordinary amount of machinery. Here, some of that machinery is external, visible, and twenty dollars a month.
Perhaps that is why I find this podcast so delightful. I wrote the research. I followed the citations. I made the historical argument. Then I gave that body of work to a tool that could return it through another doorway—and, listening to two synthetic voices discuss why an autistic researcher might need multiple representational forms to move a relational whole into communicable language, I find the form becoming part of the argument. Essay, infographic, timeline, mind map, podcast: not five different thoughts, but five ways into the same one. Accessibility does not mean finding the single simplified version through which everybody must enter. Sometimes it means allowing the whole to have more than one door.
Here’s the link to the source article with the complete reference list: https://autside.substack.com/p/we-have-been-here-all-along
Let me know what you think.
The AutSide is a reader-supported publication. To support my work, consider becoming a paid subscriber.



This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit autside.substack.com/subscribe