Illustrative · unadmitted · revision 1
Femtosecond-written perovskite/LiNbO3/chalcogenide exact optical computing cell
This is a proposed definition for criticism. It is not an experiment run, result, evidence claim, canonical admission, inventory record, or procurement request.
- Stable identifier
fs-written-exact-optical-computing- Kind
- physical
- Intent
- calibration
Exact target
- external-reference ·
fs-written-exact-computing — operator-supplied fs-written perovskite, LiNbO3, and chalcogenide exact computing proposal
Minimal decisive protocol
Finite-state exact operator readout across three material variants
Write the same finite optical circuit separately in perovskite, LiNbO3, and chalcogenide variants, inject enumerated basis states, and compare decoded outputs against an exact symbolic oracle with calibrated phase and loss accounting.
- Write and inspect matched finite circuits in the perovskite, LiNbO3, and chalcogenide variants.
- Calibrate coupling, phase, and detector response for each material variant.
- Run all basis states and selected superpositions.
- Compare raw complex outputs with the exact oracle and retain variant-specific controls.
Decision rule: The finite operator is supported only if every declared basis output in each material variant meets the exact oracle tolerance and controls isolate crosstalk.
Controls
- negative: Bypass the written circuit. (written operator; Output should match the bypass matrix, not the candidate operator.)
Observables and units
Observables| Observable | Units | Measurement | Uncertainty reporting |
|---|
| operator entry error | dimensionless | complex matrix difference to exact oracle | include phase and loss covariance |
|---|
Calibration and repetitions
- written-path phase: interferometric reference — phase drift below oracle comparison tolerance (rad)
Replicate unit: basis-state injection; minimum 24, independent 6.
Randomization: basis and circuit section order randomized
Stopping rule: complete declared basis set
Uncertainty: writing variation, coupling, phase, detector noise, and loss; complex covariance through oracle comparison; retain raw traces and exact code commit
Success and falsifiers
Success
- Decoded finite operator agrees with the exact symbolic oracle within tolerance. (maximum entry error <= predeclared tolerance dimensionless)
Falsifiers
- A basis-state output cannot be distinguished from a bypass or crosstalk model at the declared precision. (oracle residual > predeclared bound dimensionless)
Required capability groups
- writing · required, any-one, quantity 1: femtosecond direct-write platform with metrology (system) — repeatable 3-D placement and write log
Related capability types: Femtosecond 3-D writing and metrology platform
Confounds and raw artifacts
- writing changes material response during the run: interleave reference waveguides; mitigation: blockwise recalibration
- complex-output-trace · HDF5 and oracle JSON · retain raw output and write mask
Nonclaims
- Femtosecond writing alone does not establish exact computation in perovskite, LiNbO3, or chalcogenide.
- No material, device, or scale claim is admitted; the three variants remain illustrative only.
Provenance boundary
The citation supplies direct-writing context only; it does not support exact computation, any named material variant, or a device claim.
Agent-readable JSON · History · Provenance · Back to experiments