01 / CURRENT SOURCE STATUS
Source metadata is 0.1.0; no signed installer release exists.
Use the exact source commit, test output, target platform, model bundle, and documented limitations when comparing revisions.
02 / IMPLEMENTATION AREAS
Current implementation areas.
Core simulation
Netlist elaboration, modified nodal analysis, device evaluation, sparse solvers, and analysis dispatch.
Automation & validation
CLI commands, Python bindings, result conversion, golden comparison, machine-readable reports, and corpus harnesses.
Workbench GUI
The current HTML mockup defines layouts for design, simulation, results, verification, models, and project management.
Compact-model generation, periodic/RF analyses, behavioral models, and host interfaces are versioned independently. See the source README for implementation-specific limitations.
03 / WORKBENCH IMPLEMENTATION
The Workbench mockup defines the current GUI layout.
The home page renders the fixed 1440 × 900 Workbench HTML directly through an auto-fit frame. It does not embed the responsive-preview controls and does not use a screenshot.
Defined layouts
Hierarchy, schematic capture, checks, run configuration, property inspection, results, and desktop, tablet, or phone compositions.
Remaining qualification
The native and browser hosts still require feature wiring, accessibility testing, performance measurements, persistence, and release packaging.
04 / RELEASE REQUIREMENTS
Required contents of a public release.
- Pin a revision: identify the exact source commit, dependencies, toolchain, model bundle, and platform target.
- Run the gate: retain unit, integration, corpus, and host smoke-test artifacts for the release revision.
- Ship a signed artifact: publish installer provenance, checksums, support window, known limitations, and rollback path.
- Publish release notes: list user-visible changes, fixed defects, known limitations, migrations, and compatibility changes.
05 / COMMIT HISTORY
Repository commits and tags are the current change log.
Each commit identifies the changed files and parent revision. Pair it with CI output and the build environment when evaluating numerical or interface changes.