Section 13Simulation Runtime
Device, Power, Circuit, Thermal, and Firmware requirements
Defines actuators, transmissions, batteries, electrical and thermal networks, faults, and optional firmware execution.
Section relationships
| ID | Name | Priority | Requirement | Verification |
|---|---|---|---|---|
| DEVICE-001 | Typed device ports | MVP | Every device port SHALL declare quantity type, units, direction, frame where applicable, rate, causality, and cardinality. | Inspection |
| DEVICE-002 | Device state lifecycle | MVP | A device SHALL support initialization, step or activation, reset, snapshot where declared, restore where declared, and shutdown. | Test |
| DEVICE-003 | Actuator command contract | MVP | An actuator SHALL accept a timestamped command through a declared command mode and bounds. | Test |
| DEVICE-004 | Actuator saturation | MVP | An actuator SHALL support documented magnitude, rate, and state-dependent saturation. | Test |
| DEVICE-005 | Actuator latency | MVP | An actuator SHALL support deterministic or seeded command delay through virtual time. | Test |
| DEVICE-006 | Actuator deadband | Beta | An actuator SHOULD support documented deadband and hysteresis where applicable. | Test |
| DEVICE-007 | Reference motor model | MVP | The portable product SHALL provide the brushed-DC or behavioral-BLDC motor family selected by TBD-REFERENCE-MOTOR, relating voltage, current, speed, torque, losses, inertia, and limits. | Analysis |
| DEVICE-008 | Motor family coverage | Beta | The portable product SHALL provide both a parameterized brushed-DC motor model and a documented system-level behavioral BLDC motor model. | Analysis |
| DEVICE-009 | Torque-speed envelope | MVP | A motor SHALL enforce a documented torque-speed operating envelope. | Test |
| DEVICE-010 | Motor current limits | MVP | A motor model SHALL expose and enforce configured continuous and peak current limits under a documented policy. | Test |
| DEVICE-011 | Gear ratio | MVP | A transmission SHALL transform speed and torque according to an explicit ratio and efficiency model. | Test |
| DEVICE-012 | Transmission efficiency | MVP | A transmission SHALL support direction- and operating-point-dependent efficiency or a documented constant approximation. | Analysis |
| DEVICE-013 | Backlash | Beta | A transmission SHOULD support a documented backlash model. | Analysis |
| DEVICE-014 | Compliance | Beta | A transmission or actuator SHOULD support a documented stiffness and damping model. | Analysis |
| DEVICE-015 | Brake model | Beta | A device SHALL be able to apply passive or commanded braking subject to limits. | Test |
| DEVICE-016 | Servo abstraction | MVP | The portable product SHALL support a configurable servo composed from controller, motor, transmission, limits, and sensing elements. | Demonstration |
| DEVICE-017 | Battery state of charge | MVP | A battery SHALL track state of charge and delivered or absorbed charge over virtual time. | Analysis |
| DEVICE-018 | Battery voltage | MVP | A battery SHALL provide open-circuit voltage as a function of state under a documented approximation. | Analysis |
| DEVICE-019 | Battery internal resistance | MVP | A battery SHALL model terminal-voltage drop and heat generation from a documented internal-resistance model. | Analysis |
| DEVICE-020 | Battery current limits | MVP | A battery SHALL expose and enforce charge and discharge current limits under a documented policy. | Test |
| DEVICE-021 | Battery energy accounting | MVP | A run SHALL report energy delivered, recovered, dissipated, and remaining under the active power model. | Analysis |
| DEVICE-022 | Power bus | MVP | Devices SHALL be connectable to a power bus that resolves supported voltage, current, and power flows. | Test |
| DEVICE-023 | Converter efficiency | Beta | Regulators, inverters, and converters SHALL support operating-point-dependent or documented fixed efficiency and limits. | Analysis |
| DEVICE-024 | Power balance diagnostic | MVP | The Device and Power System SHALL report violations of supported energy or power-balance checks. | Analysis |
| DEVICE-025 | Simplified thermal node | Beta | A device SHALL be able to participate in a lumped thermal network with heat capacity, sources, sinks, and limits. | Analysis |
| DEVICE-026 | Device fault injection | MVP | An experiment SHALL be able to schedule supported open, stuck, degraded, noisy, limited, overheated, or disconnected device faults. | Test |
| DEVICE-027 | Fault observability | MVP | Every injected fault SHALL appear in the run manifest and event timeline. | Test |
| DEVICE-028 | Component catalog | Beta | BeforeMetal SHALL support revisioned reusable device models with provenance, uncertainty, and validity envelopes. | Inspection |
| DEVICE-029 | Manufacturer model distinction | Beta | Catalog metadata SHALL distinguish manufacturer data, inferred data, calibrated data, and assumed data. | Inspection |
| DEVICE-030 | Circuit topology | Future | The Circuit System SHALL represent electrical nodes, branches, component connections, reference nodes, and declared initial conditions when the native circuit capability is scheduled. | Test |
| DEVICE-031 | SPICE adapter | External | BeforeMetal SHALL permit selected circuits to be simulated by an optional external SPICE-compatible adapter. | Demonstration |
| DEVICE-032 | Firmware-defined device | External | A device MAY exchange peripheral and bus state with an optional virtual firmware platform. | Demonstration |
| DEVICE-033 | Device capability report | MVP | A device model SHALL report command modes, states, ports, limits, rates, snapshot support, stochastic behavior, and validity range. | Inspection |
| DEVICE-034 | Electrical primitives | Future | The native Circuit System SHALL support resistors, capacitors, inductors, independent voltage and current sources, controlled switches, diodes, wiring, and system-level loads when that capability is scheduled. | Analysis |
| DEVICE-035 | DC network solution | Future | The native Circuit System SHALL solve supported DC operating-point networks and report convergence or failure when that capability is scheduled. | Analysis |
| DEVICE-036 | Transient network solution | Future | The native Circuit System SHALL advance supported time-domain electrical networks under the Simulation Kernel's declared coupling policy when that capability is scheduled. | Analysis |
| DEVICE-037 | Reference electromechanical coupling | MVP | The reference motor, battery, power bus, and mechanics models SHALL exchange voltage, current, torque, speed, loss, and back-EMF state on documented scheduling boundaries. | Analysis |
| DEVICE-038 | Thermal network | Future | The native Thermal System SHALL represent lumped thermal capacitances, conductances, heat sources, boundary conditions, and temperature limits when that capability is scheduled. | Analysis |
| DEVICE-039 | Cross-domain energy accounting | MVP | The reference mechanical and electrical models SHALL report transferred, stored, recovered, and dissipated energy using one declared sign convention; enabled thermal models SHALL use the same convention. | Analysis |
| DEVICE-040 | Wiring model | Beta | A wiring element SHALL support resistance, current limit, connector or branch identity, and injected open or short faults. | Test |
| DEVICE-041 | Digital logic | Future | The Circuit System SHALL support event-driven Boolean and finite-width digital signals with declared voltage-threshold abstraction when that capability is scheduled. | Test |
| DEVICE-042 | Robot communication buses | Beta | BeforeMetal SHALL provide typed UART, SPI, I2C, and CAN bus abstractions without requiring instruction-level firmware emulation. | Test |
| DEVICE-043 | Bus timing and faults | Beta | A communication bus SHALL model configured rate, arbitration where applicable, latency, queueing, corruption, dropout, and disconnection behavior. | Analysis |
| DEVICE-044 | Compute resource abstraction | Beta | A compute device SHALL support task or inference latency, deadline, utilization, power, temperature, and failure state without claiming processor-cycle fidelity. | Analysis |
| DEVICE-045 | Firmware target manifest | External | A firmware-emulation adapter SHALL report supported instruction sets, boards, peripherals, timers, interrupts, and bus interfaces before execution. | Test |
| DEVICE-046 | Firmware clock synchronization | External | A firmware-emulation adapter SHALL map virtual CPU time, timers, interrupts, and peripheral events to the Simulation Kernel's declared time contract. | Analysis |
| DEVICE-047 | Hydraulic actuation | Future | BeforeMetal MAY support lumped hydraulic sources, valves, lines, cylinders, compliance, leakage, and limits through a capability-scoped model. | Analysis |
| DEVICE-048 | Pneumatic actuation | Future | BeforeMetal MAY support lumped pneumatic sources, valves, lines, cylinders, compressibility, leakage, and limits through a capability-scoped model. | Analysis |
| DEVICE-049 | Communication link | Beta | A logical wired or wireless data link SHALL support bandwidth, latency, jitter, queue, dropout, range policy, and connection-state models. | Analysis |
| DEVICE-050 | Aging and wear | Future | A device MAY support calibrated cycle, time, temperature, load, or environment-dependent degradation with explicit state and validity limits. | Analysis |
| DEVICE-051 | Temperature-dependent device limits | Beta | A device with thermal limits SHALL derive derating, shutdown, or failure behavior from committed Thermal System state under a documented policy. | Analysis |
| DEVICE-052 | Portable power execution | MVP | The Portable MVP SHALL use a documented motor-battery-bus coupling phase and SHALL reject power configurations outside the supported reference topology or requiring an unavailable general circuit solver. | Analysis |
| DEVICE-053 | Reference DC algebraic solve | MVP | Each reference power update SHALL solve the supported battery internal-resistance, wiring-resistance, and motor back-EMF relationship consistently at one virtual time and SHALL report saturation, nonexistence, or numerical failure. | Analysis |
Generated from the canonical specification. Edit section metadata or prose in docs/requirements.md; the website rebuilds this page and its relationships automatically.