Project planning / Marble racing
A planning brief for a annual licence · platform planning · sandbox validation.
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 game launch integration work should be evaluated during sandbox validation before the scope of the annual licence is accepted.
Run the integration tests in the isolated test environment. Public demo credits and test-wallet credits are separate systems.
Playable conceptMarble racing · Virtual-credit demo
Integration priority
Define who requests the launch, how the player reaches the game and which exact hostnames may embed it. API secrets stay on the operator server.
Test valid and expired launches, suspended licences, unauthorised games and unapproved subdomains.
Commercial scope
Define a recurring annual access period and what happens at renewal or expiry. Separate the software right from hosting and operational services.
Set the agreed end date and test access after it passes.
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 / Request a launch for an allowed game | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 02 / Attempt a launch after licence expiry | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 03 / Check a hostname outside the agreement | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 04 / Confirm credential revocation blocks new requests | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 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 sandbox validation. |
| 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 sandbox validation. |
| 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 sandbox validation. |
For this Aurora Rally proposal, connect each agreed right to an identifiable deliverable. Keep game launch 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-0283. Requirements must be confirmed against your actual platform and agreement.