System Boundary Worksheet
Define ownership, authority, interfaces, invariants, exclusions, and evidence before changing a game system.
Resource path 3 of 5
Game Architecture and State Management Tools
A Martinez AI Studios education product
11 free fillable tools
Free architecture worksheets for ownership, authority, persistence, migration, and reversible technical decisions.
Focused production path
Use evidence at every decision boundary
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.
State Ownership and Mutation Map
Separate accessibility, legitimate readership, write authority, persistence, and restoration for one state value.
Behavioral Contract and Test Card
Turn a player-facing promise into independently testable behavior, boundaries, failure conditions, and evidence.
Bounded AI Change Brief
Define a safe implementation boundary before an AI coding partner changes a game project.
AI Change Acceptance and Rejection Checklist
Review AI output against its brief, repository evidence, ownership boundaries, regressions, and recovery readiness.
Git Checkpoint and Restoration Checklist
Create a recoverable baseline, preserve failure evidence, and verify restoration without prescribing destructive commands.
Reproduction and Debugging Evidence Record
Separate reproducible observations, sourced expectations, hypotheses, mechanism evidence, fixes, and uncertainty.
Architecture Decision Record
Record a bounded technical decision, alternatives, evidence, risks, reversibility, consequences, and revisit triggers.
Compatibility and Migration Matrix
Test operation-specific compatibility across builds, schemas, platforms, routes, and unsupported inputs.
QA and Release Readiness Gate
Evaluate a specific candidate with traceable evidence before making a ship, hold, or conditional decision.
Milestone Evidence Packet
Package scope, candidate identity, decisions, validation, risks, accessibility, recovery, and review requests for one milestone.
A practical sequence
Define, record, verify, decide
- Define the player or product promise and the exact candidate.
- Record boundaries, owners, invariants, and unsupported assumptions.
- Run the checks and attach evidence that identifies its build or version.
- Make a human decision with an owner, recovery path, and revisit trigger.