AutoBE
    Preparing search index...

    Interface AutoBeUserMessageImageContentMetadata

    Metadata attached to user message image content.

    Image body and region-level observations are stored outside user message metadata. Visual interpretation that does not need a dedicated field should be summarized in the shared memo.

    interface AutoBeUserMessageImageContentMetadata {
        byteLength: number & Type<"uint32">;
        height?: number & Type<"uint32">;
        memo: string;
        type: "image";
        usages: AutoBeUserMessageContentMetadata.Usage[] & UniqueItems<true>;
        width?: number & Type<"uint32">;
    }

    Hierarchy (View Summary)

    • IBase<"image">
      • AutoBeUserMessageImageContentMetadata
    Index

    Properties

    byteLength: number & Type<"uint32">

    Byte length detected by the image adapter.

    height?: number & Type<"uint32">

    Pixel height detected by the image adapter.

    memo: string

    Compact handoff memo for later agents.

    Explain what the content item appears to contribute, which downstream phase should care, and what must not be inferred yet. For example, an ERD can be structural, a meeting transcript can be requirement-oriented, and one item can be both when annotations contain business rules beside structure.

    type: "image"

    Metadata branch discriminator.

    usages: AutoBeUserMessageContentMetadata.Usage[] & UniqueItems<true>

    Downstream semantic roles for this content item.

    Empty means the content item should not feed a phase directly. Supporting evidence, metadata-only value, policy limitations, intake gaps, or unsupported content should be explained in memo instead of adding a separate enum here.

    width?: number & Type<"uint32">

    Pixel width detected by the image adapter.