From 43c85d68e06ceca8a71cd8c0bef0c5dc6ac76369 Mon Sep 17 00:00:00 2001 From: Jack Gerrits Date: Sat, 28 Sep 2024 00:01:08 -0400 Subject: [PATCH] Update references (#657) Co-authored-by: Eric Zhu --- docs/design/01 - Programming Model.md | 6 +++--- .../samples/dev-team/DevTeam.ServiceDefaults/Extensions.cs | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/design/01 - Programming Model.md b/docs/design/01 - Programming Model.md index 3873c80cf..732a46c6a 100644 --- a/docs/design/01 - Programming Model.md +++ b/docs/design/01 - Programming Model.md @@ -1,6 +1,6 @@ # Programming Model -Understanding your workflow and mapping it to agents is the key to building an agent system in Starfleet. +Understanding your workflow and mapping it to agents is the key to building an agent system in AutoGen. The programming model is basically publish-subscribe. Agents subscribe to events they care about and also can publish events that other agents may care about. Agents may also have additonal assets such as Memory, prompts, data sources, and skills (external APIs). @@ -19,11 +19,11 @@ If is possible to build a functional and scalable agent system that only reacts ## Built-in Event Types -The Starfleet system comes with a set of built-in event types that are used to manage the system. These include: +The AutoGen system comes with a set of built-in event types that are used to manage the system. These include: * System Events - Events that are used to manage the system itself. These include events for starting and stopping the Agents, sending messages to all agents, and other system-level events. * ? insert other types here ? ## Agent Contracts -You may want to leverage more prescriptive agent behavior contracts, and Starfleet also includes base agents that implement different approaches to agent behavior, including layering request/response patterns on top of the event-driven model. For an example of this see the ChatAgents in the Python examples. In this case your agent will have a known set of events which it must implement and specific behaviors expected of those events. +You may want to leverage more prescriptive agent behavior contracts, and AutoGen also includes base agents that implement different approaches to agent behavior, including layering request/response patterns on top of the event-driven model. For an example of this see the ChatAgents in the Python examples. In this case your agent will have a known set of events which it must implement and specific behaviors expected of those events. diff --git a/dotnet/samples/dev-team/DevTeam.ServiceDefaults/Extensions.cs b/dotnet/samples/dev-team/DevTeam.ServiceDefaults/Extensions.cs index 9a59b6000..683d50422 100644 --- a/dotnet/samples/dev-team/DevTeam.ServiceDefaults/Extensions.cs +++ b/dotnet/samples/dev-team/DevTeam.ServiceDefaults/Extensions.cs @@ -62,7 +62,7 @@ public static class Extensions //.AddGrpcClientInstrumentation() .AddHttpClientInstrumentation() .AddSource("Microsoft.Orleans.Application") - .AddSource("Starfleet.Agent"); + .AddSource("AutoGen.Agent"); }); builder.AddOpenTelemetryExporters();