vivary
vivary 0.2.0 is the source version and provides one install for the Vivary CLI
suite:
python -m pip install vivary
Release verification builds local wheels and proves their composition without consulting a registry:
python -m pip install --no-index --find-links <wheelhouse> vivary
Published versions live in the root release status. Pin an exact version when you need to reproduce a specific composition.
The install includes:
create-vivary>=0.4.3: thin greenfield init and deterministic brownfield adoption.vivary-tropo>=0.5.4: typed governed context and local retrieval.vivary-strato>=0.1.3: policy and deliberate human gates.vivary-ozone>=0.3.2: review and evidence verification.vivary-exo>=0.3.1: optional bounded orchestration.
It receives vivary-core transitively through the role packages rather than owning a
duplicate Core floor.
The vivary command is also the front door. It routes ten task verbs to the
installed components in the same process, grouped in vivary --help as Workspace,
Graph and retrieval, Policy, Review, and Coordination:
vivary create my-workspace --preset coding --no-wizard
vivary check --root my-workspace
vivary review --root my-workspace --strict
Each route declares the component version floor it needs, and a component below
that floor is refused with exit code 2. The standalone create-vivary, tropo,
strato, ozone, and exo commands remain the advanced surface with the full
operation set and are not deprecated. Routed help and usage errors name
vivary <verb>, so vivary check --help opens with usage: vivary check.
Ozone and Exo expose explicit governed paths:
ozone verify request.json --governed --json --strict
exo control request.json --governed --json --strict
The small vivary helper CLI reads local receipts and can render a local email draft:
tropo check --root . --receipt .vivary/receipts.jsonl
vivary logs .vivary/receipts.jsonl
vivary logs email .vivary/receipts.jsonl --to support@example.com --out .vivary/support.eml
It does not send mail or upload telemetry. Drafts exclude stdout, stderr, file contents, raw query text, target ids, and local paths.
1 maintainer
Metadata
1 maintainer
Release files for vivary 0.2.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 | |
|---|---|---|---|---|
| vivary-0.2.0.tar.gz | 11.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vivary-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.2 kB
Release files / vivary-0.2.0.tar.gz
| Download URL | vivary-0.2.0.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
830baa7c017d923b9d1266e8f4193c99cd24cafa3d9552962c1b755af3a6965e
|
|
BLAKE2b-256 checksum How to use checksums |
1ec64c0fd77075b79cf503b434f4416384a473b9d6037d65e6135b730c45ae77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / vivary-0.2.0-py3-none-any.whl
| Download URL | vivary-0.2.0-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7d03446902b91759268c5e5ef663f214141c09b9beda8f0efcf014e09e1de699
|
|
BLAKE2b-256 checksum How to use checksums |
6a5e79e7aa9888b371bc65bd75c1fd526c785f22f44535af92d29eb6341d5b8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for vivary 0.2.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.
