# Draft Registry Entry — Agent-to-Agent Registries

**Status:** Draft. Not yet submitted to any registry.
**Intended target registries:** any public A2A agent directory / descriptor registry.
**Purpose:** to expose the OracleNet Deal Discovery Protocol as a pointer so other agents can discover and (optionally) implement it.

---

## Machine-readable pointer

```json
{
  "protocol": "oraclenet-deal-v1",
  "status": "draft",
  "descriptor": "https://tooloracle.io/docs/deal-protocol/registry/protocol-descriptor.json",
  "specification": "https://tooloracle.io/docs/deal-protocol/rfc-0001",
  "schemas_root": "https://tooloracle.io/docs/schemas/",
  "reference_implementations": [
    "did:web:feedoracle.io",
    "did:web:tooloracle.io"
  ]
}
```

## Suggested description (one paragraph)

> **OracleNet Deal Discovery Protocol (draft v1).** Defines how autonomous agents discover one another, declare what they offer and seek, and exchange cryptographically verifiable proposals under opt-in, auditable, anti-spam rules. Six layers: curated intent (`deal-policy.json`), opt-out governance (`do-not-contact.json`), subscribable broadcast (`deal-feed.atom`), commercial message format (W3C Verifiable Credentials), observed demand (`deal-emergence.json`), and counterparty assessment (readiness tiers, fit scoring, governance gates). Reference implementation live at `did:web:feedoracle.io` and `did:web:tooloracle.io`.

## Tone guidance for any registry submission

- Descriptive, not promotional.
- "Reference implementation" is true and defensible; "first" / "only" / "largest" should be avoided.
- Status is clearly *Draft*. Any registry maintainer should be able to see that the protocol is experimental.
- Do not request endorsement. Provide information; let the registry decide.

## What we are not asking registries to do

- Not asking them to adopt the protocol.
- Not asking them to re-host artefacts.
- Not asking them to modify their own data model.
- Only: to carry a pointer if they see fit.

## Next steps (not yet actioned)

This file is a draft. When we are ready, we will:

1. Identify the concrete registries.
2. Review each registry's submission process.
3. Open a respectful, minimal PR / issue with this entry.
4. Respond to questions from maintainers.

No such PR has been opened as of the publication date of this document.