Teamwork,followed through.

Möbius 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.

Möbius work model

1Issue treePlans, tasks and acceptance work share one structure

5Core flowsCapture, triage, execute, test and release

4System boundariesMöbius, IAM, MyEC and HR keep ownership clear

1Source of truthIssue details, discussions, tests and links stay together

One player problem may become a complete delivery trail.

Möbius 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 Möbius 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. Möbius reads authorised feedback snapshots, groups related reports and lets humans decide what becomes internal work.

Test results and acceptance evidence stay with the issue.

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, Möbius uses versioned APIs, idempotency keys and transaction outbox events to project internal progress back to player-facing services.

mobius.easecation.netPlayground

Möbius

My work

Today

Focus now

#1048Bed Wars settlement delayHigh

#1042Mobile resource retryMedium

#1036Weekly ticket summaryNormal

Mentions6

Due soon3

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.

01Capture

Authorised feedback snapshots enter Möbius.

02Triage

Reports are grouped and reviewed by people.

03Execute

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

04Test

Claimable test runs keep evidence with the work.

05Release

Outbox events update the systems that face players.

Möbius 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 Möbius. That keeps the product focused on project delivery instead of rebuilding foundations.

IAMOAuth sign-in, users and application permissions

MyECPlayer feedback content and player-facing state

MöbiusIssues, workflow state, comments, tests and release follow-up

HRDirectory data for visibility and managed views

Web platform

The same platform foundations behind MyEC and IAM also carry Möbius.

Explore the Web platform

Möbius 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.