Who wrote this system? Exploring the social system runtime

Themes: AI | Sociotech | Teams | Architecture

Note: this session will run through the afternoon break

You write the spec. You put in the prompt. AI writes the code.

But who wrote the system? What happens to ownership and connection when we no longer struggle with the code ourselves?

What happens to business and product roles when developers take over specs and prompting?

How much do you really understand and remember?

Code reflects conversations.

The ones we had.

And the ones we skipped.

Systems drift.

In code.

In how we decide and collaborate.

We try to fix this with structure. Org charts. Team boundaries.

Inverse Conway.

But living systems do not run on structure. They run on interactions.

So where is the real design space? How do you change a system while it is running?

In this session, we explore the social system runtime. We work with real situations. Tough ones. Undiscussables. Elephants in the room.

Yours included.

What emerges depends on who is in the room.

And how we engage.

Participant takeaways:

• Code reflects conversations - how do we architect conversations?
• Drift is constant - how do we work with it as a signal?
• Systems run on interactions, not structure - how do we influence interactions?
• Sociotechnical architecture works through conditions - what skills does that require?

This session:

• Short framing and presentation 
• Collaborative modeling 
• Conversations and reflections