Technology overview

We turn team deliveryinto a product system.

Mobius is the project, issue, testing and collaboration platform behind EaseCation delivery. A player signal, product decision, development task and release follow-up can stay in one traceable issue workflow.

One issue model, from player feedback to shipped change.

Mobius work model

1 Issue tree Plans, tasks and acceptance work share one structure
5 Core flows Capture, triage, execute, test and release
4 System boundaries Mobius, IAM, MyEC and HR keep ownership clear
1 Source of truth Issue details, discussions, tests and links stay together

One player problem may become a complete delivery trail.

Mobius does not replace MyEC, UC or IAM. It receives the internal context that needs action, keeps ownership and evidence with the issue, then projects progress back through controlled integrations.

Product demo

Start from what needs attention now.

The workspace shows unfinished work related to the current user. Root goals, parent context and actionable tasks stay together so the team can move without asking where the work came from.

Everything important is carried as an issue.

A Mobius issue keeps its number, Markdown body, history, permissions, participants, comments, files, tests and external links. Parent-child structure expresses ownership and decomposition.

Player reports enter as controlled snapshots.

UC still owns player conversations, replies and attachments. Mobius reads authorised feedback snapshots, groups related reports and lets humans decide what becomes internal work.

Testing is part of the work, not a separate memory.

Test runs can be created, claimed and submitted against the issue. Results, notes and evidence stay next to the decision they validate.

Progress returns to the product that owns the user.

When work is ready, Mobius uses versioned APIs, idempotency keys and transaction outbox events to project internal progress back to player-facing services.

mobius.easecation.net Playground
Möbius

My work

Today
Focus now
#1048 Bed Wars settlement delay High
#1042 Mobile resource retry Medium
#1036 Weekly ticket summary Normal
Mentions 6
Due soon 3
Recent activity

Test evidence added to #1048

The workflow stays short because the context travels with it.

Capture the signal, decide whether it should become work, execute through an issue tree, validate with test evidence, then release and project progress. Each step reads the same source of truth instead of rebuilding the story.

01 Capture

Authorised feedback snapshots enter Mobius.

02 Triage

Reports are grouped and reviewed by people.

03 Execute

Owners, state, due dates and documents live on the issue.

04 Test

Claimable test runs keep evidence with the work.

05 Release

Outbox events update the systems that face players.

Mobius sits on the Web platform and shares its foundations.

The same identity, interface contracts, delivery environments and observability used by the broader Web platform also shape Mobius. That keeps the product focused on project delivery instead of rebuilding foundations.

IAM OAuth sign-in, users and application permissions
MyEC Player feedback content and player-facing state
Mobius Issues, workflow state, comments, tests and release follow-up
HR Directory data for visibility and managed views

Mobius gives the team one place to finish the work.

A decision, its execution, test evidence and player-visible progress stay connected from start to finish.