Founder-written. How Scouren started: who you are, what you were designing, which tool wore out your patience first, and why you built Schemify instead of waiting. Two or three paragraphs, first person. Nothing here has been written for you.
Why plugins and an agent that asks first: what you believe a schematic editor owes the person using it. One specific moment beats a mission statement.
Each date comes from a repository’s first commit, its creation date or a tagged release.
Work beginsRelease
“Phase 0+1: parallel eval infra, solver poisoned-state fix, GPU pre-flight.” The simulator and the model compiler share this history; it later splits into ESpice and VerA.
Source: ESpice, VerA: first commitGm&IdW starts as a standalone gm/Id lookup-table package.
Source: GmIdW: first commitResearch, decisions, specs and architecture, and the first workspace scaffold for the editor.
Source: Schemify: first commitThe xschem importer moves out of Schemify into the Interoperate plugin, which later adds Virtuoso import and export.
Source: Interoperate: first commitVerilog-AMS tests that cite their clause, the conform harness, and configs for running any tool against them.
DRC, LVS, ERC and PEX in one engine, set up on Zig master with a Nix shell and CI.
Source: GPurify: first commitThe repositories move under the Scouren organisation.
Source: repository created_at datesVerA’s first tagged release.
Source: VerA releasesA project template for analog and mixed-signal ASICs on open tools, derived from the UWASIC TinyTapeout template.
Source: AMTemplate: first commitThe fifteenth release in five days.
Source: VerA releasesSchemify’s editor moves to private development. The file format, plugin ABI and SDKs stay open under MIT.
Source: Schemify-Plugins: first commit and READMENative builds for Linux, macOS and Windows, and a browser build.
Source: Schemify-Releases v1.0.0Founder-written. What you are working on now and what you want to be true in a year. No dates you cannot keep.