System Boundary Worksheet
Define ownership, authority, interfaces, invariants, exclusions, and evidence before changing a game system.
Resource path 5 of 5
A Martinez AI Studios education product
11 free fillable tools
Free templates for directing, reviewing, recovering, validating, and defending AI-assisted game development work.
Focused production path
Choose the smallest tool that matches the current decision. Complete it against one identified project state, then link the evidence rather than replacing uncertainty with confident prose.
Define ownership, authority, interfaces, invariants, exclusions, and evidence before changing a game system.
Turn a player-facing promise into independently testable behavior, boundaries, failure conditions, and evidence.
Define a safe implementation boundary before an AI coding partner changes a game project.
Review AI output against its brief, repository evidence, ownership boundaries, regressions, and recovery readiness.
Create a recoverable baseline, preserve failure evidence, and verify restoration without prescribing destructive commands.
Separate reproducible observations, sourced expectations, hypotheses, mechanism evidence, fixes, and uncertainty.
Record a bounded technical decision, alternatives, evidence, risks, reversibility, consequences, and revisit triggers.
Test operation-specific compatibility across builds, schemas, platforms, routes, and unsupported inputs.
Evaluate a specific candidate with traceable evidence before making a ship, hold, or conditional decision.
Package scope, candidate identity, decisions, validation, risks, accessibility, recovery, and review requests for one milestone.
Connect capstone scope, architecture, checkpoints, AI-change judgment, validation, residual risk, and final defense evidence.
A practical sequence