Engines

Everything is organized as engines — self-contained projects with their own package (theory + architecture), campaigns, runs, and notes.

There is no customer-projects layer yet. When a customer arrives, fork a similar engine (engines/<customer>_v1) and iterate on that fork.

Assembled 2026-07-27 22:48 UTC.

Quan–Lončar v1

Status: stable · quan_loncar_v1

Air-cladded Si nanobeam · trustworthy optimizer

Path: engines/quan_loncar_v1/

• Engine project
• Notes
• Overview
• Architecture
• Trust contract
• Validation evidence
• Changelog
• Campaigns

Design23 v1

Status: stable · design23_v1

Hybrid multilayer nanobeam · dual-resolution BFGS

Path: engines/design23_v1/

• Engine project
• Notes
• Overview
• Validation
• Subtracted real-axis QNM gate
• Absolute QNM integration gate
• Continuous radiation gate
• Repaired optimizer FDTD gate

Majumdar lab

Status: lab · majumdar_lab

Multilayer nanobeam lab stack (v0.3.1 package)

Path: engines/majumdar_lab/

• Engine project
• Notes
• Overview
• Changelog
• Phase 16 validation
• Performance and TE0
• Runs
• Phase theory archive

Atom Fishbone Coupler

Status: lab · atom_fishbone_coupler

Si₃N₄ air-clad slot waveguide + fishbone ridges (from scratch; working name)

Path: engines/atom_fishbone_coupler/

• Engine project
• Geometry schematic
• Notes
• Package overview
• 2026-07-27 — Unit cell geometry schematic (pre-simulation)
• Runs

Fork policy

cp -a engines/design23_v1 engines/acme_nanobeam_v1
# customize package + campaigns + notes; keep runs local to the fork

Redundant copies are intentional: each project keeps a cleanly separated theory, architecture, and result history.