AutoBE
    Preparing search index...

    Interface AutoBeUserMessageAudioContentMetadata

    Metadata attached to user message audio content.

    Audio bytes and transcript bodies are stored outside user message metadata. Transcript availability and interpretation should be summarized in the shared memo when it matters.

    interface AutoBeUserMessageAudioContentMetadata {
        byteLength: number & Type<"uint32">;
        durationSeconds?: number & Type<"uint32">;
        memo: string;
        speakerCount?: number & Type<"uint32">;
        type: "audio";
        usages: AutoBeUserMessageContentMetadata.Usage[] & UniqueItems<true>;
    }

    Hierarchy (View Summary)

    • IBase<"audio">
      • AutoBeUserMessageAudioContentMetadata
    Index

    Properties

    byteLength: number & Type<"uint32">

    Byte length detected by the audio adapter.

    durationSeconds?: number & Type<"uint32">

    Audio duration detected by the adapter, in seconds.

    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.

    speakerCount?: number & Type<"uint32">

    Number of speakers detected by the transcription adapter.

    type: "audio"

    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.