01 — The Analysis
Three layers, every engagement.
Collaboration Architecture is the deliberate design of how humans and machine systems share work. It treats the pairing as one system with one output. The question is never what the machine can do. It is what the pairing can do together.
Every engagement runs the same analysis, across the task, meta, and systems layers. Where does the work actually happen. Where is judgment applied. Where does the whole system bend under load. The answers decide what to augment and what to leave alone.
T.01
Task layer
The work itself. Inputs, actions, handoffs. Where friction is visible and measurable.
M.02
Meta layer
How the work is directed. Attention, judgment, trust calibration. Where the human must remain an agent.
S.03
Systems layer
The whole under load. Incentives, failure modes, second-order effects. Where designs endure or quietly rot.
02 — The Practice
Three disciplines, one architecture.
OB1x — THE PRACTICE. THREE DISCIPLINES, ONE ARCHITECTURE.
01 / ORBIT
Operational Research in Bridging Intelligence and Technology
Covers the full range of human-machine systems — from AI interfaces and research tools to physical autonomous systems and cybersecurity operations where human judgment is mission-critical.
02 / GRID
Guided Research for Intelligent Design
The structural method: turning observations into frameworks, protocols, and decision systems teams can run.
03 / LUMEN
Learning, UX, Machine Engineering and Networks
Where findings become usable — plain language, interfaces, and learning that put the system in people’s hands.
01 / ORBIT — EXTENDED
ORBIT includes the physical. Language models compress patterns in text; they have no native grasp of geometry, weight, occlusion, or gravity. Anything that has to move through the world — a robot arm, an autonomous vehicle, a surgical tool — needs a different kind of intelligence: spatial, embodied, grounded in a model of the world rather than a model of words. Current research in the field frames this directly: spatial intelligence is ‘as critical as, and complementary to, language intelligence.’ It isn’t a side branch of ORBIT. It’s the same discipline — designing where humans and machines meet — applied to a body instead of a conversation.
02 — Case Studies
Six studies, one discipline.
CS.01
An AI-collaboration trainer — prompting, discernment about when not to use it, daily practice. Skill without habit forgets; habit without skill runs empty.
LEARNING SYSTEMS
CS.02
An editorial publication that reads corrosion as combustion slowed past noticing. The cover is written by the phenomenon itself — rust, through a stencil.
EDITORIAL SYSTEMS
CS.03
An egg housing for a packaging client bleeding shelf share to breakage. Form followed three locked words — precise, convergent, enduring — and revision followed data.
INDUSTRIAL DESIGN
CS.04
Mixed-methods research into how people learn to work with AI — conducted, disclosed, with one. Twenty-two participants, seven themes, and a gap nobody was teaching.
UX RESEARCH
CS.05
A memory contract with an AI, a curriculum built to converge, and a running knowledge base of everything the practice taught.
PRACTICE INFRASTRUCTURE
CS.06
A physics deck for Caltech WSP where every color was chosen by the experiment, not a template. Directing an AI collaborator is a design discipline of its own.
CREATIVE DIRECTION
03 — About
I run OB1x as a solo practice. I have spent my career inside human-machine systems: control rooms, production lines, research tools, and now AI-mediated work. A background in electronic and signals systems gave me a rare vantage on cybersecurity — I learned it from the operational side, where understanding the threat and the system are the same discipline. The pattern repeats. When machines take the whole task, humans lose the thread. When machines take the right parts, humans get sharper.
My influences are unfashionable and durable. Rams taught restraint. Ive taught care at the smallest scale. Japanese practice taught me Ma — that the space between elements does the work — and Kanso, that simplicity is a discipline, not a style. The same principle runs through all of it: what you leave out matters as much as what you keep.
If you want automation, there are cheaper firms. If you want your people to stay in the loop as agents, we should talk.