Matchmaking. Moderation. In-game economy. Refunds. Bans. Live service games run on decisions made by AI systems operating at scale. When a player disputes a ban, when a regulator asks how your economy works, when a publisher audits your refund logic, you need more than a server log.
Every live service game runs on AI and automated systems that make decisions affecting real players and real money. None of those systems produce a record that holds up when someone asks a hard question.
Server logs tell you what happened. They do not tell you who authorized it, under what policy, with what authority. That gap is manageable when the stakes are low. In live service gaming, the stakes are never low.
Loot box regulators want to know how drop rates are decided. Payment processors want to know who approved a refund. A banned player's attorney wants to know whether a human reviewed the decision. Every one of these questions requires a record you probably do not have.
Your matchmaking engine, your moderation queue, your refund rules, your fraud system. All of them call the same promote() endpoint. All of them produce the same sealed record. No schema changes. No new infrastructure.
When a regulator, a platform, or a player's attorney asks a hard question about a specific decision, you open the artifact. The answer is there. Signed. Verifiable. Permanent.
At the end of the evaluation period you receive Artifact 5, a KMS asymmetric-signed bundle containing every decision recorded during the window. The private signing key is non-exportable and remains inside Google Cloud KMS. Independently verifiable by anyone with the public key.
Start with moderation, refunds, or your economy decisions. A 30-minute call to scope it. Thirty days later you have a sealed artifact you can hand to anyone who asks. $15K to $60K, evaluation only.