Create separate package genai_primitives

[polina-c]

Public discussion: Lossy Abstraction for Generated Responses

Internal discussion: go/dart-ai-primitives

• Create initial package genai_primitives #626
• update genui to take dependency on the package with local path
• publish the package
• update genui to take dependency on the package in pub.dev

[sethladd]

IIUC, this new proposed package would have shared classes for "DataPart", "ImagePart", etc.

My feedback is that we can tweak the names of these.

DataPart sounds like a StructuredJsonDataPart
ImagePart sounds like a BinaryDataPart

[sethladd]

cc @gspencergoog

[sethladd]

cc @rodydavis

[csells]

I don't think the name "ai_primitives" fits here -- AI is far more general purpose than what we're building. we're building out a set of primitives for use with generative AI, so perhaps "genai_primitives" or "llm_primitives" makes more sense.

[gspencergoog]

I don't think the name "ai_primitives" fits here -- AI is far more general purpose than what we're building. we're building out a set of primitives for use with generative AI, so perhaps "genai_primitives" or "llm_primitives" makes more sense.

That's a good point: AI includes lots of other things. I'm fine with either of those, although I'd prefer genai_primitives, to allow inclusion of other models (embedding models aren't LLMs, for instance).

[polina-c]

genai_primitives looks good to me: https://pub.dev/packages/genai_primitives

[csells]

Types to Pull In from dartantic_interface

Message/Content Types

1. Message Parts (for multimodal content):
   • Part (base class)
   • TextPart
   • DataPart (for images/binary data)
   • LinkPart
   • ToolPart (for tool calls and results)
   • ToolPartKind (enum: call, result)
2. Message Container:
   • ChatMessage
   • ChatMessageRole (enum: system, user, model)

Tool Definition

1. ToolDefinition<TInput> (new - extracted from current Tool<TInput>):
   • name, description, inputSchema
   • NO execution logic