Index · Data-T URLs only
Libraries and documents
Lumen Lattice does not republish another vendor’s libraries. The objects below are Data-T specifications. Each row is a document on this site. Runtime execution is reached through Data-T API access, which returns an engine field naming the product that ran.
Product documents
These URLs are the library contracts. A ‘library’ in 1.0 is a stable document plus the request fields it defines. There is no separate binary to mirror, and no instruction sheet copied from an accelerator vendor.
- https://www.data-t.uk/products/lumen-lattice — family overview
- https://www.data-t.uk/products/lumen-lattice/lumen-state — Lumen State 1.0, amplitude register
- https://www.data-t.uk/products/lumen-lattice/lumen-weave — Lumen Weave 1.0, tensor lattice
- https://www.data-t.uk/products/lumen-lattice/lumen-drift — Lumen Drift 1.0, density operators
- https://www.data-t.uk/products/lumen-lattice/lumen-trace — Lumen Trace 1.0, Pauli propagation
Concept documents
Concept pages fix vocabulary so product pages do not drift. They are normative for 1.0 wording.
- https://www.data-t.uk/products/lumen-lattice/amplitudes — amplitudes, bases, measurement
- https://www.data-t.uk/products/lumen-lattice/contraction — plans, slicing, bond limits
- https://www.data-t.uk/products/lumen-lattice/noise — channels and purity
- https://www.data-t.uk/products/lumen-lattice/observables — expectations and variational hand-off
- https://www.data-t.uk/products/lumen-lattice/sampling — shots versus exact weights
- https://www.data-t.uk/products/lumen-lattice/memory-model — forecasts, ceilings, dtype
- https://www.data-t.uk/products/lumen-lattice/reference — methods, errors, Pauli table
Request skeleton
A call names the product only as a preference. The router may select another engine and must disclose it. The body below is the 1.0 shape. Field names are Data-T’s.
POST /api/lumen/query with circuit.gates[], circuit.wires, query.kind (snapshot | probability | shots | expectation | reduced), query.observable when needed, noise.channels[] when needed, and options.dtype, options.engine, options.seed. The response carries engine, forecastBytes, discardedMass, and result. This path is specified here; enablement follows API access rather than a copied SDK installer.
All documents
- OverviewLumen Lattice
- Lumen StateLumen State 1.0
- Lumen WeaveLumen Weave 1.0
- Lumen DriftLumen Drift 1.0
- Lumen TraceLumen Trace 1.0
- AmplitudesAmplitudes and measurement
- ContractionContraction and bond limits
- NoiseNoise, channels, and purity
- ObservablesObservables and expectations
- SamplingSampling and shots
- MemoryMemory model and refusal
- ReferenceReference