Understand how Genesis application engineering capacity and ongoing context services work together.
AEU and the Connected service
Genesis provides two related but different things: application engineering capacity, measured in AEU, and an ongoing Connected service that maintains relevant context and platform connections as applications evolve.
They work together, but they are not interchangeable. Connected is not an unlimited entitlement to generate or customise software.
What is AEU?
AEU stands for AI Engineering Units. Genesis uses AEU to account for platform-assisted application engineering work.
AEU is used for:
- Generating a new application or a new application component.
- Genesis-assisted changes to an existing application.
- Extending business workflows, rules, interfaces or integrations through Genesis.
- Adding features, modules or other agreed functionality through Genesis.
Usage depends on the scope and complexity of the work. An AEU allocation should not be read as a promise to deliver a fixed number of screens, workflows, features or complete systems.
Changes are not automatically free because they affect an application that already exists. Equally, a proposed change should be understood and evaluated on its actual scope.
How can we see our usage?
Only your organisation's authorised administrators can view AEU consumption and available balances in the Genesis admin panel.
For material work, your team and Dalfin AI agree the scope, relevant approvals and any applicable AEU arrangements before proceeding.
Can an allocation support more than one application?
Where the agreed programme and organisational allocation permit, capacity remaining after an initial application may be used for additional applications within the same organisation. Each application and its requirements are considered on their own merits.
Your proposal or agreement confirms the allocation, conditions and applicable scope.
What does Connected do?
The Connected service supports continuity as applications and their operating context change. Genesis Context Memory can preserve relevant business rules, dependencies, engineering decisions and accepted revisions, helping later changes take account of earlier decisions.
Connected also reflects the agreed scope of ongoing Genesis platform connections and shared capabilities used by your applications. The service scope can change when your application portfolio or its complexity grows.
Connected does not, by itself, cover unlimited application generation, customisation, integration work, development labour or third-party services.
Who can make changes?
Depending on your engagement and agreed access, changes may be performed through Genesis-assisted workflows, by your own authorised technical team using other tools, or with Dalfin AI's assistance.
Genesis-assisted work uses AEU. Treatment of work carried out outside Genesis, including its review and reintegration into the accepted application, is defined by the applicable arrangements. Do not assume every external change is automatically validated, incorporated into Context Memory or supported.
How are significant expansions handled?
For substantial changes, such as an additional module, a new integration, a larger approval process or a material increase in scope, the work is assessed and approved before implementation. This helps your organisation understand how the proposed work may affect engineering capacity, delivery, operational dependencies and the Connected service.
How do we obtain an allocation or service proposal?
An AEU allocation and the Connected service are defined in the enterprise proposal or agreement. We do not publish commercial rates or standard AEU-to-feature conversion tables in this guide.
Discuss your application scope (opens in a new tab) ยท See how customisation works