Orbital AscentTwinned

Build a browser game called "Orbital Ascent: Twinned".

Concept: A metroidvania set in a derelict space station, where you control two characters at once. Rendered in photocopied zine.

THE CORE LOOP
One connected map where progress is gated by abilities, not keys. Every new ability retroactively opens places you have already walked past.

THE RULE THAT MAKES IT DIFFERENT
You control two characters at once. One input drives both, in different contexts. Never split the controls — the difficulty must come from the shared input, not from juggling.

REQUIREMENTS
- Model the map as a graph with ability-tagged edges and write a solver that proves the critical path is completable — hand-designed gating in this genre is how you ship a softlock.
- Modular ring sections that can lose pressure, power and gravity independently, changing how the player moves through them.
- Blown-out high contrast, dithered halftones, visible toner streaks and a page that shifts a pixel or two per frame.
- Runs in a browser with no build step. Vanilla JS or a single small library, ES modules, no bundler required to try it.
- Fixed-timestep update loop with interpolated rendering, so the game is frame-rate independent on a 144Hz monitor.
- All content — levels, entities, balance numbers — lives in JSON or plain data files, never inline in the logic. Tuning must not require reading code.
- Audio generated with the Web Audio API rather than asset files, so the whole thing stays self-contained.
- Feel pass, treated as a requirement and not as polish: hit-stop on significant impacts, screen shake scaled to magnitude, particles on every state change, and easing on every transition. Nothing may pop in or out instantly.
- Full keyboard support, a pause that actually pauses, and a settings panel exposing the tuning constants as live sliders. You will need those sliders.
- Respect prefers-reduced-motion: keep the fades, drop the shake and the parallax.

BUILD ORDER
1. The core loop with placeholder rectangles. No art, no audio, no menus. Make it fun as rectangles first — if it is not fun as rectangles, the look will not save it.
2. The twist, wired into that loop. This is where the design lives, so expect to rewrite step 1 once you feel it.
3. Content and balance, moved out into data files.
4. The look, applied last as a rendering layer over a game that already works.
5. The feel pass.

Scope: A month, honestly. If a system is taking longer than that, cut it rather than shipping it half-built.

Start by writing a one-page plan covering the core loop, the data shapes, and what you are deliberately leaving out. Wait for me to approve it before writing code.