Foundation
Foundation: vocabulary, mechanisms, and first-principles boundaries.
DEEPEN ALL TRACKS
A static, evidence-first plan for deepening every semiconductor domain without enabling live execution or transactional workflows.
DEPTH CONTRACT
Each domain now has the same scaffold: foundation, simulation ladder, evidence ladder, and research output. That makes future additions comparable instead of scattered.
Foundation: vocabulary, mechanisms, and first-principles boundaries.
Simulation ladder: precomputed cards that expose knobs, outputs, methods, and limits.
Evidence ladder: source anchors, exports, uncertainty, and claim fitness.
Research output: paper-ready figures, tables, methods notes, and limitations.
NINE DOMAIN ROADMAPS
The cards below are not a promise that every simulation exists today. They are the public, rights-clean backlog that keeps the platform expanding toward a comprehensive semiconductor curriculum.
Process depth connects unit operation, mechanism, inline metric, device parameter, circuit timing, memory margin, and yield consequence.
Device depth turns charge, potential, material stack, and geometry into extractable electrical curves.
Circuit depth links device curves to bias, gain, delay, noise, feedback, and variation.
Memory depth now spans SRAM cell/peripheral/I/O, DRAM/HBM locality, HBM/base-die partitioning, DRAM 1T1C sensing, retention, refresh, RowHammer, ECC/scrub guardbands, NAND threshold margin, MRAM switching/read/retention, FeFET/FeRAM, PCM, ReRAM, CIM, SCM, eDRAM/MIMCAP, 3D memory, and hierarchy placement while keeping device, cell, peripheral, controller, package, system, reliability, and evidence layers separate.
Digital depth makes cycle-level contracts, waveform evidence, assertions, timing assumptions, and fault coverage explicit.
EDA and layout depth converts geometry into parasitics, constraints, violations, timing, and power integrity without redistributing restricted assets.
Equipment and facilities depth teaches state, availability, environment, utilities, and EHS vocabulary while avoiding operating instructions.
Metrology and yield depth decides whether evidence is fit for a claim before the claim moves into process, device, or product language.
Packaging, test, and reliability depth follows evidence after wafer fabrication into interconnect, heat, hybrid bonding, screening, stress, and failure analysis.
BUILD SEQUENCE
For the next several passes, each new content card should land with a domain ID, a source spine, a precomputed dataset or figure, a limitation note, and a research-output target.
Build a process split brief that traces one unit-process change to one measurable inline metric, one device metric, one circuit or memory consequence, and one yield evidence question.
Jump to plan ->Build a device extraction packet that lets a circuit learner cite threshold, gm, capacitance, and leakage without overstating fidelity.
Jump to plan ->Build a compact circuit evidence packet where a device-level change propagates into gain, delay, power, or decision margin.
Jump to plan ->A memory evidence packet now travels from SRAM cell/peripheral/I/O evidence into DRAM/HBM locality, MRAM switching, RRAM/PCM/FeFET margin, CIM crossbar tradeoffs, controller traces, BIST, and ECC without blurring abstraction layers.
Jump to plan ->Build a verification packet where a learner can explain exactly what behavior was checked and what remains unproven.
Jump to plan ->Build a layout evidence packet that turns one geometry choice into a quantified timing, noise, or rail consequence without publishing PDK material.
Jump to plan ->Build an equipment evidence packet that explains why a process result depends on environment and availability without giving operating instructions.
Jump to plan ->Build a metrology packet that can approve or reject whether a graph is strong enough to support the claim attached to it.
Jump to plan ->Build a post-fab evidence packet that can explain what remains uncertain after a die works electrically.
Jump to plan ->BOUNDARIES
The roadmap deepens content and evidence. It does not add accounts, submissions, live server execution, facility-sensitive operation, or signoff authority.