# US 2026/0310594 A1 · Systems and methods for generating a code-failure taxonomy for remediating failures in executing software code

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0310594 A1
- Document ID: US20260310594A1
- Status: Published application
- Kind: A1
- Application number: 19/715,313
- Filed: 2026-06-22
- Published: 2026-10-08
- Earliest claimed: 2024-12-27
- Assignees: Constructor Technology AG; Constructor Education and Research Genossenschaft; Constructor Labs gGmbH
- Applicants: Constructor Technology AG; Constructor Education and Research Genossenschaft; Constructor Labs gGmbH
- Inventors: Alexander Tormasov; Giancarlo Succi; Nikolay Dobrovolskiy; Stanislav Protasov; Laurent Dedenis; Serg Bell
- Web page: https://patentgrep.com/patent/US20260310594A1

## CPC

- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Disclosed are systems and methods for generating a code-failure taxonomy. An example method includes: retrieving a plurality of scientific or technical documents and a plurality of software code each associated with a respective document and configured to programmatically implement scientific or technical computational procedures described within the respective document; generating a plurality of feature descriptors each identifying scientific or technical features of the respective document and corresponding code features of the software code; for each software code, executing the software code, detecting a code execution failure, identifying a cause of the code execution failure, generating a failure signature comprising a descriptor of the code execution failure, and generating a remediation strategy specifying one or more corrective actions; and generating a code-failure taxonomy comprising a plurality of failure classification nodes each associated with at least one of the feature descriptors and containing a respective failure signature and a respective remediation strategy.

## Claims

### Claim 1

A computer-implemented method for generating a code-failure taxonomy for scientific or technical documents, the computer-implemented method comprising:
retrieving a plurality of scientific or technical textual documents and a plurality of software code each associated with a respective textual document and configured to programmatically implement scientific or technical computational procedures described within the respective textual document;
generating, for each textual document and associated software code, a feature descriptor identifying one or more scientific or technical features of the respective textual document and one or more code features of the associated software code;
for each software code,
executing the software code, detecting a code execution failure, and identifying a cause of the code execution failure;
generating a failure signature comprising a descriptor of the detected code execution failure; and
generating, based on the identified cause, a remediation strategy specifying one or more corrective actions; and
generating a code-failure taxonomy for the scientific or technical documents comprising a plurality of failure classification nodes, each node associated with at least one of the feature descriptors and containing a respective failure signature and a respective remediation strategy.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the generating the feature descriptor includes:
using a trained machine learning model (MLM) to identify the one or more scientific or technical features of the textual document corresponding to the scientific or technical computational procedures described within the textual document;
using the trained MLM to identify in the software code the one or more code features corresponding to the identified one or more scientific or technical features of the textual document; and
generating at least one of the feature descriptors combining the one or more scientific or technical features and corresponding code features.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the one or more scientific or technical features of the textual document include at least one of a scientific or technical domain of the textual document, a computational algorithm, a scientific procedure, a mathematical formular, a chemical formula, or a data structure containing scientific or technical data.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein the one or more code features of the software code include at least one of a programming language of the software code, an algorithm of the software code, a parameter or a variable of the software code, a configuration option of the software code, or an environment requirement of the software code.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein the code execution failure includes at least one of log data, an error message, a stack trace, or an output mismatch indicating a discrepancy with one or more of the computational procedures described within the textual document.

### Claim 6 (depends on 5)

The computer-implemented method of claim 5, wherein the failure signature is based on a normalized representation of the at least one of the log data, the error message, the stack trace, or the output mismatch included in the code execution failure.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein the executing the software code includes:
generating a secure virtual environment; and
executing the software code within the secure virtual environment.

### Claim 8 (depends on 7)

The computer-implemented method of claim 7, wherein the executing the software code includes executing the software code within the secure virtual environment under a test suite, wherein the test suite includes at least one of an environment test configured to verify a software dependency in the secure virtual environment or a code execution test configured to execute a portion of the software code with a test dataset.

### Claim 9 (depends on 8)

The computer-implemented method of claim 8, wherein the test suite is associated with one failure classification node corresponding to the code execution failure of the software code.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, wherein the remediation strategy includes at least one of an environment-level modification or a code-level modification to the software code.

### Claim 11 (depends on 10)

The computer-implemented method of claim 10, wherein the environment-level modification includes a modification to at least one of a software dependency, a library version, an environment variable, or a hardware allocation.

### Claim 12 (depends on 10)

The computer-implemented method of claim 10, wherein the code-level modification includes at least one of an application of a predefined path template or a change of the software code using an MLM.

### Claim 13 (depends on 1)

The computer-implemented method of claim 1, further comprising:
repairing the software code based on the one or more corrective actions specified in the remediation strategy; and
re-executing the repaired software code until the failure signature is remediated or a termination condition is met.

### Claim 14 (depends on 1)

The computer-implemented method of claim 1, further comprising:
updating the code-failure taxonomy by determining whether a feature descriptor of a new textual document matches the feature descriptors already associated with the nodes of the code-failure taxonomy or an extracted failure signature of a new software code matches the failure signatures already associated with the nodes of the code-failure taxonomy, wherein the new software code is associated with the new textual document, and the extracted failure signature is extracted from execution of the new software code.

### Claim 15 (depends on 14)

The computer-implemented method of claim 14, further comprising:
in response to the feature descriptor matching the feature descriptors already associated with the nodes of the code-failure taxonomy or the extracted failure signature matching the failure signatures already associated with the nodes of the code-failure taxonomy,
associating with the node having the matched feature descriptor or the matched failure signature the feature descriptor, the extracted failure signature, and at least one remediation strategy that successfully remediates the extracted failure signature; and
in response to the feature descriptor not matching the feature descriptors already associated with the nodes of the code-failure taxonomy and the extracted failure signature not matching the failure signatures already associated with the failure classification nodes of the code-failure taxonomy,
generating a new failure classification node of the code-failure taxonomy, and
associating with the new failure classification node the feature descriptor, the extracted failure signature, and the at least one remediation strategy that successfully remediates the extracted failure signature.

### Claim 16 (depends on 1)

The computer-implemented method of claim 1, wherein a hierarchical structure of the code-failure taxonomy includes a multi-level taxonomy tree with each level representing a failure granularity of the code execution failure.

### Claim 17

A system for generating a code-failure taxonomy for scientific or technical documents, the system comprising processing circuitry configured to:
retrieve a plurality of scientific or technical textual documents and a plurality of software code each associated with a respective textual document and configured to programmatically implement scientific or technical computational procedures described within the respective textual document;
generate, for each textual document and associated software code, a feature descriptor identifying one or more scientific or technical features of the respective textual document and one or more code features of the associated software code;
for each software code,
execute the software code, detecting a code execution failure, and identifying a cause of the code execution failure;
generate a failure signature comprising a descriptor of the detected code execution failure; and
generate, based on the identified cause, a remediation strategy specifying one or more corrective actions; and
generate a code-failure taxonomy for scientific or technical documents comprising a plurality of failure classification nodes, each node associated with at least one of the feature descriptors and containing a respective failure signature and a respective remediation strategy.

### Claim 18 (depends on 17)

The system of claim 17, wherein the one or more scientific or technical features of the textual document include at least one of a scientific or technical domain of the textual document, a computational algorithm, a scientific procedure, a mathematical formular, a chemical formula, or a data structure containing scientific or technical data.

### Claim 19 (depends on 17)

The system of claim 17, wherein the one or more code features of the software code include at least one of a programming language of the software code, an algorithm of the software code, a parameter or a variable of the software code, a configuration option of the software code, or an environment requirement of the software code.

### Claim 20

A non-transitory computer readable medium storing thereon computer executable instructions for generating a code-failure taxonomy for scientific or technical documents, including instructions for:
retrieving a plurality of scientific or technical textual documents and a plurality of software code each associated with a respective textual document and configured to programmatically implement scientific or technical computational procedures described within the respective textual document;
generating, for each textual document and associated software code, a feature descriptor identifying respective one or more scientific or technical features of the respective textual document and one or more code features of the associated software code;
for each software code,
executing the software code, detecting a code execution failure, and identifying a cause of the code execution failure;
generating a failure signature comprising a descriptor of the detected code execution failure; and
generating, based on the identified cause, a remediation strategy specifying one or more corrective actions; and
generating a code-failure taxonomy for scientific or technical documents comprising a plurality of failure classification nodes, each node associated with at least one of the feature descriptors and containing a respective failure signature and a respective remediation strategy.
