GAIA Adventure Engine

Inspiration

GAIA Adventure Engine was born from a simple idea: turning personalized physical products and real-world spaces into interactive experiences.

I run a small personalization business, and I wanted to go beyond printing a QR code on a product. I wanted that QR code to become the entrance to a story, a mystery, a challenge or an adventure.

The challenge was that creating a different interactive experience for every customer manually is slow and difficult to scale.

What it does

GAIA Adventure Engine is a system for creating and running interactive real-world adventures connected through QR codes.

An administrator can describe an adventure in natural language. Gemini transforms that idea into a structured adventure plan containing scenes, challenges, clues, QR interactions and completion conditions.

GAIA then validates and compiles the generated structure.

Importantly, Gemini does not publish content automatically. The generated proposal is first shown as an unsaved preview. A human reviews it, accepts it, converts it into an editable draft and decides when it is ready to be published.

Players then experience the published adventure through QR codes connected to physical objects or real-world locations.

How Gemini is used

Gemini acts as the creative planning layer of the system.

The workflow is:

Administrator → GAIA Creative Director → Gemini API → structured JSON plan → GAIA validation and compilation → human review → editable draft → manual publication → playable QR adventure.

This makes AI part of a real operational workflow while keeping human control over the final experience.

How I built it

The engine is a web-based architecture using JavaScript, Netlify Functions and Supabase.

Gemini is integrated server-side through the Gemini API using structured outputs. GAIA applies schema validation, semantic validation and requested-quantity checks before a generated plan can continue through the system.

The platform also manages adventure sessions, QR progression, playable content, human editing and publication.

Challenges

One of the main challenges was allowing AI to be creative without giving it uncontrolled access to the production system.

I solved this by separating generation from publication. Gemini proposes; GAIA validates; a human decides.

Another challenge was designing the engine so the same architecture could support very different experiences instead of building a separate application for every game.

What's next

The goal is to evolve GAIA Adventure Engine into a reusable platform for small businesses, event organizers and creators.

A business could eventually create its own branded interactive experiences while GAIA provides the engine, AI-assisted creation, QR infrastructure and session management underneath.

Built With

• css3
• gemini-api
• html5
• javascript
• netlify
• netlify-functions
• openai
• supabase