Supported components

Model limits matter

Sensors use ideal bounded values, contacts do not model bounce or wear, light and sound outputs are relative indicators, and the LCD implements a tested command subset. The thermostat experiment uses the temperature module only as an ideal linear signal, its button as an ideal active-low contact and its LED as a heater-command indicator; it does not model a room or physical heater. Representable invalid polarity, missing current limiting, ground, known output contention, named-rail shorts and unsupported topologies fail closed with corrective actions. These checks are not physical-damage prediction or safety certification, and arbitrary cross-controller voltage wiring is unavailable.

CMP-019 GRAPH PRIMITIVE

Explicit junctions and separate crossings

A junction is authored topology, not a decorative or physical component. It joins three or more named endpoints in one declared net. A route from a different net can cross the same drawing point and remains electrically separate because net and endpoint identity—not pixel overlap—is authoritative.

AVR stores a first-class junction ID. Pico, ESP32-C3 and STM32 store the validated multi-endpoint net and derive the visible dot without fabricating AVR's identity model. The canonical narrow-profile examples remain authoring-only and fail closed with MODEL_LIBRARY_COMPONENT_UNAVAILABLE. A junction adds no independent Build/Run authority, resistance, current capacity, heating, parasitic, insulation or safety claim.

EXACT PUBLIC CONTRACT

Controller compatibility matrix

There are 86 unique public models and 344 profile/model cells. AVR has 64 executable models—40 Simulated and 24 Partial—plus 15 raw passive/diode/active-semiconductor/circuit-protection/connection-hardware authoring-only symbols. Each narrow controller profile has exactly 3 executable models plus 19 additional authoring-only parts. Across the complete matrix, 73 cells are executable, 72 more are authoring-only and 199 are unavailable.

AVR project modes: ordinary project-v2 shows 6 Simulated parts. Candidate-v3 exposes all 64 executable AVR models plus fifteen raw passive/diode/active-semiconductor/circuit-protection/connection-hardware authoring-only symbols with exact status and limitations. The top-adjust trimmer, common-cathode traffic light, DHT11 timed digital sensor and DS18B20 OneWire sensor are separate AVR-only models; none implies availability on the narrow 3.3 V profiles. The fixed 5 V source projects only to the existing AVR board output; it is not a bench supply. Partial always means the stated bounded behaviour, never broad hardware equivalence.

Control persistence: validated AVR button, potentiometer, switch, sensor, threshold and encoder values are canonical project data. Open never restores runtime events or executable authority and always requires a fresh Build. The current narrow profiles have no interactive control keys.

Unavailable controllers and parts are not remapped or approximated. Open the in-workbench matrix for the exact project mode and first limitation or rejection reason for every cell.

Pico, ESP32-C3 and STM32 supported parts

The general AVR editor exposes 64 executable models and fifteen raw passive/diode/active-semiconductor/circuit-protection/connection-hardware authoring-only symbols. Each 3.3 V workbench admits twenty-two component types: its fixed controller, resistor and LED are executable; ground reference, momentary button, rotary potentiometer, toggle switch, both capacitor symbols, fixed inductor, three diodes, four transistors, one phototransistor optocoupler, one fuse, one resettable PTC fuse, one four-row mini breadboard and one two-position terminal block are data-only and never grant runtime authority. The separate top-adjust trimmer, traffic-light module, four-digit multiplex display, DHT11 protocol sensor and DS18B20 OneWire sensor remain unavailable on these profiles. Narrow controllers cannot be added, duplicated or deleted.