Metadata-Version: 2.4
Name: plantcatalog
Version: 0.0.1
Summary: Evidence-backed orchid curation and reviewable catalog updates
Requires-Python: >=3.12,<4
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Programming Language :: Python :: 3.14
Classifier: Programming Language :: Python :: 3.15
Requires-Dist: PyGithub (==2.10.0)
Requires-Dist: jsonschema (==4.26.0)
Description-Content-Type: text/markdown

# Plantcatalog

Plantcatalog keeps plant wishes, confirmed specimens and listing evidence in a
validated JSON collection. It preserves source history and uncertain claims while
preparing reviewable changes and signed, data-only GitHub pull requests.

<!-- toc:start -->
**Table of contents**

- [Install](#install)
- [Use](#use)
<!-- toc:end -->

## Install

Requires Python 3.12 or later. Start in a new working directory:

```bash
python -m pip install plantcatalog
catalog --version
catalog init --output catalog.json
catalog validate
```

The Python import is `plantcatalog`; the command is `catalog`. Packages contain
code and the JSON Schema, with no collection records or source snapshots.

## Use

`catalog --help` lists command groups. `catalog batch prepare --help` explains
reviewable intake, and `catalog review render --as-of TIMESTAMP` generates a
report for an explicit timezone-aware time. Source checks and remote writes require
an explicit `--apply`; defaults prepare plans without executing them.

The initial release models orchid curation. Wishes, purchases and confirmed
possession remain separate claims. Failed or stale listing checks do not establish
stock, exact identity or delivery eligibility.

GitHub delivery uses existing `GH_TOKEN` or `GITHUB_TOKEN` access and an existing
Git signing identity. It does not create credentials, schedule work or merge PRs.

