What You Could Compose

AGC is not intended to choose a game's identity. It is intended to help creators assemble the less glamorous structure around their ideas, see the connections, and understand what still needs game-specific work.

A blacksmithing feature

“Let the player forge a sword” sounds like one feature. It may involve an inventory, recipes, tools, skill rules, fuel, time, animation, sound, user-interface feedback, saved progress, and perhaps an economy or quest. AGC could help turn that idea into a visible composition so missing responsibilities are found before they become late surprises.

The game would still decide whether forging is a menu, a timed action, a minigame, a day of world time, or a negotiation with a dragon who has opinions about metallurgy.

A puzzle action

A local sliding puzzle may validate and apply a move in one small function. A competitive online puzzle may need identity, timing, synchronization, disconnect recovery, and anti-cheat boundaries. The same plain idea—“move this piece”—can therefore lead to very different implementations.

AGC's job would be to preserve the meaning and questions without insisting that both games use the same code.

A safe item trade

Buying a sword may require one system to debit money and another to add the item. If the inventory fills up halfway through, the game must refuse the trade, undo the debit, or clearly mark it for recovery. Shared guidance can make those failure paths visible; the game and its services still own the actual transaction and data.

A genre-specific foundation

A tactics game might reuse ideas about turns, targets, and outcomes, then specialize them with grids, cover, visibility, and action points. A rhythm game might reuse action and feedback concepts but specialize them around audio time, timing windows, latency calibration, and streaks. A farming game may connect seasons, crops, inventories, relationships, crafting, and world time.

The reusable layer should remove repeated plumbing without sanding every game into the same shape.

Safer changes across several games

If several games use the same well-tested part, a correction could help all of them. AGC is intended to show which games use which exact version, what changed, what evidence is missing, and where rollback would lead. Each game would still choose whether and when to adopt it.

Where these examples stand today

These are design examples, not downloadable AGC modules. The current bootstrap can reason about small made-up descriptions and produce repeatable advisory evidence. No example on this page has been turned into a general runtime, connected to an engine, or accepted for release by a real game.