Follow the business-level Genesis journey from application requirements through engineering, testing, acceptance and ongoing change.
How Genesis works
From a business requirement to an accepted application
Genesis provides an organised approach to AI-assisted application engineering. It starts by understanding what a business needs, records the decisions behind the application, and supports the creation and controlled evolution of its software components.
The journey involves both technology and accountable people. The exact activities vary with the type, size, risk and complexity of the application.
1. Describe the outcome
Begin with a business objective, a pain point or the application you want to build. Your starting material might be a written explanation, process map, existing specification, spreadsheet, screenshots, design reference or a selected solution blueprint (opens in a new tab).
Useful information includes who performs the work, which decisions matter, what information is recorded and what other systems are involved. You may not have every detail on day one.
2. Understand the requirements
Genesis helps structure the available material into application requirements. The review considers workflows, data, business rules, user roles, interfaces, reporting, exceptions and any important operating constraints.
Where information is missing or ambiguous, questions and assumptions need to be resolved with the relevant business owners. An illustrative example or an AI-generated suggestion is not an approved rule merely because it appears plausible.
3. Confirm the application scope
The proposed scope is reviewed with the customer. This includes the business processes to be supported, the rules and approvals that govern them, the roles involved, integrations, acceptance criteria and delivery responsibilities.
Some requirements may be deferred or treated as a later phase. Changes to the agreed scope are assessed and approved before they are implemented.
4. Engineer the application
Within the agreed scope, Genesis supports the engineering of application interfaces, data structures, backend services, APIs and required workflows. The technical work is informed by the confirmed requirements and retained decisions.
Generating an initial application is not the same as proving that every workflow or business rule is correct. Complex approvals, exceptions, permissions, integrations and operational behaviour must be validated against the requirements.
5. Review and test
The resulting application is reviewed for its intended purpose. Relevant checks may include:
- Whether required information is captured and validated.
- Whether the correct people can perform and approve actions.
- Whether workflows handle normal and exceptional cases.
- Whether integrations exchange the agreed information correctly.
- Whether important business rules and safeguards behave as specified.
- Whether the application meets its agreed acceptance scenarios.
The extent of testing depends on the application and engagement. Unresolved critical matters are managed through the agreed delivery and acceptance process.
6. Accept and deploy
Application release follows the environment, controls, responsibilities and approval process agreed for the programme. The customer and Dalfin AI confirm what is being accepted, what is included in the release and who operates and supports it afterwards.
The existence of a generated interface or a completed build stage does not by itself mean the application is approved for production use.
7. Improve with retained context
After acceptance, organisations may need new functions, changed rules, additional integrations or operational adjustments. Genesis Context Memory preserves relevant decisions, dependencies and accepted revisions to inform later engineering work.
Genesis-assisted changes use AEU according to their assessed scope and complexity. The Connected service provides ongoing context and governed continuity within an agreed service scope.
Explore customisation and Context Memory
Who makes the decisions?
Your business owners confirm business processes, rules, exceptions and acceptance criteria. Your technical representatives confirm integrations, deployment and operational constraints. Dalfin AI and/or your designated engineering team perform the delivery responsibilities defined by the engagement model. Technical review and QA must establish that the result satisfies the agreed scope.
The goal is a traceable engineering process in which assumptions, responsibility and acceptance remain visible.
Example: a stock transfer approval
An organisation may require warehouse staff to request a transfer, a supervisor to approve it under defined conditions, and the receiving location to confirm receipt. Genesis can help structure this as a scoped application requirement. The business must still define authority limits, stock validation, exception handling and integration behaviour before the workflow is accepted.
This is an illustrative scenario, not a claim that a particular transfer application has been deployed.
How to start an application ยท Request a demonstration (opens in a new tab)