Manuscript Em04-A@2 · Em04-A-v2.tex · section · f5b28abc

Reported source correspondences and extraction requirements

Reported source correspondences and extraction requirements · lines 1708–1757

The following table records the implementation descriptions in the supplied verification plan. It is a model-contract checklist, not a completed source audit.

{}1.15

Mathematical contract	Reported implementation correspondence
Excited basis vector $∣1 ⟩$	`basis(2, 1)`
Lowering matrix $∣0 ⟩ ⟨ 1∣$	`destroy(2)`; verify its entries and tensor placement
One-excitation hopping $J$	`0.5 * J` multiplying $X X + Y Y$
Relaxation $γ_{r} a_{k}$	Zero-occupation downward collapse operator
Dephasing $γ_{d} /2 Z_{k}$	Reported local dephasing collapse operator; verify prefactor
Localized preparation	`initial_state(N, "single")`
No bath raising	`n_thermal == 0`
Uniform rates	Common relaxation and dephasing parameters
Position quadrature	Reported composite trapezoidal construction; verify cells, endpoints, weights, and bin assignments

For every row, a completed audit must record the export hash, source file, line range, actual expression, checked restriction, and outcome. The sentence “agrees by source-level inspection” is admissible only after that record exists.

The plan also reports notebook commands such as !pip and !cp, and a second from __future__ import annotations inside a combined export. Preserve the export unchanged. Extract ordinary Python modules with any future import at the beginning of each module; isolate notebook installation and copy commands from model execution. The presence and exact locations of these reported export issues also require source inspection.