Product foundation

Question Scheduling

See how Myndora chooses the next question and why scheduling is driven by stage and coverage rather than simple randomness.

Quick answer

Question scheduling chooses the next item by current stage and lowest-coverage eligible areas, not by simple randomness.

Why this matters

That helps the profile grow in a balanced way instead of overdeveloping one area while leaving the rest unclear.

What the scheduler is doing

The scheduler decides what the next question should be based on the current profile stage and what parts of the map have the least relevant evidence so far.

It does not pull randomly from the whole item bank.

Why stage comes first

Different stages need different kinds of questions. Early stages need broad core coverage. Later stages may need core completion or recalibration.

Stage is therefore the first filter on what can be scheduled next.

Why coverage comes next

Within the current stage, the scheduler prefers the lowest-coverage eligible areas. This keeps the profile from becoming patchy or overdeveloped in one corner.

Coverage-first scheduling is what helps the whole profile grow in a balanced way.

How to read this method

Use this page when you want to understand how Myndora chooses questions, not what each stage means in detail. The scheduler is the selection mechanism layered on top of the stage model.

That distinction matters because stages explain sequence, while scheduling explains the actual pick.

What the scheduler is optimizing for

The scheduler is trying to improve profile usefulness as efficiently as possible by prioritizing eligible areas that most need coverage for the current stage. It is not trying to maximize novelty or keep one topic going just because it was recently active.

That makes this page about selection logic specifically, while the meaning of stages and scores remains owned by their separate pages.