Yes, Aqua and Copper are genuinely active at the same time during every round of the Multitasking Game. Both tasks share one round start timestamp, appear on screen together, and keep their own independent countdown. Securing one does not pause the other; both clocks continue running from the same instant, and each task only becomes actionable when its individual acceptance window opens. The game engine treats the pair as a single parallel round rather than two sequential prompts, which is why a single press on one task never closes the round and never awards points. Atomic deadline checks run on every action, so an expired companion task cannot be bypassed by completing the other one later in the same round. This dual-deadline contract is the entire reason both tasks have to be earned in the same window, and it is also why a perfect run ends on exactly 1,000 points across the five fixed rounds. Independent logic tests verify that one task cannot score alone and that both lanes can cause a missed-round failure, so the parallel contract is enforced at the scoring level, not just visually.
How the Multitasking Game Defines True Parallelism
The Multitasking Game labels the two tasks Aqua and Copper and runs them on a single shared round start. When you choose Start both tasks, both clocks begin ticking from the same wall-clock instant rather than from a sequence of staggered begin calls. The render layer shows both cards at once, with each card printing its own explicit due offset directly under the title and a live countdown that updates from a requestAnimationFrame refresh. Because the visual refresh is only a display helper, scoring and acceptance are decided by the event timestamp rather than by animation frame count.
This shared timestamp is the only thing the two clocks have in common. Their due times are authored independently, and the order in which those due times arrive changes between rounds. So even when both timers visibly count down at the same rate, each one will hit its own NOW state at its own moment, and only the task whose own acceptance window is currently open will accept a press. The interface design reflects the parallel contract: after one task is secured, focus moves to the pending task rather than dropping back to a central control, because the second clock is still running independently.
If you press the Aqua button or the A key for the left task when its window is closed, the engine first evaluates every incomplete deadline at that exact event timestamp. That press is recorded as an early or missed action, and because the round is treated as one paired attempt, both task clocks reset together. This is what makes a single mistimed press as fatal as missing an entire deadline. The pure timing reducer that scores the round does not know whether you used pointer, touch, or keyboard, so the rules do not shift with the input method.
Inside Each Acceptance Window
Every round prints the due offsets directly on the cards. The first round, for example, shows Aqua at a due time of 1.20 seconds and Copper at a due time of 2.20 seconds. Later rounds reverse the order, bring the two deadlines closer together, or narrow the authored timing windows. These are fixed game fixtures: the values are not training standards or reaction targets, only the published timing rules of this particular challenge.
An acceptance window is defined by an inclusive boundary on each side of the printed due time. A task becomes valid from its due time minus its authored window up to its due time plus that same window. Acting one millisecond before that opening boundary fails the round as early, and leaving the action one millisecond past the closing boundary fails it as missed. The status label on each card changes from Waiting to NOW during the open window and to Secured after a valid action.
Because the deadlines are independent, securing one task does not stop the other clock. Aqua and Copper are truly parallel, so even after one card reports Secured, the other countdown continues to run from the shared start until either its own NOW window opens or it expires. No points are awarded for a single secured task, and the round only closes successfully when both lanes report Secured before either boundary closes.
| Lane attribute | Aqua | Copper |
|---|---|---|
| Shared start timestamp | Yes | Yes |
| Default key | A | L |
| Due time in round 1 | 1.20 seconds | 2.20 seconds |
| Status label on the card | Waiting then NOW then Secured | Waiting then NOW then Secured |
| Independent acceptance window | Inclusive opening and closing boundaries | Inclusive opening and closing boundaries |
| Effect of securing the lane | Does not pause the other clock | Does not pause the other clock |
| Points for a single Secure | None | None |
Play Through Five Rounds
Follow these five steps to take the Multitasking Game from the first Start press to the fixed 1,000-point finish.
- Choose Start both tasks to launch Aqua and Copper at the same instant, then read each card's explicit due time and live countdown before the first NOW state appears.
- Press the Aqua button or the A key for the left task, and press the Copper button or the L key for the right task, only while that task's card shows NOW. Native buttons also support Enter and Space when focused.
- Keep both deadlines in view while you play. Securing one card does not pause the other clock, and either can still expire even after the first task is done.
- Confirm both cards display Secured before the round closes. A pair of valid actions earns exactly 200 points and prepares the next authored pair.
- Repeat for five rounds to reach the fixed maximum score of 1,000 points, or choose Restart at any point to return score, round, errors, task state, and feedback to their exact initial values.
Errors, Restart, and the Boss Key
Error handling is deterministic. Each failure produces a signature built from the round number, the lane, and the early or missed kind. Repeating the exact same signature does not add another error to the run, because the system deduplicates identical failures. A valid completion clears the repairable error history, while a second genuinely different failure closes the run in deadlock. Once a run is closed or finished, no later press, start, or visibility event can change that terminal result.
Tab visibility is treated specially. Switching tabs or hiding the page cancels the active attempt without recording an error, which keeps browser-level background timer throttling from turning a normal visibility change into an artificial miss. When you come back, the same round is ready to start again with both clocks reset to their initial state. The shared game shell also exposes a double-Escape Boss Key for the same quick-hide use case.
Restart returns the score, round, errors, task state, and feedback to their exact initial values, regardless of how the previous attempt ended. The shared game shell stores only an optional best score in local browser storage, plus the Boss Key shortcut. If local storage is unavailable, the live game and its deterministic five-round scoring continue unchanged. Independent logic tests verify Restart equality, terminal freezing, deduplication, and second-error deadlock against separately written expected fixtures for all five rounds.
| Trigger | Effect on the round or run |
|---|---|
| Both actions land inside their own NOW windows | Round closes with 200 points and the next pair loads |
| Action lands before the opening boundary | Round fails as early, both clocks reset together |
| Action lands after the closing boundary | Round fails as missed, both clocks reset together |
| Hidden tab during an active attempt | Attempt cancels without recording an error |
| Identical early or missed error repeated | Signature is deduplicated, no extra error record |
| Two genuinely different errors in one run | Run closes in deadlock, result is frozen |
| Restart pressed at any time | Score, round, errors, task state, and feedback return to initial |
Round-by-Round Timing Variations
The five rounds are authored and fixed; there are no random rounds, adaptive difficulty values, or hidden score multipliers. Round 1 sets Aqua at a 1.20-second due time and Copper at a 2.20-second due time. Later rounds reverse the order of those deadlines, shrink the gap between them, or narrow each task's authored acceptance window. Together these changes make the second half of the run denser, but the underlying rules do not change: both tasks stay parallel, both must be secured, and only a clean finish on every round ends the run on exactly 1,000 points.
| Round | Aqua due time | Copper due time | Order of acceptance |
|---|---|---|---|
| 1 | 1.20 seconds | 2.20 seconds | Aqua opens first |
| 2 to 5 | Authored fixture, varies per round | Authored fixture, varies per round | Reversed, swapped, or closer than round 1 |
The first row is published; the second row describes the disclosed variation pattern without inventing specific values for rounds 2 through 5. What stays the same across every round is the parallel contract: both tasks share one start timestamp, each retains an independent due time, and both must be secured inside their own inclusive windows before the round awards points.
Accessibility is built into the timing layer rather than bolted on. Task buttons exceed a 44-pixel target size, focus rings stay visible, and starting a round moves focus to the task with the earliest deadline. After one task is secured, focus shifts to the pending task. Success or failure returns focus to Start, while a terminal result triggers programmatic focus so a keyboard or screen-reader user is notified of the outcome. Color supports the status display, but readable labels such as Waiting, NOW, Secured, error messages, and explicit due times carry the meaning, so the game does not require color recognition.
The Multitasking Game is recreational entertainment. It does not measure or diagnose productivity, attention, cognition, reaction time, coordination, employability, learning ability, or any medical or psychological condition. A score reflects only completion of the five fictional authored timing rounds under the stated game rules, so treat the run as a fixed puzzle to solve rather than a personal benchmark.