+
+
+
+
+
+
# Amicode
-A VS Code extension for agentic quantum-control pulse optimization — natural-language chat → LLM-authored Julia solve (Piccolo/Piccolissimo) → live run inspector → per-lab pulse catalog. Deployed onto partner-lab machines; a vendored [opencode](https://github.com/sst/opencode) binary provides the chat/LLM harness.
+### Quantum optimal control, driven by conversation.
+
+Describe the gate you want in plain language. Amicode designs the pulse, runs the
+solve, and shows you the result — without leaving your editor.
+
+A VS Code extension · built on [Piccolo.jl](https://github.com/harmoniqs/Piccolo.jl) · chat harness vendored from [opencode](https://github.com/sst/opencode)
+
+
+
+---
+
+Amicode turns a natural-language description of a control problem into an
+LLM-authored Julia optimization, runs it, and streams the result back into native
+editor panels. The physics, the solver idioms, and your lab's accumulated
+knowledge all ride along as context — so the script it writes is correct by
+construction, not by luck.
+
+## What it does
-> ## ⚠️ Source of truth = the design docs, not this code
->
-> This repository's **authoritative design lives in the `harmoniqs/amico` vault**, in this order of authority (architecture → context → diagrams → interfaces → planning → plans → specs). When code and docs disagree, **the docs win.** Scope, architecture, and interface changes happen in the vault docs first, then flow to code and issues.
+**Conversational solves.** Ask for a gate or a state preparation; Amicode writes a
+self-contained Piccolo script, runs the Ipopt solve, and captures the result. No
+boilerplate, no parameter-guessing.
-| # | Authority | Location in `harmoniqs/amico` |
-|---|-----------|------------------------------|
-| 1 | **Architecture + diagrams + interfaces** (container, solve lifecycle, chat→solve→inspector sequence, run-dir contract, provisioning flow, module decomposition §5, dependency graph §7) | [`vault/specs/spec-20260529-amicode-architecture.md`](https://github.com/harmoniqs/amico/blob/main/vault/specs/spec-20260529-amicode-architecture.md) |
-| 2 | **Context / requirements** (problem, solution, user stories S1–S38 with acceptance criteria, stable interface contracts, risks) | [`vault/specs/spec-20260529-amicode-prd.md`](https://github.com/harmoniqs/amico/blob/main/vault/specs/spec-20260529-amicode-prd.md) |
-| 3 | **Decisions** (decision log D1–D10; 157 resolved/deferred open questions) | [`vault/specs/spec-20260529-amicode-open-questions.md`](https://github.com/harmoniqs/amico/blob/main/vault/specs/spec-20260529-amicode-open-questions.md) |
-| 4 | **Project-management plan** (phases β→4, tasks β.1–4.2, per-phase Definition of Done, dependency-ordered parallel-engineer schedule, ~56-pd estimate) | [`vault/plans/plan-20260603-124231-amicode-phased-build.md`](https://github.com/harmoniqs/amico/blob/main/vault/plans/plan-20260603-124231-amicode-phased-build.md) |
-| 5 | **Review / QA** (60-agent swarm review; consolidated findings) | [`vault/reviews/review-20260603-amicode-plan-swarm.md`](https://github.com/harmoniqs/amico/blob/main/vault/reviews/review-20260603-amicode-plan-swarm.md) |
+**Physics that ships with the tool.** Platform references for neutral-atom Rydberg,
+transmon, fluxonium, trapped-ion, and bosonic systems load on demand — the
+Hamiltonians, drive conventions, and construction patterns are inlined into each
+script so it stands on its own.
-Access requires the `harmoniqs/amico` vault repo. (We chose reference-only over copying the docs in, to keep a single source of truth and avoid drift.)
+**Your knowledge, mounted.** Amicode reads your **Armonia** — the stack of vaults
+you mount (personal, team, public). Notes, specs, experiment history, and your
+pulse catalog become first-class context the assistant plans against.
-## Status of the code in this repo
+**A live run inspector.** Watch a solve converge in real time: overlaid pulse
+plots, fidelity and constraint-violation traces, per-run metrics. Every run is
+captured and revisitable.
-`src/` is the **v2 spike** — a working chat→solve→inspector prototype (CLI-direct, after the pivot away from MCP + callback-HTTP). It is a **starting point, not the authority.** Per the design audit (vault decision log D9/D10), the following are explicitly in flux or superseded — do not treat them as canonical:
+**A pulse catalog.** A versioned, warm-startable library of your best pulses —
+retrieve the incumbent for a `(platform, gate)`, warm-start from it, and promote a
+new best when you beat it.
-- **`bin/amico-run`** — being re-architected into the **D9 thin orchestrator** (spawns `julia