Project planning / Marble racing
A planning brief for a annual licence · 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 licence operations work should be evaluated during handover planning before the scope of the annual licence 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
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 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 / Confirm the permitted game identifiers | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 02 / Compare approved hostnames with the agreement | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 03 / Revoke an unused integration credential | Record the Aurora Rally build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 04 / Test account separation and access after suspension | 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 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-0608. Requirements must be confirmed against your actual platform and agreement.