Most conversations about AI and exploration start with what the model can do. The Dialogues on Technology and Society episode published September 14, 2026 starts somewhere more useful: what a human and a machine each bring to a place neither can reach alone.
The setup, briefly
NASA astronaut, engineer, and scientist Christina Koch sits down with James Manyika, Google’s Senior Vice President of Research, Labs, Technology & Society. Koch’s record includes 328 days aboard the International Space Station, the first all-female spacewalk, and a journey around the Moon on NASA’s Artemis II mission.
The supplied RSS summary describes the conversation covering Earth seen as an electric blue “lifeboat” from 250,000 miles away, the partnership between astronauts, robotics, and AI, the question “Are we alone?”, and her advice to future explorers: do what scares you, and support others.
The partnership framing is the part worth stealing
The summary’s phrase — astronauts, robotics, and AI as a partnership — is not a slogan. It is an operating model, and it maps onto how teams should think about agents.
Koch’s work is a case where the human is not supervising a tool that could do the job alone. The human is the one making judgment calls in an environment where the cost of a wrong call is extreme, while automation handles what humans are bad at: sustained precision, repeatable procedure, and monitoring that does not fatigue.
That is a different design brief than “replace the manual step.” It asks which decisions need a person in the loop because the context is ambiguous, and which ones need a machine because the context is boring. If you are building agent workflows, that split is the whole architecture. The same question shows up in execution models for orchestrators, where the choice of who holds state decides how much you can trust the system when something goes wrong.
“Are we alone?” is a search problem with a long horizon
The summary notes Koch explores that question in the episode. It does not specify how she or Manyika frame it, so treat the framing as theirs to watch rather than something to paraphrase.
What is clear from the summary is that the question sits alongside the robotics-and-AI partnership discussion. That pairing is the interesting bit for anyone building research or discovery tools: the hard part is rarely generating a candidate answer. It is deciding what counts as evidence, and staying honest about how little you have.
What this changes for a builder
Two practical takeaways, both modest.
First, if your product pairs a person with an automated system, write down the split explicitly. Which decisions require human judgment because the stakes or ambiguity are high, and which are delegated because consistency matters more than nuance? The episode’s framing suggests that split is the design, not an implementation detail.
Second, watch the episode if you want the primary source. The summary is thin on specifics — it does not detail the AI systems discussed, the mission timeline, or Manyika’s positions. The supplied RSS summary does not specify those, and that is not evidence they were left out of the conversation.
Koch’s advice in the summary — do what scares you, and support others — is the least technical line in the piece and probably the most reusable. Exploration programs work because people take on work at the edge of their competence with support around them. Teams shipping AI tools are running a smaller version of the same thing.
Sources
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.