# US 2024/0004637 A1 · Systems and methods for coordinating the deployment of components to defined user groups

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

- Number: US 2024/0004637 A1
- Document ID: US20240004637A1
- Status: Published application
- Kind: A1
- Application number: 18/369,827
- Filed: 2023-09-18
- Published: 2024-01-04
- Earliest claimed: 2018-12-18
- Assignees: Palantir Technologies Inc.
- Applicants: Palantir Technologies Inc.
- Inventors: William HICKMAN; Mark ELLIOT
- Web page: https://patentgrep.com/patent/US20240004637A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/38: for implementing user interfaces
- G06F 9/451: Execution arrangements for user interfaces
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods are provided for coordinating the deployment of frontend assets to defined user groups. Individual groups of users may be assigned to a track comprising a set of frontend assets. Each set of frontend assets may comprise each of the individual components required to generate an entire frontend for an application. In some embodiments, different versions of a single component may be assigned within different tracks. As such, one set of users may be provided a first version of an application and a second set of users may be provided a second version of that application. By associating a new or updated version of a component to a given track, a new or updated version of a component not yet ready for widespread deployment may be provided to only a limited number of users.

## Claims

### Claim 1

A system comprising:
one or more processors; and
a memory storing instructions that, when executed by the one or more processors, cause the system to:
generate a first stack or a first stack portion to deploy a first application component, wherein the first application component and the first stack or the first stack portion has a first stability level or a first confidence level;
coordinate a deployment of the first application component based on the first stack or the first stack portion;
receive an indication that the first application component is validated;
in response to receiving the indication, incorporate the first application component into a second stack or a second stack portion, wherein the second stack or the second stack portion has a second stability level or a second confidence level distinct from the second stability level or the second confidence level;
in response to incorporating the first application component into a second stack or a second stack portion, update a deployment of the second stack or the second stack portion; and
render a front end component corresponding to the second stack or the second stack portion.

### Claim 2 (depends on 1)

The system of claim 1, wherein the first stability level or the first confidence level is associated with a lower stability level or a lower confidence level compared to the second stability level or the second confidence level, and the indication is associated with the first application component having increased a stability level or a confidence level beyond a threshold corresponding to the second stability level or the second confidence level.

### Claim 3 (depends on 1)

The system of claim 1, wherein the instructions further cause the system to:
in response to receiving the indication, remove the first application component from the first stack or the first stack portion; and
the removing of the first application component from the first stack or the first stack portion comprises updating a previous mapping among any dependent application components of the first application component.

### Claim 4 (depends on 1)

The system of claim 1, wherein the indication comprises a first indication; and the instructions further cause the system to:
receive a second indication that the first application component has increased a stability level or a confidence level beyond a threshold corresponding to a third stability level or a third confidence level corresponding to a third stack or a third stack portion;
in response to receiving the second indication, incorporate the first application component into the third stack or the third stack portion;
retain the first application component in the first stack or the first stack portion; and
update a deployment of the third stack or the third stack portion.

### Claim 5 (depends on 1)

The system of claim 1, wherein the deployment of the second stack or the second stack portion is from a common server as the deployment of the first stack or the first stack portion.

### Claim 6 (depends on 1)

The system of claim 1, wherein the first application component comprises any two selected from a group consisting of: a user interface component, a library, and a program.

### Claim 7 (depends on 1)

The system of claim 1, wherein the updating the deployment of the second stack or the second stack portion comprises updating a map of dependencies among the first application component, a dependent application component, and a backend component.

### Claim 8

A method being implemented by a computing system having one or more processors and a storage media storing machine-readable instructions that, when executed by the one or more processors, cause the computer system to perform the method, the method comprising:
generating a first stack or a first stack portion to deploy a first application component, wherein the first application component and the first stack or the first stack portion has a first stability level or a first confidence level;
coordinating a deployment of the first application component based on the first stack or the first stack portion;
receiving an indication that the first application component is validated;
in response to receiving the indication, incorporating the first application component into a second stack or a second stack portion, wherein the second stack or the second stack portion has a second stability level or a second confidence level distinct from the second stability level or the second confidence level;
in response to incorporating the first application component into a second stack or a second stack portion, updating a deployment of the second stack or the second stack portion; and
rendering a front end component corresponding to the second stack or the second stack portion.

### Claim 9 (depends on 8)

The method of claim 8, wherein the first stability level or the first confidence level is associated with a lower stability level or a lower confidence level compared to the second stability level or the second confidence level, and the indication is associated with the first application component having increased a stability level or a confidence level beyond a threshold corresponding to the second stability level or the second confidence level.

### Claim 10 (depends on 8)

The method of claim 8, further comprising:
in response to receiving the indication, removing the first application component from the first stack or the first stack portion; and
the removing of the first application component from the first stack or the first stack portion comprises updating a previous mapping among any dependent application components of the first application component.

### Claim 11 (depends on 8)

The method of claim 8, wherein the indication comprises a first indication; and the method further comprises:
receiving a second indication that the first application component has increased a stability level or a confidence level beyond a threshold corresponding to a third stability level or a third confidence level corresponding to a third stack or a third stack portion;
in response to receiving the second indication, incorporating the first application component into the third stack or the third stack portion;
retaining the first application component in the first stack or the first stack portion; and
updating a deployment of the third stack or the third stack portion.

### Claim 12 (depends on 8)

The method of claim 8, wherein the deployment of the second stack or the second stack portion is from a common server as the deployment of the first stack or the first stack portion.

### Claim 13 (depends on 8)

The method of claim 8, wherein the first application component comprises any two selected from a group consisting of: a user interface component, a library, and a program.

### Claim 14 (depends on 8)

The method of claim 8, wherein the updating the deployment of the second stack or the second stack portion comprises updating a map of dependencies among the first application component, a dependent application component, and a backend component.

### Claim 15

A non-transitory computer readable medium comprising instructions that, when executed, cause one or more processors of a computing system to perform:
generating a first stack or a first stack portion to deploy a first application component, wherein the first application component and the first stack or the first stack portion has a first stability level or a first confidence level;
coordinating a deployment of the first application component based on the first stack or the first stack portion;
receiving an indication that the first application component is validated;
in response to receiving the indication, incorporating the first application component into a second stack or a second stack portion, wherein the second stack or the second stack portion has a second stability level or a second confidence level distinct from the second stability level or the second confidence level;
in response to incorporating the first application component into a second stack or a second stack portion, updating a deployment of the second stack or the second stack portion; and
rendering a front end component corresponding to the second stack or the second stack portion.

### Claim 16 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the first stability level or the first confidence level is associated with a lower stability level or a lower confidence level compared to the second stability level or the second confidence level, and the indication is associated with the first application component having increased a stability level or a confidence level beyond a threshold corresponding to the second stability level or the second confidence level.

### Claim 17 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the instructions that, when executed, cause one or more processors of a computing system to perform:
in response to receiving the indication, removing the first application component from the first stack or the first stack portion; and
the removing of the first application component from the first stack or the first stack portion comprises updating a previous mapping among any dependent application components of the first application component.

### Claim 18 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the indication comprises a first indication; and the instructions that, when executed, cause one or more processors of a computing system to perform:
receiving a second indication that the first application component has increased a stability level or a confidence level beyond a threshold corresponding to a third stability level or a third confidence level corresponding to a third stack or a third stack portion;
in response to receiving the second indication, incorporating the first application component into the third stack or the third stack portion;
retaining the first application component in the first stack or the first stack portion; and
updating a deployment of the third stack or the third stack portion.

### Claim 19 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the deployment of the second stack or the second stack portion is from a common server as the deployment of the first stack or the first stack portion.

### Claim 20 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the updating the deployment of the second stack or the second stack portion comprises updating a map of dependencies among the first application component, a dependent application component, and a backend component.
