Understand the scope, business decisions, engineering components and acceptance responsibilities of a Genesis application build.
Application generation
Engineering starts with confirmed business requirements
Genesis uses AI-assisted engineering within a structured process. It helps translate the approved application scope into software components, while preserving the decisions and context that explain why those components are needed.
The target is a usable enterprise application that matches its agreed requirements. An initial generated result still requires relevant review, testing and acceptance before production use.
What can be in scope?
User interfaces
Screens, work queues, forms and operational views appropriate to the identified users and tasks. Desktop, tablet or mobile access is specified according to the use case and agreed capabilities.
Data and records
Application entities, required fields, relationships, validation rules and record histories needed to support the business process. Data mapping, migration and retention are scoped separately where relevant.
Workflows and business rules
Defined states, transitions, approvals, exception handling and decision rules. The implementation must be checked against the customer's written requirements and accepted decisions, particularly for sensitive transactions.
Roles and permissions
Access to functions and information is governed by the roles and permissions defined for the application. The appropriate identity, authentication and authorisation arrangements must be confirmed for the engagement.
Backend services and integrations
Services, APIs, imports, exports and connections to existing systems where these are required by the approved scope. An integration is not complete until its data mapping, access controls, failure handling and relevant tests have been agreed and performed.
Reports and operational information
Dashboards, summaries, operational reporting and evidence views required by accountable users. Any figures shown in illustrative examples are sample data unless expressly identified as verified operational results.
Why the clarification stage matters
Business documents frequently leave important questions unanswered. For example:
- Who may approve an exception, and under what conditions?
- Which fields are mandatory before a record may advance?
- What happens if an external service is unavailable?
- Can a user revise an accepted transaction, or must they raise a controlled adjustment?
- What evidence must be retained for review or audit?
Genesis can help identify these questions and organise proposed answers, but business owners must confirm what is correct for their organisation. No example should silently become a binding business rule.
Review and acceptance
The agreed delivery process should define what will be reviewed, by whom and against which evidence. Acceptance typically involves representative workflow scenarios, roles and permissions, data validation, exception handling, integrations and operational requirements.
Depending on the engagement, further configuration, customisation or manual engineering may be required. The scope and responsibilities are agreed rather than assumed.
AEU and application generation
Application generation uses AEU according to the assessed scope and complexity of the work. AEU also applies to Genesis-assisted customisation of existing applications. AEU rates and commercial terms are provided through the agreed customer proposal or programme arrangement, not this public guide.
Example: equipment custody management
Consider an application that records equipment receipt, assignment, transfers, inspections and retirement. The proposed design may include an asset register, custody records, approval roles, audit history and integration with an existing finance or inventory system. The actual workflows, decisions and interfaces must be verified with the organisation before release.
This example illustrates the engineering scope; it is not a statement that a particular solution has already been built or certified.
Starting an application · How Genesis works · Request a demonstration (opens in a new tab)