Papers and Slides
Papers and slides serve different purposes. Papers give durable argument and technical detail. Slides give a fast narrative, diagrams, demos, and a way to explain the system in conversation. Public Docs should borrow clarity from both without copying either structure mechanically.
This page is a navigation aid for readers who want primary sources.
Use it when you need to cite OAN, brief a partner, compare architectures, or verify that a website explanation is backed by deeper material. The goal is not to make every reader consume every artifact. It is to make the path to deeper review obvious.

OAN Papers
The two core OAN papers are:
Read the white paper for vision, ecosystem positioning, and adoption. Read the yellow paper for protocol architecture, trust model, verification, and security properties.
Together they answer the two questions most reviewers ask first: why should OAN exist, and how does it avoid becoming just another unverified directory? The white paper answers the first at ecosystem level. The yellow paper answers the second at protocol level.
Related Research
Related research gives context for semantic discovery and broader agentic networking:
GRAIL is directly relevant to Discovery quality. AONA and DarwinNet help place OAN within a broader research program around agentic overlay networks and protocol synthesis.
These related papers should not be read as substitutes for OAN’s trust model. They provide neighboring research context: how agent discovery can become more intelligent, how agentic overlays can be framed, and how network/protocol evolution may support agent ecosystems.
Standards and Specifications
For standards-facing review and implementation details:
- IETF draft: OAN resource identity and discovery
- IETF draft: Agentic Overlay Network architecture
- IETF draft: Efficient Agent Discovery profile
- did:oan DID Method Specification
These materials are useful when you need exact language for DID, resource identity, discovery profiles, or interoperability discussion.
When using them for implementation, cross-check the current public SDK and service behavior. Drafts may evolve, and implementation may expose practical details before the draft language fully settles.
Slides
Slides are best for onboarding and presentations. The English deck gives a compact public story: why trust matters for agents, how OAN separates governance and Discovery, how did:oan and ResourcePackage work, how semantic Discovery fits, what implementation evidence exists, and how participants can join.
Use slides when explaining OAN to partners, contributors, or non-specialist audiences. Use Docs when someone needs durable reference pages. Use papers when they need citations and deeper justification.
The slides are also useful for diagrams. Many readers understand OAN faster when they first see the role separation, trust chain, resource types, and benchmark screenshots visually, then return to Docs for the stable page-by-page explanation.
Public Repository
The public Docs repository collects specifications, guides, slides, and related material:
When citing papers, prefer arXiv links. When citing standards drafts, prefer IETF Datatracker links. When citing implementation or public guides, use the relevant GitHub repository.
This keeps citations durable and audience-appropriate. arXiv is better for papers, Datatracker is better for drafts, and GitHub is better for living public guides and code.
Keeping Materials Aligned
As OAN evolves, the papers, slides, website Docs, SDK examples, public guides, and implementation should remain mutually understandable. They do not need identical chapter structures, but they should use the same core concepts: trusted resource, did:oan, Registrar, Root, Discovery, ResourcePackage, authorized domains, capability tags, lifecycle, and verification before use.
When one material changes, check the others for drift. A new domain rule, SDK configuration model, resource type, or verification step should eventually be reflected across Docs, guides, examples, and slides. Consistency is part of public credibility.