Project planning / Rocket crash
A planning brief for a annual licence · multi-brand operation · handover planning.
A rocket climbs towards orbit as its multiplier rises. Choose when to cash out before the flight ends.
Orbital Run combines cash-out timing and flight end with a rocket crash concept. For multi-brand operation, 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 conceptRocket crash · 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
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
A live crash game needs an authoritative cash-out acceptance rule and settlement timing. Network delay must not let the browser decide whether a real bet won.
| Check | Evidence to collect |
|---|---|
| 01 / Confirm the permitted game identifiers | Record the Orbital Run build, multi-brand operation 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 Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 03 / Revoke an unused integration credential | Record the Orbital Run build, multi-brand operation 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 Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 05 / Use manual cash-out during ascent | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 06 / Check the state after flight end | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 07 / Review multiplier readability | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
For this Orbital Run 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 Orbital Run evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-4360. Requirements must be confirmed against your actual platform and agreement.