Metadata-Version: 2.4
Name: vivary
Version: 0.1.10
Summary: Local-first governed context for agent work. One install for the Vivary CLI suite: create-vivary, tropo, strato, ozone, and exo.
Author: Jeff Kazzee
License-Expression: MIT
Project-URL: Homepage, https://vivary.vercel.app/
Project-URL: Repository, https://github.com/vivary-dev/vivary
Project-URL: Changelog, https://github.com/vivary-dev/vivary/blob/dev/CHANGELOG.md
Keywords: agents,workspace,knowledge-graph,scaffold,vivary
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.11
Requires-Python: >=3.11
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: create-vivary>=0.4.2
Requires-Dist: vivary-tropo>=0.5.3
Requires-Dist: vivary-strato>=0.1.2
Requires-Dist: vivary-ozone>=0.3.1
Requires-Dist: vivary-exo>=0.3.0
Dynamic: license-file

# vivary

The unpublished `vivary 0.1.10` source manifest provides one install for the Vivary CLI
suite. Release verification builds local wheels and proves their composition without
consulting a registry:

```bash
python -m pip install --no-index --find-links <wheelhouse> vivary
```

Published and source versions live in the
[root release status](../../README.md#release-status). Do not use an unpinned registry
install to verify this development line.

The source install includes:

- `create-vivary>=0.4.2`: thin greenfield init and deterministic brownfield adoption.
- `vivary-tropo>=0.5.3`: typed governed context and local retrieval.
- `vivary-strato>=0.1.2`: policy and deliberate human gates.
- `vivary-ozone>=0.3.1`: review and evidence verification.
- `vivary-exo>=0.3.0`: optional bounded orchestration.

It receives `vivary-core` transitively through the role packages rather than owning a
duplicate Core floor.

Ozone and Exo expose explicit governed paths:

```bash
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:

```bash
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.

Docs: <https://vivary.vercel.app/>
