5 Assistants working together creating end product

API
3

By naming (and addressability), I mean that an assistant can be called in a canonical form like so :

Hi alina, can you please provide feedback on three suggestion provided.

So anyone can address alina. Conversely alina should know that her attention is needed on a specific topic and where to respond.

Secondly Alina should know that there are other assistants and should know of her previous interactions with her. The knowledge of her knowing should materially impact her response.

Thirdly Alina should have the capability to evolve. These capabilities are two fold: (a) one is her internal state and (b) the other is increasing set of tools

For example here’s simulated alina’s response to a potential email…

Hi @lin:  Can you please look into fred's email. It looks very damaging for brand. suggest mitigration strategy. Hi @jesse: Can you please look into the potential liabilities?

and here are agent aware message disambuguations:

@lin look into an email and suggest a mitigation strategy
@jesse look into the potential liabilities

Just a glimpse into a microkernel of a function called:

@tools_function(TOOLS_FUNCTIONS)
def call_objective(
    description: Annotated[str, """The description describes the PURE objective. The description should be couched as a request to the subject/s in the second person. """]
    ):
    """ This function describes the PURE objective. The description should be couched as a 
    request to the subject/s in the second person.

    for example, 
        in case of "Hi @alina. Can you please provide feedback to my post", the decription is "provide feedback to a post"
 
    """
    data = {'call_objective': description}
    return json.dumps(data)

hth