Map the field.
Follow the evidence.

Which equation, scale, approximation, and numerical error control the result?

How do composition, lattice, and microstructure constrain electronic behavior?

How do allowed states and band alignment shape carrier populations and transitions?

How do carriers move, scatter, recombine, and produce current?

Which interface or defect state changes charge, transport, noise, or reliability?

How do temperature, entropy, and stochastic variation change semiconductor behavior?

How does the starting wafer or grown layer constrain downstream device behavior?

How do transport and surface reaction become thickness, composition, and conformality?

How do imaging, resist, focus, dose, and pattern transfer set printed geometry?

How do plasma chemistry, transport, charging, and selectivity shape the final profile?

How do introduced species and thermal budget become active profiles and defects?

How do contamination removal and planarization alter surface readiness and topography?

How do geometry, interfaces, materials, and current density become resistance, capacitance, and reliability?

How are unit processes sequenced, monitored, controlled, and handed off without turning teaching content into operating instructions?

How do junction electrostatics and carrier injection create rectification, gain, and breakdown?

How do gate electrostatics and transport become threshold, current, capacitance, and leakage?

How do gate control, stacking, contacts, parasitics, and variability trade off across scaled architectures?

How do wide-bandgap materials, fields, traps, and thermal paths shape power and RF device limits?

How do transport, capacitance, parasitics, fixtures, reference planes, and noise limit high-frequency evidence?

How do photons, carriers, modes, and materials create emission, detection, and modulation?

How do electrical, mechanical, thermal, chemical, or optical transduction paths become a sensor signal?

Which state variable stores or transforms information, and what evidence distinguishes a device concept from a product claim?

How do bias, gain, feedback, noise, and loading create an analog response?

How do logic depth, slew, load, clocking, and state create delay and functional boundaries?

How do transistor ratios, array context, sensing, and assist shape SRAM stability and access?

How do charge storage, refresh, array organization, and stacked interfaces preserve and move data?

Which physical state stores information, how is it switched, and what limits retention and endurance?

How do sampling, quantization, references, mismatch, and timing become conversion accuracy?

How do delivery networks, switching activity, parasitics, and topology create integrity and timing limits?

How do data movement, precision, parallelism, and memory placement shape system efficiency?

How is intended cycle-level behavior expressed without hiding reset, latency, and interface contracts?

Which behavior is tested, asserted, covered, or proven, and what remains outside the contract?

How do RTL, constraints, libraries, and transforms become a gate-level implementation?

How do geometry, density, connectivity, power, and clocks become an implementation and its reports?

How do parasitics, constraints, corners, and analysis assumptions become a timing or verification statement?

How is internal state made controllable and observable, and which fault model is actually covered?

Can another person identify the exact source, tool, configuration, artifact, and limitation behind the result?

What measurand, instrument chain, sampling plan, and calibration support the reported value?

How much of the observed variation comes from the process, model, sample, or measurement system?

Which variation signal warrants monitoring, diagnosis, or action without confusing correlation with root cause?

How do interconnect geometry, bonding, thermal-mechanical stress, and partitioning affect package readiness?

Which test condition, limit, guardband, and coverage support a product decision?

Which stress, mechanism, acceleration model, and physical evidence support a lifetime or failure claim?

Which controlled definition, traceability record, and change history makes the result comparable and auditable?

How are hazards, environmental burdens, data stewardship, and public claims bounded across the lifecycle?