Skip to main content

Select the first platform experience

For review — no decision recorded

Prepared 5 October 2026.

Decision requested​

Which reader and staff journeys should define the first bounded platform increment, and what result would stakeholders accept as useful?

The platform-first direction is agreed, but it does not select every capability shown in the designs. A concrete selection is needed before anyone can give a meaningful delivery commitment.

Current agreement​

The product combines public discovery, editorial content and account-owned participation. Email-code and Google account flows are established in source inspection. Casino identity, catalogue integration, search and contribution modules require their own delivery selection and proof.

Scoring, gamification and the parser-related packages are deferred. Their unresolved details do not need to block the current platform. A manual catalogue can work without them. Scope and status and the work overview distinguish design from implementation evidence.

Proposal for discussion​

Use one manual Casino-profile and Offer journey as the first catalogue acceptance example: staff establish the product and market, enter supported facts and terms, review a language candidate and publish it for readers. A later draft edit must leave the approved content unchanged, and updating the Offer must not require republishing the profile.

This is a proposed way to bound the first catalogue work, not a decision that it is the entire first release. Stakeholders should choose whether the same increment also requires full public search, contribution submission and moderation, or whether those are separately accepted increments. Existing account work supplies a foundation without settling those participation rules.

Illustrative result​

A reader can open one selected Casino's profile, understand a supported payment condition, inspect one Offer's cash and spin restrictions and identify the market and language. An editor can demonstrate the exact approved content and its retained history. The example is a proof of the chosen journey, not a proposed limit on the eventual catalogue.

Choices and tradeoffs​

  • Select the first market, language coverage and representative content. The configured interface languages do not prove translated catalogue content.
  • Choose required profile and Offer facts through the catalogue brief. A wider first field set needs more sources and review.
  • Decide whether the first search experience is part of this same acceptance or a separate increment.
  • Decide whether community submission and moderation are needed in this increment, and under which policies.
  • Select any commercial links or placements and their disclosure behavior. Existing separation rules do not supply approved wording or placement formats.

Response requested​

State the included reader and staff journeys, the first market/languages and a representative example for each journey. Name what must be demonstrated before acceptance. If choosing separate increments, state their order without assuming an unagreed date. Read the product overview for the experience these choices build toward.

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.