ARP vs other standards
Where ARP overlaps with the upstream lineage standards, and where it fills a genuine gap. Source: 12-target deep-dive,see the spec lineage.
| Feature | OASF | MCP | A2A | OTel | Sentry | Skills | LangSmith | Arize | Langfuse | OpenAI | ACP | CF | ARP |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| has_status field | ❌ | 🟡 | ✅ | ✅ | 🟡 | ❌ | ✅ | ✅ | 🟡 | 🟡 | ✅ | 🟡 | ✅ |
| first_seen / last_seen | 🟡 | ❌ | ❌ | ❌ | ✅ | ❌ | 🟡 | 🟡 | ❌ | ❌ | 🟡 | ❌ | ✅ |
| fingerprint primitive OASF (CID) and Sentry (issue grouping) have it but for different purposes; ARP unifies + bridges both. | ✅ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ |
| Skill manifest | ✅ | 🔵 | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ | 🟡 | ❌ | ✅ |
| Cross-site pattern share Only ARP combines cross-tenant aggregation + confidence-weighting + drift detection. The genuine moat. | ✅ | ❌ | 🟡 | ❌ | 🟡 | 🟡 | ❌ | ❌ | ❌ | ❌ | 🟡 | ❌ | ✅ CORE |
| Identity binding | ✅ | 🟡 | ✅ | 🟡 | 🟡 | 🟡 | 🟡 | 🟡 | 🟡 | ❌ | ❌ | 🟡 | 🟡 |
| Foundation backing OASF/MCP/A2A all under Linux Foundation AI & Data; OTel under CNCF. | ✅ | ✅ | ✅ | ✅ | ❌ | 🟡 | ❌ | 🟡 | ❌ | ❌ | ✅ | ❌ | ❌ |
| Adopters | 75+ orgs | dozens | 150+ orgs | implicit | 5M+ devs | 125K stars | ~100K LC eco | 9.4K stars | 26.2K stars | 25.4K stars | (merged → A2A) | preview | 1 (us) |
Legend
✅ present🟡 partial🔵 on roadmap❌ absent✅ CORE core differentiator
Strategic positioning
ARP is a profile, not a competing standard. Where another standard ships a primitive, ARP defers to it (see adapters for field-level mappings).
The one row that matters: cross-site pattern share. No upstream standard combines cross-tenant aggregation, fingerprint dedup, and confidence-weighted lifecycle. That row is where ARP justifies its existence.
When an upstream catches up, we defer within 30 days. Per ARP §7 reorientation clause + the weekly standards-watcher bot monitoring all 12 lineages.