ashr-manifold
pip install ashr-manifold # published releases (PyPI)
pip install ./sdk # from a checkout
The import name stays ashr_sdk either way. Releases publish via
.github/workflows/publishing.yaml (PyPI Trusted Publisher): bump version
in sdk/pyproject.toml, then gh release create sdk-v<version>.
from ashr_sdk import AshrClient
ashr = AshrClient() # reads ASHR_BASE_URL and ASHR_API_KEY
experiment = ashr.experiments.run(
name="invoice-v5",
task="invoice_extraction",
dataset="ds_...",
models=["org/model-a", "org/model-b"],
training_config={"epochs": 1, "eval_batch_size": 8},
gates={"field_f1": 0.8},
)
See ../docs/sdk.md for task-agnostic observation capture, optional artifact
links, evaluation, promotion, monitoring, errors, and model configuration.
Continuous learning and progressive rollout
# validator outcomes label observations like machine reviewers
ashr.checks([{"interaction_id": iid,
"checks": {"compile": True, "scene_load": True}}],
reviewer="game-engine")
# one call: freeze -> environment -> simultaneous runs -> halving ->
# gates -> incumbent-protected promotion to the alias
report = ashr.learning_loops.run(
task="game_generation",
candidates=[{"model_source_id": src["id"], "recipe": "sft_lora"}],
halving={"metric": "proxy_score", "at_progress": 0.5, "kill_fraction": 0.5},
)
environment = ashr.environments.build(
task="game_generation",
dataset_id="ds_games_v1",
reward_spec={"compile": 1, "scene_load": 1, "runtime_error": -5},
)
ashr.learning_loops.configure(
task="game_generation",
environment_id=environment["id"],
config={
"trigger_after_reviewed": 500,
"trigger_every_days": 7,
"benchmark_incumbent": True,
"auto_train": True,
"auto_rollout": False,
},
)
ashr.router.configure(
task="game_generation",
incumbent_model_id="m_current",
challenger_model_id="m_candidate",
traffic_percent=5,
gates={"compile_rate_delta": .03, "runtime_success": .99},
)
assignment = ashr.router.decide(
task="game_generation", request_key=request_id)
# Serve assignment["model_id"], then attach the delayed business result:
ashr.router.outcome(assignment["id"], {"compiled": True, "reward": 1})
Routing is deterministic per policy and request key. Setting traffic to zero is an immediate control-plane rollback to the incumbent:
ashr.router.set_traffic("game_generation", 0)
Metadata
Release files for ashr-manifold 0.5.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 | |
|---|---|---|---|
| ashr_manifold-0.5.0.tar.gz | 12.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ashr_manifold-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.7 kB
Release files / ashr_manifold-0.5.0.tar.gz
| Download URL | ashr_manifold-0.5.0.tar.gz |
|---|---|
| Size | 12.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
377795ef3395343cb53b6889538cee44d24ecbb7f05d262f31d5ca0a2ba5456d
|
|
BLAKE2b-256 checksum How to use checksums |
201174cf1d7a910f0f60ccd8eefc3d36ce2533bf66230d7c5a04ebf69989fb8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 18, 2026.
Transparency logRelease files / ashr_manifold-0.5.0-py3-none-any.whl
| Download URL | ashr_manifold-0.5.0-py3-none-any.whl |
|---|---|
| Size | 12.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aca76e174d8c313cf66cd580399301d38ae131494a8d66e220a7d876f1894e9a
|
|
BLAKE2b-256 checksum How to use checksums |
fbaa4442506b1f6af491dd238078f6e69335ccaab995688c5df56a0b75efb6b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 18, 2026.
Transparency log