Define a canonical public rules page for eco-app #169

Closed
opened 2026-07-29 05:47:17 +00:00 by coilyco-ops · 0 comments
Owner

Outcome

Define the canonical source and an implementation-ready contract for a public /rules page in eco-app.coilysiren.me, so players can find the current Sirens rules without relying on duplicated Discord posts or in-game help.

Scope

  • Identify the authoritative maintained rules source and its editor/approval boundary.
  • Define the minimum page content, update behavior, and a link back to the source.
  • Decide whether the web page should render source content directly or consume a versioned published representation.
  • File a bounded implementation issue after the source-of-truth decision is made.

Acceptance

  • One authoritative source is named, including how updates reach the web page.
  • The proposed /rules surface has explicit content and freshness behavior.
  • The decision preserves a visible provenance link and avoids a second manually maintained rules copy.
  • Any implementation follow-up is scoped without bundling Discord rich posts or in-game F1 content.

Non-goals

  • This issue does not rewrite the rules or make policy decisions.
  • Discord and in-game rule surfaces are out of scope except as consumers of the same canonical source.

Origin

## Outcome Define the canonical source and an implementation-ready contract for a public `/rules` page in `eco-app.coilysiren.me`, so players can find the current Sirens rules without relying on duplicated Discord posts or in-game help. ## Scope - Identify the authoritative maintained rules source and its editor/approval boundary. - Define the minimum page content, update behavior, and a link back to the source. - Decide whether the web page should render source content directly or consume a versioned published representation. - File a bounded implementation issue after the source-of-truth decision is made. ## Acceptance - One authoritative source is named, including how updates reach the web page. - The proposed `/rules` surface has explicit content and freshness behavior. - The decision preserves a visible provenance link and avoids a second manually maintained rules copy. - Any implementation follow-up is scoped without bundling Discord rich posts or in-game F1 content. ## Non-goals - This issue does not rewrite the rules or make policy decisions. - Discord and in-game rule surfaces are out of scope except as consumers of the same canonical source. ## Origin - Discord suggestion: [Sync rules into Eco app website](https://discord.com/channels/1300204416229441587/1530052689294262272/1530052689294262272) - Forum thread ID: `1530052689294262272` - Related: #37 (the public read-only Eco website)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/eco-app#169
No description provided.