Rename the project to Maiman Studio

"OpenOptiSim" sat one letter away from OptiSystem, the commercial tool this
project cites as its benchmark — a bad place to stand for something that
argues its models from published literature rather than from a competitor.
The architecture document flagged it and said to rename while renaming was
still cheap; before the first public release, with no dependents and no
published package, is exactly that moment.

Theodore Maiman built the first working laser in 1960, so the name points at
the physics instead of at anyone else's product.

The rename goes all the way down rather than stopping at the display name:
the Python package is `maiman`, project files are `.maiman`, and the schema
key is `maiman_version`. Leaving `oosim` underneath would have meant carrying
the old name in every import line and every saved file forever.

Screenshots are regenerated so the README shows the wordmark that ships, and
the GitHub repository is renamed to match; old links redirect.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: ehsun-sh

DESIGN.md

@@ -1,6 +1,6 @@
 # Design
 
-The visual and interaction record for OpenOptiSim's interface. It exists because
+The visual and interaction record for Maiman Studio's interface. It exists because
 [`docs/ui-mockup.html`](docs/ui-mockup.html) is a *build*, and a build without a
 written rationale is a set of numbers nobody can argue with later. Everything
 here was decided against the audience and use scene in [PRODUCT.md](PRODUCT.md);

PRODUCT.md

@@ -1,4 +1,4 @@
-# OpenOptiSim — product context
+# Maiman Studio — product context
 
 ## What it is
 
@@ -46,14 +46,14 @@ constantly and any latency compounds.
 2. Edit component parameters with their real units visible.
 3. Run, and show progress on a run that takes seconds to minutes.
 4. Display results: eye diagram, spectrum, BER curves, sweep results.
-5. Open and save `.oosim` projects.
+5. Open and save `.maiman` projects.
 6. Sweep a parameter and plot the curve.
 
 ## Constraints that are already decided
 
 * **The GUI is a client of the public Python API.** If a feature is not reachable from Python, it
   does not exist. The GUI gets no privileged access.
-* **The component palette is generated** from `oosim.manifests()`, never hand-written, so it
+* **The component palette is generated** from `maiman.manifests()`, never hand-written, so it
   cannot drift from what the engine actually offers.
 * **Result data is reduced in the engine**, never in the browser. An eye diagram arrives as a
   binned histogram of fixed size; the browser never receives a raw sample buffer.

README.md

@@ -1,8 +1,8 @@
-# OpenOptiSim
+# Maiman Studio
 
 **An open-source, modular simulator for optical communication links and photonic systems.**
 
-[![CI](https://github.com/ehsun-sh/OpenOptisim/actions/workflows/ci.yml/badge.svg)](https://github.com/ehsun-sh/OpenOptisim/actions/workflows/ci.yml)
+[![CI](https://github.com/ehsun-sh/maiman-studio/actions/workflows/ci.yml/badge.svg)](https://github.com/ehsun-sh/maiman-studio/actions/workflows/ci.yml)
 ![status](https://img.shields.io/badge/status-pre--alpha-orange)
 ![license](https://img.shields.io/badge/license-Apache--2.0-blue)
 ![python](https://img.shields.io/badge/python-3.11%2B-blue)
@@ -49,7 +49,7 @@ that would let you press Run and get a new one. Open
 [`docs/ui-mockup.html`](docs/ui-mockup.html) in a browser to click through it, and
 [DESIGN.md](DESIGN.md) for why it looks like this.
 
-![The OpenOptiSim schematic editor on its paper ground](docs/images/studio-paper.png)
+![The Maiman Studio schematic editor on its paper ground](docs/images/studio-paper.png)
 
 It ships two grounds and defaults to paper, because a schematic is a document before it is a
 screen and its plots leave the tool for reports and papers. Graphite is one click away:
@@ -70,8 +70,8 @@ pip install -e ".[dev]" && pytest
 ```
 
 ```python
-from oosim import SimulationContext, Graph
-from oosim.components import CWLaser, Combiner, Fiber, PowerMeter
+from maiman import SimulationContext, Graph
+from maiman.components import CWLaser, Combiner, Fiber, PowerMeter
 
 ctx = SimulationContext(bit_rate=10e9, samples_per_symbol=16, sequence_length=64)
 g = Graph(ctx)
@@ -131,7 +131,7 @@ filter and analyzer all have to agree for that to hold; it is
 [a test](tests/test_ber.py), not a coincidence.
 
 Both curves come from `sweep()`, and the same script writes the schematic to
-[`examples/ook_link.oosim`](examples/ook_link.oosim) — versioned JSON, diffable, runnable headless.
+[`examples/ook_link.maiman`](examples/ook_link.maiman) — versioned JSON, diffable, runnable headless.
 
 ### Coherent
 
@@ -155,7 +155,7 @@ and never look back.
 
 Nothing here is configured to come out right. The shot-noise-limited SNR is asserted against
 `R·P/(2qB)`, the counted symbol errors against
-[`ser_qam()`](src/oosim/modulation.py), and the modulator's 3 dB against `10·log10(2)`.
+[`ser_qam()`](src/maiman/modulation.py), and the modulator's 3 dB against `10·log10(2)`.
 
 ### What carrier recovery is for
 
@@ -171,7 +171,7 @@ tellingly, **launching more power stops helping**:
 
 Twelve dB of extra power buys 1.3 dB. Laser phase noise is a random walk, so it is not removable by
 subtracting a constant or a line, and it puts a ceiling on SNR that no power budget lifts.
-[`CarrierRecovery`](src/oosim/components/coherent.py) removes the ceiling using the blind phase
+[`CarrierRecovery`](src/maiman/components/coherent.py) removes the ceiling using the blind phase
 search of Pfau et al. Both halves of that claim are [asserted](tests/test_dsp.py) — the second
 would be meaningless without the first.
 
@@ -245,7 +245,7 @@ rotation    without equaliser              with equaliser
 
 Past a few degrees the unequalised branches are not degraded — they carry no recoverable data at
 all, because each is a *mixture* of both tributaries. The
-[butterfly equaliser](src/oosim/dsp.py) separates them blind, with no training sequence anywhere in
+[butterfly equaliser](src/maiman/dsp.py) separates them blind, with no training sequence anywhere in
 the link. Read the two end rows together: 90° is a clean swap rather than a mixture, so it needs no
 equaliser at all and simply delivers the tributaries the other way round — which is also why
 nothing blind can label them, and why a real link recovers the pairing from framing.
@@ -374,7 +374,7 @@ exactly zero in double precision, which would make rejection infinite and a chai
 accumulate no crosstalk at all. Real hardware specifies 30–50 dB and it is that floor, not the
 shape, that decides what leaks through a long line of them.
 
-The **[OSA](src/oosim/components/filters.py)** finally makes the signal model visible: bands and
+The **[OSA](src/maiman/components/filters.py)** finally makes the signal model visible: bands and
 noise bins rendered onto one grid, the way an instrument shows them. Its resolution bandwidth is
 not cosmetic — widening it raises the ASE trace decibel for decibel and leaves a carrier exactly
 where it is, which is the clearest demonstration of why OSNR needs a stated reference bandwidth.
@@ -469,7 +469,7 @@ What does not exist is a single coherent tool that puts them behind a usable int
 sound signal representation underneath.
 
 So the gap is **integration and user experience**, not numerics. That shapes the whole strategy:
-where a mature open-source kernel exists, OpenOptiSim wraps or depends on it rather than
+where a mature open-source kernel exists, Maiman Studio wraps or depends on it rather than
 rewriting it. The value added here is the data model, the execution engine, the component
 library, and the UI.
 
@@ -515,7 +515,7 @@ in the [architecture document](docs/ARCHITECTURE.md).
                     └───────────────────┬──────────────────┘
  ┌──────────────────────────────────────▼───────────────────────────────────────┐
  │                             Public Python API                                 │
- │        oosim.Graph · Component · run() · sweep()                              │
+ │        maiman.Graph · Component · run() · sweep()                              │
  └──────────────┬─────────────────────────────────────┬─────────────────────────┘
  ┌──────────────▼───────────────┐    ┌────────────────▼─────────────────┐
  │      Component Library       │◄──►│         Execution Engine         │
@@ -533,7 +533,7 @@ reachable from Python, it does not exist.**
 
 ## The core data model
 
-The part most worth reviewing — see [`src/oosim/signals.py`](src/oosim/signals.py). An optical
+The part most worth reviewing — see [`src/maiman/signals.py`](src/maiman/signals.py). An optical
 signal is not one array of numbers:
 
 ```python
@@ -574,7 +574,7 @@ time window, and results are reproducible.
 
 | Phase | Scope | Estimate¹ |
 | :--- | :--- | :--- |
-| **0 — Foundations** ✅ | Signal model, context, port types, component base, registry, scheduler, `.oosim` project format, sweeps, CI | ~1 month |
+| **0 — Foundations** ✅ | Signal model, context, port types, component base, registry, scheduler, `.maiman` project format, sweeps, CI | ~1 month |
 | **1 — MVP: linear link** *(essentially done)* | ✅ PRBS → NRZ → laser → MZM → fiber (α + CD) → PIN → filter → eye/Q/BER, validated end to end. **Python only, no GUI.** | ~2–3 months |
 | **1.5 — Nonlinear & amplified** ✅ | Adaptive-step SSFM, Kerr, EDFA with ASE, OSNR, PMD, APD | ~2 months |
 | **2 — Coherent transceiver** ✅ | Gray-coded M-QAM to 256, IQ modulator with bias and quadrature error, 90° hybrid, balanced detection, blind carrier phase recovery, dual polarization with a blind butterfly equaliser, root-raised-cosine shaping and matched filtering, differential quadrant encoding, receiver-side dispersion compensation over spans to 1000 km, EVM/MER, constellation diagram, validated against closed-form SER | ~3 months |
@@ -646,16 +646,16 @@ docstring — never from inspection of commercial tools.
 The core is small enough that changing it is still cheap, which makes right now the most useful
 time to push back on it. Most valuable first:
 
-* **Review the signal model and scheduler** — [`src/oosim/signals.py`](src/oosim/signals.py),
-  [`src/oosim/graph.py`](src/oosim/graph.py), and §3–§4 of the
+* **Review the signal model and scheduler** — [`src/maiman/signals.py`](src/maiman/signals.py),
+  [`src/maiman/graph.py`](src/maiman/graph.py), and §3–§4 of the
   [architecture document](docs/ARCHITECTURE.md). If something there is wrong, it is far cheaper
   to fix now than after fifty components depend on it.
 * **Tell us if this duplicates existing work.** If a project already does this well, that is worth
   knowing before several months go into it.
 * **Describe your use case.** Which components, which measurements, what you currently use and
   what frustrates you about it.
 * **Add a component.** A component is a Python class with declared parameters and typed ports —
-  see [`src/oosim/components/`](src/oosim/components/) for the pattern. Every physics block needs
+  see [`src/maiman/components/`](src/maiman/components/) for the pattern. Every physics block needs
   a test against a closed-form result; a component without one will not be merged.
 
 Open an issue for any of the above.

docs/ARCHITECTURE.md

@@ -1,4 +1,4 @@
-# OpenOptiSim — Architecture & Roadmap
+# Maiman Studio — Architecture & Roadmap
 
 > **Vision:** An open-source, modular platform for system-level simulation of optical
 > communication links and photonic circuits — the tool that fills the gap between
@@ -82,7 +82,7 @@ it rather than rewriting it.
                                         │  in-process
  ┌──────────────────────────────────────▼───────────────────────────────────────┐
  │                             Public Python API                                 │
- │        oosim.Graph · Component · run() · sweep() · analysis helpers           │
+ │        maiman.Graph · Component · run() · sweep() · analysis helpers           │
  │                    (this is the product for scripting users)                  │
  └──────────────┬─────────────────────────────────────┬─────────────────────────┘
                 │                                     │
@@ -390,15 +390,15 @@ never with exact float equality.
 
 ## 8. Project File Format
 
-The saved schematic is a versioned, human-readable, git-diffable JSON document (`.oosim`):
+The saved schematic is a versioned, human-readable, git-diffable JSON document (`.maiman`):
 
 ```json
 {
   "schema_version": 1,
   "context": { "bit_rate": 10e9, "samples_per_symbol": 16,
                "sequence_length": 1024, "seed": 42 },
   "nodes": [
-    { "id": "laser1", "type": "oosim.sources.CWLaser",
+    { "id": "laser1", "type": "maiman.sources.CWLaser",
       "params": { "power": 10.0, "wavelength": 1550.0 },
       "ui": { "x": 100, "y": 200 } }
   ],
@@ -441,7 +441,7 @@ Timelines assume one developer working part-time. They are estimates, not commit
 Repository, license, CI, packaging. `SimulationContext`, signal types, port typing, component
 base class and registry, scheduler, result store, project file format, test harness.
 
-*Exit criterion:* a two-block graph runs end-to-end from Python and from a `.oosim` file.
+*Exit criterion:* a two-block graph runs end-to-end from Python and from a `.maiman` file.
 No physics yet — and that is the point.
 
 ### Phase 1 — MVP: linear optical link (~2–3 months)
@@ -501,9 +501,11 @@ top-level link simulation remains dataflow.
   (Agrawal, *Nonlinear Fiber Optics*; ITU-T G.652, G.694.1; relevant IEEE 802.3 clauses) and
   cite the source in each component's docstring. This protects the project and makes the models
   reviewable.
-* **Naming:** "OpenOptiSim" sits close to *OptiSystem* / Optiwave for a project that explicitly
-  cites it as a benchmark. Worth choosing a more distinct name before the first public release,
-  while renaming is still cheap.
+* **Naming:** the project was renamed from "OpenOptiSim" to **Maiman Studio** before the first
+  public release, while renaming was still cheap. The old name sat close to *OptiSystem* /
+  Optiwave for a project that explicitly cites it as a benchmark; the new one carries no such
+  echo. Theodore Maiman built the first working laser in 1960 — the name points at the physics,
+  not at a competitor. The Python package is `maiman` and project files are `.maiman`.
 
 ---
 
@@ -516,7 +518,7 @@ top-level link simulation remains dataflow.
    generation.
 4. Implement the scheduler (topological sort, type validation, memory release) and prove it on a
    trivial pass-through graph.
-5. Define and freeze `.oosim` schema v1; round-trip test.
+5. Define and freeze `.maiman` schema v1; round-trip test.
 6. Build the Phase 1 chain: PRBS → NRZ → CW Laser → MZM → linear fiber → PIN → BER.
 7. Stand up the validation suite from §7 in CI, with every tolerance justified in a comment.
 8. Write the first example notebook — for a scientific open-source tool, the examples are the

docs/capture_screenshots.py

@@ -40,7 +40,7 @@
 #: rendering path, so a shorter budget yields a blank results dock.
 TIME_BUDGET_MS = 4000
 
-THEME_DEFAULT = 'sessionStorage.getItem("oosim-theme") || "light"'
+THEME_DEFAULT = 'sessionStorage.getItem("maiman-theme") || "light"'
 
 CANDIDATES = (
     r"C:\Program Files\Google\Chrome\Application\chrome.exe",