Project planning / Marble racing
A planning brief for a exclusive project · platform planning · handover planning.
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 technical evaluation work should be evaluated during handover planning before the scope of the exclusive project is accepted.
Define documentation, account ownership, secret rotation, support contacts and the acceptance record required for handover.
Playable conceptMarble racing · Virtual-credit demo
Integration priority
Evaluate the current concept against the requirements of your platform. Separate demonstrated features from changes that still require production work.
Record reproducible steps, expected outcomes and device details for each issue; retest the specific affected behaviour after a fix.
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 / List requirements absent from the concept | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 02 / Check initial loading and asset failures | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 03 / Exercise a complete demo round | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 04 / Record recovery after navigation or refresh | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 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 handover planning. |
| 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 handover planning. |
| 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 handover planning. |
For this Aurora Rally proposal, connect each agreed right to an identifiable deliverable. Keep technical evaluation 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-0593. Requirements must be confirmed against your actual platform and agreement.