Understand document generation in Alæc
Follow the path from a request and project data to a proposed file and then human review.
In this article
Components of the workflow
- Request and context
The request states the objective; the project, files, and structured data provide authorized context.
- Definition and template
The document type, sections, and rules determine the expected structure when a definition is configured.
- Generation
Alæc assembles structured data and proposed content, then processes the deliverable in the background.
- Delivery
A notification or conversation result indicates that the file is ready or that processing failed.
- Review
An authorized person checks facts, calculations, references, formatting, and approval requirements before use.
What the result means
A generated file is a working artifact. Its filename, presence in a notification, and formatting do not mean that it is issued, approved, signed, or compliant with every mandate requirement.
Practical guidance
Generation involves selecting a supported document type, supplying context, processing its configured structure and retrieving a file. These stages can have different outcomes. A conversational explanation, a started workflow or a ready notification should be checked against the actual file and the requested scope before the work is considered complete.
Advanced tips
Treat repeat generation as a new version with its own inputs and review. If a template or project value changes between runs, compare the resulting structure as well as the prose; the same request can legitimately produce different sections.