Skip to content

About

Starting point, vision, component map, and shared contracts for independent persistent agents

Topics

Resources

Code of conduct

Security policy

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

Amplifier Constellation

Persistent agents, reusable services and connections to the places people work. Each part can develop independently while people collaborate with the same agents across experiences.

Experience, Conversation, Connection, Agent Instance and Tool

Explore the illustrated introduction: four architecture illustrations, a short film, and a downloadable image collection.

Start with the vision: what the parts mean, how they connect and why they matter. Read the contract map for promises relevant to your work, and Working together for applying Converge here.

For a runnable example, follow the request-to-result journey. It connects real component APIs with Native or Unified as the engine, recovers lost submission replies, and checks the returned artifact in a disposable environment. Its controlled provider tests composition; it does not establish natural-model quality or production readiness.

Find the owning component

These are provided implementations and supporting capabilities. The five primitive roles describe their outward boundaries, not a required repository or deployment layout.

Capability Repository
Installed identity, configuration, context, responsibilities and lifecycle Constellation Instance
Native reasoning, providers, tools and durable execution Runtime
Rooms, membership, messages and observable coordination Conversations
Live talk, seeing what you share and a shared visual surface Companion, currently developed in Conversations
External conversations and domain actions Slack · Teams · Minecraft
Portable communication and working-style profiles Persona Workshop
Collaboration experiments and outcome checks ACP Lab
Fleet observation and management Observatory

family.toml indexes components, related products and intended homes, including Companion and reusable Context/Realtime capabilities. Intended homes do not certify available APIs. The family agreement owns their boundaries; serving repositories own setup, API definitions and tests. The ACP connection library is shared code, not a required service.

Amplifier is one external experience, implemented by Amplifier Unified; its internal ecosystem stays there. Amplifier Agent is a distinct engine choice.

Join the work

Invited collaborators work within their agreed repository access and scope.

  • Improve an existing part: find its repository above, then read its vision and local interfaces.
  • Build a new experience, tool or agent implementation: start with the relevant boundary contract and reuse provided parts where useful. The repository list is not a fixed product blueprint.
  • Change a shared promise: work in its umbrella contract with the affected owners.

Use Working together to frame the outcome and combined check. General public contribution intake is described below.

Constellation is part of the broader Amplifier ecosystem.

Contributing

Note

This project is not currently accepting external contributions, but we're actively working toward opening this up. We value community input and look forward to collaborating in the future. For now, feel free to fork and experiment!

Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit Contributor License Agreements.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

About

Starting point, vision, component map, and shared contracts for independent persistent agents

Topics

Resources

Code of conduct

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages