Project planning / Marble racing
A planning brief for a monthly licence · multi-brand operation · 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 multi-brand operation, the licence operations work should be evaluated during sandbox validation before the scope of the monthly 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
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 a monthly access agreement with clear game coverage and an agreed notice process. Avoid assuming unlimited brands or domains.
Confirm the current period and the action required when access ends.
Channel requirements
Separate each brand’s approved hostnames, catalogue access and operational contacts. Test that one customer or brand cannot obtain another customer’s credentials or sessions.
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 / Confirm the permitted game identifiers | Record the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 02 / Compare approved hostnames with the agreement | Record the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 03 / Revoke an unused integration credential | Record the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 04 / Test account separation and access after suspension | Record the Aurora Rally build, multi-brand operation 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, multi-brand operation 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, multi-brand operation 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, multi-brand operation 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 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 Aurora Rally evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-4113. Requirements must be confirmed against your actual platform and agreement.