Project planning / Marble racing
A planning brief for a custom build · mobile web · discovery.
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 mobile web, the game launch integration work should be evaluated during discovery before the scope of the custom build is accepted.
Produce a written requirements list and identify missing information before quoting implementation work.
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
Agree a commissioned production against a specific brief, review milestones and acceptance criteria. Decide which work begins only after the concept is approved.
Map requested changes to the build and record acceptance evidence.
Channel requirements
Prioritise narrow screens, touch controls, interrupted connections and browser navigation. Test portrait and landscape where the design supports them.
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, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 02 / Attempt a launch after licence expiry | Record the Aurora Rally build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 03 / Check a hostname outside the agreement | Record the Aurora Rally build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 04 / Confirm credential revocation blocks new requests | Record the Aurora Rally build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 05 / Select each of the six contenders | Record the Aurora Rally build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 06 / Review lap progression | Record the Aurora Rally build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 07 / Check the winner presentation | Record the Aurora Rally build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
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-0673. Requirements must be confirmed against your actual platform and agreement.