Scope and status
The agreed direction is to build the public product and its editorial tools first. Scoring, community rewards and automated source preparation can be added later. The exact first platform feature set still needs agreement.
What the labels mean
| Label | What you can conclude |
|---|---|
| Agreed direction | The product or architecture choice has been recorded. Work may still be needed to implement it. |
| Implemented in inspected code | A dated inspection found the behavior in the application source. The work record says what was inspected. |
| Design or proposal | The document describes intended behavior or a choice for discussion. |
| Deferred | This capability belongs to later work; its start date has not been selected. |
| Verified in an environment | A dated check identifies the environment and the behavior that actually worked there. |
A document marked For review asks for feedback. It does not mean the feature is available or that its proposed rules have been accepted.
Where the project stands
The application inspection on 3 October 2026 found email-code and Google sign-in, session handling, account profile access and nickname onboarding. Several home-page and search sections still used example data or display-only state. The inspection did not establish implemented Casino, search, contribution, discussion or scoring modules.
The catalogue model, publication rules and search requirements give that work its design direction. Some choices are agreed, while the detailed scope and publication minimums remain open. See work and progress for the inspected outcomes and documents for agreement for the decisions needed next.
These records do not establish current live availability. No live demonstration is claimed on the strength of a design document, source inspection or screenshot.
Future work
Community gamification is a confirmed future capability. Its mechanics and engine remain open. Casino scoring and the source-collection, editorial preparation and operator-publication packages are also deferred. They do not block useful manual catalogue work.
Future capabilities explains those branches. The old Event Demo and n8n evaluation are project history, not the scope of the current platform.