Merge Request
A formal proposal to merge changes from one branch into the canonical document, collecting AI and human review before anything lands on the main branch.
A merge request (MR) is the ceremony around merging a proposed change into a canonical document. The proposer opens an MR describing what changed and why. Reviewers — human and AI — read the diff, leave line-anchored comments, and approve or request changes. Nothing merges until the readiness criteria are met.
The model is borrowed from software development (GitHub calls this a “pull request”) but adapted for design documents. In code, a merge request is primarily about catching bugs and enforcing style. In design, it is primarily about catching inconsistencies, surfacing cross-discipline conflicts, and creating a recorded decision.
The paper trail is the point. Six months after a balance change shipped, the merge request tells you: who proposed it, what the diff looked like, what the AI Game Designer and QA Tester found, who approved it, and when it landed on main.
How it works in Gameframe
Gameframe’s merge request model works on any document type — prose specs, structured GDDs, balance spreadsheets. The merge readiness rail shows: reviewer approvals, Specialist Reviews status (no critical findings), and conflict detection. All three must be green before the merge button activates.
Line-anchored comments let reviewers quote the exact sentence or table cell they are commenting on. Findings from the eleven Specialist Reviews personalities appear as first-class reviewers in the MR thread.
Branches and merge requests are available on all Gameframe plans.