Puzzle design research
What We Refuse to Claim About Our Own Games
It would be easy to describe every game as popular, brain-boosting, and the best in its category. None of those statements would be backed by anything this project has measured. The repository's evidence contract treats claim, evidence, and review as separate steps, and that separation has a visible cost: there are things these guides simply do not say. Naming them is more useful than implying them.
What this guide helps you decide
A game publisher can claim anything about its own games. What does BeanNest decline to claim, and why?
This research states the claim boundary applied to BeanNest game documentation. It is a description of policy and practice in this repository, not a statement about other publishers.
Try it on the anchor product: BeanNest Games /.
No popularity or ranking claims
A game page can state its rules, modes, controls, and published behavior from repository evidence. It does not call a game the most played, the best, or a favourite because this documentation does not offer traffic or ranking evidence for those claims.
Difficulty names are not player-outcome guarantees
A product may expose named difficulty presets, and the existence of those presets is a documented fact. The guides do not convert that label into a claim that a player will find the puzzle easy or hard unless the repository has measured player outcomes that support the statement.
No cognitive or medical benefit claims
The evidence contract excludes brain-training, memory-improvement, therapeutic, and medical outcomes. The documentation can explain the decisions a puzzle asks the player to make without turning those mechanics into an unmeasured health or learning result.
No unmeasured performance promises
Frame rate, battery use, input latency, and load time depend on hardware and browser conditions. Where the repository has only mechanism or measurement-limit evidence, the guides describe that boundary instead of promising a device-specific performance result.
Competitor comparisons require competitor evidence
A comparison between BeanNest games can cite the rules published by those games. A claim that BeanNest is faster, better, harder, or more capable than a named external product would require a separate evaluation of that product, so this corpus does not make that comparison.
How the boundary is visible in the corpus
Research guides name their evidence artifacts, state a methodology, and list claims intentionally excluded from the page. That structure makes the claim boundary inspectable: a reader can see both what the source supports and what the page deliberately declines to infer.
First-party evidence and provenance
How we checked this
We reviewed the repository's evidence contract for its stated claim exclusions and confirmed that each exclusion is reflected in the published game documentation and in the research guides in this cluster.
- Method
- We reviewed this repository's evidence contract and the published game metadata, then traced the shipping behaviour to confirm the mechanism described here. We deliberately did not read or publish a hidden solution state.
- Environment
- Repository source review of the current main branch. No live traffic, account data, or player-identifying information was read.
- Captured
- Reviewed by
- BeanNest Studio
Repository evidence artifacts:
docs/gameplay-reconstruction/EVIDENCE-CONTRACT.mddocs/platform/MODULE-OPERATING-MODEL.md