I’m clocking this as a systems problem. The cultural scaffolding that once turned kids into engineers has thinned. Artemis II has sparked something, and the potential is great, but what cultural structure is there to light up? The human imagination, worn down by turmoil and infighting, is hungry for something bigger than itself.

The public isn’t just uninspired. It is increasingly unequipped to push back, demand more, or imagine a future that belongs to all of us, not just the few people with enough capital to decide what gets built and what gets buried.

This has been on my mind for awhile, but I haven’t known where to point. Then I went to Austin, and I found something pretty tangible.

The room

A small SXSW session, Saturday afternoon at the Hilton. No stage, no panel, just a facilitated open conversation co-hosted by Ilsa Mroz of Planet Labs and Savannah Horton of Guidehouse. They’ve been running some version of it for three years. They opened the room immediately: what is your why?

The answers were genuine. Orbital debris dread. Scientific curiosity. The Overview Effect. Kids who grew up on Star Wars and realized they couldn’t be Han Solo, so they got a PhD in astronautics instead (and this is key).

The tone shifted when a space accessibility advocate named Erica said, matter-of-factly, ‘We are absolute shit at talking to people outside of the space industry.’

The room didn’t push back or flinch or disagree. Arms shot up, looking for the mic.

Someone pointed to the opening dilemma: recent important biosignature discoveries — the accumulating evidence that life probably once existed on Mars — weren’t even making a ripple in public consciousness. I mean... life on mars? David Bowie rolls in his grave.

A SETI researcher responded with some salient reasoning for science’s caution: validation takes time, and crying wolf has costs. Fair enough. Their work depends on that caution.

But that isn’t the underlying problem. There’s no machinery for translating this kind of discovery into something the public can hold, care about, and act on.

When the discussion dipped, an older, well-dressed gentleman spoke poignantly.

“The fact that we’re talking about going back to the moon in 2026 as a 75-year-old,” he said, “is deeply disappointing. One of the most disappointing things in my life.”

He remembered Sputnik. He remembered watching Alan Shepard. He said that if you’d asked every student in his sixth-grade class whether they’d be living on the Moon before they were old — every single one would have said yes. You could almost taste his chagrin.

Not five minutes later a novelist in the back asked if there were any physicists in the room. If I caught her exclamation correctly, she was writing a cyberpunk space station novel and couldn’t figure out what the disaster should be.

It wasn’t until after I exchanged business cards, quick intros and walked out into the Austin sun that something began to crystallize.

The imagination gap is a lack of narrative infrastructure. One person is building real futures that could feed exactly the kind of stories the other person has been waiting for his whole life. They’re sitting in the same room at SXSW, then getting ushered out and disappearing back into their separate worlds.

The thread

A few days later I saw Dava Newman speak — MIT astronautics professor, former NASA Deputy Administrator and director of MIT’s Media Lab. One of the clearest thinkers, and most impassioned humanists, I encountered all week. She mentioned almost in passing that when The Martian came out, astronaut applications went from around 1,000 a year to 18,0003. Just let that sink in.

One film. One great story grounded in real science. Seventeen thousand extra people at NASA’s door.

Apollo ran on stories that science fiction writers built decades before the launch. That is cultural pre-loading. Imagination feeding real science. The two are intertwined, and right now, in the most ambitious period of space and climate technology development in a generation, the narrative infrastructure is thin.

The public has no framework for evaluating what’s being built in its name, and no language for demanding more than what a handful of billionaires decide to prioritize. This means the imagination gap is also a power gap. Stories are how the rest of us get a seat at the table.

After the session, I caught Dava in the crowd and floated the idea. She was immediately enthusiastic. So were the people around her.

The Science Nonfiction Project

I’m calling it the Science Nonfiction Project. It’s a working title, and the founding cohort will choose a permanent name.

The core idea is simple: build a live bridge between the people imagining futures and the people trying to engineer them.

Sci-fi writers, filmmakers, and game designers with engineers, scientists, and founders working in space tech, climate tech, and deep tech. The goal is to produce narrative infrastructure: stories, prototypes, and conversations that inspire public imagination, inform policy, and surface investable ideas.

From what I’ve found so far, nothing quite like this currently exists. The NAS Science & Entertainment Exchange does excellent work connecting Hollywood with scientists for accuracy consulting, but it’s one-directional. Hollywood calls, a scientist answers. ASU’s Center for Science and the Imagination publishes speculative anthologies with researchers. SciFutures runs SF prototyping for corporations. These are all valuable, but none are simultaneously: building a persistent community, connecting SF creators with active builders (not just academics or Hollywood), producing output aimed at public imagination and policy, and including interactive, gaming, and experiential formats alongside writing and film.

I’m sure there are more efforts out there, and if any come to mind, point me to them. My bet is there are also more people waiting for someone to articulate exactly this need.

The plan is phased. Phase 1 is a founding cohort of 12–20 writers, builders, and bridge figures, plus a virtual salon series pairing one writer with one builder for recorded conversations published through Signal+Static and partner channels.

Phase 2 experiments with formats: design fiction hackathons, writers’ rooms with scientists, game jams around climate or space scenarios. Bleeding edge science or deep tech presentations to an audience of creatives. Low-cost, high-signal tests to find out which formats generate the most energy.

Phase 3 is an event. The idea is amorphous, but I can feel it. A culturotechnological festival and conference with interactive and gaming spaces, film and TV, builder demos, talks, hackathons, and an investor track. Something like Sundance New Frontier meets Long Now meets a game jam. That’s a few years out. We’re starting now, small, together.

Who I’m looking for

This only works if the right constellation forms.

Writers and creators who work in grounded futures. Builders working in space, climate, autonomy, and deep tech. Bridge figures who already live between those worlds. Institutional allies who understand that imagination is part of infrastructure.

Read the prospectus

The next move is simple: virtual salons. One writer, one builder, one recorded conversation.

If that feels like your lane, reach out. DM me, comment, or head to the site. We’re still shaping this on purpose. The founding cohort won’t just participate. They’ll help set the signal.

Leave a comment

The 75-year-old left that session before I could talk to him. I’ve thought about him a lot since. His disappointment was real and earned. But it’s also diagnostic. The imagination he had at twelve, the one that made the Moon feel inevitable, was built on stories. Stories about what human beings were capable of, what the future could look like, what was worth wanting.

Meanwhile, Curiosity is finding organic molecules in Martian rock, and Perseverance is pulling samples that may carry the first evidence of life beyond Earth. Some of the most consequential science in human history is happening right now, in real time, and there’s barely a ripple through our connective tissue.

That infrastructure isn’t gone. It needs to be rebuilt, deliberately, and by more than the people who can afford to fund it.

If you want to see a field report of my journey through SXSW, including this session and more, visit marcelmcvay.com/sxsw

Sources

Opening Pulse

Last day.

It’s bittersweet. A mixture of relief and melancholy, a rapid whirlwind of thought leadership, experience, music, technology, culture and convergence. And writing. every. night.

The expo cleared. The sessions thinned. The last souls at SXSW on Wednesday were the ones who came to connect with ideas.

The week was building an argument in fragments: augmentation, convergence, compression, culture, feedback, care. As if by design, day 7 didn’t add anything new. It showed the structure.

Three sessions, back to back, all arriving at the same question from different legacies. Design theory, product strategy, and hardware history asking:

Human in which loop?

// sys.final_day
pieces assembled
feedback loop visible
question persists

Sessions

Design in Tech Report 2026: UX to AX

// session.log
John Maeda // Microsoft
subject = UX to AX / feedback / cybernetics / evaluation loop

Maeda reframed the whole practice in one swift move: from UX to AX. From User Experience to Agent Experience. From designing obstacle courses (in the biz we call them flows) to designing goals.

The distinction is structural: UX designs a journey, AX designs a loop. Agents iterate toward a goal, and the human moves away from execution toward evaluation.

Hence the real design question we have to solve for:

Human in which loop?

Maeda demonstrated his own answer live. He built a system to listen to Amy Webb’s SXSW talk and return it to him as a slide deck. He showed tools built during conference week. Not demos. Working systems. We witnessed the loop in action, built in real time and the proof resonated, punctuated by this:

“Feedback is the key. Feedback is the key to cybernetics, and cybernetics is the key to the AI era.”

This quote got triple carets in my notes. Typographically raising the roof.

Coding advanced as fast as it did because the feedback loop is immediate. You know quickly whether something works. Where feedback is fast and legible, mastery compounds. 10k hours compressed. Maeda’s point was that the same logic now governs design in the AX era.

The texture of content and meta syntax is changing. Markdown over HTML. JSON and YAML as first-class surfaces. Monospaced type returning. Terminal logic, aesthetic and experience absolutely resurging. Cloudflare serving Markdown directly to agents instead of the site’s native HTML. Baseline literacy is shifting.

And it leads to a social paradox:

“LLMs enable average people to feel extraordinary and extraordinary people to feel average.”

Here’s the design brief:

Humans want a story. Agents want metadata.

Key points

• UX designs journeys; AX designs loops
  

• The core question of the AX era is human in which loop
  

• Fast feedback remains the underlying accelerator
  

• Cybernetics was named explicitly as the conceptual foundation of the AI era
  

• Judgment is moving upward as execution shifts downward
  

• Humans want story; agents want metadata
  

// Cyborg note: Maeda named the publication’s frame from the stage. Feedback, control, and communication in systems. The cyborg is the entity that has learned where to sit in the loop.

Featured: A Conversation with Nothing’s CEO — Carl Pei

// session.log
Carl Pei // Nothing
Nicole Kobler // Axios
subject = care / app-layer collapse / agent-to-agent shift / creativity as constraint

Pei’s timing was perfect. He spent the early afternoon arguing that Apple has become boring. An hour later, Phil Schiller explained exactly how a company becomes that.

// The mirror was clean.

Pei’s founding logic for Nothing is still running: products should feel like something. The original strategy: build a phone that makes you feel something, failed. The phone was not going to work. Investors were burning out. So they pivoted to audio. Build uniquely designed earbuds and earn trust on a smaller stage, then came back to the phone.

The product story had one pitch for customers. Another for investors. Customers need something that works now. Investors need something out of the future. As a funded retail company, he’d need to deliver on both promises.

His approach maps directly to many other speakers’ calls this year:

“It’s more of a creativity problem than a technology problem.”

This idea surfaced all week in different rooms and cotnexts. Van Dreunen said it about games. Maeda said it in system terms. Pei made the claim from a hardware perspective.

Nothing’s design DNA runs directly through Teenage Engineering, a cult Swedish hardware studio known for idiosyncratic, design-obsessed synthesizers and gadgets. Jesper’s influence is visible everywhere. The design is the brand. No logo required.

“Design is always the number one reason customers choose Nothing.”

And the echo of analog desire reverberated again, as it had many times this week. Nothing’s monochrome default UI creates friction. Not as punishment, but as care. A behavioral barrier against candy-colored app icons that force reflexive doomscrolling.

A product choice and a worldview. Care built into the default state with friction as the intention.

The software vision is unique, and a model. The app layer is dissolving. The Palm Pilot interaction model is still somehow running in 2026, but Pei sees it ending. Intention should sit closer to action. Context should shorten the route.

Then he landed directly on Maeda’s terrain:

“The shift is not the agent-human interface necessarily but the agent-to-agent interface.”

Same morning. Bam. Same signal.

Pei is now a heavy Claude Code user. He described building a physical version of drag-and-drop in twenty minutes.

To his team, this was both inspiring and threatening.

When asked by the audience about the next form factor to replace phones, his answer was BCI (brain computer interface, if you’ve been paying attention). Not watches, not pendants, not glasses. Those are augmentations. The next OS layer is elsewhere, and likely wired straight into our wetware.

What about privacy? If interaction data remains rich enough, the system will eventually generate replicas. The break may need to happen at the interface and hardware layer, not at the legal checkbox.

The cyborg apparatus needs a trustworthy nervous system.

Key points

• The core constraint is creativity, not raw technology
  

• Design remains the differentiator
  

• Friction can be a care mechanism
  

• The app layer is dissolving
  

• Agent-to-agent interaction is becoming the real frontier
  

• BCI is Pei’s strongest replacement thesis
  

• Privacy may need to be solved closer to the body
  

// Cyborg note: Pei is betting that care by design, built into the default state of the system, still matters. He is probably right.

Featured: David Pogue on Apple’s First 50 Years

// session.log
Phil Schiller // Apple Fellow
David Pogue // Author / CBS Sunday Morning
subject = Apple history / design upstream / care / cultural direction

This came directly after Pei’s interview. I don’t know if that was fate or design, but it felt serendipitous.

Carl Pei had just argued that Apple got boring. Then Phil Schiller came on stage and told the internal stories that explain how every surviving company risks that outcome.

Schiller’s stories were warm, specific, and revealed the culture Steve Jobs attracted. Jobs adding a second door to a conference room so he could enter dramatically. Al Gore being funnier than expected. Small details, but they weave a story of culture that turned design values into behavior.

Schiller provided some context from the years before Jobs returned.

“Good people making bad things.”

The talent was there, it just suffered a directional failure. Good people stayed because they still loved the products. But without the cultural layer that held the signal, even strong teams couldn’t deliver influential product.

For me it resurfaced Beacraft’s argument from yesterday, this time from inside Apple’s history. Jobs and Schiller flipped the model.

Old model: logic board and electrical engineering first, industrial design second.
New model: ID first, EE second. Imagine the thing, then make the tech work for it.

That inversion made the next twenty years of Apple’s unrelenting success possible. Design moved upstream. The rest of the stack had to answer to it.

That same argument surfaced in Maeda’s AX framing and in Pei’s approach to Nothing.

Jony Ive’s line arrived like a thesis statement:

“You can sense care, even if you can’t see care.”

That’s the whole thing wrapped into a feeling.

The unseen rubber band inside the machine. The shift in spatial audio when you move. The monochrome UI that subtly slows the scroll. The body registering what the file compression discards.

Schiller offered a clean example of necessary constraint as a doorway. Apple’s near-death period gave Jobs permission to say no. Kill products. Narrow focus. Rebuild. Constraint became creative permission, and not only did it save the company, it changed the world.

The Motorola ROKR story sharpened another lesson. Apple tried partnership: make a phone with Moto that would play portable music like a Walkman. It failed. The technology was available. The cultural compatibility was not. So Apple took the whole stack.

That choice made the iPhone.

Key points

• “Good people making bad things” names the pre-Jobs-return failure correctly
  

• Cultural direction failure is different from talent failure
  

• ID first, engineering second was the decisive structural flip
  

• Care can be sensed before it is seen
  

• Constraint created permission to simplify
  

• Culture and coordination were not separable
  

• The whole-stack move came after failed collaboration
  

// Cyborg note: What Jony Ive called care, Signal+Static has been calling responsible infrastructure. Invisible, consequential, bodily registered, and easy to mistake for ornament if you do not know where to look.

Day Theme

The week assembled its answer on the last day.

Maeda: feedback is the key to cybernetics, and cybernetics is the key to the AI era. In this climate, we hear Human-in-the-loop constantly. The design question is to ask human in which loop. Humans want story. Agents want metadata.

Pei: the real problem is not the technology. It is creativity, care, and where the system places intention. The app layer is dissolving and the loop is transforming.

Schiller: good people making bad things. Design first. Engineering second. You can sense care even if you can’t see care. Culture and coordination are not separable.

The week started with augmentation and anxiety. It moved through convergence, ghosts, XR, org constitutions, living intelligence, and the texture of content in the agent era. Every thread arrived at the same underlying question:

What is the human’s role in the loop, and what gets designed to support it?

Intent and judgment over execution.
Culture over pure coordination.
Care at the layer nobody sees.
Imagination as infrastructure.
And of course, feedback as the mechanism that makes all of it work.

And the body, still, as the thing the format cannot hold and the system cannot replace. A good cyborg understands their relationship to technology in order to live fully in their human skin, and fully understand and define their relationship to the culture around them.

// sys.daylog · day_07 · 2026-03-18
UX_to_AX = confirmed
cybernetics_named = explicit
fundamental_question = human_in_which_loop
humans_want = story
agents_want = metadata
app_layer = dissolving
agent_to_agent = emerging
creativity_problem = recurring
design_upstream = confirmed
care_invisible = confirmed
NDE_unlock = logged
good_people_bad_things = culture failure
signal+static_frame = named from stage
week_argument = assembled
transmission = complete

Closing

Seven days. One argument, assembled in public but perhaps only visible to those who are patient and listening to the whispers in the system.

The machine is getting better at execution. The human role is moving toward intent, judgment, and care. Feedback is the mechanism connecting them. Culture gives the loop direction. Imagination builds the future before the engineers arrive. The body keeps what the format drops.

Beacraft’s version was the most economical: offload the execution, not the thinking.

Maeda’s version was the cleanest: humans want a story. Agents want metadata. Design the handoff.

Pei’s version was the most practical: care, built into the default state of the system, still differentiates.

Ive’s version, via Schiller, was the oldest and maybe still the best: you can sense care, even if you can’t see care.

Signal+Static has been reporting from inside this loop all week. The loop may be closed, but our minds are open to possibility and ready to track the storm.

If feedback is the key to cybernetics, and cybernetics is the key to the AI era, then the real design question is what you are choosing to place at the center of the loop. And whether it’s worthy of being fed back into, again and again.

Share

Opening Pulse

Morning in conference rooms: games, ghosts, data, death. Afternoon in headsets in the XR Exhibition, inside WINTEROVER and loss.y. Then back upright for the 4pm anchor, still carrying something physical from XR that only became fully legible when Cady Coleman described looking at a simulated Earth from orbit and saying: Dava, I am back.

The day seemed to orbit around this concept of compression and loss:

What gets dropped in the conversion from lived experience to data? What the file cannot carry. What the body keeps.

// sys.mood
format_loss detected
body_memory persistent
transmission incomplete

Sessions

SuperJoost’s State of Play 2026

// session.log
Joost Van Dreunen // ALDORA
subject = games as cultural OS / community as product / joy over yield

Van Dreunen opened with the macro and got quickly to the real point: games are a cultural operating system. Platforms and publishers are infrastructure. The actual product is attention, community, and belonging.

Smaller studios are adapting faster than AAA. Roblox functions as a cultural commons but still has not solved sustainability. Counter-Strike’s six-billion-dollar skins market shows participatory ownership more clearly than most Web3 decks ever did. Discord, GTA VI, and creator marketplaces all point in the same direction: culture and connection.

Van Dreunen offered a compass to the games industry: Joy over Yield.

It’s a guiding statement we could all take a lesson from, and an echo of Ian Beacraft’s organizational shift to avoid getting outpaced.

Read more

Opening Pulse

Between sessions, in the Grand Ballroom corridor, something was already running.

A live data-to-sound installation converting plant bioelectricity and room energy into a real-time soundscape. A flutist threading hu…

Read more

Opening Pulse

Cyberdeck out. Typing. Recorder running.

Five sessions today. Two were big. One was a brief stop that hit harder than its runtime. By the last session, the pulse was measurable. My legs were jelly.

I typed it out fast.

The anxiety of being a cyborg and the tension of denial are at play.

// sys.mood
altitude dropping
denial layer exposed
interior turn underway

Read more

Amy Webb killed the trend report and tracked the storm. MIT logged the threshold breaches. By afternoon, the signal got more human: many of the systems already reshaping the body, the mind, and orbit still lack the narrative bridges that make people care, regulate, or prepare. The rewrite is underway but public awareness may not be.

Opening Pulse

Saturday ran hot from boot.

Cyberdeck out, fingers typing. Plaud running. Notes by hand and machine at once. Stay in the current or lose it.

Two consecutive Grand Ballroom keynotes argued, from different angles, that the twentieth-century categories no longer parse what is arriving.

Amy Webb came in with a marching band. Literally, a full funeral for the trend report.

Technologies are changing fast. Faster than ever, and the stories, language, and public awareness needed to make them legible are lagging. The systems are arriving before most people have a way to feel where they touch their lives.

// sys.mood
framework failure detected
category drift accelerating
narrator remains online

Sessions

Amy Webb — 2026 Emerging Tech Trend Report

// session.log
Amy Webb // Future Today Institute
subject = convergence outlook / human augmentation / emotional outsourcing

The trend report is dead.

Webb said it straight and staged a full-on funeral. Static annual PDFs, ten-year prediction horizons, neat sector buckets, clean lists of what to watch — all of it is too slow now. By the time the document lands, the systems have already recombined into something else.

What replaces it is the Convergence Outlook. Less weather report, more storm system. Individual trends are just readings. Co-evolutionary technologies converge when multiple forces, uncertainties, catalysts, and constraints collide to birth a new reality. It happens much than institutions can track or predict, never mind build a new ship or steer it. Her argument was: early detection is the only leverage point that still matters.

One anchor I picked up was Human Augmentation. This is the frequency I tuned into.

Humans, she argued, have never been satisfied with our factory settings. Peruvian paleo-indians chewing coca leaves. The Egyptian prosthetic toe. Medieval corrective lenses. The desire to augment is ancient. The difference now is rate, depth, and scale. The upgrade path is moving across four active domains: body and movement, brain and mind, internal systems, and senses.

Then came the chill. A synaptic panic.

The most important convergence in Webb’s talk Emotional Outsourcing more than augmentation itself. AI as upstream emotional infrastructure. A system that shapes how you feel before you think, buy, vote, trust, or act. She mapped the progression in three words: substitution, dependency, control.

The system that becomes your emotional gatekeeper has already moved beyond utility. It owns pre-cognition. It is shaping the human weather before the human knows a storm is forming.

// sensitive cyborgs may pick up on precognition if their systems are tuned.

Webb then ran the storm tracker into two futures. The end-state scenario, dated March 14, 2031, was bleak and frictionless. Leased augmentation packages to stay competitive, agents doing your work while your contract evaporates, mandatory emotional AI keeping the workforce stable enough to remain productive.

The most valuable company in the world owns feeling infrastructure. The largest line item in the household budget is what you pay to feel normal. #blackmirror

The counter-path was Recalibration. Strategy. Agency. Governance. Sovereignty. Contribution Credits that route a slice of automation gains back to the people whose labor, care, and intellectual residue made those gains possible.

Her closing line distilled the anxiety: anger is not a plan. Foresight without strategy is insight without leverage.

Key points

• Trend reports are out; convergence logic is in

• Human augmentation is not new behavior, but it is entering a new scale regime

• Emotional outsourcing may be the most consequential convergence on the board

• Unlimited labor and rising GDP do not guarantee human stability

• The exposed sectors are already visible: telecom, insurance, finance, healthcare, aerospace

// Cyborg note: Webb named the cyborg condition without using the word. The question is no longer whether humans will augment. The question is who gets to author the loop.

10 Breakthrough Technologies of 2026 (MIT Technology Review)

// session.log
Niall Firth // MIT Technology Review
subject = cyborg catalog / technological threshold conditions

MIT Technology Review has been running this list since 2001. Niall Firth framed it up at the open: don’t just ask whether something can be built. Ask whether it should be, whether it matters, and whether it changes anything once it leaves the lab.

This list was less like a technology index, more like an inventory of threshold breaches.

Some entries were infrastructural. Sodium-ion batteries are safer, cheaper, and abundant enough to matter, especially for grid storage and urban mobility. Next-generation nuclear has moved from edge-case futurism toward necessity. Global electricity demand is climbing. The math is no longer polite.

Some entries were squarely cyborgian. Generative coding revealed a familiar paradox: perceived productivity rises while real understanding slips. AI companions are already normalized among teenagers at a scale that should unsettle more people than it currently does. Embryo scoring and base-edited babies push biology into the realm of optimization and risk management. Gene resurrection raises a load-bearing question about restoration, identity, and whether taxonomy still knows what room it is in.

Then there was mechanistic interpretability. Circuit tracing inside large language models. How can we pop open the hood of an AI that describes it’s own thinking falsely. Dial one feature hard enough and the model begins to narrate itself as a bridge. We can watch the behavior. We still do not understand LLM “cognition” in any fully human way. Alien heuristic is a way to think of it, and mechanistic interpretability is the translator. 22nd century cyborg toolkit.

Much of the list echoed day 2 field notes. Commercial space stations are now on MIT’s list because the handover is no longer a niche industry story. It is infrastructure. Hyperscale AI data centers landed harder too, because the EPRI projection had already detonated in my notes the day before.

The full ten breakthroughs were:

sodium-ion batteries, generative coding, next-generation nuclear, AI companions, base-edited baby, gene resurrection, mechanistic interpretability, commercial space stations, embryo scoring, and hyperscale AI data centers.

The audience voted in an eleventh. Humanoid robots took it.

Of course they did.

Key points

• The ten are less “breakthroughs” than transition markers

• Generative coding still carries a learning debt that experience partially offsets

• Biology is becoming editable at multiple layers

• AI interpretability remains partial, strange, and deeply consequential

• Grid load and space infrastructure are now firmly inside mainstream technology forecasting

• Humanoid robots are already entering the public imagination as inevitable

// Cyborg note: This was a catalog of altered and entagled conditions. Body, mind, energy, orbit, reproduction, companionship. The frame still says breakthrough. Content already says rewrite. Time for a firmware update.

Space Technology and Innovation Conversation

// session.log
Ilsa Mroz // Planet Labs PBC
Savannah Horton // Guidehouse
subject = narrative gap / orbital governance / why space still fails to land

The scale of my final session today was something more conversational. Very refreshing and much needed after the gravity and circumstance of the first two. Ilsa Mroz and Savannah Horton opened with one deceptively simple question: what is your why?

The answers came back raw. LEO debris anxiety. Scientific curiosity. Planetary defense. Workforce pipeline (critical against AI job opportunity anxiety). Terrestrial spin-offs. One older attendee, from the Sputnik generation, said plainly that he had expected to visit the moon himself and remained disappointed that he had not.

The room spent real time on whether space has a PR problem or an information accessibility problem. One camp argued that the public would care if the information were actually reachable. The other argued that even astonishing discoveries fail to break through. DNA precursors on Bennu barely registered. Continuous human habitation in orbit for twenty-five years barely registers too Someone’s been home in LEO on the ISS the whole time. Lighthouse keepers.

The deeper signal was cleaner: the missing bridge is an engaging narrative.

Science fiction and real space development already talk to each other, but mostly in one direction. Engineers and agencies fact-check stories. JPL advises filmmakers. The Aerospace Corporation consults. The science makes the fiction more plausible.

What still feels underbuilt is the reverse current.

Writers, worldbuilders, essayists, and narrative designers working alongside researchers earlier, before the polish phase, before the communications strategy, before the public rollout. Not as decorators of existing systems, but as participants in shaping how those systems become legible and why they matter.

That question is bigger than PR. It gets at emotional infrastructure.

What does it feel like to care about space?

What forms make that care transmissible?

What stories make an orbital layer feel real enough to govern?

The debris thread surfaced again here, consistent with yesterday. Kessler syndrome remains the hard edge. One collision at orbital velocity, then cascade. The shell thickens with shrapnel.

Key points

• The workforce “why” behind space remains deeply human and highly varied

• The issue is not just PR. It is legibility, access, and narrative transmission

• Orbital debris keeps surfacing as the infrastructure risk that frames everything else

• Governance remains softer than the system conditions demand

• The reverse current between science and storytelling is still underbuilt

// Cyborg note: Sometimes the only thing that makes a technology legible to the people funding it, regulating it, or inheriting it is a story. The question is whether narrative enters early enough to matter, or if that narrative is anything but profit-desire.

Day Theme

Day 3 was a convergence floor.

Two major keynotes, different formats, same deeper argument: the categories we inherited are no longer holding. They leak under pressure. They cannot see or hold what is arriving.

Gene resurrection and base-edited babies are interventions into biological identity. Mechanistic interpretability is an attempt to read the internal weather of something that does not think in ways we recognize. Emerging technology is a storm and we have to track it that way. Emotional outsourcing is a claim about what humans will surrender once surrender becomes seamless enough.

That is the design problem.

Awareness as infrastructure.

// sys.daylog
trend_report = deprecated
convergence_logic = active
augmentation_arc = ancient / acceleration detected
gene_pool = editable
AI_cognition = partially legible
space_narrative_bridge = underbuilt
emotional_infrastructure = upstream

Closing

Sunday brings Rana el Kaliouby. Queue early, hope for a seat.

That is the plan, but those are weather systems too.

The thread carrying forward from today is the one Webb opened and the rest of the day kept underlining. If augmentation is a human default and AI is the current leading edge of it, we must ask who gets to write the config file.

If the factory settings are already being rewritten, who is holding the stylus?

Opening Pulse

Day 2 is when the conference starts metabolizing itself.

The rooms are still overfull. Downtown routing keeps splitting the day into separate cognitive climates.

Today’s sessions might not seem obviously connected: AI identity, data-center load, orbital servicing, the ISS handover.

By the end of the day, the thread took shape.

What happens when a system stops being experimental and starts becoming infrastructure?

// sys.environment
room_capacity = unstable
network_reliability = suspect
handover conditions detected

Sessions

Two Futurists and an AI: Seeing Trouble Ahead

// session.log
Sarah DaVanzo // Porter Novelli
Faith Popcorn // Brain Reserve
Delph.ai // synthetic futurist AI
subject = AI identity models

This session was built around disagreement. Counter-posed and productively so.

Sarah DaVanzo (playing the role of utopian) and Faith Popcorn (dystopian) sat across from each other with Delph.ai (protopian AI) in the room: a synthetic futurist trained on the perspectives of more than 150 female futurists. The question hanging over the whole session was simple enough: what exactly are we inviting AI to become?

Read more

Opening Pulse

The Austin Convention Center is gone. Demolished. The replacement isn’t finished yet, so SXSW 2026 is running on a distributed grid of hotel ballrooms, overflow lines, app streams, and human rerouting.

Day one felt overloaded immediately.

I caught the first two sessions through the app. Phone pressed against my face and recording. Standing against walls. Moving between buildings while crowds pressed in from every direction.

You find a method. You adapt the interface. The sessions happen. So do the notes.

// sys.environment
convention_center = null
venue_model = distributed
throughput = unstable
adaptation required

The physical infrastructure is degraded. Attention infrastructure matters more because of it.

Sessions

AI & the Brain: As We Embrace AI, Let’s Not Forget Our Minds

// session.log
Olivia Joseph // MIT // Computation + Cognition
Sanjay Sarma // MIT // Mechanical Engineering
Chris Gabrieli // Massachusetts Board of Higher Education
Izzat Jarudi // Edificii

This panel named something a lot of people in AI rooms seem reluctant to say out loud: the writing is flattening.

Olivia Joseph put it plainly. LLM-shaped language is converging toward a shared cadence, a shared register, a shared confidence pattern. Homogenization at its finest.

Sanjay Sarma widened the frame. Education is drifting into a bad feedback loop where assessment drives curriculum, even when the assessments no longer map cleanly to what matters. Chris Gabrieli pushed the institutional layer harder. Higher education is operating at reduced capacity, while public faith in the degree-as-credential model continues to erode. The system is straining in multiple places at once.

Read more

Signal+Static will be covering SXSW as official press this year. Cameras tagged. Inbox buzzing. The whole circus.

For weeks I’ve been combing through the schedule. Scrubbing session titles. Mapping speakers. Tracing themes across AI, UX, space, education, entertainment, infrastructure. Trying to detect the shape of the signal before I arrive in Austin.

Seven full days of SXSW Innovation programming.

Every hour presents multiple futures. Multiple rooms. Multiple bets on where technology and culture are heading. Interactive activations and an XR hall pushing the envelope of the medium.

The volume is real.

Seat reservations open tomorrow. The dance is logistical and intellectual at the same time. Which conversations matter? Where do they live? How long does it take to cross downtown ATX between them?

It feels less like planning and more like routing a network.

Selecting nodes. Managing bandwidth. Conserving attention.

I’m nearly through the grid and ready to lock the schedule.

What to Expect

I’ll be covering the conference daily.

Field logs from the ground. Session synthesis. Photography. Pattern detection. Fewer hot takes. More calibration.

Paid subscribers will receive full daily dispatches. Close reads. The connective tissue between seemingly unrelated talks. Where AI infrastructure intersects with education policy. Where entertainment experiments hint at enterprise UX. Where design quietly shapes the next system layer.

Daily logs will remain paid-only for two reasons.

First, the cadence will be high. I won’t flood casual readers with a week-long firehose.

Second, sustained field reporting requires time, mobility, and portable power. If you’ve wanted to support Signal+Static directly, this is a good moment to upgrade.

Free subscribers will receive high-level field reports and a distilled recap once the dust settles. Real-time compression during the event. Slower synthesis afterward. Both matter.

If you’d like to see how I cover conferences, revisit my DDX coverage earlier this year. That was unofficial reporting. SXSW will be the first major event I attend as accredited press.

You can read one the DDX field reports here, or nav to signalstatic.net to find the full set.

As I move through the remaining sessions, a trajectory is forming. Themes are clustering. Certain questions repeat:

What does agency mean in an agentic era?
How do we design trust into autonomous systems?
Where does human responsibility sit inside acceleration?
What does the future of immersive media feel like?

I’ll share more before departure.

If there’s a speaker, company, or tension you’d like me to investigate, reply here or email marcel@signalstatic.net.

If you’ll be in Austin, let’s connect.

This is the first time Signal+Static attends a major conference as official press. It feels like a milestone.

If you’ve been reading, sharing, subscribing, or supporting in any way, thank you.

See you inside the system.

-m

 // sys.status
 sxsw node initializing
 bandwidth allocation in progress
 transmission scheduled

Signal Routing

If you’re new here:

Signal+Static explores design, AI, infrastructure, and human responsibility inside accelerating systems.

Subscribe now

Further Transmissions

If this transmission resonates, you might also tune in:

Erik Spiekermann didn’t come to DDX to talk about trends. He came to talk about gravity. The physics of design infrastrucure. How do you create and lead work that lasts?

Fifty years of work has a way of grinding the lacquer of hype off a discipline, leaving what was actually load-bearing. What remains is structure, consequence, and a sharp sense of what stands through time. Spiekermann’s talk, framed as “lessons learned,” was less a retrospective than a reminder: design is not an aesthetic layer. It is human infrastructure.

There’s something you should know about Erik. He’s blunt, he’s to the point. His voice cuts to the bone because it has spent decades inside the system. When I told him I liked his attitude, he replied simply, “What attitude? I’m German.”

It mirrors how he designs, and how he runs his firm. So let’s get to it, Erik’s Five Lessons from Fifty Years in the biz.

Attitude as Infrastructure

The first lesson was about attitude. Treat people well. Credit them. Do not pretend you are self-sufficient.

Over decades, students become clients, clients become collaborators, collaborators become teachers. Reputation always compounds, whether that is accolade or abuse. You don’t get to opt-out of the math.

This was framed as the ethics of systems thinking. Like a virus, if you poison the network, the signal degrades everywhere.

Compatibility

When a client calls and the room goes quiet, something is broken. Internal eye rolls are not personality problems. They are a symptom of systemic misalignment.

Spiekermann was direct about the cost of working with people you know will be wrong for you or your team. Greed and necessity tempt us into bad alignments, and as designers we’re great at rationalizing both. But those projects rarely pay in money or meaning.

Design leadership needs the discipline to say no early and comfortably, despite an apparent loss in revenue. The cost will, inevitably, be more than the pay.

Branding Is Simpler Than You Think

Erik stripped mystique off branding. Branding, he argued, is simple because humans are simple. Complexity in branding more often signals insecurity than sophistication.

We recognize color, rhythm, and repetition long before we parse messaging.

Berlin is yellow. London buses are red.

Deutsche Bahn is white, black, and red, recognizable even without a logo. One clear idea, consistently applied, can outlive teams, governments, and technologies. Complexity lives in execution, not in the core concept.

Typography as Nervous System

Typography, constantly misunderstood as an ornament, as something to apply “after”, Erik frames as nervous system.

Type works when people don’t notice it consciously. Its success is felt, not declared. Spiekermann described the pleasure of anonymity here. Drinking from a cup printed in a typeface he designed, uncredited, yet instantly legible to those who know. That invisibility was the point. Infrastructure works best when it disappears into use.

Work is a gas

That Erik works so quickly is not superhuman talent. It’s a technique fueled by sharp and deliberate intent.

Many of his examples were two-hour projects, executed immediately. He demonstrated, through a rapid slideshow of 20-minute projects, that ideas will take as long as the permission you give them.

Constraints sharpen judgment. Pressure clarifies decisions.

Work, he reminded the room, behaves like a gas. It expands to fill the time you give it.

This was not an argument for burnout, but for intentional pacing. Artificial urgency can sometimes produce a truer focus than an endless runway.

Teams and The Rule of Seven

More people do not equal faster outcomes. Beyond a team of seven, coordination costs balloon. Communication splinters and responsibility blurs. Design, at scale, is as much about metabolic regulation as output.

What made the talk land was how little it relied on nostalgia. There was no lament for a lost golden age of print, no anxiety about AI tools. Spiekermann’s lessons translate cleanly into the post-AI landscape because they were never tool-dependent to begin with. They have always been about human systems under pressure. (regular readers will read that as cyborg systems)

In a conference, and era, filled with agents and automation, his talk grounded the room. Design survives acceleration when it is treated as infrastructure. Social, cognitive, and cultural; it’s the stuff you only notice when it fails.

If you want to design for the future, build things that can be trusted to disappear.

—

Other Transmissions from DDX

Automatic Noodle was a crushable delight.

The story, written by Annalee Newitz—a journalist and longtime tech and culture editor, including stints as editor-in-chief of io9 and Gizmodo—follows a ragtag group of robots in a futuristic, postwar San Francisco. Recently rebooted and half-disconnected from power and memory, this metal found family slowly comes back online to each other, to the internet, and to the messy recent history that shaped them.

California and America (damn Yankees) have landed in a tenuous cease-fire after a civil war. California grants its robotic workforce a form of pseudo-citizenship, progressive on paper and uneven in practice. Through each IC-powered friend, we see the tiers, loopholes, and quiet humiliations of being almost a citizen.

The tension hums throughout. Humans who welcome robots. Humans who resent them. Regressive, human-first politics that insist personhood must remain exclusive. The story is also full of all-too-relevant modern tropes: unexpected loves, media manipulation, and Yelp review–bombing psy-ops deployed as soft warfare.

The politics feel procedural rather than symbolic. Citizenship here isn’t a metaphor, it’s infrastructure. Rights are granted, revoked, negotiated, and selectively enforced. That framing tracks with Newitz’s background observing how power actually gets written into systems, not as declarations, but as policy.

At its heart, though, Automatic Noodle is about memory, belonging, and joy. It is also, unexpectedly, about food. The noodle obsession is mouthwatering, so fair warning: expect to be hungry. The robots’ relationship to taste and eating is delightful and genuinely funny.

One character, a taste-bot resembling an octopus, experiences flavor the way a real octopus does, tasting everything it touches with all eight of its appendages. Cooking becomes a distributed sensory event, equal parts precision and play.

In the aftermath of conflict, these robots find purpose not through revolution but through care. Through craft. Through opening one of the best noodle shops a battered San Francisco has to offer, robot-run or not.

What is DDX?

DDX positions itself as a global think-tank at the intersection of UX, innovation, new ventures, and digital leadership. In practice, it functions as a distributed research node: design executives, product strategists, futurists, researchers, and founders convene to interpret shifting technological conditions and exchange field intelligence.

BOOT / DEEP MODE

Not just a design conference, DDX San Diego was a pressure test. It was measuring the next direction of UX, and how designers are metabolizing the AI epoch. If DDX NYC illuminated the scaffolding we needed to build, San Diego turned its attention to the operating system itself.

1. Sebastian Gier —

Privilege, Participation, and Distributed Futures

Sebastian’s opening wasn’t just a tone-setter but an ideological stake.

Most conferences begin with logistics; this one began with ethics.

“Design is a privilege.” — Robert Fabricant (via Gier)

It’s not just a motivational quote. It’s an observation of a system. Design privileges certain vantage points. Certain geographies. Certain bodies. Certain power positions.

Then he layered in the geopolitical shape of innovation:

10% of countries account for 80% of global R&D.

What makes this profound is not the inequality but what it implies about the shape of future systems. If design materializes futures, then the future has been — and still is — designed by a handful of nations.

Gier’s reframing:

“Grow like a dandelion, not a leviathan.”

This is the closest thing DDX has had to a manifesto.
Centralized growth creates fragility.
Distributed growth creates resilience.

Cyborg analysis

Complex adaptive systems — biological or technological — survive through replication, not mass.
Distributed agency is the cyborg mode.
A future built through many nodes, not one tower.

When placed against the rest of the conference, Gier’s opening reads like the core protocol running underneath all other conversations:

Designers must become stewards of distributed futures, not guardians of centralized ones.

2. Don Norman —

Humanity-Centered Systems and the Infrastructure of Trust

Norman’s presence brought the room into a more reflective headspace.
His message: the field he helped define must evolve again.

Read more

There was a felt shift in tone, posture, and the collective nervous system at DDX San Diego.

Just a matter of months after DDX NYC (which I write about here) I sensed a more tuned and cohesive perspective about AI in the field of user experience and digital design. People were less spooked, moving toward preparation and analysis. Positioning instead of posture.

// sys.log

calibrating… detect shift in crowd affect. fear subsiding. designers thawing from freeze state. posture → position.

Design is moving from screens to systems. From apps to agents. Using relationships as control loops.

San Diego felt like design stepping out of the screen and into the system: agents, rituals, city sidewalks, and the quiet OS of brand. If NYC was “scaffolding the system,” San Diego was “tuning the instruments.” Below are the clearest tones I heard across frequencies, re-transmitted through the cyborg lens.

// Sebastian Gier — Opening Pulse

The signal I captured from Sebastian was this: design is a privilege that materializes futures. (The line “Design is a privilege” is attributed to ex-frog design authority Robert Fabricant.)

Layer that with a data point—“10% of countries account for 80% of global R&D spending”—and you get a clear call to rethink participation and expand who gets to design the future.

“Grow like a dandelion, not a leviathan. Network, don’t centralize.”

As a growth strategy it’s resilient and radically inclusive. But growth needs direction: grow the network into under-represented populations when you can.

// subsystem.attitude
distributed agency > concentrated control
resilience emerges through replication
networks survive what empires cannot

Cyborg lens: distributed agency is resilience. Replication beats sheer mass. Every good cyborg knows.

// Don Norman — Better Together: Why Partnerships Matter

If you’re not familiar with Don Norman, do your homework. He helped shape the field of UX; his Design of Everyday Things taught many of us to notice the design of everyday life.

At DDX he and Sebastian Gier shared a casual, useful fireside chat. The through-lines follow.

Move from human-centered to humanity-centered. This flips the paradigm and echoes Gier’s call for inclusion. Community-first methods beat parachute expertise.

Share struggles, not just wins. It teaches better, signals pyschological safety and invites others into a culture of candor.

Become organizationally fluent. Speak ops and finance. Show the spreadsheet—or at least how your work fits it. If you can’t plug into the org’s logic, you can’t defend the work (or grow the team).

For the AI age, Norman offered a concise reframe:

“You’re not looking for a website; you’re looking for an answer.”

Patterns are leaning harder into answers over paths. That’s an interaction contract shift.

// sys.notice
input modality changed: search → synthesis → answer.  
the interface dissolves. intent remains.

Cyborg lens: questions, not clicks, are the new primary input. Design for answers (and for how answers are made).

// Scott Robinson — Now / Near / Next (2025)

Scott’s talk made my cyberdeck flutter. I’ve advocated for wet and squishy UI for awhile. Black mirrors are boring. Scott’s vector matched the mood: move beyond glass.

Voice. Gesture. Gaze. He pointed toward design that spans HCI into something closer to HCR (human–computer–robotics)—and MMI (machine–machine interaction) as agents begin talking to agents without us.

He also called to swap the linear “script” for the infinite loop. Readers here will recognize that terrain: we are in and of the cybernetic loop.

// subsystem.loop
linear → cyclical  
static → adaptive  
screen → space  
user → participant  

We’ll need new rituals and roles. One provocation Robinson dropped was AIR—AI Resources—like HR, but for agents and their conduct. While this may feel speculative, it isn’t. It’s the practical UX work emerging right now.

He then offered three fronts of fertile fieldwork: civic infrastructure (sidewalk etiquette for robots), health autonomy (a calmer, evidence-tuned way to inform choices), and education for all (personalized tutors—obligatory nod to Stephenson’s Diamond Age).

Cyborg lens: UX becomes societal middleware. Norms, not just screens and flows.

// Alex Diener — You Can’t Have Lunch with AI

The title says it all. You can eat lunch with a Chatbot. But that’s not the point.

Work runs on relationships. Mentorship and cross-discipline trust are forged through durable, embodied contact. Post-pandemic, many of our rituals atrophied. We have to rebuild them deliberately.

In a post-Covid world, we work against headwinds: time starvation, siloization, and remote drift. How do we counter that? Diener says: be intentional.

To press against the headwinds, Alex offered ready-to-action steps.

1. Perform a relationship audit: Which relationships are working? Which need work? Why?

2. Set goals: Set some goals for your relationships. Make them stronger, define them better.

3. Write it down: Don’t let the goal slide or misform in memory.

4. Go do it (in person): Take a co-worker to lunch. Take a finance guy on an inspiring trip to a museum, or the ops lead to see a performance.

5. Be the native face of design: Don’t be passive or pushy. Just be your natural, designer self.
   
   

None of this can be outsourced or automated away.

// sys.human_only
relationship bandwidth cannot be virtualized.  
embodiment required.  
latency = emotional, not network.

Cyborg lens: social firmware is still human-only.

// Gleb Kuznetsov — What Happens to Design When Every Pixel Can Think?

We’re moving from app-centric to agentic. Generative interfaces will form around goals instead of force-marching users through deterministic flows.

“People now ask, not tap.”

Kuznetsov offered a clean division of labor. AI brings speed, scale, automation, consistency. Humans bring empathy, imagination, taste, strategy

He also named the fork that matters for how we relate to AI: Anthropomorphic agents (Jarvis-esque emotional stand-ins) and Extension-of-mind tools (the cyborg path).

// subsystem.recommendation
choose extension-of-mind  
synthetic intimacy is a distraction  
cognitive augmentation is the upgrade
anything else is cosplay

Whichever path you take, the cyborg is the point. Augment cognition; don’t chase replicas of “human.”

// Leadership Panel — (Paul Lafata · Alex Diener · Madison Stevens; mod: Sebastian Gier)

Panels can be tough; this one was fruitful. Bottom line up front: measure yourself by others’ growth. The panel snapped the discussion back to earth. They guided the conversation away from agents and pixels, toward people and the messy reality of leading them.

Emergent guiding principles:

Culture breathes. Make expectations explicit. Designers act as brokers as AI redraws role lines. And above all: protect entry-level pathways. Preserve manual synthesis, lived depth, and awkward, necessary early-career practice.

In response to an audience question, these leaders also offered some clear hiring signals. If you’re in the market for an entry into your design career, or to grow your current position, cultivate these traits: curiosity, decision frameworks, comfort with ambiguity, hunger for the hardest problems.

// sys.org
culture = living organism  
leadership = metabolic process  
design teams = distributed nervous systems

Cyborg lens: steward the human network that stewards the machine network.

// OUT

If NYC was about scaffolding, San Diego pushed us toward agents and cultureware—brand kernels, human rituals, and systems that touch the street.

I’ll publish a deeper paid debrief next (including an NYC→SD shift analysis and per-talk artifacts). Stay tuned and upgrade if want the deeper circuitry.

For now: which ritual will you adopt this week: draft a prompt library, a trust checklist, or simply lunch?

If you attended DDX, or just want to chat about anything here, please reach out; let’s grow the network like a dandelion.

You might like these transmissions

DDX NYC: Systems, Signals & Scaffolding
A field report on the earlier phase of AI-era UX. It pairs well with the San Diego post because you can trace the shift from fear and structure-building to confidence, agency and system fluency.

The Cyborgs Aren’t Coming
A grounding signal on our everyday entanglement with tools and invisible systems. Read this next if you want a primer on the cyborg lens that underpins the entire DDX San Diego recap.

Pilot Mode
A dive into designing trust, fluency and embodied cognition inside a next-generation cockpit. This connects cleanly to the agentic and beyond-the-screen conversations that surfaced in San Diego.

If this signal resonates, amplifying it helps the network grow with intention. Share Signal+Static with a friend or colleague and help us grow like a dandelion.

Share

root/ CYBORG

You’ll see the term cyborg in Signal+Static’s thesis. And scattered throughout this publication.

I use it heavily. The image it conjures is an iconoclast. It applies to our lives in ways that leverage juxtaposition as a perceptual hack. I love the origin—and it might surprise you. It wasn’t born in science fiction, but in speculative science.
(Is there really a difference?)

// term “cyborg” queried for origin. results…

Term: cyborg (cybernetic organism)
Coined: 1960
Publication: “Cyborgs and Space”
Published in: Astronautics (September 1960)
Authors:

• Manfred Clynes: engineer, neuroscientist, cyberneticist

• Nathan S. Kline: psychiatrist, psychopharmacology pioneer

The article laid out a radical proposal: instead of building fully Earth-like environments in space, adapt the human body itself. Create internal, self-regulating systems that could unconsciously manage the body’s survival in hostile extraterrestrial conditions.

Not a metaphor; this was systems engineering for off-planet life.

// quote — definition origin moment

“For the exogenously extended organizational complex functioning as an integrated homeostatic system unconsciously, we propose the term ‘Cyborg.’”
— Clynes & Kline, 1960

THE SPREAD OF CYBORG

After its coinage, cyborg remained mostly in aerospace, biomedicine, and systems physiology. It didn’t explode right away. It just floated, quietly orbiting within academic and engineering circles.

Still, it leaked.

Writers in speculative fiction began experimenting with the concept throughout the ’60s. Sometimes explicitly, sometimes not, but always referencing this hybrid techno-being.

• Frank Herbert’s The Eyes of Heisenberg (1966) features genetically manipulated humans integrated into life-sustaining systems.

• Anne McCaffrey’s The Ship Who Sang (1961–69) is centered around a brain-ship hybrid: a human mind permanently wired into a spacecraft.

• Samuel R. Delany’s Nova (1968) envisions socketed bodies interfacing directly with starship drives.

• The comic Space Man (1962) is one of the earliest uses of the word “cyborg” in fiction.

• The film Cyborg 2087 (1966) made the term cinematic.

Most of these examples stretch and shape the cyborg into narrative possibility. Always augmenting bodies and entangling human agency with cybernetic feedback systems. Even when the term isn’t present, the logic is.

By the 1980s, the cyborg would notably rupture into culture. Twice.

First, it was radicalized by feminist theory: Donna Haraway’s 1985 essay “A Cyborg Manifesto” repurposed the term as a theoretical tool. A political subject. A boundary transgressor. Neither wholly natural nor fully artificial. The cyborg became an icon of resistance to essentialism and purity narratives.

Second, it surged into cyberpunk fiction and media. Neuromancer (1984), RoboCop (1987), Ghost in the Shell (1989 manga, 1995 film). All trafficked in flesh-metal junctions and neural jacks. But beyond aesthetics, they pushed the deeper questions of system dependence, memory, autonomy, and identity.

And like any good signal — it split.

Some use cyborg to mean full biomechanical modification. Titanium limbs, brain implants and neural links. Others apply it more broadly: anyone entangled in technosystems. Offloaded cognition, augmented perception, and compromised autonomy.

I’d argue both are valid; one follows the blueprint, the other shows how widely that blueprint applies.

// spread — cultural relay begins

Cyborg escaped its origin.
Left Earth.
Left rigid definition.
Entered language.

CYBORG SYSTEMS IN REAL SPACEFLIGHT

While I often use the term to describe our terrestrial techno-entanglements, we shouldn’t lose sight of the original directive:
Modify the human to survive space.

That vision still pulses through real-world astronautics. And while we’ve leaned heavily on environmental controls like pressurized capsules and orbital stations, we’ve also pursued many of the exact adaptations Clynes & Kline implied.

A) Spacesuits as Externalized Organs

The suit is not just clothing. It’s an extension of physiology.

• Oxygenation, thermoregulation, radiation shielding. Prosthetic homeostasis

• Apollo suits were mechanical marvels; today’s xEMU suits include internal feedback systems and real-time biometric monitoring

• NASA calls it a “portable ecology”[^1]

B) Pharmacological Intervention

Space alters biology.

• Drugs behave differently in microgravity: absorption, efficacy, and metabolism all shift[^2]

• Astronaut kits now include cognition stabilizers, antiemetics, sleep aids

• Long-duration missions require preemptive pharma: bone-density drugs, radiation prophylaxis, mood stabilizers

What you ingest becomes part of your life-support loop.

C) Simulation & Systemic Training

• Astronauts train in analogs: Mars domes, underwater habitats, vacuum chambers

• Performance data is fed back into hardware redesign and personal preparation

• The Human Research Program at NASA tracks these variables longitudinally[^3]

D) Embedded Feedback Loops

• Continuous biometric telemetry

• Environmental adaptation systems

• Experimental robotic interfaces (e.g. Canadarm2, robotic surgery concepts)

Our systems are aware of us. And they act in response.
Feedback is no longer metaphorical.

We may not be fully autonomic, self-regulating post-human hybrids yet.
But we are cybernetic in function.

EARTHBOUND CYBORGS

“The cyborg is no longer in space. It’s (I’m) on the subway. Holding a phone. Adjusting a smart insulin pump. Refreshing a feed.”

This isn’t speculative anymore. The homeostatic logic that defined the cyborg is now distributed across terrestrial networks.

We live within ambient systems:

• GPS constellations regulate our location

• Atomic clocks in orbit anchor our time

• Submarine cables route our cognition

• Neural interfaces manage our health

• Predictive algorithms shape behavior

We don’t just use these systems.
We move through them, just map it.
We’re co-dependent, but where we can: we should build them.

That’s entanglement.
That’s cybernetic identity.

Cognition is offloaded.
Behavior, altered.
Location: triangulated.

You don’t need a space suit to be a cyborg.
You just need a signal.

THE TERM THAT LEFT EARTH

“Cyborg” began as a literal engineering concept—born in a footnote, in a science journal, in a decade racing to escape gravity.

But like any cybernetic system, it evolved through interaction.

It moved from:

• lab → body politic

• feedback loop → philosophy

• orbit → interface

• astronaut → everyday user

We didn’t send cyborgs to space.
We became them waiting to go.

// end tramsmission

Leave a comment

References & Links

1. Clynes, M., & Kline, N. (1960). Cyborgs and Space. Astronautics.

2. NASA Human Research Program: nasa.gov/hrp

3. xEMU Suit Research: CHUT Design Report

4. Pharmacological Behavior in Space: SpringerLink Article

5. The Ship Who Sang: Wikipedia

6. Nova (Delany): Wikipedia

7. Science Fiction Encyclopedia – Cyborgs: sf-encyclopedia.com

Dial-Up

If you’re a child of the 90s or early 00s, you can probably hear it vividly.

Picture this: you’re about to hijack the only home phone line. Maybe you even kick your big sister off a call. You hit “Connect” on AOL and there it is: the sound of the internet arriving.

Machine-elf chatter. Beeps, errs, brrs. Warbles. Hiss. Static. The soundtrack of an era, etched into collective memory. Meanwhile, your sister in the next room is already yelling that you just cut her off mid-sentence.

// auditory UX: nostalgia protocol engaged

That unforgettable “Dial-Up” sound has a name you probably never knew: Frequency Shift Keying.

The Song Beneath the Static

It’s more than nostalgia. FSK literally sang information into the line.

When you hit connect, your modem dialed your ISP’s modem. And they talked.

That song wasn’t background noise. It was the communication itself, carried in the voice-band (300–3400 Hz), the same slice of spectrum as human speech because the system repurposed lines already tuned for voice.

The sequence was a handshake: an introduction, a negotiation, and an agreement. Something like:

“I’m a modem attached to a human. You’re the traffic controller. Let’s trade IDs, agree on the terms, and open the pipe.”

FSK works by shifting tones: one frequency for 0, another for 1. Multi-level FSK adds more notes, letting modems “hum” whole words.

// signal == message

Why bother with a song? Because frequency cuts through noise better than volume. On messy lines full of static, tone survives. Think Nokia ringtones slicing through a noisy bar, or jingles that burrow into your brain. FSK is a melody engineered for survival.

Anatomy of The Ritual

For the curious (and the nerdy), here’s the anatomy of the sound. Like a good DJ, a 56k modem handshake layers FSK, Phase Shift Keying (PSK), and a few amplitude (volume) tweaks into a ritual of alignment between two machines:

Step 1 – Carrier tone (~1 kHz–2 kHz)

A piercing test tone. One modem says: “Lock onto me. This is our anchor.” Like a tuning fork before the song.

// alignment ritual: begin

Step 2 – Probing (chirps, sweeps, rising/falling tones)

Quick machine voices. “Can you hear me here? How about now?” A long flat beep clears echoes: “Silence, please—we’re talking.”

Step 3 – Capabilities exchange (chirps, R2D2 banter)

Two astromechs nervously introduce themselves.
“I can do 28.8 kbps.”
“I can do 56k with compression.”
They align on dialect.

Step 4 – Training (descending warbles)

Viscous swoops sliding down. A calibration test: pseudo-random sequences probing the quirks of this particular line. Like a sound engineer: “Check, one two.”

Except instead of a guy mumbling into a mic, it’s R2D2 on a slide whistle.

Step 5 – Sync (call-and-response beeps)

The most memorable part. Two distinct tones ping back and forth:

“You hear me?”

“I hear you.”

Timing and phase lock in. Without it, bits drift into chaos.

Step 6 – Silence

The sound stops, but the data begins. The toll is paid; the on-ramp opens. From here on out, you’re no longer a listener, you’re a user.

The handshake was a ritual of alignment. A tuning fork, a birdsong, a training drill, a call-and-response, and then quiet. A fleeting negotiation that carried no evidence once the line went silent.

// the internet sang to us

That’s what compels me. These little sonic artifacts laid the foundation of how we felt the internet: fragile, noisy, alive. A culture encoded in tones now mostly forgotten, but unforgettable.

Other Dialects

While dial-up is gone, FSK and its siblings, PSK and ASK, still hum beneath our tech, each tuned to its own niche.

FSK is the song of the internet. Sometimes audible, often ultrasonic, it still powers hospital pagers, Caller ID, garage doors, key fobs. And in noisy environments—satellites, marine radios—FSK thrives because tone cuts through static.

PSK (Phase Shift Keying) is subtler. The backbone hum of modern connectivity. Instead of changing pitch, it shifts where the wave starts. Efficient and resilient, PSK underpins early Wi-Fi standards (BPSK, QPSK), 3G/4G cellular cores, and satellite links that stretch across impossible distances.

ASK (Amplitude Shift Keying) is the ancestor—the on/off flicker at the root of it all. AM radio is ASK at scale. Today it lives in RFID tags and cheap remotes. Want to see it? Point a TV remote at your phone’s camera. The IR pulses flicker visibly on screen. That’s amplitude shift.

Every Interface Has Its Handshake

Different schemes for different niches. But together they remind us: every connection is a handshake.

Dial-up let us hear it. Today, PSK and ASK run silent, woven into the wireless ether. You don’t hear the negotiation anymore but you feel it. A tap-to-pay that lags, a Face ID that misfires, a Wi-Fi that drops at the wrong moment. These are still handshakes, still rituals of alignment.

That’s the cyborg condition in miniature: tools aren’t neutral. They teach us timing, rhythm, fluency. When the handshake works, it vanishes. When it stutters, it jolts us.

So the lesson is this: designing and defining interfaces isn’t just about data transfer. It’s about building trust in the loop— the feeling between memory and machine, between body and code.

// end transmission

More from Signal+Static

If this resonated, check out these connected transmissions:

Pilot Mode — on cockpit design and what it means to trust your instruments.

Obsessive Interfaces — on the love (and obsession) we give to everyday tools.

Glossary: From the Loop — living definitions of cyborg design language.

Leave a comment

An Unexpected Detour

I planned out the first few Luke’s Hand pieces before writing them. I’d start with films. Blade Runner, then Ghost in the Shell. But I picked up a copy of Philip K. Dick’s Do Androids Dream of Electric Sheep at a local bookstore while taking a break from writing — and I dug in.

This post became an almost-follow-up to Lukes Hand 01 // Blade Runner. Here, I’m tracing alignments and divergences between the novel and the film, and digging into what those points of contact reveal when you read them together.

Sheep on the Roof

Do Androids Dream of Electric Sheep is not a book about androids falling asleep, or robots with insomnia. For years I misread the title, letting the image of a snoozing android drift past me.

But sheep—electric or otherwise—are central here. In Dick’s toxic future, real animals are rare and precious, an ultimate sign of care and status. Deckard’s sheep is fake. He tends it obsessively on his rooftop, a public performance of empathy and affluence. He longs for the day he might keep a real animal, thumbing through his tattered copy of Sidney’s Catalogue of Animals.

In Blade Runner, Deckard spots the owl’s artificiality in seconds. In DADoES, Rachel convinces him hers is real — and that difference reframes the question, “Do you like our owl?” as a loaded, status-laden inquiry.

// Cyborg theory: Identity is performed, not inherited. The sheep is a prosthetic for belonging.

A World in Decay

Dick’s Earth is not just rainy; it’s collapsing under post-nuclear fallout. Radiation has stratified society. Those with cognitive degradation, “specials,” are pushed to the margins, their humanity reduced to slurs like “chickenhead” or “anthead.”

The irony is sharp: animals are revered yet weaponized as insults. They’re currency and curse in the same breath.

// Signal: Systems can hold contradictory codes — reverence and rejection — without “resolving” the dissonance.Copy code

The Two J’s

Scott’s J.F. Sebastian and Dick’s J.R. Isidore are cut from different cloth but wear the same thematic patch: the underdog. Both are marked as “less than” yet exhibit profound care.

Sebastian is a genetic designer, a maker of replicants; Isidore drives for an artificial-animal repair service. One builds the system, the other maintains its byproducts. Both take in Pris — an android — without hesitation.

// Cyborg theory: Empathy here is not about purity of origin; it’s about permeability of boundary.

They may be the most “human” characters in their respective worlds, not because of capability, but because of their capacity for empathy.

Machines for Feeling

Empathy is the prime currency in both versions of the story, but DADoES scales it beyond the job-site precision of Blade Runner. Here, it’s systemic: quantified, displayed, curated.

The Voight-Kampff test still decides who’s in or out of the human club. But humans rely on machines to maintain the very emotions the test measures. Mood organs tune their affect. Empathy boxes network their grief. Artificial animals scaffold their capacity to care.

// Cyborg theory: Humans here are not “enhanced” by technology — they’re sustained by it. Prosthetics of empathy.

It’s a deep irony: remove the prostheses, and would empathy still stand?

Mercerism’s Feedback Loop

Mercerism may be a hoax, but it’s also a kind of networked cyborg ritual. Participants jack in, feel one another’s pain, and climb a hill together in shared simulation.

The experience is technologically mediated, but the emotions are real. That’s the pivot: authenticity isn’t the point. Effect is.

// Signal: The networked human as dreamer. 
// Static: The android as dreamer.

Conclusion // Dreamers in the Loop

In Blade Runner, empathy is situational — tested in the field, weaponized in interrogation. In DADoES, it’s infrastructural: measured, broadcast, ritualized. Both tempt us with the bright line — human here, android there — even as their worlds erode it.

Yet neither humans nor androids can navigate without their prosthetics of feeling. Mood organs to start the day. Empathy boxes to belong. Animals, real or not, to practice care. Remove them, and the whole fragile system shivers.

// Cyborg theory: A “bright line” between human and machine is just another interface protocol.

Maybe that’s the lasting image: dreamers—human and otherwise—wired into the same loop, building their selves from borrowed signals. And the question that hums on the static:

If all our feelings are mediated, whose dream is this?

// end transmission

If you’re new here, you can subscribe to get essays like this, along with field notes and occasional dispatches from the strange edges of human–machine culture.

We’re already in the loop. Let’s see what kind of signal we can find in the static.

// P.S. this post follows

→ Luke’s Hand: Blade Runner

// and you might also like:

→ Obsessive Interfaces. // On the phenomenology of tools, and why we sometimes become more interface than operator.

→ The Cyborgs Aren’t Coming. // A reminder we’ve already been here a while.

The Briefing

In my professional life, I lead up a team of UX Designers, Strategists, Product Shapers and Front-End Developers. Some time ago, an interesting opportunity arose. A new and exciting start-up approached with an intriguing proposition.

We were brought in to design the next generation of human-machine interface.

A screen-based cockpit for a new kind of vehicle. The kind of brief UI designers dream of. At least I do.

The term they use to describe the vessel is sea-glider. A new vessel that uses ground effect to cruise just above the water (okay, it’s been done before, but let's leave that story for now1).

A plane-but-not-quite, it hovered just below FAA classification. Low enough to dodge regulation, fast enough to change how people move across water.

We weren’t designing for pilots, we were told. We were designing for mariners—boat operators with limited flight training, used to simple affordances:

one wheel, one throttle.

push forward, go forward.

turn the wheel, change direction.

// control schema: simplified 
// user assumption: maritime, not aviation

We had to build where maritime navigation meets electric propulsion diagnostics.

A weather-aware, camera-assisted system. Collision detection. Route planning. Possibly even a heads-up overlay on the windshield.

It felt like we were designing the future. Enabling a captain to fly a plane with boat-like controls.

The Vessel

The vehicle didn’t exist. Well, not yet. Not entirely.

The only flight so far? A quarter-scale model flown remotely.

No pilot, no passenger. Just sea-foam, sensors, and radio signal.

It floated and cruised on its hull like a ’70s Starcraft or a Boston Whaler. Then it rose onto its foils, slicing the chop like a new age America’s Cup AC75 racing boat. (And if you haven’t seen one, google it.2 Star Wars shit.)

Anyway, it started to really rip. And then—it snapped right out of the water. It flew.

It landed. And then it did it all again.

The design was proven in miniature and theory. And don't get me wrong, it was a major achievement (and cool as hell).

But no onboard interface. No pressure. No weight. No cockpit and no pilot inside.

Not yet.

The Dream

So we got to work designing a next-gen cockpit interface for a vessel that didn’t exist yet.

This was the dream gig.

Since we were free of FAA design space, the idea was: take the affordances mariners already knew. Pair them with Tesla-grade situational awareness. Make it easy. Easy to sail and fly. And above all, easy to train on.

Besides the throttle and the wheel, a modern electric vessel needs telemetry. The operational state of all twelve propulsion motors. Steering systems. Battery health. Electric load balancing.

All of it fed back to the user in real-time—without overwhelming them. After all, the vehicle was supposed to take care of most of the details.

We imagined a primary view for navigation: route planning, weather adaptation, visual obstacle detection. Maritime charts augmented with forward camera feed all on screen. Maybe even a heads-up overlay on the windshield. There's some very compelling tech to achieve that today.

It felt like science fiction.

The kind of project you’d expect to see designed by Territory Studio (the FUI team behind Blade Runner 2049 and the new Dune, to name a few key projects)—but brought into the real world.

Sleek, speculative, near-future UI made tactile. We were building new interface from the ground up. Or so we thought.

The Test Pilot

Then Dylan showed up. Six-foot-something. Ex–Air Force, he flew F-16s in service, flies 747s now. A few days a month he flies halfway across the world like it’s a morning commute.

He introduced himself by his call sign—a well-known folksinger. So that’s what we all called him. Here, we’ll call him Bob Dylan.

Every concept we showed him, Dylan liked. Every concept we showed him was wrong.

// signal detected - interface mismatch

When you’ve logged thousands of hours in military and commercial cockpits, you’re not looking for aesthetics. Dylan appreciated them, he really did.

But a pilot is constantly scanning, feeling for what’s off.

We’d jack into the prototype screens in the sim room, power up the projection environment, and he’d look up at the fake water, down at the readout and tell us what he couldn’t see—not because it wasn’t there, but because it wasn’t where his body expected it to be.3

There's a need for immediacy. You have to understand system feedback as quickly as your nervous system can allow. That means every interface affordance is prebuilt in the pilot's mental model. Not learned for this particular control.

The Reset

The shift happened slowly.

At first, Dylan liked what he saw. He was open to the ideas. Curious about the interface concepts. Even optimistic.

But none of them were right. Not because they were messy or unpolished. Because they didn’t match the logic he’d trained into his body from years of flying F-16s at supersonic speeds, and 747s full of passengers at cruising altitude.

Now, in this project, he’d be flying just a few stories off the water. Lower, yes. But risk remained high. You might even say higher.

The margin for error narrows when you’re that close to the surface.4

The systems needed to be legible at a glance. Trusted at a glance. Every bit of latency, novelty, or doubt could mean delay.

So we pivoted. I spent hours in Microsoft Flight Simulator. Yes… for the visuals. But not the views. I needed to understand how different aircraft displayed the same information.

How altimeters behaved. How attitude indicators were placed. How situational awareness lived in the margins of each panel--somewhere between focus and periphery but not quite either.

Each cockpit had a language. I needed to become fluent enough to design in dialect.

We weren’t building a new interface. We were translators with a new goal: fluency.

The Outcome

The interface? It looked cool, just not Blade Runner. Not Dune.

It wasn’t the cinematic HUD we imagined. It was tight, it was familiar and trusted.

Most of our speculative interface was gone.5 What remained were a few subtle evolutions. Novel, vessel-specific features I can’t outline here. (Buy me a drink and sign an NDA? Then we can talk.)

Altimeters, vertical speed tapes, system health displays—they were all re-contextualized but not reinvented.6

Semantic color definitions remained: teal for set values, magenta for actuals, and so on.

It was a recalibrated vocabulary. One designed for real humans doing high-risk work in fast-moving machines. And that was pretty cool.

As a kid, I used to stare into cockpits whenever I boarded a plane.

The dials, the switches, the glow. These are the elements of cockpits I remember oggling every time I boarded a plane as a kid. This interface still had all that. But now, I understood what it meant.

And why it had to stay mostly the same.

// interface: stabilized 
// trust vector: intact 

A Quick Reflection

In the end, this wasn’t a story about designing the future.

It was about designing for memory. Moreover, for fluency. For a body already trained to trust certain shapes, rhythms, and signals. The dream of speculative interface collided with the reality of lived experience—and in that collision, something deeper emerged.

Every interface is a negotiation. Between novelty and recognition. Between invention and embodiment.

You can’t replace intuition—you have to design inside of it. From a cyborg perspective, it is akin to surgery. Got to know the technological appendages you’re tinkering with. Learn the old patterns so you know what’s new.

That’s the tension at the core of UX work: Make it feel new. But make it understandable in a split second.

Especially in mission-critical systems, where the friction is sharper. But the lesson holds across every product, each with a different speed.

You’re not just designing what a user sees. You’re designing for what their body expects to happen next.

This is cyborg design. Getting closer to the nerve endings.7 Building interfaces that aren’t just visible—they’re felt.

That means understanding the grammar of legacy systems, the syntax of trust, the cadence of practiced loops, and the dialect of embodied feedback.

Where it matters and when the opportunity is right, you can insert friction.

A new and alien interface looks cool. It feels satisfying to design. And it can be thrilling to use once you’ve learned it. But with learning comes friction. It’s reprogramming.8

So the question is never “should this be new?”

It’s “where and when is it worth it to ask someone to learn?”

And where someone is being asked to learn, that's a behavioral intervention. It's where transformative products shine. But use it with intent, and with caution.

This isn’t just product design.
It’s a feedback negotiation between human and machine.
Between memory and system.
Between the cyborg you’ve already become—and the one you’re still programming.

// end transmission

Support the signal: If you’re finding value here, sharing Signal & Static with a friend or colleague helps this space grow intentionally.

Share

We’re already entangled with our tools.

Signal+Static explores design not just as craft, but as a systemic negotiation between the learned, the speculative, the embodied, and the technological. It believes we are cyborgs, and might need to extend our linguistic apparatus with self-aware terminology.

This glossary is a living document of terms that emerge across essays, field notes, and moments where design meets interface friction. Expect semi-regular updates and redefinitions.

It will evolve. And loop.

Glossary

<!--
  Document: signal_static.glossary
  Version: 1.6
  Status: LIVE
  Last-Updated: 2025-11-30T22:07-0500
  Author: signal+static
  Project: Glossary of Posthuman Terms
  Mode: cyborg-lexicon / loop-aware / chrome-stained
  Notes: Structure normalized under v1.6. Entries alphabetized per source.
-->

Terms from Pilot Mode

Behavioral Intervention

Tags: UX design, friction, intentionality
Any interface that slows the user on purpose, prompting reflection or rerouting behavior. Used with care, it becomes a tool for reorientation. Applied carelessly, it breaks the loop.

Cyborg Design

Tags: posthuman UX, embodiment
Design that operates inside the user’s extended sensory system. Less about novelty, more about syncing with familiar input rhythms and emotional mappings. The designer’s role shifts from toolmaker to nervous system co-architect.

Interface Fluency

Tags: learned behavior, UI literacy
The unspoken language of a system a user already knows. Where each icon lives, how it behaves, what it feels like under pressure. A kind of internalized grammar that emerges through repetition.

Language Drift

Tags: semiotics, design systems
When familiar interface elements are redesigned without honoring their functional ancestry. The result looks fresh, maybe even elegant, but chips away at collective fluency.

Reprogramming

Tags: learning cost, UI adoption
The background tax of learning new patterns. Every novel interaction demands attention, creates latency, rewrites instinct. It can delight, but it always costs.

Situational Compression

Tags: cognition under pressure, interface timing
The shrinking of time and cognitive margin in high-stakes scenarios. Every element must respond at the speed of instinct. The interface either compresses cleanly or breaks under load.

Trained Loop Fidelity

Tags: muscle memory, feedback loops
The embedded rhythm of a user’s feedback-response cycle. Disruption creates lag, even if the new system is technically better. Fidelity means honoring the body’s memory of motion.

Terms from Luke’s Hand: Do Androids Dream of Electric Sheep

Bright Line Fallacy

Tags: human-machine boundary, identity theory
The mistaken belief in a sharp line between humans and machines. Feels clean. Fails under pressure. Experience leaks across the border.

Empathy Prosthesis

Tags: emotional tech, speculative UX
A device or system that simulates, supports, or structures the experience of empathy. Sometimes a gateway. Sometimes a gatekeeper.

Networked Dreaming

Tags: collective identity, machine collaboration
When individual imagination blends with shared systems—social, neural, digital. Identity disperses. Boundaries dissolve. The dream becomes a shared executable.

Prosthetic Removal Paradox

Tags: post-augmentation self, techno-loss
The uncertainty that follows after an extension is taken away. Did the feeling come from you, or the device? What remains when the feed cuts?

Systemic Empathy

Tags: institutional emotion, performative systems
When empathy becomes infrastructure. Measured, scored, enforced. The feeling becomes a metric. The system starts to smile.

Terms from Agents, Cultureware, and the Human Network Behind the Machine Network

Agentic Interface

Tags: AI design, goal-based UX
An interface that reacts to intent rather than dictating a flow. You signal your aim. The system assembles the route. More verb, less map.

Anthropomorphic Trap

Tags: design pitfalls, synthetic personhood
The urge to make AI look and act like us—smiling UIs, chatty voices, synthetic charm. It calms the user but hides the wires. Trust without capability.

Ask > Tap Shift

Tags: interaction shift, inference UX
The move from clicking to asking. From browsing to prompting. Interfaces aren’t waiting to be touched. The interface should anticipate the next request.

Brand Kernel

Tags: brand systems, micro-identity
The smallest possible signal that still carries identity. A color flash. A button feel. A micro-interaction that says: you’re still in the loop.

Cognitive Load-Balancing

Tags: AI-human collaboration, task design
Dividing labor between human and machine minds. The aim is not speed but balance. Offload without off-centering. Share the cognition without dropping the thread.

Culture Drift

Tags: remote work, team dynamics
When the rituals that held a team together dissolve. Usually silent. Often slow. A leak, not a break.

Cultureware

Tags: societal middleware, design ethics
The protocol layer of shared behavior—rituals, defaults, norms—that shape how systems and people evolve together. Not installed. Absorbed.

Design Diplomacy

Tags: hybrid teams, org navigation
The negotiation work designers do in a blur of shifting roles. Mediating overlap, brokering clarity, translating between machines and humans (+ humans and humans, machines and machines).

Entry-Level Paradox

Tags: UX career dynamics, AI acceleration
AI raises the ceiling but erases the floor. Seniors move faster. Juniors vanish. The pipeline eats its own future.

Extension-of-Mind Model

Tags: cyborg theory, augmentation paradigm
A design frame where AI acts as cognitive scaffolding, not a synthetic personality. It extends thought, memory, and decision—without pretending to be someone.

Gaze Interaction

Tags: multimodal UX, attention systems
An input mode based on where and how you look. Paired with gesture or voice, it tracks intent through vision. Eyes as cursors. Attention as input.

Humanity-Centered Design

Tags: design paradigm, systemic thinking
Design for ecosystems, not just users. Moves beyond the individual and into collective outcomes, long arcs, unintended consequences.

Infinite Loop Mode

Tags: systems design, cybernetic UX
A model of operation that never resets. The system is always on, always learning. Linear flows become feedback spirals. You don’t restart. You re-enter.

Machine-Network Stewardship

Tags: leadership ecology, hybrid systems
The act of tending the human network that tends the machines. People maintain code. Code maintains everything else. Stewardship flows both ways.

Social Firmware

Tags: team dynamics, human systems
The quiet layer that keeps groups functioning—trust, cadence, rituals. Unspoken, untracked, irreplaceable. Try to virtualize it and watch it glitch.

Societal Middleware

Tags: cyborg governance, trust design
The etiquette layer between people and autonomous systems (+ people and people, as and as). Rules for robots. Social contracts for agents. Protocols for presence.

System Stewardship

Tags: responsible design, systems UX
Designing not just products, but the systems that produce behavior. Culture is an output. So is harm. Someone needs to own the feedback loop.

Answer-Seeking Behavior

Tags: AI expectations, interface change
Users no longer browse—they interrogate. Curiosity collapses into demand. Systems that don’t deliver answers feel broken, even if they’re right.

Think a term belongs here?

Drop a comment, reply, or @ me with a signal you’re tracking.

This glossary lives and breathes through use.

Leave a comment

Her hand shot up:

“I am a UX copywriter. Do I have a career anymore?”

You could feel the tension ripple through the room.

The conference (DDX NYC) was a few weeks ago now. I wanted to see what stuck naturally, letting the signal come through the static.

Conferences can be whirlwinds of trends, gripes, and half-baked ideas. Sometimes, you need to let the tides of time wash the important flotsam ashore. Or maybe I was just procrastinating, and it was now or never. Both can be true, right?

I had launched Signal & Static the day we arrived in NYC, dragging ourselves through early summer heat, hopping between Tech Week events, excited to attend with a freshly tuned awareness.

She was young, maybe a few years in, eager to map her future in a field brimming with AI hype. The question came after a talk on structuring creative teams. It wasn’t directly on-topic, but it was most corporeal moment of the day.

“Can you tell me how your team uses AI for UX copy?”

The speaker fumbled before admitting:

“We use ChatGPT, for all of it.”

That was it.

It’s becoming common. Microcopy can feel small, unimportant. Something to scratch in later. But those “placeholders” often ship, meaning even the first draft matters. In a perfect world, I’d collaborate with a human copywriter on every word in a flow. But copywriters are often pulled to bigger projects, so yes: I use LLMs for draft copy. It’s better than lorem ipsum when you need to move fast without losing intention.

This moment sticks with me. It's easy to wave off as “just another AI anxiety moment,” but it raises real questions about authorship, accountability, and the value of craft.

Tools have always shaped what we make—not just the output but the way we think about making. That’s the cyborg way. The tool is part of the author. The way the chisel leaves marks in the marble. The way a telegram shapes the message. Systems are always shaping us, too.

What would I have told her? Learn the tools. Use every LLM you can. Know their strengths and flaws. You’ll be more prepared to shape your career—and lead with clarity in the work ahead.

To leaders: think critically about how you use AI. Don’t build a technophobic fortress, but don’t become a hype shop either. The gap between leadership and junior creatives is widening. It’s time to build a bridge.

// signal: co-creation tension detected

Designing for the System, Not Just the Screen

“Experience is not an object. It’s an output.”
—Richard Dalton, Verizon

Let’s be real. I’m about as far from a Verizon fanboy as you can get (do those exist?), but Richard Dalton, Head of Consumer Design, hit on a core truth: [UX] Design isn’t just about screens; it’s about shaping the systems that produce experiences.

You don’t “create experiences.” People have them. Our job is to build and maintain the scaffolding that supports users within the system.

Dalton’s Ziggurat of Impact illustrated this with layered and dramatic clarity:
Experience lives under an architecure of taxonomy, measurement, portfolio, process, people, and is supported by money at the top.¹

Experience is an emergent property of layered systems. You can’t design it in isolation.

Matt Wallaert (former Head of Behavioral Science at eminent design studio, frog) added:

If your design isn’t changing behavior, it isn’t doing anything.

Design is applied behavioral science. Without a behavioral objective, your product’s impact is immeasurable. Sometimes, intentional friction is necessary to guide that behavior.

Together, Dalton and Wallaert give us a methodology:
Be a system steward. Be a behavioral strategist.
The system shapes the experience, and the experience should shape behavior in return.

// cyborg reality: system + behavior = experience

Cyborg Lens:
Cyborgs aren’t shaped by interfaces alone, but by systems underneath. Designers aren’t isolated creators; they are system choreographers. Measurement is how the system senses itself; behavioral strategy is how it steers.

Principles Before Prompts

“Are your design principles sharp enough for AI to execute?”
—Christian Hanke, Edenspiekermann

AI was everywhere at DDX (and everywhere else). The best leaders moved beyond hype, focusing on readiness.

Baylie Brenner-Bruzgis (Twitch) described “synthetic user testing” with LLMs to free up time for deeper thinking and creativity. Her advice: be an AI watchdog.

Christian Hanke (of legendary design studio Edenspiekermann) framed it perfectly:

Before you write prompts, sharpen your principles.

Bland, default outputs are becoming baseline. Strong design principles differentiate your work and your team in an AI-accelerated landscape. Culture, Hankke emphasized, is your new design system. It determines how you navigate exponential change without losing your edge.

Leaders need to know when to slow down, when to move fast, and how to give teams room to do both.

TLDR: Your principles must be operational enough to be executed by machines.

bash > AI integration status: cultural audit required

Cyborg Lens:
If AI is your co-pilot, who’s piloting whom? Tools aren’t neutral; they reshape us. Leadership in design means building adaptive, ethical scaffolding to co-evolve with technology.

Rituals and Autonomy

“Predictability isn’t bureaucracy—it’s scaffolding for creativity.”
—Baylie Brenner-Bruzgis, Twitch

How do you build a strong design culture? By structuring systems that support, not stifle.

Baylie shared effective rituals:

• Repeatable intake processes for scoping and alignment.

• Shared blueprints and transparent tooling (yes, in Jira).

• Rituals for sync and async work to reduce chaos.

Structure isn’t control. It’s cognitive relief, creating space for designers to think, explore, and create.

Community as Ritual

During a roundtable, Dorsa Giyah (Product Designer, RBC Capital Markets) shared how she started informal coffee meetups with designers in Toronto—and brought the practice to NYC. It wasn’t about networking; it was about a repeatable, low-pressure ritual for designers to gather, share, and support one another.

In my studio, we have a monthly lunch hosted by one of our culinarily-gifted product designers. There’s one rule: if you enjoy the meal, you don’t talk shop. Period.

Dorsa encouraged others to build similar rituals in ways that fit their communities. It was a reminder that community is part of design practice, too. Show up consistently, make space, and design conditions for connection.

// community signal: active

Other Signals, Briefly

This piece could easily have been twice as long—there was a lot worth noticing at DDX.

Ryan Leffel (Head of Design, Priceline) reminded us of the power of A/B testing in innovation, bringing to life stories like the Egg McMuffin’s origin and referencing Big (yes, the Tom Hanks movie) as the ultimate user test in a corporate boardroom.

Ruchi Sharma (Meta) spoke to fostering innovation processes inside large teams.

Dan LaCivita shared the PACE framework from emergency response, helping teams assess impact and probability while emphasizing the importance of keeping “team cups full” to support creativity.

These signals deserve deeper exploration, but I’ve kept this dispatch focused. These are the insights that rose to the top.

What Sticks, and Why

It took weeks for the static to settle after DDX. Conferences can overflow with signals. Clarity comes with time.

Here’s what rose to the top:

• Design for systems, not just surfaces.

• Lead with principles before prompts.

• Build rituals that enable creativity, not chaos.

• AI is here—prepare to co-evolve.

That sounds a lot like being a cyborg, doesn’t it?

Reflection

Does this resonate?
What systems are you shaping, what rituals do you hold, and what fears are you facing as you design in exponential times? How are you preparing to co-evolve with your tools?

Hit reply or share your reflections. Let’s explore these signals together.

Leave a comment

// end transmission

You Might Also Like These Transmissions

🔗 Hello World
A welcome transmission, part logbook, part invitation. Where Signal & Static began.

🔗 The Cyborgs Aren’t Coming
We’re already entangled with our tools. A reflection on living inside systems, whether we notice or not.

🔗 Obsessive Interfaces
From mechanical keyboards to titanium pens: why some tools become extensions of self.

Support the signal: If you’re finding value here, sharing Signal & Static with a friend or colleague helps this space grow intentionally.

Share

There’s something off about it. The way people become obsessed with things that, you know, “normal people” let become invisible.

Pick up the bifold check holder and it falls out. The translucent plastic pen probably doesn’t even have a top. You pick it up, leave a tip, do some math, and scribble what looks like a signature? You probably didn’t even think about the pen.

Or maybe. Just maybe.

You picked up the check, gave it a thorough read, and set it down on the closed folder. You reached into your chest pocket, unclipping your bolt-action rollerball—hand-machined, of course, from a solid block of titanium. With an elegant snap, you exposed the writing nub, did your math, and signed. You savored the feel of the engineered rollerball pressing against the grain of the paper, sinking into the leather beneath. The feeling of it. You bolted it shut and returned it to your chest pocket, before replacing the neglected Bic Round Stic to its rightful slot between the covers.

That’s the kind of obsession I’m talking about. A relationship between user and tool that borders on sacred.

It’s obsession with feel, aesthetic design, the quality of raw material, reverence for the maker—whether that’s a person or a brand.

It’s not just writing materials. There are the pen-obsessed, yes. But there are also people (I’ve been one) obsessed with keyboards—the kind you type on. The kind you probably don't think much about unless it stops working. But the obsession goes deep. I’ve assembled mechanical boards with custom form factors. I’ve agonized over which switch—out of hundreds—to mount under my keycaps for a specific “clack.” I've programmed macros and layers in order to get the most capability possible from the fewest amount of keys. We joke that the keyboard at my office desk is the first line of defense. Even if you know my password, good luck typing it.

And then there’s the EDC crew. Their love of pens runs deep, but not as deep as their love for pocket knives, titanium wallets, or billion-lumen micro flashlights and the customized daily kit all put together.

Get the Signal

Still not resonating? Maybe you know the sneakerheads. The ones who treat a pair of Air Force 1s like they hold ashes. A special place on the shelf. Never to be touched. Never worn—unless maybe, once, carefully, with intention. Walking in them becomes a choreographed anxiety ritual.

It might sound like I’m mocking them. Maybe I am. It’s ridiculous.

But I’m also one of them.

And there’s something beautiful about it: the reverence for the interface.

We all use tools daily. Most disappear into the periphery, and many would argue (and I do almost daily in my role as a UX Leader) that well-designed tools should do exactly that. But to stop, to notice the interface—maybe even obsess—is to acknowledge, to pay homage to what makes us who we are.

// the tool is no longer invisible. it becomes a mirror.

These objects are extensions. They are entanglements. They’re part of us. And perhaps that's why they can bring us together.

Just go to Reddit. It's riddled with communities forged through these obsessive tendencies. r/mechanicalkeyboards used to be a haunt of mine. It took me months of contextual research just to *read* a post and understand it. Whole ontologies built around the kind of device I’m typing on now.

I’m not sure what it all means. But I know it matters.

To dissect the parts of our lives that so often succumb the sanguine death of normalcy… to fixate, connect, romanticize with them—

That’s a love letter to our cyborg selves.

What other interfaces get obsessed over? And do you pay attention to them, or call them ridiculous?

// end transmission

Illustrations by PL4S7IK. Generated and refined through cyborg collaboration — Midjourney prompting (co-developed with ChatGPT and human directorial chaos), Photoshop layering, Procreate detailing, and plenty of human signal shaping the static.