Epic: Build the ATOS web prototyping environment

[recklessnode]

Objective

Build a static-first React/TypeScript/Vite application that serves as the ATOS digital twin and prototyping environment.

The implementation contract is defined in:

• AGENTS.md
• docs/architecture/web-prototyping-environment.md

Required first vertical slice

• Render a deterministic six-hex-tile scenario.
• Include a guideway loop, station, passenger platform, cargo depot, and charging siding.
• Model a nominal 100 W DC source with distributed conductor resistance and loads.
• Visualize voltage, current, losses, source utilization, and load shedding.
• Generate commuter, express-passenger, local-cargo, and battery-support chits.
• Display available vehicles and service capacity.
• Build at least one feasible temporary consist and route.
• Show pending chits, route reservations, look-ahead state, and deficiency gates.
• Export and import the scenario as versioned JSON.

Agent-sized work packages

• Initialize npm workspace, React/Vite app, tests, linting, GitHub Pages workflow, and Vercel configuration.
• Define versioned scenario schema and deterministic six-tile fixture.
• Implement hex coordinate, rotation, connector, and placement libraries.
• Implement tile and set-piece registry.
• Implement layout editor and synchronized selection state.
• Extract the operational guideway graph from placed tiles.
• Implement resistive DC network and constant-power load approximation.
• Implement load classes and deterministic shedding.
• Implement domain types for universal chits, assets, vehicles, stations, and manifests.
• Implement candidate carrier generation and requirement classification.
• Implement heuristic dispatch, consist formation, routes, and reservations.
• Implement deficiency gates and aggregate infrastructure recommendations.
• Implement simulation clock, random contract buckets, and fault injection.
• Add deterministic end-to-end scenario tests.

Acceptance criteria

1. npm test passes.
2. npm run build produces a static deployment.
3. The same scenario and random seed produce identical dispatch and power results.
4. The user can identify why every unsatisfied chit remains unsatisfied.
5. The prototype operates without a backend.
6. All database SQL added later remains PostgreSQL-compliant.

Agent coordination

Each agent should claim one unchecked work package, create a focused branch or pull request, include tests, and avoid unrelated refactors. Domain contracts and scenario schemas must be reviewed before UI code depends on them.