Planned operating model
How MOOSACO is intended to work once the core stack is live.
This page describes the production workflow, not a list of features that already exist. The public shell is live now; auth, judging, contest operations, forums, and staff tooling are still under construction.
End-to-end flow
When the system is complete, the student journey should look like this.
Each step depends on real infrastructure. MOOSACO only makes sense when the pipeline from published problem to judged submission to contest discussion is backed by actual systems.
01
Create an account
Auth will let users save submissions, progress, standings, and forum identity. Until that exists, public pages stay informational.
02
Open published problems
Problems are intended to appear only after staff review, with clean statements, metadata, sample I/O, and vetted test data.
03
Send code to the judge
Solutions will be compiled and executed in isolated judge workers so verdicts reflect real evaluation instead of mock output.
04
Review results and iterate
Users will eventually see runtime, memory, verdict details, and account history only when those records come from the backend.
05
Compete and discuss
Once the core systems are stable, MOOSACO can open individual contests, clarifications, and moderated forum discussion.
Core systems
The planned platform is bigger than a problem list.
The public experience depends on several internal and user-facing systems working together. This is the model the current shell is pointing toward.
Accounts and identity
Authentication is planned to anchor saved work, standings, and discussion identity. No fake sessions or pretend profiles should appear before it exists.
Problem publishing
Original sets and imported material will go through staff review before publication. The public shell is intentionally not an open problem-submission flow.
Isolated judge
The production judge is intended to run code in isolated execution environments with language tooling, resource limits, and trustworthy verdicts.
Individual contests in v1
Contest support is planned around scheduled individual competition first. Team contests are not part of the initial public model described here.
Forums and clarifications
Problem discussions, announcements, and contest clarifications are intended to live behind auth with moderation once those controls are ready.
Internal staff tooling
Admin tooling is part of the real system: reviewing imports, publishing updates, and managing content so the site can stay accurate as it grows.
Public shell status
What this page is not claiming.
None of the workflows above are wired end to end yet. Until they are, MOOSACO should present roadmap and launch material honestly rather than simulate user activity or operational tooling.
- Real sign-in, saved submissions, and account analytics
- Backend judging, verdict history, and submission review
- Contest registration, live scoreboards, and frozen standings
- Forum posting, moderation actions, and staff import workflows