A processing device executes a multi-threaded rule engine having multiple threads. A first thread is associated with user interactions. A second thread is associated with timing events. A third thread is associated with asynchronous execution of the rule engine. A rule engine core is accessible to the second and third threads. The processing device receives user input and generates a first command to perform a first action in view of the user input while executing the first thread. The processing device stores the first command in a queue where the first command is one of multiple commands stored in the queue. The processing device retrieves the multiple commands from the queue and processes the multiple commands using the rule engine core while executing the third thread. The rule engine core is inaccessible to the second thread while in use by the third thread.
Please help me write a proper abstract based on the patent claims. CLAIM: 1. A method comprising: executing, by a processing device, a multi-threaded rule engine comprising a first thread associated with user interactions, a second thread associated with timing events, a third thread associated with asynchronous execution of the rule engine, and a rule engine core accessible to at least one of the second thread or the third thread; receiving user input by the processing device while executing the first thread; generating, by the processing device while executing the first thread, a first command to perform a first action in view of the user input; storing the first command in a queue, wherein the first command is one of a plurality of commands stored in the queue; retrieving, by the processing device while executing the third thread, the plurality of commands from the queue; and processing, by the processing device while executing the third thread, the plurality of commands using the rule engine core, wherein the rule engine core is inaccessible to the second thread while in use by the third thread. 2. The method of claim 1, further comprising: placing a state machine of the multi-threaded rule engine into a reactive state, wherein the reactive state causes all commands in the queue to be processed asynchronously as they are added to the queue; adding, by at least one of the first thread or the second thread, a second command to perform a second action to the queue; and responsive to the second command being added to the queue, retrieving the second command from the queue and processing the second command by the processing device while executing the third thread. 3. The method of claim 2, further comprising: receiving a first instruction to halt the reactive state; stopping the third thread from accessing the rule engine core; placing the state machine into an inactive state; receiving a second instruction to enter a passive state; and placing the state machine of the multi-threaded rule engine into the passive state. 4. The method of claim 3, further comprising: generating, by the processing device while executing the first thread, a third command to perform a third action; storing the third command in the queue, wherein the third command is one of an additional plurality of commands stored in the queue; retrieving the additional plurality of commands from the queue by the processing device while executing the third thread; and processing, by the processing device while executing the third thread, the additional plurality of commands using the rule engine core, wherein the rule engine core is inaccessible to the second thread while in use by the third thread. 5. The method of claim 3, further comprising: in response to determining that the rule engine core is in an inactive state, generating, by the processing device while executing the second thread, a third command to perform a third action after a time limit; storing the third command in the queue; retrieving the third command from the queue by the processing device while executing the second thread; and processing, by the processing device while executing the second thread, the third command using the rule engine core, wherein the rule engine core is inaccessible to the third thread while in use by the second thread, wherein in response to processing the third command, the second thread enters into a rest state. 6. The method of claim 5, wherein the third action is associated with the time limit, the method further comprising: starting a timer by the processing device while executing the second thread; determining that the time limit has been reached by the timer; and storing, by the processing device while executing the second thread, a fourth command to perform a fourth action in the queue. 7. The method of claim 1, further comprising: locking the rule engine core while the processing device executing the third thread retrieves the plurality of commands from the queue, wherein the rule engine core is unlocked unless a thread is retrieving commands from the queue. 8. A system comprising a memory; and a processing device, operatively coupled to the memory, to: execute a multi-threaded rule engine comprising a first thread associated with user interactions, a second thread associated with timing events, a third thread associated with asynchronous execution of the rule engine, and a rule engine core accessible to at least one of the second thread or the third thread; receive user input while executing the first thread; generate, while executing the first thread, a first command to perform a first action in view of the user input; store the first command in a queue, wherein the first command is one of a plurality of commands stored in the queue; retrieve, while executing the third thread, the plurality of commands from the queue; and process, while executing the third thread, the plurality of commands using the rule engine core, wherein the rule engine core is inaccessible to the second thread while in use by the third thread. 9. The system of claim 8, wherein the processing device is further to: place a state machine of the multi-threaded rule engine into a reactive state, wherein the reactive state causes all commands in the queue to be processed asynchronously as they are added to the queue; add, by at least one of the first thread or the second thread, a second command to perform a second action to the queue; and responsive to the second command being added to the queue, retrieve the second command from the queue and process the second command by while executing the third thread. 10. The system of claim 9, wherein the processing device is further to: receive a first instruction to halt the reactive state; stop the third thread from accessing the rule engine core; place the state machine into an inactive state; receive a second instruction to enter a passive state; and place the state machine of the multi-threaded rule engine into the passive state. 11. The system of claim 10, wherein the processing device is further to: generate, while executing the first thread, a third command to perform a third action; store the third command in the queue, wherein the third command is one of an additional plurality of commands stored in the queue; retrieve the additional plurality of commands from the queue while executing the third thread; and process, while executing the third thread, the additional plurality of commands using the rule engine core, wherein the rule engine core is inaccessible to the second thread while in use by the third thread. 12. The system of claim 10, wherein the processing device is further to: in response to determining that the rule engine core is in an inactive state, generate, while executing the second thread, a third command to perform a third action after a time limit; store the third command in the queue; retrieve the third command from the queue while executing the second thread; and process, while executing the second thread, the third command using the rule engine core, wherein the rule engine core is inaccessible to the third thread while in use by the second thread, wherein in response to processing the third command, the second thread enters into a rest state. 13. The system of claim 12, wherein the processing device is further to: start a timer while executing the second thread; determine that the time limit has been reached by the timer, wherein the third action is associated with the time limit; and store, while executing the second thread, a fourth command to perform a fourth action in the queue. 14. The system of claim 8, the processing device is further to: lock the rule engine core while the plurality of commands are retrieved from the queue, wherein the rule engine core is unlocked unless a thread retrieves commands from the queue. 15. A non-transitory computer readable storage medium comprising instructions that, when executed by a processing device, cause the processing device to: execute, by the processing device, a multi-threaded rule engine comprising a first thread associated with user interactions, a second thread associated with timing events, a third thread associated with asynchronous execution of the rule engine, and a rule engine core accessible to at least one of the second thread or the third thread; receive user input by the processing device while executing the first thread; generate, by the processing device while executing the first thread, a first command to perform a first action in view of the user input; store the first command in a queue, wherein the first command is one of a plurality of commands stored in the queue; retrieve, by the processing device while executing the third thread, the plurality of commands from the queue; and process, by the processing device while executing the third thread, the plurality of commands using the rule engine core, wherein the rule engine core is inaccessible to the second thread while in use by the third thread. 16. The non-transitory computer readable storage medium of claim 15, including further instructions that, when executed by the processing device, cause the processing device to: place a state machine of the multi-threaded rule engine into a reactive state, wherein the reactive state causes all commands in the queue to be processed asynchronously as they are added to the queue; add, by at least one of the first thread or the second thread, a second command to perform a second action to the queue; and responsive to the second command being added to the queue, retrieve the second command from the queue and process the second command while executing the third thread. 17. The non-transitory computer readable storage medium of claim 16, including further instructions that, when executed by the processing device, cause the processing device to: receive a first instruction to halt the reactive state; stop the third thread from accessing the rule engine core; place the state machine into an inactive state; receive a second instruction to enter a passive state; and place the state machine of the multi-threaded rule engine into the passive state. 18. The non-transitory computer readable storage medium of claim 17, including further instructions that, when executed by the processing device, cause the processing device to: generate, while executing the first thread, a third command to perform a third action; store the third command in the queue, wherein the third command is one of an additional plurality of commands stored in the queue; retrieve the additional plurality of commands from the queue while executing the third thread; and process, while executing the third thread, the additional plurality of commands using the rule engine core, wherein the rule engine core is inaccessible to the second thread while in use by the third thread. 19. The non-transitory computer readable storage medium of claim 17, including further instructions that, when executed by the processing device, cause the processing device to: in response to determining that the rule engine core is in an inactive state, generate, while executing the second thread, a third command to perform a third action after a time limit; store the third command in the queue; retrieve the third command from the queue while executing the second thread; and process, while executing the second thread, the third command using the rule engine core, wherein the rule engine core is inaccessible to the third thread while in use by the second thread, wherein in response to processing the third command, the second thread enters into a rest state. 20. The non-transitory computer readable storage medium of claim 19, including further instructions that, when executed by the processing device, cause the processing device to: start a timer by the processing device while executing the second thread; determine that the time limit has been reached by the timer, wherein the third action is associated with the time limit; and store, while executing the second thread, a fourth command to perform a fourth action in the queue.