Documents for agreement
This is the place to review a proposal, understand the consequence of a choice, and find what has already been agreed. The briefs below are prepared for stakeholder feedback. No decision is recorded for these new briefs.
Each document can be shared separately. Reply with its title and revision date, the question you are answering, and either acceptance, requested changes or a decision to defer. How review works explains how that response becomes a recorded outcome.
Parser v1.1.1 examples
Parser v1.1.1: examples and flexibility is a standalone review of source-to-result examples, nested bonus terms, regional contexts and configurable definitions. Use its questions to confirm whether the proposed results preserve the information you need. Reviewing it does not select parser implementation or change the current platform scope.
Current platform questions
| Document | Decision to make |
|---|---|
| Payload collections and fields | Do the eleven proposed collections, their fields, nested terms, relationships and publication minimums fit the catalogue? |
| First usable platform scope | Which complete reader and staff outcomes should the next selected scope deliver? |
| Catalogue and publication | Which facts are required, how are they reviewed, and what should readers see when content is incomplete or withdrawn? |
| Search experience | Which exact conditions and result behaviors should the first search support? |
| Community and moderation | Which contributions and interactions should be selected, and how should review and correction work? |
These are related choices; reviewing them does not commission implementation. The first-scope decision determines which detailed questions need to be resolved for that delivery.
Future design discussions
| Document | Why discuss it | Timing |
|---|---|---|
| Casino scoring | Agree what a score measures and what evidence permits it to be shown | Deferred |
| Community rewards | Choose useful actions, mechanics and the delivery arrangement | Confirmed future capability; implementation deferred |
| Source collection and editorial automation | Review the bounded welcome-offer package and its separately scoped integration | Deferred |
Feedback on these documents does not select a start date or add the work to the current platform scope.
Recorded direction
The following choices are already recorded in the project's accepted decisions. They provide the context for the open briefs.
| Recorded date | Agreed direction | Reader explanation |
|---|---|---|
| 21 September 2026 | Build the platform first; keep scoring, gamification and parser-related packages for later | Scope and status |
| 22 September 2026 | Separate public presentation, editorial content and product state; use one staff workspace | Editorial workspace |
| 28 September 2026 | Use email codes and Google for public accounts, with a private email and public nickname | Accounts |
| 3 October 2026 | Use grouped public search with a selected search engine and explicit filter meanings | Search |
| 3 October 2026 | Keep the product service responsible for structured public Casino and Offer reads while the CMS owns the content | Catalogue model |
Human review of publication and separation of Casino trust, contributor reputation, rewards and commerce are also established principles. The dates above identify the recorded decisions, not feature release dates or a new stakeholder sign-off.
For topics not yet selected, see research and product ideas.