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.
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
File-local ontology component written by the function-calling schema.
Mirrors the component field in
IAutoBeDatabaseOntologyFileComponentApplication.IWrite.
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")
User message file id bound to this file 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.
A unique identifier for the event.
Function calling trial statistics (total, success, failure counts).
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.
Token consumption breakdown (input, output, cache hits).
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.
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"
Event fired when DB ontology derives table designs from a raw file work item.
This event mirrors the
componentfield written byIAutoBeDatabaseOntologyFileComponentApplication.IWrite. It carries only afile_id, not canonical provenance, source ids, or evidence ids.Author
Samchon