glyphh
Ada for Python. Your models live in your Glyphh runtime; this calls them at the runtime's address with a runtime key.
pip install glyphh
from glyphh import Ada, AdaError
incidents = Ada().model("incidents") # GLYPHH_RUNTIME_URL, GLYPHH_RUNTIME_KEY; or Ada(url, key)
incidents.record({"error": {...}, "resolution": {...}}, outcome="raise circuit breaker")
r = incidents.decide({"error": {"what": {"class": "TimeoutError", "message": "payment gateway timed out"}}})
if r.done:
apply(r.data["fix"])
elif r.waiting: # needs_input or needs_approval: r.prompt says what
r = incidents.resume(r.run_id, ask_someone(r.prompt))
bot = incidents.query({...}, clearance=0.5) # a caller who may not see the secured layers
GLYPHH_RUNTIME_URL is the runtime's own address: https://<machine>.glyphh.app for one Glyphh hosts, or
https://<host> for one you host yourself. The key is made on the platform's Keys page (https://platform.glyphh.ai).
Ada.models(), Ada.deploy(repo, commit), Ada.run(run_id), Ada.log(run_id), Ada.cancel(run_id);
Model.call(function, inputs, version=, clearance=) reaches any function. A refusal raises AdaError(code, message, status): E_AUTH, E_LIMIT, E_MODEL_MISSING,
E_RUN_MISSING, E_BAD_REQUEST, E_UNREACHABLE. On a hosted runtime, a record past the plan's managed
precedents is a failed run whose data.code is E_LIMIT_PRECEDENTS. The contract both SDKs are tested against is
../../contract.
3.0.0: a new name, and a break
This package was glyphh-ada (from glyphh_ada import Ada) up to 0.4.0; it is glyphh now
(from glyphh import Ada). The API is the same; only the name and the import changed.
The name glyphh on PyPI is Glyphh's already: up to 2.6.7 it was the old HDC runtime (glyphh-runtime), a different
library with a different API. 3.0.0 is a major version so that nothing pinned to glyphh<3 picks this up by
surprise: code written for 2.x does not run on 3.x. Pin glyphh>=3 for this SDK.
glyphh-ada is deprecated and gets no new versions: pip uninstall glyphh-ada && pip install glyphh, then change
glyphh_ada to glyphh in your imports.
License
MIT (LICENSE).
1 maintainer
Metadata
1 maintainer
Release files for glyphh 3.0.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 | |
|---|---|---|---|---|
| glyphh-3.0.0.tar.gz | 7.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| glyphh-3.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.9 kB
Release files / glyphh-3.0.0.tar.gz
| Download URL | glyphh-3.0.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
adbfdf7293d52f8f9cbd04ff59540b3ccc588eb98f9a81c00a63db0fbf326670
|
|
BLAKE2b-256 checksum How to use checksums |
b0c8dabfa0134655fd2dad62157bdb55d5539f3912117ab5d556f4c3bf999376
|
| 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 Oct 18, 2026.
Transparency logRelease files / glyphh-3.0.0-py3-none-any.whl
| Download URL | glyphh-3.0.0-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
468143934540529bcb1ac04e7fcaf80cdb1b9206cd023c4572cb079e16714fa5
|
|
BLAKE2b-256 checksum How to use checksums |
76e54e526c4c1a6a6f7d362b9f3ba0008d41bb7fcf977e8110f84b71694592c1
|
| 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 Oct 18, 2026.
Transparency logSecurity for glyphh 3.0.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for glyphh-3.0.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 18, 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.
