CMOS inverter lesson
Concept sequence and review gate.
Open route ->DOMAIN LANE / CIRCUIT
How does a device-level curve become gain, delay, and oscillation?
ROUTE STACK
This lane collects the learning packets, replay labs, simulation objects, and evidence routes that belong together. It is a filter, not a new workflow engine.
Concept sequence and review gate.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->SIMULATION FILTER
Paper-writing users can enter from this page and open the relevant run cards, exports, methods, limits, and evidence without first watching a lecture.
Sweep VIN, plot VOUT, estimate switching point, sampled gain, and noise margins.
Use ring-oscillator transients to extract per-stage delay across stage count and load.
Close an odd inversion loop and turn inverter delay into a measurable oscillation frequency.
Replay output voltage and output resistance to see when a current mirror stops behaving like a current source.
Replay input differential, offset sigma, decision probability, regeneration time, and fail-rate proxy for memory and comparator intuition.
Replay VDD and temperature to connect standard-cell delay, switching energy, leakage, and an EDP-style index.
DEEPENING PLAN
Circuit depth links device curves to bias, gain, delay, noise, feedback, and variation.
Build a compact circuit evidence packet where a device-level change propagates into gain, delay, power, or decision margin.
Open all-domain roadmap ->EVIDENCE BACKLOG
The backlog keeps future additions useful rather than noisy. New pages should enter through a domain tag, public source anchor, model boundary, and precomputed evidence package.
BOUNDARIES
Every domain can grow as education, simulation replay, and evidence planning. The page must not become a job board, tool controller, recipe workflow, upload service, or signoff surface.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
SOURCE SPINE
These source links help name the domain. They do not convert teaching replays into certified measurements, process recipes, facility procedures, or product signoff results.
External SPICE-compatible solver reference; the public card is a precomputed educational surrogate.
Open source ->External Python SPICE interface reference kept behind a license/dependency boundary.
Open source ->Open synthesis source spine for future digital timing evidence packages.
Open source ->Open physical-design flow reference for future STA and standard-cell sizing replays.
Open source ->NEIGHBOR DOMAINS
Semiconductor work is coupled. These links keep the site navigable when one claim crosses process, device, circuit, memory, equipment, metrology, or reliability boundaries.
What changed on the wafer, and what evidence proves it?
Open domain ->How do charge, potential, materials, thermal path, and carriers become I-V, C-V, RF, or power-device evidence?
Open domain ->How does memory preserve, sense, move, disturb, retain, protect, and place data across SRAM, DRAM, HBM, NAND, MRAM, FeFET, SCM, CIM, and hybrid memory systems?
Open domain ->What cycle-level contract was actually checked?
Open domain ->How do layout markers, connectivity reports, parasitics, and timing evidence become a public-safe verification claim?
Open domain ->What tool or facility condition supports the process, and what is still not an operating instruction?
Open domain ->Is the measurement fit for the claim?
Open domain ->What evidence remains after the die is fabricated, bonded, packaged, screened, and stressed?
Open domain ->