Project planning / Coin pusher
A planning brief for a exclusive project · platform planning · discovery.
An underwater treasury gives the familiar coin-pusher mechanic an atmospheric ocean world and a fresh visual identity.
Coral Treasury combines coin movement and pushing with a coin pusher concept. For platform planning, the licence operations work should be evaluated during discovery before the scope of the exclusive project is accepted.
Produce a written requirements list and identify missing information before quoting implementation work.
Playable conceptCoin pusher · Virtual-credit demo
Integration priority
Translate the commercial agreement into a specific catalogue, approved hostnames, expiry rules and support responsibilities.
Check activation, expiration, suspension and key rotation using test accounts before handing access to the customer.
Commercial scope
Define the exact scope of exclusivity: game, artwork, brand, territory or channel. Exclusivity has value only when its boundaries are explicit.
Confirm ownership of third-party assets and define what may be reused.
Channel requirements
Start with the operator’s actual browser, wallet and player journey requirements. This brief is a planning scenario, not a claim of compatibility with an unnamed casino.
Game-specific decision
Define how simulated coin movement relates to any future monetary result. Do not derive real payouts from an untrusted browser simulation.
| Check | Evidence to collect |
|---|---|
| 01 / Confirm the permitted game identifiers | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 02 / Compare approved hostnames with the agreement | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 03 / Revoke an unused integration credential | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 04 / Test account separation and access after suspension | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 05 / Observe overlapping coin motion | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 06 / Check the push action and visual response | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 07 / Review the end-of-round state | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
For this Coral Treasury proposal, connect each agreed right to an identifiable deliverable. Keep licence operations changes explicit in the statement of work.
The current game is a playable concept. Test wallet behaviour is available separately in the developer sandbox. Real-money wagering is disabled in that sandbox.
A live build requires server-authoritative gameplay, validated payout maths, partner-specific wallet integration and applicable testing. This brief is a planning aid, not evidence of certification or an existing platform connector.
Adjust the environments and test cases for this Coral Treasury evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0141. Requirements must be confirmed against your actual platform and agreement.