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.
Iteration number of the requirements analysis being implemented.
Indicates which version of the requirements analysis this authorization implementation is based on. This helps track the alignment between security implementation and business requirements across iterations.
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 the deterministic authorization decorator/payload phase begins.
This event brackets the start of generating the per-actor
@{Actor}Authdecorators and{Actor}Payloadtypes, which are emitted deterministically (no LLM). The authorization provider is written later, in the shared write phase, and streams through therealizeWrite/realizeCorrectevents like any other realize function — not under this bracket.Author
Michael