Project planning / Premium cinematic slot
A planning brief for a custom build · aggregator review · handover planning.
A cinematic five-reel slot with winning cascades, reactor wilds, vault free spins and original action sounds. Customise your edition in Game Studio.
Solar Vault combines cascades and reactor wilds with a premium cinematic slot concept. For aggregator review, the licence operations work should be evaluated during handover planning before the scope of the custom build is accepted.
Define documentation, account ownership, secret rotation, support contacts and the acceptance record required for handover.
Playable conceptPremium cinematic slot · 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
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
Obtain the partner’s real integration specification first. Catalogue identifiers, launch fields and wallet semantics must be mapped to that specification; no named aggregator connector is implied.
Game-specific decision
Three winning cascades charge the reactor; initial vault keys trigger free spins. Customer presentation settings do not change the mathematical model.
| Check | Evidence to collect |
|---|---|
| 01 / Confirm the permitted game identifiers | Record the Solar Vault build, aggregator review 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 Solar Vault build, aggregator review environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 03 / Revoke an unused integration credential | Record the Solar Vault build, aggregator review 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 Solar Vault build, aggregator review environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 05 / Check autoplay stop and loss limits | Record the Solar Vault build, aggregator review environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 06 / Verify event-synchronised action sounds | Record the Solar Vault build, aggregator review environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 07 / Verify customer edition isolation | Record the Solar Vault build, aggregator review environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
For this Solar Vault 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 Solar Vault evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0750. Requirements must be confirmed against your actual platform and agreement.