AutoBE
    Preparing search index...

    Interface AutoBeDatabaseOntologyFileSchemaEvent

    Event fired when DB ontology writes a schema draft from one raw file.

    This event mirrors the schema field written by IAutoBeDatabaseOntologyFileSchemaApplication.IWrite. It carries only a file_id and namespace context, not canonical provenance, source ids, or evidence ids.

    Samchon

    interface AutoBeDatabaseOntologyFileSchemaEvent {
        acquisition: Pick<AutoBePreliminaryAcquisition, Kind>;
        completed: number;
        created_at: string & Format<"date-time">;
        file_id: string & Format<"uuid">;
        id: string;
        metric: AutoBeFunctionCallingMetric;
        namespace: string;
        schema: AutoBeDatabaseOntologyFileSchema;
        step: number;
        tokenUsage: IAutoBeTokenUsageJson.IComponent;
        total: number;
        type: "databaseOntologyFileSchema";
    }

    Hierarchy (View Summary)

    • AutoBeEventBase<"databaseOntologyFileSchema">
    • AutoBeAggregateEventBase
    • AutoBeProgressEventBase
    • AutoBeAcquisitionEventBase<
          | "analysisSections"
          | "previousAnalysisSections"
          | "previousDatabaseSchemas",
      >
      • AutoBeDatabaseOntologyFileSchemaEvent
    Index

    Properties

    acquisition completed created_at file_id id metric namespace schema step tokenUsage total type

    Properties

    acquisition: Pick<AutoBePreliminaryAcquisition, Kind>

    Summary of preliminary data acquired by the agent during RAG.

    Contains lightweight identifiers for each kind of preliminary data that was loaded into the agent's local context before producing its output. Only the kinds specified by the Kind type parameter are present.

    completed: number

    Number of items completed.

    Tracks how many items have been successfully processed so far in the current operation. This value increments as each item is completed, providing real-time progress indication.

    The ratio of completed to total gives the completion percentage: progress = (completed / total) * 100

    created_at: string & Format<"date-time">

    Timestamp when the event was created.

    ISO 8601 formatted date-time string indicating when this event was emitted by the system. This timestamp is crucial for event ordering, performance analysis, and debugging the agent workflow execution timeline.

    Format: "YYYY-MM-DDTHH:mm:ss.sssZ" (e.g., "2024-01-15T14:30:45.123Z")

    file_id: string & Format<"uuid">

    User message file id bound to this file schema worker.

    This mirrors the file_id worker context that supplied raw structure to the worker. It is not a sidecar source id, evidence id, or provenance key.

    id: string

    A unique identifier for the event.

    metric: AutoBeFunctionCallingMetric

    Function calling trial statistics (total, success, failure counts).

    namespace: string

    Business namespace of the target table.

    Mirrors the namespace context used when the schema worker writes the schema payload.

    schema: AutoBeDatabaseOntologyFileSchema

    File-local ontology schema written by the function-calling schema.

    Mirrors the schema field in IAutoBeDatabaseOntologyFileSchemaApplication.IWrite.

    step: number

    Iteration number of the requirements analysis this draft reflects.

    This is progress context added by the event stream, not a function-calling write field or source identity.

    tokenUsage: IAutoBeTokenUsageJson.IComponent

    Token consumption breakdown (input, output, cache hits).

    total: number

    Total number of items to process.

    Represents the complete count of operations, files, endpoints, or other entities that need to be processed in the current workflow step. This value is typically determined at the beginning of an operation and remains constant throughout the process.

    Used together with the completed field to calculate progress percentage and estimate time to completion.

    type: "databaseOntologyFileSchema"

    Unique identifier for the event type.

    A literal string that discriminates between different event types in the AutoBE system. This field enables TypeScript's discriminated union feature, allowing type-safe event handling through switch statements or conditional checks.

    Examples: "analyzeWrite", "databaseSchema", "interfaceOperation", "testScenario"

    Settings

    Member Visibility

    On This Page

    Properties