# US 2026/0310432 A1 · Systems and methods for blocking deployment of unsatisfactory files using event detection

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

- Number: US 2026/0310432 A1
- Document ID: US20260310432A1
- Status: Published application
- Kind: A1
- Application number: 19/172,626
- Filed: 2025-04-07
- Published: 2026-10-08
- Earliest claimed: 2025-04-07
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Clayton Mottley; Alexander Misihowsky; Theodore Timothy John; Nicholas Visalli; Madison Behm; Benjamin Lewinter; Kiran Rao
- Web page: https://patentgrep.com/patent/US20260310432A1

## CPC

- G06F 8/60: Software deployment
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A device may monitor an event bus of a development environment, implemented on a user device, while a document is open in the development environment. The device may detect based on monitoring the event bus, a sequence of events indicative of use of assistive content generation to generate candidate content in the document. The device may detect an inclusion of the candidate content in a file in a file repository, and the file may be designated for deployment in a serving system. The device may block, based on detecting the inclusion of the candidate content, the file from deployment in the serving system.

## Claims

### Claim 1

A system for blocking deployment of unsatisfactory files using event detection, the system comprising:
one or more processors; and
one or more memories storing instructions that, when executed by the one or more processors, cause the system to:
monitor an event bus of a development environment, implemented on a user device, while a code document is open in the development environment;
detect, based on monitoring the event bus, a sequence of:
a first event indicative of a presentation, in the code document, of an inline element that contains candidate code, and
a second event indicative of an input into the user device for accepting the candidate code into the code document;
identify, subsequent to the sequence of the first event and the second event, that the code document contains the candidate code,
wherein detection of the sequence of the first event and the second event, and detection that the code document contains the candidate code is used to detect use of assistive coding in the code document;
detect an inclusion of the candidate code in a source code file in a code repository,
wherein the source code file is designated for deployment in a serving system;
determine, based on detecting the inclusion of the candidate code, a proportion of code in the source code file that used assistive coding; and
block, based on the proportion of code in the source code file satisfying a threshold, the source code file from deployment in the serving system.

### Claim 2

A method for blocking deployment of unsatisfactory files using event detection, the method comprising:
monitoring, by a device, an event bus of a development environment, implemented on a user device, while a document is open in the development environment;
detecting, by the device, based on monitoring the event bus, a sequence of events indicative of use of assistive content generation to generate candidate content in the document;
detecting, by the device, an inclusion of the candidate content in a file in a file repository,
wherein the file is designated for deployment in a serving system; and
blocking, by the device and based on detecting the inclusion of the candidate content, the file from deployment in the serving system.

### Claim 3 (depends on 2)

The method of claim 2, wherein detecting the sequence of events comprises:
detecting a first event indicative of a presentation, in the document, of an inline element that contains the candidate content; and
detecting a second event indicative of an input into the user device for accepting the candidate content into the document,
wherein detection of the sequence of the first event and the second event is used to detect use of assistive content generation.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
identifying, subsequent to the sequence of the first event and the second event, that the document contains the candidate content,
wherein detection of the sequence of the first event and the second event, and detection that the document contains the candidate content, is used to detect use of assistive content generation in the document.

### Claim 5 (depends on 2)

The method of claim 2, wherein detecting the sequence of events comprises:
detecting a first event indicative of a presentation, in the document, of an inline element,
wherein the first event is a first native event of the development environment;
normalizing the first native event to a first common event that is independent of any development environment,
wherein the first common event indicates the candidate content being shown;
detecting a second event indicative of an input into the user device,
wherein the second event is a second native event of the development environment;
normalizing the second native event to a second common event that is independent of any development environment,
wherein the second common event indicates acceptance of the candidate content;
and
determining, based on the first common event and the second common event, use of assistive content generation in the document.

### Claim 6 (depends on 2)

The method of claim 2, wherein detecting the sequence of events comprises:
detecting a first event indicative of a first input into the user device relating to an input to an assistive system of the development environment; and
detecting a second event indicative of a second input into the user device for insertion of an output of the assistive system into the document,
wherein detection of the sequence of the first event and the second event is used to detect use of assistive content generation.

### Claim 7 (depends on 2)

The method of claim 2, wherein monitoring the event bus comprises:
monitoring the event bus using an event listener of an extension of the development environment.

### Claim 8 (depends on 7)

The method of claim 7, wherein the candidate content is generated by an additional extension of the development environment.

### Claim 9 (depends on 2)

The method of claim 2, wherein detecting the inclusion of the candidate content in the file in the file repository comprises:
monitoring the file repository for modifications to a plurality of files in the file repository;
detecting, based on monitoring the file repository, a modification to the file; and
detecting, based on detecting the modification to the file, the inclusion of the candidate content in the file.

### Claim 10 (depends on 2)

The method of claim 2, further comprising:
caching the candidate content with an association to a user of the user device.

### Claim 11 (depends on 10)

The method of claim 10, wherein detecting the inclusion of the candidate content in the file in the file repository comprises:
detecting that a modification to the file is made by the user; and
retrieving the candidate content from a cache based on the association to the user.

### Claim 12 (depends on 2)

The method of claim 2, further comprising:
determining, based on detecting the inclusion of the candidate content, a proportion of content in the file that used assistive content generation; and
determining whether the proportion of the content satisfies a threshold,
wherein blocking the file from deployment comprises:
blocking the file from deployment based on the proportion of the content satisfying the threshold.

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
determining the threshold based on an experience level of a user of the user device.

### Claim 14 (depends on 2)

The method of claim 2, wherein blocking the file from deployment in the serving system comprises:
receiving a request to deploy the file to the serving system; and
terminating the request.

### Claim 15 (depends on 2)

The method of claim 2, wherein detecting the inclusion of the candidate content in the file in the file repository comprises:
detecting the inclusion of candidate code in a source code file of a code repository.

### Claim 16 (depends on 15)

The method of claim 15, wherein detecting the inclusion of candidate code in the source code file of the code repository comprises:
detecting a commit to the code repository;
comparing new code of the commit with candidate code snippets that have been detected within a threshold time before detection of the commit; and
determining, based on comparing the new code with the candidate code snippets, that the candidate code is present in the new code.

### Claim 17

A non-transitory, computer-readable medium, comprising instructions that, when executed by one or more processors, cause operations comprising:
monitoring an event bus of a development environment, implemented on a user device, while a document is open in the development environment;
detecting based on monitoring the event bus, a sequence of events indicative of use of assistive content generation in the document to generate candidate content in the document,
wherein at least one event of the sequence of events includes an event indicative of an input into the user device; and
detecting use of assistive content generation in the document based on detecting the sequence of events.

### Claim 18 (depends on 17)

The non-transitory, computer-readable medium of claim 17, wherein the instructions further cause operations comprising:
detecting an inclusion of the candidate content in a file in a file repository,
wherein the file is to be deployed in a serving system; and
blocking the file from deployment in the serving system based on detecting the inclusion of the candidate content.

### Claim 19 (depends on 17)

The non-transitory, computer-readable medium of claim 17, wherein detecting the sequence of events comprises:
detecting a first event indicative of a presentation, in the document, of an inline element that contains the candidate content; and
detecting a second event indicative of an input into the user device for accepting the candidate content into the document,
wherein detection of the sequence of the first event and the second event is used to detect use of assistive content generation.

### Claim 20 (depends on 17)

The non-transitory, computer-readable medium of claim 17, wherein detecting the sequence of events comprises:
detecting a first event indicative of a first input into the user device relating to an input to an assistive system of the development environment; and
detecting a second event indicative of a second input into the user device for insertion of an output of the assistive system into the document,
wherein detection of the sequence of the first event and the second event is used to detect use of assistive content generation.
