docs: project standard, event research and lobby season spec - #214
Merged
Conversation
Three documents that the upcoming lobby work builds on: - olf-minestom-project-standard.md: 23 architecture rules derived from ManisGame, Cygnus, Tamias and the theEvilReaper libraries, each with a rationale and an enforcement mechanism. Falco's falco-archunit module already enforces six of them and is the reference implementation. - event-modi-plan.md: research on seasonal events. Key finding, measured from Steam telemetry: cosmetic seasonal events move concurrent players by roughly zero (Deep Rock Galactic October: -0.37%, -12.16%, -4.92%) while content releases move them 20-150% and lift the floor for months. Decoration is brand upkeep, not a growth lever - so its cost must stay small. - spec-lobby-saison-events.md: the requirements themselves. 49 user stories across 7 stages, 13 non-functional requirements, EARS acceptance criteria and MoSCoW priorities, following the OLF requirement-engineering standard. - rollout-log.md: the record NFR-011 asks for, tracking which feature sat at which release stage.
This was referenced Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #213.
What this adds
Four documents under
docs/that the Stage branches implement against.spec-lobby-saison-events.md— the requirements49 user stories across 7 stages, 13 non-functional requirements, EARS acceptance criteria, MoSCoW priorities. Follows the OLF requirement-engineering standard.
event-modi-plan.md— the research behind itThe finding that shaped the spec, measured from Steam telemetry and spot-checked against the source tables: cosmetic seasonal events move concurrent players by roughly zero. Deep Rock Galactic runs both kinds in the same game — cosmetic Octobers at −0.37%, −12.16%, −4.92%, content seasons at +154%, +59%, +142%. Dead by Daylight and Destiny 2 agree independently.
Decoration is brand upkeep, not a growth lever. That is why the spec caps seasonal visuals at "data, not code" — the effort belongs in content.
olf-minestom-project-standard.md— the conventions23 architecture rules with IDs, each with a rationale and an enforcement mechanism, derived from ManisGame, Cygnus, Tamias and the theEvilReaper libraries. Falco's
falco-archunitalready enforces six of them and is the reference implementation.rollout-log.mdThe record NFR-011 requires: which feature sat at which release stage, when, and why it moved.
Note
Two open decisions are recorded in the spec rather than silently assumed: contributor consent for the relicense (#213), and whether the extension migration lands before October — if it does not, Stage 4 slips to 2027 rather than colliding with the event.