Project planning / Marble racing

Aurora Rally
Brand customisation

A planning brief for a exclusive project · 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 brand customisation work should be evaluated during commercial scoping before the scope of the exclusive project 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

Brand customisation

Document the brand assets, interface language, animation style and sound requirements before asking for a reskin.

Review visual assets at real display sizes and check that text and controls remain readable during play.

Commercial scope

Exclusive project

Define the exact scope of exclusivity: game, artwork, brand, territory or channel. Exclusivity has value only when its boundaries are explicit.

Confirm ownership of third-party assets and define what may be reused.

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 / Record font and artwork usage rightsRecord the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
02 / Review long labels and localisation expansionRecord the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
03 / Check contrast and control visibilityRecord the Aurora Rally build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
04 / Agree sign-off on the first playable buildRecord 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

  • Scope of exclusivity
  • Asset ownership
  • Reuse restrictions

For this Aurora Rally proposal, connect each agreed right to an identifiable deliverable. Keep brand customisation 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-4193. Requirements must be confirmed against your actual platform and agreement.