solvi.experimental¶
The experimental package itself: STATUS (for each piece: what it is, since when, what it is missing to graduate, the
script that measures it, the deadline), DEADLINE, and the helpers each piece uses to warn on import and to mark the
decisions it takes part in. Importing this package warns about nothing; each piece warns when it is imported. See
Experimental.
solvi.experimental — pieces that work and are tested but have not yet shown a measured gain (or a measured use) that the rest of solvi promises. Their API may change in any release, and each one either graduates or is removed by its deadline.
from solvi.experimental import STATUS
STATUS["lora"] # {"since": "0.7", "missing": "...", "script": None, "deadline": "a future release"}
What marks them:
- importing one warns once per process (
solvi.ExperimentalWarning, a UserWarning: silence it withwarnings.filterwarnings("ignore", category=solvi.ExperimentalWarning)); - a decision made by a System that uses one records it:
meta["experimental"]in the stored decision (the names, e.g.["lora"]), and the system report counts them; - nothing stable imports them, and the top-level
solvipackage does not re-export them. One command-line entry loads one on request:solvi hook(hooks).
Graduating needs a pre-registered bar, a script in benchmarks/ that measures it, the bar met and reviewed, no import
of anything experimental, a conformance check and a docs move; the old path is then kept for one release. A piece that
does not graduate by its deadline, or that measures negative, is removed and the negative result published. The
deadline set at 1.0 was 1.2; it passed with the pieces still here, so it now reads "a future release": no release is
named until one is decided.
This package itself imports none of them: import solvi.experimental does not warn.
warn_on_import ¶
Called at the top of each experimental module: one ExperimentalWarning, located at the import that loaded it — once per module per process (a module imported again, by a package walk or after it left sys.modules, is quiet: long runs keep their logs clean).
mark ¶
Say that system decides with the experimental piece name: its decisions record it (meta["experimental"]).
→ the system.
Counterexample refinement (experience)¶
RefinementSession implements bounded paid counterexample-guided iteration and optional observations.
ObservationOption, ObservationChoice and select_observation expose finite committee disagreement selection.
These APIs do not activate registry operations or authorize side effects. See experience
for verified-domain scope, source contracts, budget accounting and durable read reconciliation.