Project planning / Marble racing

Aurora Rally
Licence operations

A planning brief for a one-time licence · multi-brand operation · commercial scoping.

Your project scenario

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 commercial scoping before the scope of the one-time licence is accepted.

Turn the evaluation into deliverables, ownership terms, acceptance evidence and a responsibility matrix.

Aurora Rally concept artworkPlayable concept

Explore Aurora Rally ↗

Marble racing · Virtual-credit demo

Integration priority

Licence operations

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

One-time licence

Define a right to use the agreed build, with the brands, domains and delivery scope written down. A one-time payment does not automatically transfer ownership.

Specify whether maintenance is included or separately renewed.

Channel requirements

Multi-brand operation

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

Race progress and contender selection

Specify when contender selection locks and how the authoritative result would be represented. Keep the race animation consistent with the approved result model.

Acceptance checklist

CheckEvidence to collect
01 / Confirm the permitted game identifiersRecord the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
02 / Compare approved hostnames with the agreementRecord the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
03 / Revoke an unused integration credentialRecord the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
04 / Test account separation and access after suspensionRecord the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
05 / Select each of the six contendersRecord the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
06 / Review lap progressionRecord the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
07 / Check the winner presentationRecord the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.

Agreement review

  • Permitted usage
  • Delivered version
  • Maintenance responsibility

For this Aurora Rally proposal, connect each agreed right to an identifiable deliverable. Keep licence operations changes explicit in the statement of work.

Scope boundary

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.

Plan the test workload

Adjust the environments and test cases for this Aurora Rally evaluation. Start with the checklist above, then add partner-specific cases.

42 planned test executions.

Planning reference GQX-4228. Requirements must be confirmed against your actual platform and agreement.