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
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")
A unique identifier for the event.
Array of module sections defined for this document.
Each module section represents a top-level heading (## level) with its title, purpose, and initial content. These sections establish the document's primary structure.
Retry attempt number for this event.
Starts at 0 for the first attempt. Increments each time the review rejects and the generation is retried. When retry > 0, completed may exceed total due to repeated work.
Current iteration number of the module section generation.
Indicates which version of the module structure is being generated. Increments with each retry after review feedback.
Executive summary of the document.
A concise overview (2-3 sentences) describing the purpose and scope of the requirements document.
Document title (# level heading).
The main title of the requirements document that will appear at the top of the generated markdown file.
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 during the module section (#) generation phase of the hierarchical requirements analysis process.
This event represents the first step in the hierarchical document generation pipeline where the Analyze Writer Agent creates the document's top-level structure including title, summary, and module section outlines.
The Module Agent operates as part of the "generate → review" pattern where:
Key characteristics of the module generation process:
Author
Juntak