Argus SDK
Argus SDK is Esthien's developer toolkit for the Argus decision boundary. The 0.8
release line provides the enforcement-boundary protocol stack: typed proposals,
the policy language with load, validate, diff and compose, and the attestation
and evidence chain, with a Python API, the argus command-line interface, five
language bindings, and a ROS 2 safety node.
Releases
| Version | Status | Where |
|---|---|---|
| 0.8 | Current release line | PyPI, package esthien-argus-sdk |
| 0.7.4 | Previous release | PyPI, package esthien-argus-sdk |
The command surface of the 0.8 line is runtime-info, regression-eval,
evaluate, policy check, policy diff, evidence verify, and evidence
export. Install the current patch release with
pip install esthien-argus-sdk.
The release process validates these host tuples:
| Operating system | Architectures |
|---|---|
| Windows | x64, arm64 |
| macOS | x64, arm64 |
| Linux | x64, arm64 |
Each tuple has a recorded installation, CLI, Python API, and evaluation result. Host validation in continuous integration is a supported-host record, not a hardware support claim. No physical board, sensor, or instrument is part of the programme inventory, and a passing tuple does not establish measured hardware or field performance.
Release files carry Sigstore bundles named <artifact>.sigstore.json, verified
with scripts/verify_signature.py. The Windows installer is distributed
unsigned; Authenticode signing is an open item and requires no change to the
Python package.
Current evidence boundary
- The default evaluation path writes
digital_source_verificationevidence. - Output source hashes provide integrity traceability. They are not release signatures or a safety certification.
- The SDK does not establish hardware timing, thermal, power, functional-safety certification, production silicon, or customer-system qualification.
- Measured-evidence classes require a separately controlled measurement record and are not asserted by any release.
Distribution boundary
The product distribution path exposes a deliberately narrow command surface. It does not claim source-code secrecy, package encryption, hardware binding, security certification, or production key custody. Those controls require separately approved technical and operational evidence. Release signing is described under Releases.
Local development
Requirements:
- Python 3.11 or later
- A supported Python environment with NumPy, SciPy, and scikit-learn
python -m venv .venv
.\.venv\Scripts\Activate.ps1
python -m pip install --upgrade pip
python -m pip install ".[dev]"
argus --version
argus runtime-info
argus regression-eval --sample --out out\smoke
The default regression profile is packaged with the SDK, so the sample command works without relying on a source-tree-relative configuration path.
Python API
from argus import ConfidenceCoupledSafetyEnvelope, ProfileCompiler
compiler = ProfileCompiler()
envelope = ConfidenceCoupledSafetyEnvelope()
The public Python imports are versioned with the package. Product packages do not expose internal research, hardware-design, or roadmap material.
CLI
argus --version
argus runtime-info
argus regression-eval --sample --out <directory>
argus --help
runtime-info reports the detected host, the validation matrix, and the evidence
boundary of the installed release.
Candidate-release build
The candidate builder creates a controlled wheel, dependency inventory, and a machine-readable release manifest. It does not create a public source archive, sign an artifact, or approve distribution. Native packages are built and validated per host tuple.
python -m pip install build==1.6.1
python scripts\build_release.py --out C:\temp\argus-sdk-release-candidate
Any distribution remains blocked until the required host tuples pass, the dependency inventory receives security review, the artifact is signed with an approved release key, and a release-approval record is complete.
Repository layout
src/argus/ Python API and CLI
src/argus/resources/ Packaged reference profiles
tests/ Unit, integration, conformance, and formal checks
config/ Source configuration and research inputs
scripts/build_release.py Controlled candidate artifact builder
packaging/windows/ Windows installer source and command wrapper
.github/workflows/ Host verification and candidate-build workflows
The 0.8 surface
| Component | Description |
|---|---|
| Proposal protocol | Typed ProposedAction schema, canonical binary encoding, provenance chain |
| Policy language | Load, validate, evaluate, diff, and compose, with typed decisions and clauses |
| Authority capabilities | Scoped, expiring, single-use capability tokens checked at the boundary |
| Attestation protocol | Merkle-chained evidence records with signed batch roots and offline verification |
| Evidence export | The versioned exchange bundle an external evaluator verifies offline at L1, L2 and L3 |
| ROS 2 safety node | Subscribes to controller proposals, publishes bounded commands, exposes envelope state |
Each component ships with a recorded evidence class; the release that contains a component is the release that carries its claim.
License and contact
This repository is proprietary. Access does not grant a redistribution or commercial-use license. Contact Esthien Labs for evaluation or licensing discussion.
Metadata
Release files for esthien-argus-sdk 1.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 |
|---|---|---|---|---|
| esthien_argus_sdk-1.1.0.tar.gz | 200.5 kB | Without provenance | Details for esthien_argus_sdk-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| esthien_argus_sdk-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for esthien_argus_sdk-1.1.0-py3-none-any.whl |
Total release size: 409.5 kB
Release files / esthien_argus_sdk-1.1.0.tar.gz
| Download URL | esthien_argus_sdk-1.1.0.tar.gz |
|---|---|
| Size | 200.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d6981a7587802b692c3f58ee1dcd8c0feaec367aeea36df819574d0122632746
|
|
BLAKE2b-256 checksum How to use checksums |
7b734023846c233ecb11bed867f946863799ed44ed9b952481dbc8461da4cc91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.15
|
Release files / esthien_argus_sdk-1.1.0-py3-none-any.whl
| Download URL | esthien_argus_sdk-1.1.0-py3-none-any.whl |
|---|---|
| Size | 209.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8eb432aca5d0aec8bcf22e68cc8d89e6498dc8a979b725bf2e8f67370cfbc63
|
|
BLAKE2b-256 checksum How to use checksums |
eae385d690b1647814d9cb25c82f95150bddb4578ab507cf220bba4dc7d696eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.15
|
Security for esthien-argus-sdk 1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.