docs: document project sponsorship roles (#84)

Signed-off-by: Imran Siddique <45405841+imran-siddique@users.noreply.github.com>

Author: imran-siddique

README.md

@@ -8,6 +8,10 @@
 
 End-to-end integration examples showing cMCP, Agent Manifest, and TRACE working together across deployment scenarios. Each example is self-contained and runnable on a fresh cloud VM. Running them shows how the projects compose: cMCP enforces policy at the tool call boundary, Agent Manifest carries the identity and capability declaration, cA2A attenuates authority at the agent-to-agent boundary, and TRACE emits a signed Trust Record for every tool invocation so you can see what the full audit trail looks like in practice.
 
+Project support is recognized in [SPONSORS.md](SPONSORS.md). Sponsorship is
+separate from example authorship, fixture identities, partner provenance,
+adoption, and project governance.
+
 ## Examples
 
 | Example | What it shows | Platform | Compliance |

SPONSORS.md

@@ -0,0 +1,20 @@
+# Sponsors
+
+AgenTrust Examples is an open-source project. Sponsors provide funding,
+engineering time, infrastructure, or other in-kind support. Sponsorship does
+not confer project ownership, governance authority, or control over technical
+decisions or example results.
+
+## Current sponsors
+
+### OPAQUE Systems
+
+Founding engineering and infrastructure sponsor, and contributor to the
+AgenTrust example ecosystem.
+
+## Recognition policy
+
+Sponsor recognition is separate from example authorship, partner provenance,
+and adoption. Vendor names and identities inside example manifests, policies,
+fixtures, and deployment profiles describe the scenario being exercised; they
+do not identify the owner of this repository or its projects.