Catalogue and product design
Work record: catalogue documents reviewed 5 October 2026; parser examples added 6 October 2026.
The project has a connected description of the product and concrete documents for the choices still to make. This work can be reviewed before the corresponding screens and workflows are built.
What has been prepared
| Design artifact | What a stakeholder can examine |
|---|---|
| Payload collections and fields | Eleven concrete collections: exact field names, types, requiredness, nested structures, relationships and linked JSON examples for field-by-field agreement |
| Parser v1.1.1: examples and flexibility | Worked source-to-result examples, nested bonus terms, context handling and controlled definition changes; proposed design with evidence limits |
| Casino information | Which facts a profile should explain, including payments, legal statements, games and support |
| Bonus Offers | How separate offers, stages and benefits work, with a worked example of different limits |
| Catalogue model | How Casino, Brand, Company, Market, profile and Offer relate |
| Publishing journey | How an editor retains sources, corrects a draft, obtains approval and publishes a revision |
| Publication details | Independent profile/Offer publications, language choices, retained history and withdrawal |
| Search experience | Grouped result types, visible conditions, market and language behavior |
The catalogue work includes both a broad model and a proposed manual authoring structure. The examples distinguish an award from a wagering requirement, an Offer cashout cap and an ordinary withdrawal limit. They also show why missing terms and contradictory claims cannot be filled in by assumption.
What is agreed and what remains open
The platform direction, ownership of editorial and product data, public account model and search direction are recorded decisions. The detailed catalogue fields, publication minimums, first feature scope and several public display behaviors still need agreement.
For example, a Casino profile and an Offer can publish independently. The behavior when a profile is withdrawn while an Offer remains published still needs a product decision. The model makes that question visible; a diagram does not choose the answer.
Review the catalogue and publication proposal or the search proposal. Each brief identifies the requested decision and links back to the explanation it would change.
Evidence boundary
These are product and design artifacts. Their presence does not establish new catalogue collections, integrated search, staff screens or a deployed feature. The application work records describe the narrower implementation evidence. Earlier research and examples remain available in the research library.