openagent-control 0.1.0__tar.gz

openagent_control-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

openagent_control-0.1.0/PKG-INFO

@@ -0,0 +1,241 @@
+Metadata-Version: 2.4
+Name: openagent-control
+Version: 0.1.0
+Summary: Agent identity & governance control plane: policy-gated, credential-brokered, cryptographically audited tool execution for autonomous agents.
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: mcp,model-context-protocol,ai-agents,agent-governance,opa,rego,oauth2,spiffe,audit,zero-trust
+Author: Shail Shah
+Author-email: shailvshah@gmail.com
+Requires-Python: >=3.11,<3.13
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Security
+Classifier: Topic :: System :: Systems Administration :: Authentication/Directory
+Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
+Classifier: Typing :: Typed
+Provides-Extra: persistence
+Requires-Dist: alembic (>=1.13.0,<2.0.0) ; extra == "persistence"
+Requires-Dist: asyncpg (>=0.29.0,<0.30.0) ; extra == "persistence"
+Requires-Dist: cryptography (>=43.0.0,<44.0.0)
+Requires-Dist: fastapi (>=0.115.0,<0.116.0)
+Requires-Dist: greenlet (>=3.0.0,<4.0.0) ; extra == "persistence"
+Requires-Dist: httpx (>=0.27.0,<0.28.0)
+Requires-Dist: mcp (>=1.28.1,<2.0.0)
+Requires-Dist: opentelemetry-api (>=1.26.0,<2.0.0)
+Requires-Dist: opentelemetry-sdk (>=1.26.0,<2.0.0)
+Requires-Dist: pydantic (>=2.8.0,<3.0.0)
+Requires-Dist: pydantic-settings (>=2.4.0,<3.0.0)
+Requires-Dist: pyjwt (>=2.9.0,<3.0.0)
+Requires-Dist: pyyaml (>=6.0.0,<7.0.0)
+Requires-Dist: redis (>=5.0.0,<6.0.0) ; extra == "persistence"
+Requires-Dist: sqlalchemy[asyncio] (>=2.0.0,<3.0.0) ; extra == "persistence"
+Requires-Dist: uvicorn[standard] (>=0.31.1,<1.0.0)
+Project-URL: Changelog, https://github.com/shailvshah/openagent-control/releases
+Project-URL: Documentation, https://github.com/shailvshah/openagent-control/blob/main/docs/deployment.md
+Project-URL: Homepage, https://github.com/shailvshah/openagent-control
+Project-URL: Issues, https://github.com/shailvshah/openagent-control/issues
+Project-URL: Repository, https://github.com/shailvshah/openagent-control
+Description-Content-Type: text/markdown
+
+# openagent-control
+The zero-config security, governance, and telemetry proxy for the autonomous AI workforce.
+
+## What it is
+
+Autonomous agents typically run on static service accounts and hardcoded API keys.
+That forces a choice between over-privileged agents and brittle workflows, and leaves
+no cryptographically trustworthy record of what an agent actually did.
+
+`openagent-control` sits between an agent and the tools it calls — today, MCP
+(`tools/list` / `tools/call`) — and enforces three things on every call:
+
+1. **Identity** — the agent is a workload with its own identity, not a shared secret.
+2. **Policy** — every tool call is evaluated against explicit policy (Open Policy
+   Agent / Rego) before it reaches the target system; a scoped, short-lived
+   credential is issued only on allow.
+3. **Audit** — every decision produces an Ed25519-signed, hash-chained receipt, so a
+   compliance reviewer can prove after the fact what was authorized and executed.
+
+See [docs/design.md](https://github.com/shailvshah/openagent-control/blob/main/docs/design.md) for the full design,
+[docs/adr/](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/README.md) for the reasoning behind each decision — including
+what's a real implementation today versus a deliberate v1 stub —
+[docs/roadmap.md](https://github.com/shailvshah/openagent-control/blob/main/docs/roadmap.md) for where the codebase stands against the
+phased enterprise rollout plan, and [docs/user-journeys.md](https://github.com/shailvshah/openagent-control/blob/main/docs/user-journeys.md)
+for how an agent developer, platform engineer, registry operator, or compliance
+reviewer actually uses it, and [docs/deployment.md](https://github.com/shailvshah/openagent-control/blob/main/docs/deployment.md) for
+installing and running it.
+
+## Status
+
+Early foundation, not production-ready. In particular:
+
+- **Identity defaults to a stub.** `OAC_IDENTITY_MODE=header` (the default) trusts an
+  `X-Spiffe-ID` header rather than performing real SPIFFE/SPIRE attestation — only
+  safe behind a network boundary that has already authenticated the caller.
+  `OAC_IDENTITY_MODE=jwt-svid` cryptographically validates a SPIFFE JWT-SVID bearer
+  token (the shape SPIRE issues) but still needs an actual SPIRE deployment to be a
+  full production path — see [ADR-0005](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0005-workload-identity-via-spiffe-stubbed-in-v1.md).
+  `OAC_IDENTITY_MODE=oidc-jwks` validates a real access token from Okta or Microsoft
+  Entra ID against its published JWKS — see
+  [ADR-0010](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0010-oidc-jwks-identity-for-okta-and-entra.md).
+- **Token exchange defaults to a stub**, with real Okta-compatible (RFC 8693) and
+  Microsoft Entra (OBO) adapters available via `OAC_TOKEN_EXCHANGE_MODE` — see
+  [ADR-0004](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0004-mcp-as-the-v1-protocol-surface.md).
+- **The ledger's signing key defaults to in-process** (regenerated on restart) unless
+  you inject your own `ReceiptSigner`; there's no KMS/HSM adapter yet. Chain state
+  itself, however, is durable and replica-safe once `OAC_DATABASE_URL` is set — see
+  [ADR-0003](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0003-ed25519-hash-chained-audit-ledger.md) and
+  [ADR-0009](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0009-postgres-persistence-and-redis-caching.md).
+- No Human-in-the-Loop approval flow, no sidecar/native-SDK deployment pattern, no
+  cross-organization (DID/VC) identity yet — tracked in
+  [ADR-0001](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0001-hybrid-interception-pattern.md) and
+  [ADR-0007](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0007-decentralized-identity-is-a-future-extension-not-v1-scope.md).
+
+## Architecture
+
+Hexagonal (ports & adapters) — see
+[ADR-0006](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0006-hexagonal-architecture-for-the-control-plane.md).
+
+```
+src/openagent_control/
+├── domain/          # pure models + Protocol ports — no I/O, no framework imports
+├── application/       # GovernedExecutionService — the transport-agnostic use case
+├── adapters/            # concrete implementations of each port (OPA, ledger, identity, db, ...)
+└── gateway/               # FastAPI app: routes + dependency wiring, no policy/crypto logic
+```
+
+| Port | Default adapter | Also available (settings-selected) |
+|---|---|---|
+| `PolicyEngine` | Open Policy Agent (Rego), `policies/mcp_authz.rego` | — |
+| `IdentityProvider` | header-trusting stub | JWT-SVID validation, OIDC/JWKS (Okta, Entra ID) |
+| `AgentRegistry` | file (`registry/agents.yaml`, git-reviewed) | Postgres (`oac.agents`), optionally Redis-cached |
+| `Ledger` | in-process Ed25519 hash-chained receipts | Postgres-backed, replica-safe chain (`oac.execution_receipts`) |
+| `TokenExchange` | stub | RFC 8693 (Okta-compatible), Microsoft Entra OBO — optionally Redis-cached to each token's own expiry |
+| `MCPUpstream` | MCP Streamable HTTP via the official MCP SDK (ADR-0011) | plain JSON-RPC over HTTP, for non-MCP internal endpoints |
+| `AuditExporter` | stdout/log | — |
+
+## Install
+
+```bash
+pip install openagent-control                  # gateway + OPA
+pip install 'openagent-control[persistence]'   # + Postgres / Redis support
+
+openagent-control init ./oac                   # starter registry + policy
+export OAC_REGISTRY_PATH=./oac/agents.yaml
+openagent-control doctor                       # checks every dependency
+openagent-control serve
+```
+
+Or with containers — `docker compose up` (gateway + OPA),
+`--profile persistence` for Postgres/Redis, `--profile demo` for the
+walkthrough stack. Full guide: **[docs/deployment.md](https://github.com/shailvshah/openagent-control/blob/main/docs/deployment.md)**.
+
+With no registry configured the gateway starts and **denies every agent** — a
+fresh install trusts nothing until you register something.
+
+## Development
+
+```bash
+make install      # poetry install --all-extras
+make quality      # black --check, ruff, mypy
+make test         # pytest with coverage (95% gate)
+make check        # quality + test
+make up           # docker compose: gateway + OPA
+make up-demo      # + demo IdP and governed MCP server
+make doctor       # verify config and dependencies
+make test-packaging  # build a wheel, install it clean, run it from elsewhere
+```
+
+Requires Python 3.11+ and [Poetry](https://python-poetry.org/). The integration
+tests additionally need the `opa` binary (`brew install opa`); without it they
+skip rather than substitute a fake policy engine.
+
+Once running (`make up`), obtain an access token the way a real workload does —
+an OAuth 2.0 client-credentials grant — then send a governed tool call:
+
+```bash
+TOKEN=$(curl -s -X POST http://localhost:8090/oauth2/v1/token \
+  -u finance-invoice-svc:scenario-only-not-a-real-secret \
+  -d grant_type=client_credentials | jq -r .access_token)
+
+curl -X POST http://localhost:8000/mcp/v1 \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer $TOKEN" \
+  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"read_query","arguments":{"quarter":"Q3"}}}'
+```
+
+The upstream MCP server validates the short-lived credential the gateway brokers
+for it, so the same request sent directly to `localhost:8080` is refused. See
+[examples/enterprise_scenario/](https://github.com/shailvshah/openagent-control/blob/main/examples/enterprise_scenario/README.md).
+
+## Persistence & caching (optional)
+
+Unset by default — the gateway runs with the in-process ledger and file registry,
+zero extra infrastructure. The Postgres/Redis stack is an **optional extra**
+(`pip install 'openagent-control[persistence]'` / `poetry install --extras persistence`)
+and is lazy-imported, so the default deployment doesn't pay its ~20MB of resident
+memory or its install footprint. Set `OAC_DATABASE_URL` to switch the registry and
+ledger to Postgres (own `oac` schema, migrated via Alembic), and `OAC_REDIS_URL` to
+cache registry lookups (30s TTL) and brokered tokens (capped at each token's own
+expiry). See [ADR-0009](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0009-postgres-persistence-and-redis-caching.md).
+
+```bash
+make up-persistent               # docker compose --profile persistence: + postgres, redis
+make db-upgrade                  # alembic upgrade head against OAC_DATABASE_URL
+```
+
+To point at your own Postgres instance instead: `export OAC_DATABASE_URL=postgresql+asyncpg://user:pass@host/db`
+then `make db-upgrade`.
+
+## Examples
+
+- **[examples/enterprise_scenario/](https://github.com/shailvshah/openagent-control/blob/main/examples/enterprise_scenario/README.md) — the
+  full stack with nothing stubbed.** A LangGraph agent, real OIDC/JWKS identity,
+  real OPA, real RFC 8693 credential brokering, and a real MCP server over real
+  SQLite that validates the brokered credential's signature, audience, and scope.
+  It also demonstrates the property that distinguishes a control plane from a
+  logging proxy: an agent that **bypasses the gateway is refused by the upstream**,
+  because the token it holds is scoped to the gateway, not to the API. The same
+  assertions run in CI (`tests/integration/`), so the demo cannot rot.
+
+  ```bash
+  brew install opa && poetry install --with examples
+  poetry run python -m examples.enterprise_scenario.scenario
+  ```
+
+  Its [`keycloak/`](https://github.com/shailvshah/openagent-control/blob/main/examples/enterprise_scenario/keycloak/README.md) suite runs
+  the same identity and RFC 8693 adapters against **real Keycloak 26.4** — an
+  IdP this repo didn't write, so it can't share our bugs. That check earned its
+  keep on the first run: it caught the identity adapter misreading Keycloak's
+  service-account `sub` as a human sponsor, which would have 401'd every
+  autonomous agent.
+
+  The same is done for the MCP protocol itself against **GitHub's production
+  MCP server** (`tests/integration/test_github_mcp_conformance.py`), which is
+  how we found that the original upstream adapter did not speak MCP at all —
+  see [ADR-0011](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0011-mcp-streamable-http-via-the-official-sdk.md).
+
+- [examples/langgraph_governed_agent/](https://github.com/shailvshah/openagent-control/blob/main/examples/langgraph_governed_agent/README.md) —
+  a deterministic, zero-API-key demo of a LangGraph agent whose tool calls are
+  allowed, denied, and cryptographically receipted by the gateway:
+
+  ```bash
+  poetry install --with examples
+  make up
+  poetry run python -m examples.langgraph_governed_agent.demo
+  ```
+
+- [examples/oidc_identity_demo/](https://github.com/shailvshah/openagent-control/blob/main/examples/oidc_identity_demo/README.md) — the
+  gateway authenticating agents with real Okta/Entra-shaped OIDC access tokens
+  (signature, audience, and orphan-agent checks), fully offline against a mock
+  IdP:
+
+  ```bash
+  poetry run python -m examples.oidc_identity_demo.demo
+  ```
+

openagent_control-0.1.0/README.md

@@ -0,0 +1,196 @@
+# openagent-control
+The zero-config security, governance, and telemetry proxy for the autonomous AI workforce.
+
+## What it is
+
+Autonomous agents typically run on static service accounts and hardcoded API keys.
+That forces a choice between over-privileged agents and brittle workflows, and leaves
+no cryptographically trustworthy record of what an agent actually did.
+
+`openagent-control` sits between an agent and the tools it calls — today, MCP
+(`tools/list` / `tools/call`) — and enforces three things on every call:
+
+1. **Identity** — the agent is a workload with its own identity, not a shared secret.
+2. **Policy** — every tool call is evaluated against explicit policy (Open Policy
+   Agent / Rego) before it reaches the target system; a scoped, short-lived
+   credential is issued only on allow.
+3. **Audit** — every decision produces an Ed25519-signed, hash-chained receipt, so a
+   compliance reviewer can prove after the fact what was authorized and executed.
+
+See [docs/design.md](https://github.com/shailvshah/openagent-control/blob/main/docs/design.md) for the full design,
+[docs/adr/](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/README.md) for the reasoning behind each decision — including
+what's a real implementation today versus a deliberate v1 stub —
+[docs/roadmap.md](https://github.com/shailvshah/openagent-control/blob/main/docs/roadmap.md) for where the codebase stands against the
+phased enterprise rollout plan, and [docs/user-journeys.md](https://github.com/shailvshah/openagent-control/blob/main/docs/user-journeys.md)
+for how an agent developer, platform engineer, registry operator, or compliance
+reviewer actually uses it, and [docs/deployment.md](https://github.com/shailvshah/openagent-control/blob/main/docs/deployment.md) for
+installing and running it.
+
+## Status
+
+Early foundation, not production-ready. In particular:
+
+- **Identity defaults to a stub.** `OAC_IDENTITY_MODE=header` (the default) trusts an
+  `X-Spiffe-ID` header rather than performing real SPIFFE/SPIRE attestation — only
+  safe behind a network boundary that has already authenticated the caller.
+  `OAC_IDENTITY_MODE=jwt-svid` cryptographically validates a SPIFFE JWT-SVID bearer
+  token (the shape SPIRE issues) but still needs an actual SPIRE deployment to be a
+  full production path — see [ADR-0005](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0005-workload-identity-via-spiffe-stubbed-in-v1.md).
+  `OAC_IDENTITY_MODE=oidc-jwks` validates a real access token from Okta or Microsoft
+  Entra ID against its published JWKS — see
+  [ADR-0010](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0010-oidc-jwks-identity-for-okta-and-entra.md).
+- **Token exchange defaults to a stub**, with real Okta-compatible (RFC 8693) and
+  Microsoft Entra (OBO) adapters available via `OAC_TOKEN_EXCHANGE_MODE` — see
+  [ADR-0004](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0004-mcp-as-the-v1-protocol-surface.md).
+- **The ledger's signing key defaults to in-process** (regenerated on restart) unless
+  you inject your own `ReceiptSigner`; there's no KMS/HSM adapter yet. Chain state
+  itself, however, is durable and replica-safe once `OAC_DATABASE_URL` is set — see
+  [ADR-0003](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0003-ed25519-hash-chained-audit-ledger.md) and
+  [ADR-0009](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0009-postgres-persistence-and-redis-caching.md).
+- No Human-in-the-Loop approval flow, no sidecar/native-SDK deployment pattern, no
+  cross-organization (DID/VC) identity yet — tracked in
+  [ADR-0001](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0001-hybrid-interception-pattern.md) and
+  [ADR-0007](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0007-decentralized-identity-is-a-future-extension-not-v1-scope.md).
+
+## Architecture
+
+Hexagonal (ports & adapters) — see
+[ADR-0006](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0006-hexagonal-architecture-for-the-control-plane.md).
+
+```
+src/openagent_control/
+├── domain/          # pure models + Protocol ports — no I/O, no framework imports
+├── application/       # GovernedExecutionService — the transport-agnostic use case
+├── adapters/            # concrete implementations of each port (OPA, ledger, identity, db, ...)
+└── gateway/               # FastAPI app: routes + dependency wiring, no policy/crypto logic
+```
+
+| Port | Default adapter | Also available (settings-selected) |
+|---|---|---|
+| `PolicyEngine` | Open Policy Agent (Rego), `policies/mcp_authz.rego` | — |
+| `IdentityProvider` | header-trusting stub | JWT-SVID validation, OIDC/JWKS (Okta, Entra ID) |
+| `AgentRegistry` | file (`registry/agents.yaml`, git-reviewed) | Postgres (`oac.agents`), optionally Redis-cached |
+| `Ledger` | in-process Ed25519 hash-chained receipts | Postgres-backed, replica-safe chain (`oac.execution_receipts`) |
+| `TokenExchange` | stub | RFC 8693 (Okta-compatible), Microsoft Entra OBO — optionally Redis-cached to each token's own expiry |
+| `MCPUpstream` | MCP Streamable HTTP via the official MCP SDK (ADR-0011) | plain JSON-RPC over HTTP, for non-MCP internal endpoints |
+| `AuditExporter` | stdout/log | — |
+
+## Install
+
+```bash
+pip install openagent-control                  # gateway + OPA
+pip install 'openagent-control[persistence]'   # + Postgres / Redis support
+
+openagent-control init ./oac                   # starter registry + policy
+export OAC_REGISTRY_PATH=./oac/agents.yaml
+openagent-control doctor                       # checks every dependency
+openagent-control serve
+```
+
+Or with containers — `docker compose up` (gateway + OPA),
+`--profile persistence` for Postgres/Redis, `--profile demo` for the
+walkthrough stack. Full guide: **[docs/deployment.md](https://github.com/shailvshah/openagent-control/blob/main/docs/deployment.md)**.
+
+With no registry configured the gateway starts and **denies every agent** — a
+fresh install trusts nothing until you register something.
+
+## Development
+
+```bash
+make install      # poetry install --all-extras
+make quality      # black --check, ruff, mypy
+make test         # pytest with coverage (95% gate)
+make check        # quality + test
+make up           # docker compose: gateway + OPA
+make up-demo      # + demo IdP and governed MCP server
+make doctor       # verify config and dependencies
+make test-packaging  # build a wheel, install it clean, run it from elsewhere
+```
+
+Requires Python 3.11+ and [Poetry](https://python-poetry.org/). The integration
+tests additionally need the `opa` binary (`brew install opa`); without it they
+skip rather than substitute a fake policy engine.
+
+Once running (`make up`), obtain an access token the way a real workload does —
+an OAuth 2.0 client-credentials grant — then send a governed tool call:
+
+```bash
+TOKEN=$(curl -s -X POST http://localhost:8090/oauth2/v1/token \
+  -u finance-invoice-svc:scenario-only-not-a-real-secret \
+  -d grant_type=client_credentials | jq -r .access_token)
+
+curl -X POST http://localhost:8000/mcp/v1 \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer $TOKEN" \
+  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"read_query","arguments":{"quarter":"Q3"}}}'
+```
+
+The upstream MCP server validates the short-lived credential the gateway brokers
+for it, so the same request sent directly to `localhost:8080` is refused. See
+[examples/enterprise_scenario/](https://github.com/shailvshah/openagent-control/blob/main/examples/enterprise_scenario/README.md).
+
+## Persistence & caching (optional)
+
+Unset by default — the gateway runs with the in-process ledger and file registry,
+zero extra infrastructure. The Postgres/Redis stack is an **optional extra**
+(`pip install 'openagent-control[persistence]'` / `poetry install --extras persistence`)
+and is lazy-imported, so the default deployment doesn't pay its ~20MB of resident
+memory or its install footprint. Set `OAC_DATABASE_URL` to switch the registry and
+ledger to Postgres (own `oac` schema, migrated via Alembic), and `OAC_REDIS_URL` to
+cache registry lookups (30s TTL) and brokered tokens (capped at each token's own
+expiry). See [ADR-0009](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0009-postgres-persistence-and-redis-caching.md).
+
+```bash
+make up-persistent               # docker compose --profile persistence: + postgres, redis
+make db-upgrade                  # alembic upgrade head against OAC_DATABASE_URL
+```
+
+To point at your own Postgres instance instead: `export OAC_DATABASE_URL=postgresql+asyncpg://user:pass@host/db`
+then `make db-upgrade`.
+
+## Examples
+
+- **[examples/enterprise_scenario/](https://github.com/shailvshah/openagent-control/blob/main/examples/enterprise_scenario/README.md) — the
+  full stack with nothing stubbed.** A LangGraph agent, real OIDC/JWKS identity,
+  real OPA, real RFC 8693 credential brokering, and a real MCP server over real
+  SQLite that validates the brokered credential's signature, audience, and scope.
+  It also demonstrates the property that distinguishes a control plane from a
+  logging proxy: an agent that **bypasses the gateway is refused by the upstream**,
+  because the token it holds is scoped to the gateway, not to the API. The same
+  assertions run in CI (`tests/integration/`), so the demo cannot rot.
+
+  ```bash
+  brew install opa && poetry install --with examples
+  poetry run python -m examples.enterprise_scenario.scenario
+  ```
+
+  Its [`keycloak/`](https://github.com/shailvshah/openagent-control/blob/main/examples/enterprise_scenario/keycloak/README.md) suite runs
+  the same identity and RFC 8693 adapters against **real Keycloak 26.4** — an
+  IdP this repo didn't write, so it can't share our bugs. That check earned its
+  keep on the first run: it caught the identity adapter misreading Keycloak's
+  service-account `sub` as a human sponsor, which would have 401'd every
+  autonomous agent.
+
+  The same is done for the MCP protocol itself against **GitHub's production
+  MCP server** (`tests/integration/test_github_mcp_conformance.py`), which is
+  how we found that the original upstream adapter did not speak MCP at all —
+  see [ADR-0011](https://github.com/shailvshah/openagent-control/blob/main/docs/adr/0011-mcp-streamable-http-via-the-official-sdk.md).
+
+- [examples/langgraph_governed_agent/](https://github.com/shailvshah/openagent-control/blob/main/examples/langgraph_governed_agent/README.md) —
+  a deterministic, zero-API-key demo of a LangGraph agent whose tool calls are
+  allowed, denied, and cryptographically receipted by the gateway:
+
+  ```bash
+  poetry install --with examples
+  make up
+  poetry run python -m examples.langgraph_governed_agent.demo
+  ```
+
+- [examples/oidc_identity_demo/](https://github.com/shailvshah/openagent-control/blob/main/examples/oidc_identity_demo/README.md) — the
+  gateway authenticating agents with real Okta/Entra-shaped OIDC access tokens
+  (signature, audience, and orphan-agent checks), fully offline against a mock
+  IdP:
+
+  ```bash
+  poetry run python -m examples.oidc_identity_demo.demo
+  ```