Three rules and a loop.

Genre without borders

Mechanics, worlds and audiences combined on purpose, not by accident.

A crossing starts as a question: what does a roguelike owe a city-builder? We prototype the answer before we argue about it.

Intelligent systems as collaborators

Design, code and art made with intelligent models in the loop, directed and owned by people.

Models draft, test and critique alongside the team. People set the direction, make the calls and own the result. Both are in the credits.

Shared community and funding

Pooled resources, open process and fair credit for every indie who contributes.

Budgets, process and credits are published for every build, so anyone who contributes can see exactly where their work went.

Cross

Pick a pairing. Write the one-line hook. If it doesn't fit on a sticky note, it's two games.

Prototype

A short sprint, one mechanic, no art. Does the crossing produce a decision a player cares about?

Co-develop

Models in the loop for design docs, code and art drafts. People direct, review and decide.

Playtest

The community gets the build. They break it, we take notes, everyone gets credited.

Ship or shelve

Either way the devlog says what we learned. Shelved builds stay open to the commons.