Agree the manual catalogue and publication model
For review — no decision recorded
Prepared 5 October 2026.
For the concrete data structure, open Payload collections and fields. It puts all eleven collections, field types, nested structures and JSON examples on one page. Use that document to request field changes; use this brief to discuss editorial requirements and what readers see.
Decision requested
Which profile and Offer facts must the first manual catalogue support, and how should the public page handle content that is absent, withdrawn, expired or missing in the reader's language?
These decisions make the proposed editor workflow and reader examples concrete. They are needed before a field layout or attractive card can be treated as an accepted product contract.
Current agreement
A Casino, Brand and Company have distinct identities. One Brand can present several Casinos; an established Casino has one current Brand. A profile needs that association before publication, although an incomplete draft can lack it.
Several independent Offers may share a Casino, market and purpose. Each Offer publishes separately from the profile; its dependent stages and benefits publish together. Currency choices select supported terms, and identical currency does not rule out distinct eligible variants. Human approval, retained support and exact published revisions remain required.
Proposal for discussion
The manual design uses one profile for each Casino and market, with shared facts and separately approved language copy. It gives each market-scoped Offer its own identity and applicable term variants. Legal statements, payment conditions and welcome stages stay with the subject they describe. Source support and unresolved issues remain visible during review.
A publication candidate resolves the exact facts, language and supporting relationships before approval. Earlier approved content remains inspectable when later drafts or shared records change. This proposed detail extends the agreed independent publication units; it does not impose the deferred welcome workflow's whole-draft reset policy on all content.
Illustrative result
An editor publishes a profile and two separate welcome Offers. Correcting the spins cashout cap in one Offer changes neither the other Offer nor the profile. Reordering its stages preserves the connection between each condition and its source. A payment method's deposit minimum cannot become its withdrawal minimum through a shared list.
Choices and tradeoffs
- Select required profile fields and type-specific Offer minimums. Missing material eligibility or restrictions cannot be guessed to fill the form.
- Agree how editors resolve identity uncertainty and incomplete Brand or Company information. A name or domain alone is not a complete duplicate/merge rule.
- Decide the page treatment for a missing or withdrawn profile, expired Offers, missing language content and a temporary source failure. Source failure is not proof that content does not exist.
- Decide any reviewed language fallback and how the interface handles a currency with no supported terms. Language cannot supply market or currency fallback.
- Confirm the first selected mechanics. Cashback, VIP programmes and events need their own terms and can remain separate future increments.
The tradeoff is between a smaller, source-supported first catalogue and broader coverage that needs additional definitions and editorial work. A reviewed narrative can explain an unfamiliar feature before it supports factual filters.
Response requested
List the required profile facts and Offer types, then answer each composition case above with the intended reader result. Mark unresolved identity or source questions explicitly. Use Casino profiles, Bonus Offers, the catalogue model, Offer terms and publication details to review the proposal.
Recorded outcome
No decision recorded. This brief does not authorize implementation or change delivery timing. Share the specific page and version through the existing discussion channel. Respond with accept, requested changes or defer, identifying the question concerned. How to review explains how an actual agreement is recorded and reflected in the product documents.