Mechanic prototype
Explore one interaction with deliberately limited content and presentation.
Artifact: Playable experiment and observation notes
Acceptance: The agreed test question can be evaluated in the build.
Turn a game idea into a defined question, a bounded playable scope and a useful next decision.
Founders and producers who need to test a mechanic, an implementation risk or a representative slice before committing to wider production.
Scope and acceptance are agreed for your assignment.
Explore one interaction with deliberately limited content and presentation.
Artifact: Playable experiment and observation notes
Acceptance: The agreed test question can be evaluated in the build.
Investigate a dependency, integration or performance uncertainty.
Artifact: Technical notes and a reproducible example
Acceptance: The findings describe what worked, what failed and what remains unknown.
Discuss a representative experience with explicit fidelity and production boundaries.
Artifact: Review build, scope record and reuse assessment
Acceptance: The slice meets the agreed quality, behavior and review criteria.
Share the player action, intended audience, target device, decision deadline, reference material and test participants or reviewers. Agree asset rights and what is deliberately excluded.
Define the question → choose fidelity → build a narrow loop → observe tests → record findings → decide to iterate, stop or expand.
Separate reusable systems from temporary prototype code. Document the parts that need redesign before production instead of assuming every prototype is a foundation.
A prototype does not validate market demand, retention or commercial success without a suitable real-world study. Art polish and production readiness are separate decisions.
Yes. Discuss the task, required inputs, acceptance criteria and the decision it should support.
Ask to review an actual build, source walkthrough or sample artifact relevant to your task. Proposed R&D is not presented as completed work.