I suppose this will vary from jurisdiction to jurisdiction, but for the most part, the idea of assigning a patent to a machine system seem precluded by the more general inability of machine systems to have legal rights at all other than the right of property to not be defaced or destroyed by anyone other than the property owner. Rights to ownership and control in general are typically limited to humans and collective entities such as governments and private corporations created to disaggregate the interests of communities of humans from the specific individuals making up that community at one particular time.

There have been some exceptions, such as Leona Helmsley bequeathing part of her estate to her dog, but just as with infants or mentally unfit humans who may possess rights of ownership but not understand them well enough to make appropriate decisions regarding disposition, that money was put into a trust.

Putting aside the philosophical and legal theory questions regarding what kind of entities can or should have rights and the ability to own property, there are more practical questions that would need to be answered. If you really wanted to assign a patent to an automated system that generated an idea, how would you do it? What is the boundary of this system separating it from its environment? We have a fairly clear answer to this when the system in question is a biological organism. But a software system? Is it the process ID of the first process spawned from the executable file you used to instantiate the system before querying it? Presumably that was killed at some point well before you ever filed the application. The server or servers it ran on? Those also may be ephemeral. Some content-addressing tagging system identifying a released version of the software? Well then the specific instances you ran to generate the idea shares ownership with a bunch of other instances that didn't do jack. The source code? Now it's shared with even more potential instances that don't exist yet and may never exist.

Do you snapshot the entire state machine consisting of register and memory contents across all hardware servers as they happened to exist at the moment of creation? Then what? As long as it is possible to physically realize this system by restoring the snapshot to currently powered on hardware with a sufficient similar processor architecture and operating system the system lives forever? But if that operating system or architecture disappears then it dies and the rights expire? Does the snapshot itself retain some kind of legal rights even if it is never physically realized and only exists as a file? Seemingly no, as even a potentially intelligent system that is in a state of hibernation has no interests and can't make decisions.

So now we have a further question. Even if we can somehow define an acceptable boundary of what even constitutes the entity that has rights, we have to define at what point it is still considered to be alive. It's not clear for even a single process on a single server that is getting pre-empted and potentially paged out anywhere from a few times a day to billions of times per second, but much less clear for a distributed system that relies upon replaying log-structured files shared across an unreliable network. Humans get death certificates when a physician determines the heart has been stopped long enough that it is unlikely to ever come back. But for a distributed system that relies on log consistency, it can always potentially come back as long as some combo of hardware and software exists that can interpret the state transition commands to restore its state and someone with the power to plug servers together, turn them on, and hit enter makes the decision to do it. The lifetime of such a system is arbitrary.