Roadmap & Genius Sync Protocol

This document outlines the living plan for the Genies Unified Game Template and defines the protocol for how AI agents (Genies) interact with, audit, and update game repositories.

Genius Sync Protocol

The Genius sync protocol dictates how the Genius Engine autonomously operates on a codebase. It follows a strict 6-step lifecycle:

1. Orient: The agent reads the hub documents (index, roadmap, fun-stack) to understand the game’s current state and goals.
2. Perspective Audit: The agent analyzes specific domains (e.g., UI, Netcode, Game Design) using targeted perspectives.
3. Hypothesis Generation: The agent formulates improvement hypotheses, scoring them by Impact × Confidence / Effort.
4. Implement: The agent executes the approved or highest-ROI hypothesis, writing code or documentation.
5. Verify: The agent strictly verifies the changes in code (via tests, type-checks, or local e2e) before updating the Knowledge Base.
6. Quartz Sync Comment: The agent leaves a structured sync comment in the relevant Quartz document, summarizing the verified change and updating status enums.

Living Plan

Near-Term

• Materialize the core docs pack structure (Hub, Template, Patterns, Audits).
• Publish template contracts (unified-state, Nakama Genie RPCs, plugin genius block).
• Publish patterns index + Fun Audit / deep-roast report template.
• Deepen template contracts and Hub docs with actionable schemas and full scorecards.
• Establish baseline automated audit playbooks (executable) in ./audits/.

Later

• Wire Genius cron jobs and dedicated skills for continuous evaluation.
• Integrate optional Genie Game Master (GM) hooks directly into the Nakama backend.

Workstream Status