Kessetsu Documentation

Describe a circuit, simulate it, check measurable requirements and export its schematic. Use the free Web Hub without an account or install the local CLI for engineering and AI-agent workflows.

Start here

• Tutorial: build your first circuit and verify its frequency response.
• Web editor: examples, files, panels, simulation, exports and sharing.
• Why Kessetsu?: how the combined workflow complements SPICE and EDA tools.
• Cookbook: calculations, reusable blocks, agent loops and device models.
• Parameter studies: multi-condition experiments and reports.
• Research data: local CSV mapping, evidence and scalar comparisons.
• Finite parameter fitting: calibration-only selection with separate holdout validation.
• Memristor pulse protocol: a reproducible threshold-model study with convergence and held-out stimulus checks.
• Portable research packages: bundle exact study evidence, permitted dependencies and rerun instructions.
• Python and Jupyter: inspect simulations, studies and research evidence in Python.
• SPICE netlist import: convert the supported subset into editable, canonically verified .kess.

Language and command reference

• Language: components, pins, units, parameters and modules.
• CLI: commands, overrides, JSON output, file safety and exit codes.
• Simulation and assertions: analyses and PASS/FAIL results.
• Engineering measurements: metric definitions, arguments and units.

Models and engineering output

• Device models: local files, compatibility, provenance and examples.
• Components and simulation limits: what is modeled and what is not.
• Export formats: SVG, PNG, PDF, JSON, SPICE, KiCad and LTspice.
• Troubleshooting: diagnostics, browser storage and installation help.

Updates and support

• Changelog: versioned features, fixes and migration notes.
• Report an issue: include the version, a minimal reproducible circuit and the diagnostic, without private model files.
• Security reporting and license.

Simulation results describe the supplied circuit, models and conditions; they are not a guarantee of physical hardware performance. Each reference explains relevant assumptions.

For source contributions, read CONTRIBUTING.md and the architecture rules. Product planning and operational records are maintained separately; this documentation focuses on using and extending the released product.