allclouds.pl
allclouds.pl / inLABs

inLABs — research projects

Through the inLABs research programme, allclouds.pl invites organisations, companies and research partners who want to have a real influence on the development of the concepts presented here to work with us. We offer flexible forms of cooperation, different levels of partnership and benefits from taking part in creating new technologies, which will not be available to other clients on the same terms once the solution reaches the market

Contact form

Research projects
The inLABs research programme

Organisations · Companies · Research · partners · inLABs · research programme · CDT · HCG · AICF · SAVANT-AI · GENESIS-AI · Questions · and hypotheses · described before · the research · Validation · expert · reviews, · comparisons · Result · including partial or · negative · A person · decides · AI provides · material for assessment · COOPERATION · RESEARCH PRINCIPLES

COOPERATION

Co-creating technologies before they reach the market

Research carried out together with partners

01A real influence on how concepts developfor organisations, companies and research partners who want to co-create the concepts presented
02Flexible forms of cooperationdifferent levels of partnership, tailored to the organisation
03Benefits of taking partnew technologies which, once on the market, will not be available to other clients on the same terms
5

research projects in the inLABs portfolio

2

funding applications submitted under the FENG programme

1

methodology already developed — HCG

4

completed research projects — commercialisation of results

PORTFOLIO

Five projects, separate scopes*

At least one project in every phase of the process

The process followed in the inLABs programme

1 · Concept · research · questions · and the limits · of responsible · use · 2 · Methodology · / prototype · methodological · foundations or · early · prototypes · 3 · Application to · FENG · submitted, · awaiting a · decision · 4 · Research · and validation · cases, · expert · reviews, · comparisons · 5 · Result · positive, · partial or · negative · CDT · concept · Details · SAVANT-AI · early prototypes · Details · AICF · FENG application · Details · GENESIS-AI · FENG application · Details · HCG · methodology developed, · research ongoing · Details · RESEARCH QUESTION · RESEARCH RESULT

* Each project has its own research scope. The descriptions do not represent finished deployments, available features or integrations between projects

INLABS PROGRAMME CHARTER

What all inLABs projects have in common

We do not guess. We verify

Mission and nature of the programme

inLABs is allclouds.pl's research and development programme, established to create and test technology concepts responsibly before they become market solutions. The programme combines research, domain knowledge and organisational practice to address real problems related to the use of artificial intelligence under controlled conditions. Each project has its own subject, research questions, limits and assessment criteria

Partnership

Research is carried out together with partners. Organisations, companies and research partners take part in shaping the problems, scenarios and methods of validation, which gives them a real influence on how the concepts develop. The form and scope of cooperation are matched to the partner's competences, responsibilities and capabilities. Taking part in the programme means co-creating knowledge and technology at the research stage, not buying a finished product

Continuity of the research process

inLABs manages its portfolio so that it includes at least one project in every phase of the process: from concept and prototype, through funding and research, to a verifiable result. This organisation ensures continuity of work, the exchange of experience and the ability to carry conclusions over to subsequent projects without blurring the distinctness of their scopes. Projects sitting side by side in the portfolio does not mean they are technically integrated, share an operating environment or exchange data

Standard of rigour

Every hypothesis needs to be tested, and every result must be traceable and assessable in a defined context. A partial or negative result is a legitimate research outcome if it honestly shows the limitations of a concept, the need to change assumptions or the need for further verification. The programme reveals uncertainty instead of replacing it with apparent certainty, and separates evidence from claims

In the projects
A negative result is also a result
“A partial or negative result will be a valid research outcome”
Uncertainty shown, not hidden
“The system should clearly show its limitations instead of replacing human judgement with apparent certainty”

Accountability and limits

A person makes decisions and remains accountable for their consequences. The solutions studied in inLABs may organise knowledge, present context, support assessment and point to issues that need checking, but they do not take over the judgement of an authorised person. The programme respects access rules, consent to the use of information, the ability to trace information back to its sources, and the right to correct and delete knowledge where applicable

In the projects
A person decides
“CDT can provide the context needed, but it does not make decisions and does not relieve a person of accountability”

Communication principle

The public description of a project serves to present its goal, status and limits clearly. It is not a promise of a product, deployment, integration, pilot programme or commercialisation date. Detailed procedures, configurations, data and unpublished results remain outside the public description. The programme's credibility comes from the quality of the research, transparency about limitations and accountability for the conclusions it draws

In the projects
No claims of integration
“This description does not mean a finished integration, a shared operating environment or data flows between these solutions”
No product promises
“This page does not announce a product, a pilot programme, availability or a commercial schedule”
Details outside the public description
“Detailed procedures, configurations, data and results are not part of this public description”
CATALOGUE OF RESEARCH AND DEVELOPMENT PROJECTS

Active inLABs projects

CDT
Cognitive Digital Twin

We study how to preserve knowledge related to tasks, decisions and work context — without reproducing a person's identity or taking over their accountability

1 · Concept2 · Methodology / prototype3 · FENG application4 · Research and validation5 · Result
Research problemOrganisational knowledge is dispersed, context-dependent and easily lost when roles or teams change
HypothesisUseful knowledge can remain linked to its source, task, date and level of certainty
ApproachAcquiring knowledge covered by consent, linking it to a task and presenting it to the person who continues to make the decision
LimitCDT is not a digital copy of a person, an employee monitoring tool or an autonomous decision-maker

Research on the continuity of expert knowledge

CDT (Cognitive Digital Twin) is a concept being developed in inLABs to organise knowledge related to a particular person's tasks and everyday work context. We study how this knowledge, together with its rationale and information about its currency, can be collected, organised and used responsibly. The goal is to support continuity of work, not to reproduce a person's identity or take over their decisions and accountability

The technology is not intended to imitate a person or present uncertain information as certain. Above all, we want to distinguish honestly between what can be described and passed on and the knowledge that still requires experience, conversation and practice

Why it is being developed

Important organisational knowledge is usually dispersed across procedures, decisions, instructions, other documents, conversations and everyday practice. When a role, team composition or priorities change, it is easy to lose not only information about what was done, but also the reasons for choosing a method, the conditions considered and the precautions taken

Simply collecting files does not solve the problem. Information unconnected to a specific task, person, source and creation date can be difficult to find, out of date or used incorrectly. Conversely, overgeneralising an expert's experience can create a false sense of certainty, especially in unusual situations that require years of practice

That is why we study how to preserve knowledge continuity without reducing it to a list of facts. This includes consent to use information, access rules, knowledge ownership, the ability to correct and delete it, currency and responsible use. The system should clearly show its limitations instead of replacing human judgement with apparent certainty

Potential application scenarios

The examples below show possible research directions. They do not describe finished deployments, available features or services

Research scenario
01Introducing a successor to demanding tasksCDT could help organise the information needed by a person taking over responsibility for complex tasks: the most important sources, conditions, earlier decisions and exceptions. Such material is meant to make it easier to prepare for a conversation with the expert and for subsequent independent work, not to replace the expert automatically
Research scenario
02Reconstructing the context of a decisionWhen a team returns to a matter after some time, it may need information about what was known when the decision was made, what constraints applied at the time and what needs to be checked again. CDT does not make the decision for the team, but helps prepare reliable material for assessment
Research scenario
03Retaining knowledge when a team or role changesResearch could help identify the knowledge that is truly needed to maintain continuity of work and separate it from materials that are out of date or cannot be applied in the new situation. This could make handovers better prepared, while keeping the person and the organisation in control of how the information is used
Research scenario
04Human collaboration with AI toolsAn AI tool could receive only the context that consents and permissions allow it to use. This could help it understand the task better without gaining access to all resources or the right to act on its own. This is a direction requiring further research, not a description of a current integration with a specific system

Role in the inLABs ecosystem

Scope

CDT concerns knowledge related to the tasks, memory and work context of a specific person. Within the wider inLABs portfolio it can be considered alongside TWIN:DESK, as the working environment, and SAVANT-AI, which studies the knowledge of the whole organisation. These projects, however, have separate scopes. This description does not mean that they share an operating environment, data flows or a finished integration

Limits

The limits of responsibility are clear. CDT does not manage organisational change, does not control access to models and does not assess whether a given person has the competence to approve a decision. That last question is covered by separate inLABs work on HCG. Nor is CDT a tool for monitoring employees. It can provide the context needed, but it does not make decisions and does not relieve a person of accountability

Research approach

We assume that useful knowledge must stay linked to the task, context, source, date of creation and level of certainty. The system should help recognise not only facts and procedures, but also the conditions under which they apply, their rationale and signals that information needs to be confirmed again

We are studying three core capabilities: acquiring and organising knowledge covered by consent, linking it to a specific task and presenting it to the person who still makes the decision on their own. The result is not meant to be a digital copy of a person, but a clearly labelled supporting tool that helps people understand, check and pass on knowledge

Not all knowledge is easy to describe. Some experience can be written down as facts and procedures, some can be drawn out in conversation, and some can only be learned through observation and practice in a specific situation. We do not promise to fully reproduce this last category. The more honest solution is to indicate when contact with an expert or practical preparation is needed

Research methods and validation

Developing CDT requires checking both the quality of the knowledge collected and the rules for using it. We are planning controlled research cases, expert reviews and voluntary studies with people of different levels of experience, conducted with appropriate data protection. We will compare ways of describing context, communicating uncertainty and preparing materials for the person taking over tasks

The assessment will cover, among other things, usefulness in a specific task, consistency with the sources, how current the information is, clarity about limitations and the quality of the information passed to a person for further assessment. In parallel, we are studying the rules for consent, access, identifying the author of the knowledge, and correcting and deleting it. Detailed procedures, configurations, data and results are not part of this public description

Project statusCDT is still at the concept development stage. Current work focuses on refining the research questions, the limits of responsible use of knowledge and ways of testing the solution in real working conditions. We are also analysing how to reconcile the usefulness of context with a person’s right to decide about their own knowledge
HCG
Human Competence Gate

We study when a person’s involvement in an AI-supported decision really matters, and what conditions informed approval of a result must meet

1 · Concept2 · Methodology / prototype3 · FENG application4 · Research and validation5 · Result
Research problemFormal human approval does not always mean real control over the decision
QuestionHow can we tell whether the approver understands the context, risk and limitations of an AI recommendation?
OutcomeA methodology for assessing the conditions for informed human participation in the decision-making process
LimitThe description does not mean a finished integration or the automatic granting of decision-making rights

When a person’s involvement in an AI decision really matters

HCG (Human Competence Gate) is a way of checking, before an AI-supported decision is approved, that the right person understands the situation, can assess the recommendation and consciously takes responsibility for the decision made

In many processes the organisation uses AI recommendations, but a person still decides what happens next. The methodological foundations of HCG have already been developed, and the corresponding control stage is described in the CDF implementation methodology. Within inLABs we are now studying how to apply such a check in specific processes and how to assess its effectiveness

Why approval alone is not always enough

A person being present in the process does not in itself guarantee the quality of oversight. When recommendations appear frequently and their content is complex, approval can become a reflex. The decision-maker may not have a full picture of the premises, exceptions or limits of the recommendation. In such a case the system has a formal record of approval, but the organisation still does not know whether the decision was actually considered

This problem is particularly important where a decision affects a client, an employee, operational safety, resources or the continuity of a process. Speed is valuable, but it cannot lead to a situation in which a person signs off a result without being able to understand what it means in the case at hand

A second challenge is the difference between general knowledge and preparation for a specific decision. A competent person does not always have the current context of the matter, and a person who knows its details may need support in assessing the limitations of an AI recommendation. The organisation therefore needs an approach that does not reduce accountability to the user being present in front of the screen

HCG answers the question of how to make a person’s decision really matter: before an action is approved, it makes it possible to make sure that the person responsible understands the specific matter and has the competence needed to assess it

It is important to keep a sense of proportion: the amount of attention and support should match the significance of the specific decision, rather than creating the same obstacle for every action

Where HCG may matter

The scenarios below are possible directions of application, not a description of deployments or available features

01Supported decisions in procurement processesIn an organisation, an AI recommendation can help organise the information needed to assess options. The control point under study would help the approver confirm that they understand the key assumptions, limitations and consequences of the decision before taking action
02Changes with a significant operational impactWhen changing a configuration, priorities or the way a process is carried out, an AI recommendation may require informed confirmation by the right person. Such a check could direct their attention to the context of the decision and indicate that additional explanation or an expert’s involvement is needed
03Working with recommendations in complex mattersIn matters requiring domain knowledge, AI can organise and summarise the available information, but it does not take responsibility for assessing it. HCG helps establish whether the decision-maker sees the significant limitations and knows when not to rely solely on the AI recommendation
04Introducing AI into new roles and processesIn the early period of working with AI, teams learn how to interpret its results and where automatic support ends. We are studying whether the first decisions of a given type require particular attention, and how to design such points of reflection without slowing down every action

In methodological terms, approving an action may require confirmation that the person responsible has the appropriate competence and understands the matter. HCG does not, however, determine which decision is right; that remains with the person responsible for the process

Role in the inLABs ecosystem

Scope

HCG plays a cross-cutting role: it concerns the moment when a person is to assess or approve an AI-supported action. It is not a separate application, a training platform or an HR system. Its scope covers the relationship between the recommendation, the context of the decision and the accountability of the person authorised to act

Limits

CDF and HCG complement each other, but they can be used independently. In CDF, questions of human competence are addressed at the stage where the organisation checks its readiness for informed approval of AI-supported decisions. A separate line of inLABs work is CDT, which concerns the continuity of knowledge about a person’s work. AICF, devoted to operational oversight of compliance, is also being developed independently. This description does not mean a finished integration, a shared operating environment or data flows between these solutions

HCG does not replace the organisation’s policies, risk assessment, access control, expert knowledge or human decisions; nor does it remove the accountability of the deploying organisation. It is not used for individual profiling of employees. Using it does not require the other elements of the ecosystem

Principle of the approach: from recommendation to an informed decision

The starting point of the work is a simple hypothesis: formal approval has limited value if the approver does not understand what the decision concerns and what its limits are. HCG studies how the elements requiring informed assessment can be presented before a decision, so that the person remains a real participant in the process

The approach can be described through three elements. The first is the context of the decision: what it concerns and what information is important. The second is understanding: whether the approver can relate to the assumptions, limitations and possible consequences. The third is responsible action: approval, consultation or withdrawal. This model refers to the requirements for human competence and oversight described in the AI Act and ISO/IEC 42001, but it is not a declaration of conformity or legal advice

The aim is not to replace human judgement with an automatic assessment. The goal is a way of organising decisions that helps a person consider a specific matter carefully. HCG therefore differs from general training or a universal checklist: it takes into account the situation, the responsibility assigned to the role and the limitations of the given recommendation

The approach must remain understandable to the person using it. The research will therefore concern not only the moment of decision itself, but also whether the context presented helps people see uncertainty rather than seemingly removing it

Research and validation

Further research on HCG may include analysis of different decision situations, expert reviews and a comparison of several ways of supporting a person before an action is approved. We will assess, among other things, how clearly the context is presented, whether an additional check is justified, how useful it is for the decision-maker and whether the person’s role in the whole process can be explained clearly

The limits of this approach also need to be defined. An additional check should improve the quality of decisions, not become an empty formality or an excessive burden on the process. The research must therefore take into account different roles, levels of risk and the real conditions in which the organisation operates

It will be important to assess whether the form of support leaves the decision-maker with a clear basis for their own judgement, instead of suggesting automatic certainty. Depending on the scenario, both qualitative analyses and comparisons of how the process behaves before and after the control point is introduced may be needed

Subsequent work may focus on distinguishing the decisions in which a human control point is genuinely justified, on ways of presenting the limitations of recommendations and on keeping a clear boundary between AI support and human accountability. Every future scenario requires a separate assessment of the context, risk and organisational rules, and an accountable decision owner

Project statusThe methodological part of HCG has been developed; its extensions and measurement remain the subject of research. This page does not announce a product, a pilot programme, availability or a commercial schedule
AICF
AI Compliance Framework

The project studies how to turn compliance requirements for generative AI systems into verifiable controls, evidence and human decisions

1 · Concept2 · Methodology / prototype3 · FENG application4 · Research and validation5 · Result
Research problemDeclarations of compliance are hard to turn into repeatable operational actions and evidence
HypothesisExplicit criteria and controlled trials can make the assessment of a GenAI system more verifiable
ValidationComparisons, expert reviews and qualitative and quantitative assessment in a defined context are planned
StatusThe funding application has been submitted; carrying out the research depends on the outcome of the assessment

Towards operational compliance control for generative AI

AICF (AI Compliance Framework) is an inLABs research and development project for which we are seeking funding under the European Funds for a Modern Economy (FENG) programme. We want to study how organisations can continuously oversee the compliance of their use of generative AI with regulations, standards and their own rules. We do not want to reduce compliance to a one-off checklist. We plan to examine how to describe the organisation’s requirements clearly, relate them to a specific task and retain the evidence later needed by the person responsible for the assessment. Work will begin only once funding has been granted; the project cannot be launched without a positive outcome of the application assessment

Why this research matters

Generative AI increasingly supports business processes in which data, decisions and obligations change. A policy or assessment prepared before deployment is still needed, but it does not always explain what to do after a change of task, model, data source, tool or organisational conditions. AICF is meant to focus precisely on this gap between a written requirement and the way AI is actually used

Requirements are not static in practiceOrganisations have to take into account regulations, standards, contracts and their own rules. Each of these sources may change at a different pace and matter differently to individual teams, processes and data. We want to study how to keep these requirements clear as the way AI is used changes. We do not assume that a single rule or a single result is enough in every situation
Evidence is often fragmentedInformation confirming how AI works is often scattered across systems and people. As a result, it is hard to establish what was actually checked, which issues were considered important and what action should be taken next. We plan to study how to combine the context of use, compliance requirements and a record of decisions in a way that can later be verified. The aim will be better accountability, not replacing experts
Control mechanisms must be understandable to peopleControl mechanisms must help the people responsible understand the situation and decide what to do next. A solution may be technically advanced, but if it cannot be understood, challenged or overseen, it will not solve the underlying problem. That is why transparency, the ability to reconstruct the course of a decision and human accountability are as important to us as control itself

Potential application scenarios

The examples below show possible research directions. They do not describe client deployments, product commitments or the current availability of a solution

01AI-supported internal workIn a controlled workflow within the organisation, AICF could be used to study how requirements are taken into account in an AI-supported task. We also want to check whether such an assessment remains available for later verification by the person responsible. A possible outcome would be a clearer basis for discussion when a use case changes or raises doubts
02Regulated business processesIn processes shaped by more than one source of obligations, the research is meant to check whether a unified picture of controls supports qualified verification. The goal will not be automatic certification of a process or a binding legal assessment, but better visibility of significant issues and limitations
03A change in policy or operational contextWhen a policy, operating rule or significant condition changes, the research scenario involves identifying the places where the change may require renewed attention. We want to study how an organisation could turn such a signal into a documented need for verification instead of leaving it implicit
04Moving from project to operationTeams building AI-based services may need to link design requirements with their later operational use. In this scenario, AICF research is meant to cover only the operational phase; pre-deployment assessment, approval, deployment and risk acceptance remain with the appropriate people, methodologies and processes of the organisation

Role in the inLABs ecosystem

Scope

AICF is a separate research and development project with its own scope. We plan to study the operational side of compliance control, not the way the requirements themselves are defined or the systems through which people use AI. The description does not cover oversight of other work in the inLABs portfolio

Limits

CDF organises the process of controlled AI implementation, and PROXY:AI supports controlled access between users, applications, agents and models. SAVANT-AI is a separate research and development project focused on knowledge and reasoning at the scale of the organisation. AICF can be considered alongside these items, but this page does not claim a deployed integration, a shared execution environment or production data flows. AICF does not create the organisation’s requirements or policies, does not assess maturity before deployment and does not take over responsibility for the decision

From requirements to verifiable evidence

At a public level, the research can be summed up as a simple relationship:

We want to check whether requirements can be written down in a way that makes it easier to assess AI-supported actions in a specific context. We also plan to study whether significant changes can be signalled without creating a false sense of certainty, and whether the evidence collected helps the person responsible understand and challenge the basis of a decision. AICF is meant to concern ongoing compliance control; it will not be a universal security tool, a legal opinion or a system that approves decisions automatically. This description does not constitute legal advice

Detailed mechanisms, data models and decision procedures are deliberately left out of this public description. What matters is the direction of the planned research: control that is more continuous, interpretable and linked to real accountability within the organisation

Research methods and validation

AICF is a research and development project whose assumptions will require evidence, not claims, once it has been launched. The work is to include limited test cases, controlled comparisons with suitably chosen reference approaches and qualified expert assessment. The assessment will concern the comprehensibility, consistency, traceability and robustness of the approach in a defined context. It will also take into account situations in which requirements overlap and the available information is incomplete

The results will require careful interpretation. A positive result in one scenario will not establish universal compliance, legal sufficiency or suitability for another organisation. A partial or negative result will be a valid research outcome: it may show where human verification, a clearer requirement or a different approach to control is needed. Detailed research materials and unpublished results will not be part of this page

Project statusAICF is currently at the stage of applying for funding under the FENG programme; the application has been submitted and is awaiting a decision. We plan to study the rules, evidence models and validation methods needed for operational compliance control in generative AI environments, together with the limits of its use. The project cannot be launched without a positive outcome of the application assessment
SAVANT-AI
Semantic Autonomous Versatile Advanced Network Technology — Artificial Intelligence

We study how to bring together organisational knowledge, expert experience, AI agents and business systems in a single, controlled working context

1 · Concept2 · Methodology / prototype3 · FENG application4 · Research and validation5 · Result
Research problemThe knowledge needed to complete a task is scattered across people, documents and systems
DirectionControlled delivery of the right context to a task without unrestricted access to resources
ProgressEarly prototypes are available for testing selected assumptions
LimitThe project is not an announcement of a finished product or a claim of full agent autonomy

Research on controlled work with organisational knowledge

SAVANT-AI (Semantic Autonomous Versatile Advanced Network Technology — Artificial Intelligence) is an inLABs research and development project. We are studying how to bring together organisational knowledge, expert experience, AI agents and business systems in a single, controlled working context. It is not about replacing people or announcing a finished product. We want to check whether complex organisations can make better use of scattered information while preserving human accountability, access rules and the ability to trace information back to its sources

Why this research is needed

Important organisational knowledge is created in documents, operational systems, expert conversations and everyday decisions. Each source shows only part of the situation, often describing it in different language and from a different perspective. To answer one important question, a team has to find the information, check how current it is, establish what it means and reconcile it across departments. This is necessary, but time-consuming and prone to losing context

A second problem is knowledge that depends on specific people. When experience is not visible to other teams, or it is unclear where to look for the right expert, the organisation finds it harder to learn from its own decisions and changes. The risk grows when processes are complex, data is sensitive and the consequences of a mistake go beyond one department

Searching documents alone is not enough. The question also has to be understood in the context of the task, information has to be combined carefully, access rules have to be taken into account and a person has to be able to assess the conclusion received. SAVANT-AI explores this space without assuming that every answer can or should be produced automatically

Potential application scenarios

The examples below are research directions, not a description of deployments or available features, nor a promise of results

01Industrial operations and critical infrastructureIn an organisation where knowledge about processes, events and exceptions is created in many departments and systems, the direction under study could help teams find the relevant context for jointly considering a problem. A potential outcome would be more complete preparation of material for decisions by the people responsible for the process
02Continuity of expert knowledgeWhen key knowledge is scattered across specialists, procedures and the history of events, SAVANT-AI may be a subject of research into safely pointing out areas that need to be filled in or discussed with an expert. The goal is not to take over a person’s competence automatically, but to reduce the risk that important context remains invisible
03Regulated organisationsIn sectors where permissions, the provenance of information and the ability to review decisions matter, the work may test whether such an approach supports the analytical process. Any value depends on the specific application, data, environment and controls; the technology itself does not confirm regulatory compliance or security
04Collaboration between teamsFor decisions that cross departmental boundaries, the research may test whether organised context makes it easier to formulate questions, compare perspectives and document open issues. A possible result is a better basis for discussion and verification, not an autonomous resolution

Role in the inLABs ecosystem

Scope

SAVANT-AI has a separate research scope: it focuses on knowledge and reasoning at the scale of the organisation. The documentation also anticipates dependencies that go beyond conceptual complementarity: TWIN:DESK would remain the working environment and the place where users interact with knowledge, and PROXY:AI would provide controlled access between users, applications, agents and models. The way the implementation itself is carried out would be organised by CDF. These are, however, relationships anticipated in the documents, not confirmed by a working solution

Limits

GENESIS-AI, which concerns the path from requirements to an application package, remains a separate direction; we describe their proximity in the portfolio as a separation of scopes. This page does not claim a shared execution environment, data flows or a working integration. SAVANT-AI does not replace permission mechanisms, responsibility for implementation or human decisions

General principle of the approach

The starting point is simple: an organisation can make better-founded decisions when the right sources, the user’s question and expert knowledge are analysed together instead of remaining in separate places. The system receives only information approved for use and a question embedded in a specific task. It then helps organise the context, indicate uncertainty and determine what still needs to be checked. The result is meant to be material that supports a person’s assessment

The difference compared with simple search lies in studying the relationships between information, roles and the consequences of using knowledge. This does not mean, however, that the system automatically understands the organisation, makes decisions or determines whether conclusions are correct. The scope, reliability and usefulness of the answers remain the subject of research and depend on the quality of the sources and the context of application

Research methods and validation

Work on SAVANT-AI may include comparisons with suitably chosen baseline approaches, expert assessment and qualitative and quantitative study in controlled cases. The properties analysed may concern the relevance of the context, usefulness for the user, the ability to find the basis of reasoning, robustness to data changes and the limits of the solution’s use

An important part of validation is also checking when an answer should not be treated as sufficient: when the sources are incomplete, contradictory, unavailable or require a decision by an authorised person. Security, privacy and compliance will be assessed in relation to a specific environment, data and way of use, not declared as a universal property. On this page we do not present experimental results, benchmarks or non-public procedures

Project statusSAVANT-AI is a research and development project based on earlier conceptual work and early prototypes, with a planned research scope and assessment criteria. The work concerns refining the research problems, the limits of responsibility and the categories of evidence needed for later validation. The further direction includes assessing the quality of context, studying human collaboration with the system and analysing limitations across different classes of applications
GENESIS-AI
Generative Engine for Software Innovation Systems

The project studies whether approved requirements and explicit control criteria can lead to more consistent, reviewable software artefacts

1 · Concept2 · Methodology / prototype3 · FENG application4 · Research and validation5 · Result
Research problemThe original intent easily drifts away from the code, tests and documentation produced in later stages of work
HypothesisShared assessment criteria can increase the consistency of artefacts and make their technical review easier
ValidationControlled comparisons, reviews and an assessment of repeatability across different classes of problems are planned
StatusThe FENG application is awaiting a decision; the experiments have not yet begun

Towards a more controlled path from requirements to software

GENESIS-AI is an inLABs research and development project for which we are seeking funding under the European Funds for a Modern Economy (FENG) programme. The project concerns the use of generative AI in software engineering. We plan to examine how to move from approved business and technical requirements to a consistent package of application elements that can be reviewed and assessed. Responsibility for engineering decisions will remain with people

The research is to cover selected types of web applications. Mobile and desktop applications and real-time systems remain out of scope. We do not want to replace the product owner, the architect or the development team. We want to check whether better organisation of work, regular verification and the ability to trace the link between a requirement and the result increase the reliability of AI-supported work. Delivery depends on funding being granted; the project cannot be launched without a positive outcome of the application assessment. GENESIS-AI is a research and development project, not an announcement of a finished product or service

Why this research is needed

Generative AI can quickly produce fragments of software. It is much harder to build a complete application that still serves its real purpose. That is why we plan to focus GENESIS-AI research on four related problems, provided the project receives funding

Requirements can be incomplete and ambiguousA business description often combines facts, unspoken assumptions and terms understood differently by different people. If these ambiguities enter an automated process, the resulting solution may work correctly from a technical point of view but fail to meet the organisation’s needs. We want to study how to detect and clarify such problems before they carry over into further application elements
Application artefacts can fall out of step with one anotherAn application is not just code. Interfaces, data structures, tests, documentation and deployment materials should describe the same system. If they are produced separately, a change in one place can cause a contradiction in another. We plan to examine how to control the consistency of the whole solution, rather than treating its generation as a single opaque step
Speed is not proof of qualityA fast result may be hard to maintain, unsuitable for a given environment or insufficiently secure. Correctness, maintainability, portability, reliability and security are categories of assessment, not properties that can simply be assumed
Responsibility cannot be handed over to a modelGoals, constraints, the acceptable level of risk and acceptance of the solution remain the responsibility of people. GENESIS-AI is meant to study how an AI-supported process can provide material for assessment and mark the moments that require review, without pretending that automation replaces responsible judgement

Possible applications

Research scenario
01Internal applications with a clearly defined scopeGENESIS-AI, provided it receives funding, is meant to be used to study the preparation of limited web applications based on requirements previously reviewed by domain and technical experts. In such a context it will be possible to assess consistency with the requirement, the consistency of the artefacts and the possibility of developing them further
Research scenario
02Verifying a solution conceptA reviewable application package could help a team assess whether a proposed process, information model or user interaction matches the intended problem. The result would still require technical assessment and would not in itself be a finished deployment
Exploratory scenario
03Repeatable work of development teamsTeams building similar classes of applications may be interested in research into more repeatable preparation of code, tests and documentation. The key question is whether structure-based assistance reduces inconsistencies without hiding assumptions or weakening engineering accountability
Exploratory scenario
04Development in an environment with higher requirementsGENESIS-AI may be studied in organisations that use their own processes to manage change, control access and approve the results of engineering work. The project itself does not, however, determine the legal or regulatory compliance or the security of a specific application; these depend on the organisation’s data, environment, controls and decisions

Role in the inLABs ecosystem

Scope

GENESIS-AI is meant to focus on the path from approved requirements to a package of application artefacts intended for review. Other items in the inLABs portfolio have separate scopes: CDF organises AI implementation, TWIN:DESK is the working environment, PROXY:AI concerns controlled access and SAVANT-AI — organisational knowledge

Limits

The GENESIS-AI research documentation does not establish dependencies on these elements, so we describe their proximity in the portfolio as a separation of scopes rather than a confirmed technical integration, a shared execution environment or production data flows. GENESIS-AI will not replace the CDF implementation methodology, the TWIN:DESK working environment, the access boundary and policies of PROXY:AI or the research on knowledge and reasoning carried out in SAVANT-AI. Any interaction between these elements would require separate, verified foundations

Approach and operating principle

GENESIS-AI is meant to study the relationship between three levels:

Approved requirements are to be the point of reference. On their basis, related application elements would be produced in a controlled way and then checked. The finished package would go to the people responsible for technical assessment and for the decision on further development or possible deployment

This is a general description of the planned way of working, not of the solution’s architecture. We want to check whether better organisation of requirements and explicit checking of results can reduce the gap between the original intent and the outcome. We also plan to study whether shared assessment criteria for code, tests and documentation lead to a more consistent result than producing these elements independently. These are hypotheses to be tested only after the project has been launched; the experiments have not yet begun and depend on funding being granted

Research methods and validation

The reliability of GENESIS-AI is to be assessed through complementary, planned classes of research: controlled comparisons with reference approaches, reviewed cases, testing of repeatability across different classes of problems and qualitative and quantitative assessment in a defined context. The analysis is to cover, among other things, consistency with requirements, functional and integration correctness, reliability, maintainability, portability, security, controllability and usefulness for the engineering team

The assessment will not be based solely on demonstrations or the volume of material produced. Automated checks will require expert interpretation, and repeated trials should distinguish a lasting effect from chance. A partial or negative result will be a valid research outcome; evidence of failure will be equally important: unresolved ambiguity, divergence between artefacts, limitations of the review or the need for additional human work

The planned direction of further work, to be carried out once funding is granted, includes studying fidelity to requirements, managing ambiguity, consistency across the artefact life cycle, reliability across different classes of problems and ways of conducting reviews without losing human accountability

Project statusThe project is currently at the stage of applying for funding under the FENG programme; the application has been submitted and is awaiting a decision. The research questions, hypotheses, assessment categories and the type of evidence needed for validation have been described for the purposes of the application. Their actual implementation, scope and research results depend on funds being granted and will begin only once the project has been launched; without a positive outcome of the assessment the project will not be launched
Three core capabilities

1 · Knowledge covered by consent · acquisition and organisation · 2 · Link to the task · context, source, date of creation, · level of certainty · 3 · The person who decides · still makes the decision · on their own · Consent, access, correction and deletion · rules for using knowledge · Contact with an expert · when knowledge cannot be described or passed on · KNOWLEDGE · A PERSON DECIDES

From recommendation to an informed decision

1 · AI recommendation · basis for assessment · 2 · Context of the decision · what it concerns and what · information is important · 3 · Understanding · assumptions, · limitations, possible · consequences · 4 · Responsible · action · a person's decision · Approval · Consultation · Withdrawal · RECOMMENDATION · HUMAN DECISION

From requirements to verifiable evidence

1 · The organisation's requirements · regulations, standards, contracts and own · rules · 2 · Operational context of · AI · a specific task supported by · AI · 3 · Evidence for verification by · a person · understandable · and open to challenge · Change signal · a change of policy, task, model, data source or tool · Person responsible for the assessment · the decision remains with a person · REQUIREMENTS · VERIFICATION

High-level model

1 · Organisational knowledge · and the question · only information approved for · use · 2 · Controlled context to · check · organised context, indicated · uncertainty · 3 · Assessment and decision · a person · material supporting the assessment · Sources and permissions · the ability to go back to the sources · What still needs to be checked · when sources are incomplete or contradictory · KNOWLEDGE AND QUESTION · HUMAN DECISION

Three levels studied in GENESIS-AI

1 · Approved requirements · business and technical · 2 · Controlled process · of software production · related application elements, · checked · 3 · A package of artefacts · that can be reviewed · code, tests, documentation · Shared assessment criteria · for code, tests and documentation · Technical assessment and a person's decision · on further development or possible deployment · REQUIREMENTS · REVIEW

Would you like to influence the development of the CDT project?

Would you like to influence the development of the HCG project?

Would you like to influence the development of the AICF project?

Would you like to influence the development of the SAVANT-AI project?

Would you like to influence the development of the GENESIS-AI project?

Contact form

NEXT

What else to explore

inLABsSAIE
Next step
SAIE

Three layers, one AI working environment — the problem, the solution and who it is for

Next: SAIE

TWIN:DESKAI working environment: domain assistants, company knowledge, agents and 48 features

PROXY:AIAI control gateway: policies, Zero-Code Switch, WORM register and 54 features

CDF methodologyAI implementation step by step: initial assessment, phases F0–F6, oversight and CogOps

Quality policy and certificatesQuality policy and ISO certificates, including ISO/IEC 42001

https://www.allclouds.pl/en/inlabs/