Project planning / Marble racing
A planning brief for a exclusive project · platform planning · commercial scoping.
Six marbles race over three laps in a luminous arena. Pick a contender and watch the race unfold.
Aurora Rally combines race progress and contender selection with a marble racing concept. For platform planning, the wallet integration work should be evaluated during commercial scoping before the scope of the exclusive project is accepted.
Turn the evaluation into deliverables, ownership terms, acceptance evidence and a responsibility matrix.
Playable conceptMarble racing · Virtual-credit demo
Integration priority
Map player identifiers, currency units, transaction identifiers and response codes before connecting a casino wallet.
Run balance, debit, credit, refund, insufficient-funds and retry cases. Keep every test account separate from production.
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
Specify when contender selection locks and how the authoritative result would be represented. Keep the race animation consistent with the approved result model.
| Check | Evidence to collect |
|---|---|
| 01 / Compare balances before and after each transaction | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 02 / Retry a transaction with the same identifier | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 03 / Reject a reused identifier carrying a different amount | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 04 / Confirm that a refund cannot exceed or repeat its original debit | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 05 / Select each of the six contenders | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 06 / Review lap progression | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 07 / Check the winner presentation | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
For this Aurora Rally proposal, connect each agreed right to an identifiable deliverable. Keep wallet integration 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 Aurora Rally evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0393. Requirements must be confirmed against your actual platform and agreement.