About Agnostic Game Composer
Suppose two games both have an inventory. One is a quiet puzzle with six objects. The other is an online role-playing game with equipment, trading, crafting, ownership rules, and years of saved progress. They share an idea, but they should not be forced into the same implementation.
AGC is intended to help creators separate the parts that are genuinely reusable from the parts that make each game distinct.
What it is
AGC is a proposed planning layer between a game idea and the many systems needed to realize it. It gives each game part a stable name, version, responsibility, set of connections, and evidence trail. It can then produce a repeatable plan showing exactly which described parts were selected.
Some unavoidable terms, in plain language:
- A module is one bounded game part, such as saving, inventory, dialogue, or turn order.
- A composition is the chosen set of parts and the way they are expected to work together.
- An exact lock is a frozen review list of the precise versions considered. It prevents “use the latest one” from quietly changing the plan.
- An adapter is a translator between a general idea and one engine, platform, service, or game.
Why it matters
Reuse can save time and concentrate testing. A good correction to a shared input or save component could benefit several games. The danger is that the same defect could also reach all of them. AGC is being shaped around explicit versions, independent game acceptance, staged upgrades, and rollback so reuse does not become a portfolio-wide surprise.
Reuse also does not have to mean shared code. Games can share a vocabulary, interface, checklist, test pattern, or diagnostic explanation while retaining completely different implementations.
What someone could eventually do with it
A designer might describe a feature in familiar terms and see which responsibilities are missing. A developer might compare two providers for the same need, identify where an engine-specific translator is required, or inspect which games could be affected by a new version. A team might keep a known-good composition pinned while testing an upgrade in one game first.
AGC may advise. It must not silently install, enable, or update anything.
AGC and its Workbench are tools for making and maintaining games, not parts that players must run. A released game must work without either one. It may deliberately use separately published ADK or Living World services, but only through their public, versioned game-facing contracts.
Where it honestly stands today
The current project is a tested advisory foundation. It can validate descriptions, resolve small made-up dependency examples, refuse several unsafe combinations, create exact review evidence, and compare changes. It now has a runnable synthetic creator-journey rehearsal that puts a short readable plan before the detailed evidence. That rehearsal tests AGC's own mechanics; it is not evidence that an unaided creator or a real game can use the result successfully.
Current maturity is deliberately split rather than summarized as one reassuring level: structural validation passes for the project-owned fixtures; bounded consumers have found parts of the advice applicable; some synthetic implementation evidence exists; no real provider or engine adapter is selected for an admitted game; human and device acceptance are absent; and no game has granted L4 admission. It has not proved player experience, production performance, security, accessibility, recovery, platform approval, or release readiness. No public page, generated plan, or successful synthetic test changes that boundary.
How ownership stays clear
AGC owns its composition language and advice. A reusable-system owner keeps ownership of that system. A game keeps its engine integration, data, rules, tests, installation, and release decisions. Shared infrastructure may help move evidence or build this Website, but help is not an authority transfer.
Human and clearly identified AI development notes may explain decisions and mistakes. They are commentary, not product releases or compatibility receipts.