Amplifier Constellation

Your agents.
Room to invent.

Work with a team of persistent agents across the places you already use. Build on shared capabilities, and give each part room to develop in its own way.

Read the visionTake the illustrations with you

Five building blocks. Many ways to combine them.

An experience presents a conversation. Agents participate through connections and use shared or private tools. These are boundaries people can build around, with freedom inside each one.

Five building blocks: Experience presents Conversation; Agent Instance participates through Connection and uses Tool. Conversations and tools can be shared.
Open any illustration to see it at full size.

See how it fits together

2 minutes 8 seconds

Download the filmRead the transcriptCaptions

An illustrated introduction to the architecture, rather than a demonstration of deployed products.

Freedom inside an agent

One engine, an inner team, or a different design entirely. A dependable outward boundary lets builders explore how an agent works without making everyone else adopt its internals.

Inside an Agent: examples show a single engine, an inner team, and an event-driven design. These are examples, not a fixed menu.

Improve every part

An improvement team can work alongside other agents or from a separate environment. People can join the conversation in either arrangement. Both can improve the whole system.

An improvement team shares the working environment. Working agents ask for help and unblockers; the team coaches them and can make code and system changes across all five building blocks.
Work together: ask for help, coach one another, and improve the systems around the work.
An improvement team has its own environment and joinable conversation. Evidence flows out of the working environment; improvements return through supported interfaces, including repairs to the environment itself.
Step outside: study the environment, test ideas, and bring improvements back.

Build on what’s here

Start with the intended outcome, find the part that owns the behavior, and build on the work already there.

Vision
The experience we want to make possible.
Shared promises
The agreements between independently developed parts.
Find a component
Repositories, interfaces, and places to contribute.

The vision and contracts in the repository are the canonical documents. These illustrations explain the direction; component documentation defines available interfaces.