Pre-execution governance control layer for managing artificial intelligence system actions

1 . A method performed by at least one computer processor executing computer program instructions stored on at least one non-transitory computer-readable medium, the method comprising:

(A) intercepting, by a control layer positioned between an artificial intelligence system and an execution system, an execution request generated from an output of the artificial intelligence system, and storing the execution request in a holding state in which the execution request is inaccessible to the execution system, wherein the execution system is configured with a default-deny execution posture that rejects execution requests lacking a valid authorization artifact;

(B) classifying, by the control layer, the execution request based on governance-relevant attributes to identify a governance handling category for the execution request;

(C) assigning, by the control layer, a discrete execution state to the execution request by applying governance logic to the governance handling category, wherein the discrete execution state is one of execution permitted, execution denied, or execution deferred pending oversight;

(D) generating, by the control layer, an immutable governance record associated with the execution request prior to any authorization of the execution request, wherein the authorization artifact is not generated unless the immutable governance record exists;

(E) performing, by the control layer, one of:

(E)(1) in response to the discrete execution state being execution permitted, generating the authorization artifact, the authorization artifact being a machine-verifiable data object containing cryptographic or structural verification data that is verified by the execution system before performing any action; or

(E)(2) in response to the discrete execution state being execution denied, withholding the authorization artifact;

(F) in response to the discrete execution state being execution deferred pending oversight, routing, by the control layer, the execution request to an oversight system, wherein the execution request remains in the holding state during oversight, and wherein the oversight system returns a response comprising one of approve execution, deny execution, or request modification;

(G) in response to the response being request modification, attaching, by the control layer, machine-enforceable modification constraints to the execution request; and

(H) enforcing the machine-enforceable modification constraints at a user interface level by blocking submission of a resubmitted execution request that does not satisfy the machine-enforceable modification constraints, and enforcing the machine-enforceable modification constraints at the control layer by rejecting a resubmitted execution request that does not satisfy the machine-enforceable modification constraints.

2 . The method of claim 1 , wherein in response to receiving a resubmitted execution request that satisfies the machine-enforceable modification constraints, (A), (B), (C), (D), and (E) are performed on the resubmitted execution request.

3 . The method of claim 1 , wherein the machine-enforceable modification constraints comprise two or more of: prohibited elements, required removals, mandatory scope restrictions, and required disclosures.

4 . The method of claim 1 , wherein the governance-relevant attributes comprise impact domain, affected parties, reversibility, and potential risk exposure.

5 . The method of claim 1 , wherein a same governance handling category produces a same discrete execution state under same predefined governance rules.

6 . The method of claim 1 , wherein the control layer validates the response from the oversight system before processing the response, and discards the response and maintains the execution request in the holding state if the validation fails.

7 . The method of claim 1 , wherein the oversight system cannot directly execute actions and cannot issue authorization artifacts, and can only return the response to the control layer.

8 . The method of claim 1 , wherein the immutable governance record is stored in a governance store that is append-only, separate from execution system logs, and not writable by the artificial intelligence system or the execution system.

9 . The method of claim 1 , wherein the authorization artifact comprises validity constraints including at least one of time limits or usage limits.

10 . The method of claim 1 , wherein the artificial intelligence system comprises a workplace safety system that generates the output as a proposed task assignment for a worker, and wherein the governance-relevant attributes comprise training qualification status of the worker relative to requirements of the proposed task assignment.

11 . The method of claim 1 , wherein the artificial intelligence system comprises a safety compliance system that generates the output as a proposed safety compliance action for a worksite, and wherein the governance-relevant attributes comprise at least one of jurisdictional regulatory requirements associated with a geolocation of the worksite or worker qualification status relative to task-specific safety requirements.

12 . A system comprising at least one non-transitory computer-readable medium having computer program instructions stored thereon, the computer program instructions being executable by at least one computer processor to perform a method, the method comprising:

(A) intercepting, by a control layer positioned between an artificial intelligence system and an execution system, an execution request generated from an output of the artificial intelligence system, and storing the execution request in a holding state in which the execution request is inaccessible to the execution system, wherein the execution system is configured with a default-deny execution posture that rejects execution requests lacking a valid authorization artifact;

(B) classifying, by the control layer, the execution request based on governance-relevant attributes to identify a governance handling category for the execution request;

(C) assigning, by the control layer, a discrete execution state to the execution request by applying governance logic to the governance handling category, wherein the discrete execution state is one of execution permitted, execution denied, or execution deferred pending oversight;

(D) generating, by the control layer, an immutable governance record associated with the execution request prior to any authorization of the execution request, wherein the authorization artifact is not generated unless the immutable governance record exists;

(E) performing, by the control layer, one of:

(E)(1) in response to the discrete execution state being execution permitted, generating the authorization artifact, the authorization artifact being a machine-verifiable data object containing cryptographic or structural verification data that is verified by the execution system before performing any action; or

(E)(2) in response to the discrete execution state being execution denied, withholding the authorization artifact;

(F) in response to the discrete execution state being execution deferred pending oversight, routing, by the control layer, the execution request to an oversight system, wherein the execution request remains in the holding state during oversight, and wherein the oversight system returns a response comprising one of approve execution, deny execution, or request modification;

(G) in response to the response being request modification, attaching, by the control layer, machine-enforceable modification constraints to the execution request; and

(H) enforcing the machine-enforceable modification constraints at a user interface level by blocking submission of a resubmitted execution request that does not satisfy the machine-enforceable modification constraints, and enforcing the machine-enforceable modification constraints at the control layer by rejecting a resubmitted execution request that does not satisfy the machine-enforceable modification constraints.

13 . The system of claim 12 , wherein in response to receiving a resubmitted execution request that satisfies the machine-enforceable modification constraints, (A), (B), (C), (D), and (E) are performed on the resubmitted execution request.

14 . The system of claim 12 , wherein the machine-enforceable modification constraints comprise two or more of: prohibited elements, required removals, mandatory scope restrictions, and required disclosures.

15 . The system of claim 12 , wherein the governance-relevant attributes comprise impact domain, affected parties, reversibility, and potential risk exposure.

16 . The system of claim 12 , wherein a same governance handling category produces a same discrete execution state under same predefined governance rules.

17 . The system of claim 12 , wherein the control layer validates the response from the oversight system before processing the response, and discards the response and maintains the execution request in the holding state if the validation fails.

18 . The system of claim 12 , wherein the oversight system cannot directly execute actions and cannot issue authorization artifacts, and can only return the response to the control layer.

19 . The system of claim 12 , wherein the immutable governance record is stored in a governance store that is append-only, separate from execution system logs, and not writable by the artificial intelligence system or the execution system.

20 . The system of claim 12 , wherein the authorization artifact comprises validity constraints including at least one of time limits or usage limits.

21 . The system of claim 12 , wherein the artificial intelligence system comprises a workplace safety system that generates the output as a proposed task assignment for a worker, and wherein the governance-relevant attributes comprise training qualification status of the worker relative to requirements of the proposed task assignment.

22 . The system of claim 12 , wherein the artificial intelligence system comprises a safety compliance system that generates the output as a proposed safety compliance action for a worksite, and wherein the governance-relevant attributes comprise at least one of jurisdictional regulatory requirements associated with a geolocation of the worksite or worker qualification status relative to task-specific safety requirements.