Future capabilities
The platform can provide useful Casino information and Offers through manual editorial work. Automated collection, Casino scoring and community rewards add different kinds of value later. They do not have to arrive together.
The custom parser, editorial preparation, operator publication and scoring are deferred. Gamification is confirmed future direction and is also deferred; its engine and mechanics remain open. No start date is selected. The additional catalogue families below are proposals rather than committed features.
More kinds of promotion
A welcome package does not describe every promotion. The wider catalogue proposal keeps each mechanic's conditions explicit:
| Proposed mechanic | What a reader would need to understand |
|---|---|
| Cashback | Rate, eligible-loss or other stated basis, calculation period, cap and restrictions on credited funds |
| Incremental unlock | Qualification milestone, amount released, permitted use and wagering or withdrawal conditions |
| Standalone spins or no-deposit | Qualification, games, spin value, winnings treatment and withdrawal restrictions |
These terms describe an advertised proposition, not a particular player's calculated reward. Free spins alone do not mean no deposit is required. A calculation period or unlock milestone should not be forced into a deposit stage just because that structure already exists.
Casino loyalty and VIP programmes would describe tiers and programme benefits. Casino events would describe timed activities and advertised prizes. Both are distinct from online.casino's own contribution rewards.
Explain unfamiliar features without inventing filters
The catalogue cannot anticipate every Casino feature. A source-supported, editor-reviewed description can preserve a subject, its context and known limits before a dedicated structured comparison exists. Uncertain applicability must remain explicit.
For example, an editor could explain a service perk without turning it into a yes/no search filter. A factual filter needs a defined meaning, supported values and matching rules. The exact minimums for such narrative publication remain open.
How the work can grow
The roadmap describes dependencies, not dates or a requirement to finish every catalogue family before adding another capability.
The manual branch needs agreed profile/Offer fields, sources, publication requirements and public composition rules. It can prove that a draft edit leaves the approved revision unchanged and that one Market's facts do not leak into another. It does not depend on a parser or a score.
The first deferred parser package is bounded to a supported welcome package. Its CMS import must retain context and source support, reuse existing identities and handle repeated or late results. Fetching a readable general-terms page is not the same outcome as extracting every structured policy fact from it.
Editorial preparation then produces supported welcome terms, a headline and summary from eligible retained input. Operator publication reviews one complete welcome draft with its chosen whole-draft approval policy; a replacement proposal remains separate from the old human draft. Other families remain manual until their acquisition and editorial treatment are selected. Module checks can use controlled inputs; proving the live source-to-page journey is a separate integration step.
Explore the separate branches
- Source to draft explains the deferred welcome-offer automation and the work still needed to connect it.
- OC Score explains the draft methodology and why publishing a fact does not approve it for scoring.
- Community rewards explains historical candidate mechanics and the open engine decision.
- Offers and disclosure explains the separation between commercial relationships and independent product measures.
For current selection, use the first platform scope brief. The review directory also has separate questions for scoring, rewards and future automation. Feedback on those future designs does not bring them into current delivery.