# Racsor

> Racsor is a development and simulation environment for physical systems, starting with robotics. It provides a connected computational representation of complete physical systems—mechanical assemblies, electronics, firmware, control logic, requirements, and verification evidence—before committing iterations to hardware.

## Overview

- **Product Name**: Racsor (also known as Racsor IDE / Racsor Physical Systems)
- **Domain**: Physical systems engineering, robotics simulation, multidisciplinary hardware development
- **Website**: https://racsor.com
- **Status**: Under active development (Early access waitlist open)
- **Tagline**: "Build physical systems before you build them physically."

## The Problem Racsor Solves

Physical machines (such as robots, drones, aerospace vehicles, and industrial machinery) operate as single integrated systems, yet modern development tools remain deeply fragmented across isolated silos:
- Mechanical engineers work in 3D CAD
- Electrical teams design in EDA/schematic suites
- Embedded software engineers write firmware in code editors
- Controls teams simulate in specialized mathematical tools
- Test and verification data is scattered across spreadsheets and trackers

When one subsystem changes (e.g., motor sizing, mass distribution, bus latency), downstream assumptions become invalid without immediate notification. Teams often only discover integration failures after fabricating expensive physical hardware prototypes.

## The Racsor Solution

Racsor introduces a continuous computational substrate that connects multidisciplinary engineering state:
- **Connected System Model**: Unifies mechanical geometry, electrical properties, kinematics, control software, requirements, and test suites into a single graph.
- **Deterministic Revisions**: Every change is versioned with explicit traceability of what dependencies and assumptions are affected.
- **Shared Engineering State**: Both human engineers and autonomous engineering agents interact with the same unified model rather than parsing disparate disconnected file formats.
- **Simulation Continuum**: Simulations and engineering studies are executed against specific system revisions to evaluate behavior dynamically.

## The 4-Stage Development Loop

1. **Build (Develop the System)**: Mechanical, electrical, firmware, and controls evolve against shared engineering context.
2. **Simulate (Evaluate Behavior)**: Execute relevant multi-physics simulations and kinematics studies directly against a specific system revision.
3. **Verify (Check Observations)**: Automatically compare simulation results against system requirements, safety bounds, and constraints.
4. **Iterate (Change What Failed)**: Rapidly refine models and automatically re-run only the affected engineering analyses before building physical prototypes.

## Initial Domain: Robotics

Robotics represents the quintessential multidisciplinary engineering domain, where dynamics, actuators, electronics, thermal properties, control loops, and embedded software tightly couple. Validating Racsor's core engine in robotics establishes the foundation for broader physical engineering domains, including aerospace, industrial automation, and complex mechanical machinery.

## Links & Resources

- Official Website: https://racsor.com
- Waitlist Access: https://racsor.com/#waitlist
- Development Roadmap: https://racsor.com/#roadmap
- Technical Documentation for LLMs: https://racsor.com/llms-full.txt