Build ASTERION, a futuristic spaceship command deck that feels like a beautifully crafted, playable science-fiction interface. This is a fun interactive website: the visitor is the captain of an exploration vessel approaching an unfamiliar star system. Use the attached better-interface reference throughout design, implementation, browser review, and documentation. Deliver the finished experience within this assignment.

VISUAL DIRECTION

Make it immersive and unmistakably a spacecraft control panel. Aim for cinematic instrument lighting, thoughtful typography, precise technical labels, a memorable ship identity, and a strong central navigation or ship visualization. Give the interface character through original graphics, restrained motion, meaningful readouts, and occasional dry ship-computer humor. Choose a coherent visual language rather than copying a franchise. The palette, layout, illustration approach, and ship design are yours to decide. Keep operational information legible: tiny decorative text, glow, scan lines, or animation must not obscure controls. Desktop can feel like a panoramic bridge; mobile should become a usable captain's console, not a shrunken desktop.

THE EXPERIENCE

Include a ship/mission header, an interactive star chart with three fictional destinations, power management, a readable ship-status view, and a short captain's event log. Show useful fictional telemetry such as hull integrity, fuel, reactor power, shields, and mission phase. Small decorative indicators can enrich the atmosphere, but clearly distinguish them from actual controls. The main activity is to choose a destination, configure the ship, and perform a simulated jump.

REQUIRED INTERACTIONS

1. Select a destination on the star chart or an equivalent keyboard-accessible list. Update its details, route visualization, and estimated journey information. Provide three distinct fictional places with short evocative descriptions.
2. Allocate a fixed 100-unit power budget among engines, shields, and scanners. Start at 40/35/25. Controls must be understandable, keyboard accessible, and prevent negative values or allocations above the budget. Show remaining power, and make at least one related status change meaningfully when allocation changes. Retain a minimum engine allocation of 30 as a jump prerequisite; explain that prerequisite when unmet.
3. Initiate a jump only when a destination is selected, sufficient engine power is assigned, and fuel is available. Review the destination and fuel use, confirm, then show a short sequence followed by an arrived state. Deduct a fixed 10 fuel units from an initial 100, update the current location, and append an event to the log. Prevent duplicate activation while a jump is in progress, and disallow jumping to the current location. Clearly explain blocked actions. Keep the sequence bounded to a few seconds and skip nonessential motion under reduced-motion preferences.
4. Include an accessible reset-simulation action so the visitor can try again. A concise help panel should explain the three-step journey. Any additional visible controls must do something coherent or be clearly identified as unavailable; do not create dead buttons.

SCOPE

All data and controls are fictional and local to the browser. This is not connected to real equipment. No accounts, wallet connections, backend, external telemetry, paid media generation, or credential requirements. Prefer original SVG, CSS, or lightweight canvas visuals bundled with the static export. No audio autoplay or flashing effects. Respect reduced motion and provide a way to pause substantial ongoing decorative animation. Keep the page responsive and performant; no large 3D dependency is necessary. Preserve creative freedom within these functional requirements.

REVIEW AND DELIVERY

Build with Vite, React, and TypeScript unless the assignment requires otherwise; use relative asset paths and a single page or hash routing. Run the final production build and typecheck. Use the assigned browser to inspect desktop and mobile versions of the final export, test the complete select-destination/power/jump/reset journey, keyboard focus and dialogs, invalid/blocked states, overflow, console errors, and failed resource loads. Apply Better Interface's six design disciplines and correct observed defects. Record actual checks and limitations honestly. Use the current design skill without introducing a separate Impeccable critique/polish or new sub-agent experiment.

Commit the source, lockfile, README, root DESIGN.md, and completed dist/ static export. Document the final tokens, components, responsive rules, and how to build another matching ship-console screen. Provide an identical artifacts/DESIGN.md, artifacts/validation.md with commands, viewport sizes, interaction evidence, findings/fixes and limitations, and actual final artifacts/desktop.png and artifacts/mobile.png screenshots. Package dist contents in artifacts/website.zip with index.html at its root; handle named artifacts according to the worker's instructions. Close browser sessions after checking. Public GitHub source and a hosted IPFS preview are requested.