| Acceptance | Quality check the engine runs at the end of each pipeline: passed, warning or failed. |
| Business object | Transactions, Web Panels, Work Panels, Procedures, Reports, Query Objects and SDTs: where the application logic lives. |
| Call tree | Diagram of who calls whom, starting from an object or an entry point. |
| Cluster | Group of objects that work together in the same functional area, inferred from the dependency graph and the location in the KB. |
| Confidence | Score from 0 to 100 (high, medium, low) indicating how much evidence backed the analysis of an object. |
| Connection | AI provider, model and credentials saved under a name, for the narrative. |
| Connector | UltraGX component for Windows that opens a KB with the installed GeneXus, read-only, and exports it to text. |
| Data flow diagram (DFD) | Diagram of which objects read and write which tables. |
| Declaration | Object that only defines a type, a structure or a setting (attribute, domain, SDT, external object, pattern settings). Not narrated by default. |
degraded | Narrative result for an object when the model cited names that do not exist in it. Not published. |
| Demo / full edition | Licence types. The demo lasts 10 days and details 25 objects; the full edition documents everything offline. |
| Deterministic annex | Last part of each object document, with the complete technical evidence of the analysis. |
| Engine | ultragx-engine, the program that analyses the KB and writes the documentation. The application runs it for you. |
| Functional profile | Classification of what an object does (for example, data maintenance, query, batch process). |
| Implicit SQL | The query GeneXus generates for a For each, reconstructed by the engine: base table, joins, conditions and order. |
| KB (Knowledge Base) | The GeneXus knowledge base: all the objects of an application. |
| Knowledge pack | Structured summary of an object: functional understanding, interaction model, data usage, dependencies, risks and gaps. |
| Library object | Object from an imported module (from GeneXus or third parties), not developed in the KB. |
| Live (source) | Reading the KB directly with the installed GeneXus, through the connector. |
| Narrative | Prose written by a language model and validated against the facts of the object. |
| Pipeline | The complete run of the engine on a KB: reading, analysis, relationships and writing. |
| Project | The output folder of a documented KB. |
| Pseudocode | Readable translation of each event and subroutine of the object. |
| Rebuild roadmap | Suggested order for rebuilding the application, in phases, according to the dependencies between clusters. |
| Stub | In the demo, summary document of an object outside the sample. |
| Text export | GeneXus 17 and 18 format that stores each object as a text file, in src/ and ref/ folders. |
| User notes | Comments the team adds to objects; they are kept between runs and take precedence over inferred statements. |
| Viewer | Static website generated for each project, browsable offline. |
| XPZ | GeneXus object export file (compressed XML). |
UltraGX