- Step through: the engine's debugger in the tab (wasm engine_debug) or the app, a slider forward and back, the next step named with its line and its gate marked on the diagram; each qubit's phase disk with a purity ring and its Bloch sphere in plain SVG; the amplitude and phase table; the reduced state of chosen qubits; under noise the noisy state against the noiseless one; and the branch tree with its weights, a branch chosen to put the path on it. - Editing by the drawing: a palette gate dropped on a wire, a drawn gate dragged to other wires or places, or moved and deleted from the keyboard, each made by the engine in the program's text (engine_visual_edit) and recorded as the reader's edit; a gate its statement does not make alone is refused with its line. - The diagram described to a screen reader in the engine's words, and the drawing saved as the engine's SVG or LaTeX (engine_picture). - The desktop app answers the same calls natively (debug off the window's thread). The wasm workflow's counts are 16 native and 9 under Node; the Studio's browser test checks each view. Co-Authored-By: Claude Opus 5.5 <[email protected]>
6 lines
254 B
JSON
6 lines
254 B
JSON
{
|
|
"identifier": "default",
|
|
"description": "The Studio's window: the core bridge, by which it calls the app's own commands (run, plan, lint, critique, shortcuts, draw, debug, verify, save).",
|
|
"windows": ["main"],
|
|
"permissions": ["core:default"]
|
|
}
|