SCQ Design Kit

Learn the models, follow the assumptions, and connect physical design to interpretable predictions.

A circuit diagram, an electromagnetic field solution, and a quantum state describe different parts of the same design problem. This site helps you connect them without confusing a model, a mathematical operation, and an observable.

Start with the question you have. Each explanation names its physical inputs, conventions, assumptions, result, and limits. Package documentation supplies version-specific APIs and execution instructions; this site supplies the cross-package reasoning.

Four ways to read

Overview

Stay here for the site’s purpose, the design feedback loop, and how to read citation and claim categories.

Learning Paths

Choose a connected sequence through Foundations, EM/circuit modeling, quantum models, or network response and measurement. Each step answers one question and points to the next.

Knowledge

Look up a concept or method, inspect an equation’s assumptions, or follow its References.

Architecture

See how physical inputs and package-owned results fit together. Keep intended handoffs separate from capabilities actually supplied by your selected package version.

How a design learns from evidence

flowchart TB
    Inputs["Physical design and<br/>declared assumptions"] --> Model["Model and study question"]
    Model --> Prediction["Simulation and<br/>interpretable observables"]
    Prediction --> Comparison["Compare with evidence"]
    Comparison --> Revision["Reviewed revision proposal"]
    Revision --> Inputs

A simulation predicts behavior under its declared inputs. A measurement adds experimental evidence with its own acquisition and calibration assumptions. Their comparison can suggest a revision; it does not silently overwrite the original model or evidence. The Architecture page expands this loop into package responsibilities and distinct simulation and instrument paths.

Read the claim as well as the citation

A citation identifies a source; it does not mean that the source supports every nearby equation. The prose distinguishes four kinds of contribution:

Category	What to look for
Direct quote	Short quoted words, an original source, and a source location. The words belong to that source.
Reorganized explanation	Primary support beside the relevant statement. The teaching order and explanation are ours, not a claim to quote the source.
This-page derivation	Starting definitions, model sources, assumptions, and the actual algebra. An extension is not attributed wholesale to a starting-model paper.
Proposal or engineering choice	The chosen convention or suggested use, its basis, and its status. A useful choice is not a universal physical law or an accepted target.

Follow a native citation to the page’s bibliography. Follow Knowledge References when you need its support range, source-device context, or an unresolved bibliographic identity. A source-support gap stays visible; it is not repaired by a decorative citation. Authors can use the Authoring Guide for the native syntax and page structure.

Package documentation

Use the selected version’s resources for actual operations and result meaning: OrPen SC PDK, SCGSim, SCNSim, and SCQSim. Legacy Workbench consumers retain their selected Runtime authority. A link does not establish that a package implements a target architecture or that two backends are interchangeable.

Project-specific designs, layouts, numerical bindings, and evidence remain with their classified source owners. This public site does not aggregate private project pages, package sites, or their search indexes. Its source is the private SCQ_Design repository; the reading site is SCQ Design Kit.