Agency is the autobiographical comprehensive treatment — the book that traces the architecture back through the rooms it was already running in before there was a name for it. A Laotian-Chinese-Vietnamese-Canadian household with five languages on a Sunday afternoon. A scooter merging at speed in Ho Chi Minh City with a sleeping newborn. A husband apologizing in a kitchen at the wrong altitude. A walk along a Vancouver seawall where the same scene gets opened twice — once at the surface, once at depth.
The book moves through four movements. Movement I — The Lens. Seven chapters of felt experience that build the diamond from the ground up: the beach where a story was being written around the narrator without his consent, the multi-language home where identity was already running as a spectrum, the box spring that nobody drilled before the deal closed, the qualifier that sounds like humility and functions as exit, the architecture of the invisible firing at red lights and grocery belts, the board that voted before anyone in the room understood what they were voting on.
Movement II — The Architecture. Three chapters that name the structure the lens has been revealing: metacognition has altitude, the instrument is bilateral by design, the diamond regenerates fractally. The same geometry from Another Diamond, Another Hinge — but here it arrives after the felt installation, so the structure lands as recognition rather than as instruction.
Movement III — The Kitchen. A hypothetical demonstration of bilateral operation: a husband at M1, a wife at M5, an apology that is structurally complete and yet lands at the wrong altitude. The chapter teaches what bilateral failure looks like in clean form.
Movement IV — Organizational Scale. A community solar program. A sales-side team that climbed without drilling. Implementation consultants who drilled without climbing. The seam between them that procurement guarantees. The same architecture that ran in the kitchen, now scaled to a multi-million-dollar engagement, producing the same failure for the same structural reasons.
And then the book arrives at The Walk. Not a closing chapter. The structural keystone. Everything that came before is what The Walk is built on.
The Walk is the practitioner walking his own seawall — the route to drop the kids off at school — and watching the code run on himself in real time. A sign that fell over on the path. The scanning underneath every helpful act. Says who aimed at the deepest inheritance. The fortress of the lean-tos. The cold reply to Rebecca in his own kitchen with the awareness available and the code overriding it. "The awareness was there. The code was faster. The seeing and the doing were simultaneous — I was watching myself do it from inside the body that was doing it." The basement underneath everything: I am not enough. Three words written in the body of a child who didn't have the language to argue with them, organizing every layer above.
And the repair. At the dinner table, kids three feet away in their own world. Not I'm sorry about the tires. Not I'm sorry I was harsh. I weaponized my ability to climb to attack you. And I'm sorry. Aimed at the mechanism, not the event. By the same source that delivered the wound. The install run in reverse.
And then the walk back through every scene the reader saw at the surface in Movement I — the dating couple, the retired couple, the divorced couple, the swing dancers in the window — each one opened again at depth, the architecture visible, the reader having walked the whole path alongside the writer.
This is where the locus of agency lives — not in mastery, not in escape from the code, but in the going back. "Some days I find it. Some days I walk back." The earned field. Not the kid's open field. The one that exists on the other side of letting the code be visible and surviving the visibility.
For: the reader who wants the architecture in the most personal register the corpus offers. The book where the framework's autobiography is part of the proof — and where the practice itself is what the practitioner is offering, not the framework.
Companion works: Architecture of the Invisible shares this book's structural arc in a felt register; Another Diamond, Another Hinge covers Movement II at greater formal depth.
Movement I includes the chapter The Box Spring — eight rooms running one mechanism at radically different scales, from a box spring behind a couch to the renaming of an ocean. It has been surfaced here as its own page because the dimension it operationalizes — how task-level decisions today harden into bedrock through nothing but the passage of years — sits parallel to the bilateral dimension that Five Scenes operationalizes, and deserves a first-class architectural surface.
Read The Box Spring →I close my eyes. Take a deep breath. Not a thinking breath — a remembering breath. Walk with me.
Fall. The leaves change. The sweaters come back out. The air sharpens and the world gets narrower and something in you settles. It's time to focus.
Winter. Christmas. Family. The fireplace and the familiar. That week between Christmas and New Year's where you don't know what time it is — what day it is, for that matter. The world pauses and you pause with it. There's silence.
Spring. Promises of yesterday. Flowers start to bloom. The air is crisp. The sun seems to shine crisper. Sunglasses come out. People seem more cheerful — or maybe you're more cheerful and the world is just reflecting it back.
Summer. Love. Dreams. Possibility. Concerts and fairs and long nights that don't feel long enough. Passion — for something, for someone, for the version of yourself that only exists when the days stretch and the rules soften and the world feels like it's offering you something it wasn't offering in January.
But between spring and summer — there's a space. A breath. A pause. To prepare for what summer is about to bring.
Not one season or the other. The in-between. And it has a smell.
I was visiting a friend at her university. Nothing planned — just catching up, killing time. Her roommate asked if she could join us. Sure. The three of us hung out. Turned out we knew some of the same people — names overlapping, the world getting smaller.
My friend called it a night. I wasn't tired. The roommate wasn't tired. So we kept talking. And at some point — the way it happens when the conversation is easy and nobody's watching the clock — someone suggested the beach.
It's thirty-five minutes away. I drove.
We get to the beach. Nobody's there. Just us and the ocean and a moon so bright it makes the water glow. If you had to draw this up in a movie, this was the scene.
I'm not performing anything. I'm just there.
The mother on the scooter. She is merging into traffic at speed. The newborn is asleep on her lap. There is no helmet on either of them. A van is coming up behind her at twice her speed, and the van is honking — the long pre-passing honk that means I am coming up behind you, hold your line, I am about to pass on your left.
She does not flinch. The newborn does not wake. The van passes. The mother continues. The order operated. Nobody felt encroached on. Nobody flipped a bird. The honk was information about a position on the road, processed as information, acted on as information, completed without residue.
The honk in Vietnam is not what the honk is in Vancouver.
Same instrument. Same air pressure. Same sound wave hitting the same eardrum. Mechanically, acoustically, physically identical. But the honk is its own spectrum, and the two schemas read it differently because they are running it across different ranges.
In Vietnam the honk is a continuous range of road communication. A short tap means I am here, do not back up. A longer tone means I am about to pass, hold your line. Two quick taps means thank you. A sustained note means I am alerting you to something ahead, look up. A burst means I am turning into your path, please yield. Different durations, different patterns, different volumes — each one a position on the spectrum of what a honk can communicate.
The North American schema collapses the entire range to a binary. Honking is rude, or honking is necessary. There is no continuous range of road communication. There is one instrument with one meaning, and the meaning is almost always negative because the codified schema does not have a field for honk as communication.
The honk in Vancouver is not a position update. The honk in Vancouver is an accusation. The driver who honks in Vancouver is not informing anyone. The driver is asserting a claim against a violation. The honk is the protest. The receiving driver registers it not as information but as judgment, and the judgment lands in the body the way any other judgment lands — as something to defend against.
Same horn. Same air. One schema runs the honk across a continuous range. The other schema runs the honk through a binary. The same mechanical event becomes two completely different operations because the spectrum the schema is metabolizing has been collapsed to its lowest dimensional form.
Two people are sitting in a kitchen. He has just apologized.
He apologized for the thing she named yesterday — that he forgot to pick up the prescription on his way home. He drove past the pharmacy. She had to go out at nine after a long day. The prescription was for her mother.
His apology was specific. I'm sorry I forgot. I should have written it down. I had it in my head and then the call from work hit and I lost it. I'll set a reminder next time. It won't happen again.
It is a good apology by the standard of apologies. He named what happened. He took responsibility. He did not deflect. He committed to a specific change in behavior. If you graded apologies, he would have scored well.
Her face does something. Not anger. Something quieter. Her shoulders, which had been tight, do not soften.
She says: Thank you. She is not thanking him for the apology. She is closing the conversation.
Both of them are walking diamonds. They are walking them at different altitudes.
He is operating his entire diamond at task and tradeoff level. The meaning rung is not where he is standing.
She is at M5. She is operating from meaning. The prescription, the apology, the conversation — all of it is being filtered through the meaning she is standing at: I am the absorbable one in this marriage.
Her hinge does not close. Because the apology landed at M1, and she is standing at M5, and an apology delivered at M1 cannot close a hinge at M5. The altitudes did not meet.
Sensation is qualitatively neutral.
The psyche doesn't care whether you inflict it in a good way or a bad way.
The pulse is the same.
The sorting makes it two different experiences.
There's a little shop along the seawall. Walking up towards it, their sign — the one that faces the path, the one that catches people mid-stride — is face down on the ground.
I pick it up. Set it back in place. Straighten it so it faces the path again.
Nothing. A two-second thing. Keep walking.
It's still in my head. A two-second thing that should have stayed a two-second thing. But my brain didn't keep walking. Something snagged. How on these walks, I look for ways to help people. Small things. Unnoticed things. A thumbs up to someone who parallel parked well. Holding a gate for a stranger with a stroller. Moving a branch off the path. Each one tiny. Each one producing a small pulse of something I didn't want to look at too closely.
Altruistic, it appears. Until you dig.
Why am I looking for these moments? Not stumbling into them. Looking. Scanning. My walks aren't just walks. They're searches. For what? For the chance to change someone's state. For the look on the parallel parker's face when a stranger validates what they just did. For the nod from the stroller parent.
And once I could see that, the next question arrived on its own. What's underneath the search? What conviction is running underneath the altruism — so deep, so old, so quiet — that it requires daily evidence to keep it from surfacing?
The walk kept going. My body kept moving. But the terrain had changed.
I gave her a cold reply.
Not loud. Not harsh. Cold. The specific temperature of a person who wants you to feel the weight of the inconvenience. Who wants the apology to cost you something before he accepts it. I knew what I was doing. I could feel the precision of it — the way the coldness was calibrated to land exactly where her guilt was already sitting. Not to resolve. To deepen.
She apologized again. I dug the coldness a little deeper.
I could see it. That's the part I need you to understand.
I wasn't blind in the kitchen. I wasn't at the surface, unaware, inside the machinery with no gap. I could see the instrument firing. I could feel the precision — the way the coldness was calibrated, the way the altitude shift was selected, the way the words were aimed. I knew exactly what I was doing. I knew exactly where it would land. I knew exactly what it would cost her.
And I couldn't stop it.
The awareness was there. The code was faster. The seeing and the doing were simultaneous — I was watching myself do it from inside the body that was doing it. The half-second wasn't absent. It was overridden. The code had the wheel and the awareness was in the passenger seat, watching the road, seeing the turn coming, unable to reach the steering.
That's worse than not seeing it.
This is the bottom.
Not the sorting. Not the mirror. Not the ledger. Not the fortress or the weapon or the pulse that doesn't care which direction it fires. All of those are above. All of those are produced by what's underneath them.
The verdict is underneath everything. It was installed before you had language for it. Before you could argue with it. Until the code was so complete, so total, so foundational, that it stopped feeling like something that happened to you and started feeling like something that is true about you.
I am not enough.
Three words written in the body of a child who didn't have the language to argue with them. Organizing every layer above it before he knew there were layers.
It wasn't the next day. It was a few days later. After the machinery had cooled. After the code released the wheel. After the distance arrived and the awareness that was present in the kitchen became available to act on. Not new information. The same information. Finally reachable.
I told Rebecca at dinner.
The kids were there. Emily and Zeke in their own little world. Forks and chewing and whatever seven-year-olds and four-year-olds talk about when the adults at the table are somewhere else entirely.
I didn't apologize for the tone. I didn't explain the tires. I didn't offer the better version of the same conversation aimed at the same altitude.
I told her I weaponized my ability to climb to attack her. And that I was sorry.
Feel where those words are aimed.
Not at the event. Not at the tires. Not at the miscommunication about the keys or the three walks or the $200. If I had apologized for those things — I'm sorry I got frustrated about the keys, I'm sorry I was harsh about the tires — the apology would have landed at the surface. At the event.
The wound wasn't the tires. The wound was the weapon. The wound was the discovery — hers, sitting in her body for days — that the person who reads every room used the read on her. That the precision she's seen me use to hold space for strangers and colleagues and friends was the same precision I aimed at the place I knew would land hardest. That the instrument doesn't distinguish.
So the repair had to reach the wound. Not the event. The mechanism. I named the instrument, not the content. I named what the architecture was doing — not what the argument was about.
The code says not enough. The code scans and sorts and mirrors and ledgers and builds and aims, all in service of managing a verdict that was written before I could speak. And the code will keep running. Tomorrow. On the next walk. In the next room. The code doesn't uninstall in one conversation at a dinner table.
But it can be seen. And naming it — out loud, to the person it landed on, without a wall — is how the code starts to lose its grip. Not because the naming fixes it. Because the naming makes it visible. And the code's power was always in its invisibility.
The sign on the seawall. The cold reply in the kitchen. The repair at dinner.
The same walk. The same instrument. The same code.
Three directions. And the only one that cost me anything real was the one where I let the code be seen.
Same path. Same seawall. Same cherry blossoms, if the season is right. Walk with me one more time.
The couple on their first date. You saw them earlier and you saw the surface — two people being cute on a bench. You see them now and you see the architecture.
The retired couple. You saw them and you saw commitment. You see them now and you see what commitment actually is. Not the absence of the code — the management of it.
The shop. The sign. Still standing.
I walked past it this morning. Didn't need to pick it up. I felt the absence of the task. No sign to pick up. No deposit to make. No pulse to feel.
The scanning was still running. The architecture was still looking. The code doesn't take a day off because you wrote a book about it.
But I could see it running. Not from the passenger seat, watching and unable to reach the wheel. From somewhere closer. Alongside. The way you walk alongside a river — not controlling it, not stopping it, but seeing the current. Knowing which direction it flows. Knowing what it carries.
The code says: land. The shadow says: this is how. The instrument says: I can.
You're not in the open field. Neither am I. But the field is there. On the other side of seeing. On the other side of the fortress, and the weapon, and the sorting, and the mirror, and the ledger, and the code. On the other side of says who aimed at the deepest thing you carry.
Not the kid's field. The earned one.
Some days I find it.
Some days I walk back.