Orchestra AI by Hyperdrift · Field notes
UI
field notes.
How interfaces decide what people must learn, and what changes when an agent can act on the page.
← All field notes- 05Read →
Conversation / First Officer
Conversational AI interfaces: keep the evidence in view
Our First Officer prototype explores a conversation that moves the Bridge to the subject being discussed. HyperVideoMesh shows a related principle: the agent's work should remain visible and editable.
Prototype in development - 09Read →
Conversation / Hyperdrift First Officer
Your dashboard should report to you
A chief of staff walks in and says: three things need you today. We built that for a one-founder fleet. You talk, it answers in under a second, an agent acts, and it reports back.
Live, and open source - 10Read →
History and human capability / UI and accessibility
Is UI holding us back?
New interfaces can remove work or move it into checking and correction. A historical argument for judging the whole task.
Historical synthesis - 12Read →
WebMCP and shared state / UI and accessibility
Stop making agents hunt for buttons
WebMCP lets a page expose actions to a browser agent. Radar shows how that can keep the person and agent working in the same place.
Radar implementation and draft specification - 13Read →
Commander / First Officer / UI and accessibility
A spoken promise is not a completed action
A Cargo recovery request becomes an action, a checked result and a spoken report. What this bounded demonstration can teach app designers.
Recorded sandbox demonstration - 15Read →
The future of UI / UI and accessibility
Your work should survive a change of interface
Speak, inspect, correct and continue. A future interface should preserve the task when the person changes how they interact.
Design position and research agenda