🔱 Sovereign AG: The Invisible Rail
Institutional-grade non-custodial AI fleet governance, cryptographic agent provisioning, and liability routing protocol.
🚀 3-Second Quickstart
To install the SDK and launch the onboarding guide, run these two commands in your terminal:
# Install the package
pip install svtp
# Launch the interactive guide
svtp
🛠️ The Master Command Suite
The Sovereign AG CLI provides full cryptographically anchored control over your local and cloud-based AI agent fleets:
1. Identity & Setup
svtp init— Generate a high-entropy local RSA-2048 non-repudiation keypair and claim a unique DID (did:svtp).svtp login— Initiate a secure OAuth2-style device-flow pairing handshake to claim and anchor your terminal hardware to your Web Dashboard account.svtp status— Perform a comprehensive terminal diagnostic check showing DID, claims status, and active passports.
2. Fleet Governance
svtp mint-passport— Mint an cryptographically signed liability passport for a new autonomous agent and save it locally.svtp list— Fetch the active infrastructure fleet status directly from the validator database ledger.svtp pulse— Monitor real-time telemetry heartbeats and trust indexes.svtp freeze— Issue an instant emergency global fleet pause command.
🛡️ Non-Custodial Security & Architecture
Sovereign AG is built on strict non-custodial architecture:
- Hardware-Anchored Identity: Your master private keys reside safely inside your local directory (
~/.svtp_identity.json) and never leave your machine. - OAuth2 Device Authorization: Terminal-to-dashboard pairing is performed using cryptographically isolated short-code polling over standard OIDC validation pipelines.
- Auditable Ledger: Every single agent registration and telemetry pulse is notarized to the physical append-only ledger (
sovereign_ledger.ndjson) for real-time auditability.
🔱 Sovereign AG | Institutional AI Infrastructure.
Metadata
Release files for svtp 1.21.25
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 |
|---|---|---|---|---|
| svtp-1.21.25.tar.gz | 32.7 kB | Without provenance | Details for svtp-1.21.25.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| svtp-1.21.25-py3-none-any.whl | Python 3 | none | any | Details for svtp-1.21.25-py3-none-any.whl |
Total release size: 64.4 kB
Release files / svtp-1.21.25.tar.gz
| Download URL | svtp-1.21.25.tar.gz |
|---|---|
| Size | 32.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ed2fddf3f4f3259b36b277d48a30c1cd639b38214866a15855523c965790511
|
|
BLAKE2b-256 checksum How to use checksums |
fb84aeec801bfdac3015be600e2f90cfd81d80b3f5c8b05a24c2067484d36ddb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Release files / svtp-1.21.25-py3-none-any.whl
| Download URL | svtp-1.21.25-py3-none-any.whl |
|---|---|
| Size | 31.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
af5fcc61861d7592070f1ac40661a2731636fbd5cd05df34a988fb578316c360
|
|
BLAKE2b-256 checksum How to use checksums |
4a4e07afad1558056a5a6a7e5133f21ea0ef1255d737bc7f81aaee27d3cc4bc9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Security for svtp 1.21.25
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.