Unique identifier for this user message content item.
A UUID assigned by the message intake pipeline so downstream phases can reference one precise content item without relying on array position, filename, file metadata, or modality-specific payload shape.
Metadata attached after file intake.
Source-kind adapters may attach trusted structural metadata such as byte length, a CSV profile, or text line count. Filename, MIME type, source id, and governance state remain orchestrator-owned.
Original filename.
Type discriminator for identifying the specific content modality.
Provides type-safe discrimination between different content types such as "text", "audio", "image", and "file". This discriminator enables proper type narrowing and ensures that each content type is processed according to its specific characteristics and requirements.
The type field is essential for the multimodal content processing pipeline, allowing the system to route different content types to appropriate handlers while maintaining type safety throughout the conversation flow.
URL or data URL from which the file bytes can be read.
User message content for file uploads.
Handles file attachments in user messages through URL-backed content. Used when users need to share documents, specifications, code files, or other resources as part of their development requirements.
Author
Samchon