experiment-core
Still in active development.
Small, domain-neutral contracts and a local runtime for supervised experiments: bounded operations, resource ownership, durable intent/result records, cancellation, explicit approvals and immutable artifacts.
pip install experiment-core
Python 3.10+; depends only on jsonschema. No LDCon, agentbridge, provider CLI
or hardware dependency. Host applications supply authentication and physical
device adapters; unknown writes are never replayed automatically.
Tests cover schemas, lifecycle transitions, resource conflicts, cancellation,
approval/adoption and recovery of recorded operations. Run python -m pytest -q.
The process-locking runtime is tested on Linux.
Metadata
Release files for experiment-core 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| experiment_core-0.1.0.tar.gz | 48.7 kB | With provenance | Details for experiment_core-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| experiment_core-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for experiment_core-0.1.0-py3-none-any.whl |
Total release size: 86.1 kB
Release files / experiment_core-0.1.0.tar.gz
| Download URL | experiment_core-0.1.0.tar.gz |
|---|---|
| Size | 48.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47cc28005d29893b4a5c83641967ca18ae3ae236f0951902b6b988b530a79382
|
|
BLAKE2b-256 checksum How to use checksums |
1ced1f9d1ff657ff72c32c4c563d2c7ee25709f0d552465e321365a42d7cb0a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logRelease files / experiment_core-0.1.0-py3-none-any.whl
| Download URL | experiment_core-0.1.0-py3-none-any.whl |
|---|---|
| Size | 37.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d1d5417e049589d7e68f7ca811af03a2c7c20adbbf7104c4466565ce63d3188
|
|
BLAKE2b-256 checksum How to use checksums |
f871595f8d6e601e7c3b48edc56a7044a190b32de383fd1b518696a66b78f00a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logSecurity for experiment-core 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for experiment_core-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.