Metadata-Version: 2.5
Name: agentgov-core
Version: 0.2.0
Summary: Shared invoke-boundary core for agent-governance-demo: host adapters, entitlement/policy resolution, the governance envelope, and the registry Postgres schema. Not published to PyPI yet — built as a local wheel and installed into registry-api/services-workflows images (Phase 5 §5.8).
Author-email: "receptor.bio" <oss@receptor.bio>
License: Apache-2.0
Requires-Python: >=3.10
Requires-Dist: botocore
Requires-Dist: cryptography
Requires-Dist: fastapi
Requires-Dist: httpx
Requires-Dist: psycopg[binary]
Requires-Dist: pyjwt
Description-Content-Type: text/markdown

# agentgov-core

Shared invoke-boundary core for [`agent-governance-demo`](https://github.com/receptor-bio/agent-governance-demo):
per-platform host adapters (`hosts/`), the governance envelope (`envelope.py`), entitlement/policy
resolution (`openfga.py`, `cedar.py`), the registry Postgres access layer + schema (`db.py`,
`schema.sql`), and the shared URN/tuple helpers (`urns.py`, `tuples.py`) that `registry-api` and
`services/workflows` both consume — replacing the `sys.path` trick `services/workflows/activities.py`
previously used to reach `registry-api`'s app code directly.

**Not published to PyPI yet.** Built as a local wheel in each consuming Dockerfile's multi-stage
build, and installed with `pip install -e packages/agentgov-core` for local dev. See
`docs/PHASE_STATUS.md`'s Phase 5 §5.8 entry for the plan to publish it for real via PyPI Trusted
Publishing (the same OIDC pattern `receptor-bio/axiom-sc` already uses) — deferred, not blocking.

Not a general-purpose library: this package's boundary is driven entirely by what
`services/workflows/activities.py` and `services/registry-api/app/` actually import, not by any
external API-design goal.
