ISO 8601 timestamp indicating when the multi-lingual generation process was completed.
Marks the exact moment when all target-language files were rendered and written. Used to determine whether the multi-lingual artifacts are current relative to other pipeline stages.
ISO 8601 timestamp indicating when this history record was created.
Marks the exact moment when this history entry was initiated or when the corresponding agent activity began. This timestamp is fundamental for maintaining chronological order, tracking development progress, and understanding the temporal relationships between different phases of the vibe coding process.
Unique identifier for this history record.
A UUID that uniquely identifies this specific history entry within the system. This identifier enables precise referencing, cross-linking between related history records, and maintaining referential integrity across the development timeline and different agent activities.
Generated multi-lingual source files as key-value pairs.
Each key is a relative file path and each value is the rendered file content. Files vary by target language — for Java, entries include DTO class files and Spring Boot configuration sources produced from the validated database schema and OpenAPI document.
Iteration number of the pipeline output this multi-lingual pass was performed against.
Indicates which generation of the upstream artifacts this run reflects. If this value is lower than the current interface or realize step, the multi-lingual artifacts may be stale and require regeneration.
A value of 0 indicates the initial generation; higher values represent subsequent passes triggered by upstream changes.
Type discriminator indicating the specific kind of history record.
Provides type-safe discrimination between different history record types such as "analyze", "database", "interface", "realize", "test", "userMessage", and "assistantMessage". This enables proper type narrowing and ensures that history records are processed according to their specific characteristics and requirements.
History record generated when the Multi-lingual agent produces localized artifacts for the application.
The Multi-lingual agent takes the completed pipeline outputs (Prisma schemas, OpenAPI document, implementation code) and re-renders them with property names and descriptions translated into additional target languages (e.g., Java DTOs, localized OpenAPI descriptions).
Author
sunrabbit123