Principles

Engineering convictions, held provisionally.

These are not product claims. They are the ideas Dispatch is being built to test. They should change when experience gives us better ones.
01

AI participates; people remain responsible.

Dispatch is not trying to replace developers. It is testing how people can retain judgment while agents become visible, useful collaborators.

02

Capabilities can strengthen workflows.

Repeatable workflows are valuable. Shared primitives can give them more room to adapt when the work changes.

03

Shared workspaces clarify handoffs.

When people and agents can see the same state and artifacts, collaboration is easier to inspect, continue, and question.

04

Composition can complement orchestration.

Small operations can combine at the edge of the work without requiring every decision to be centralized.

05

Visible state supports trust.

Context and progress are easier to debug and question when they are available to the people doing the work.

06

Long-running work deserves support.

A meaningful change can outlive a chat window, browser session, or an afternoon.

07

Context remains useful.

Decisions, links, and artifacts can retain value after the immediate task is done.

08

Learning is a useful outcome.

A system can help a team better understand its own work, whether or not that work is automated.