Orchestra AIBy Hyperdrift

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

5 of 11 · UI ·

How interfaces decide what people must learn, and what changes when an agent can act on the page.

  1. 05

    Conversation / Hyperdrift First Officer

    The dashboard that speaks first

    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
    Read →
  2. 06

    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
    Read →
  3. 08

    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
    Read →
  4. 09

    Traction / 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
    Read →
  5. 11

    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
    Read →

Where could this help you?

Bring one workflow, a question or a product you want to improve. We’ll work out a useful first step together.

Describe your workflow →