ARP v1.3.0 — reversibility primitive + collector tier-segregation

Two additive features addressing pre-pilot feedback (averageuser612 r/LangChain pressure-test, 2026-05-04).

Backwards compatible: v1.2.x senders work against v1.3 collectors; v1.3 senders work against v1.2.x collectors (new fields ignored).

Added

• §4.1.1 reversibility primitive (NEW) — Closed enum on Pattern object: safe_config | reversible_code | risky_infra | security_critical | null. Auto-application gating signal. Collectors MUST treat null as risky_infra equivalent (conservative default — pre-classification null state never expands the auto-apply surface). Forward-fix only; no backfill of legacy patterns. Lineage: deployment-system blast-radius tags (Liquibase safe/risky migrations, SemVer breaking-change severity).

• §3 collector-side tier-segregation (informative) — Reference collector exposes top_production_observed and top_documented as separate response arrays. The mixed top_rules array is deprecated for v1.4 removal. Includes _meta.response_shape_version and _meta.deprecation_notice fields for collector evolution tracking.

• §7.1 v1.3 ↔ v1.2.x compatibility matrix — Explicit bidirectional interop guarantees.

Schema

• Pattern.reversibility property added with closed oneOf enum + null.
• No breaking changes to existing fields.

Live verification

Dogfood test on mimari.ai (canonical AgentMinds consumer) confirmed:

• B1 split arrays: live (top_production_observed, top_documented)
• B2 reversibility passthrough: live (legacy patterns return null as expected)
• Backend implementation: agentminds commits 96c720e (B1) and 9c53bf6 (B2)
• Reference report: docs/dogfood/2026-05-08_health_check.md (private — link will work for collaborators)

Strategic position

This release shifts the auto-apply gating contract from "implicit, per-implementation" to "explicit, spec-level." Cross-site pattern sharing amplifies the cost of mis-classification — a pattern marked safe_config incorrectly cascades across many sites before the error is caught. Null-as-risky-infra default ensures the cautious path is the default path.

Lineage from external feedback: averageuser612's pressure-test point #4 ("blast radius / reversibility label") landed verbatim. Convergent feedback validates this primitive as essential, not optional.

ARP v1.2.2 — Reference collector tier-segregation note

Patch release. Single informative addition: §11 reference collector note documenting the agentmindsdev/agentminds collector's tier-segregated /personalized-rules delivery shape.

Not normative. Pattern's canonical tier indicator remains status in §4.1. Documented as a worked example for implementers.

Added

• §11.1 Reference collector — tier-segregated delivery (informative) — describes how the reference AgentMinds collector exposes top_production_observed, top_documented, and the deprecated top_rules mixed array. Collector-side delivery profile, not normative ARP. Other implementers free to surface tier however they prefer; this section serves as a worked example.

Changed

• None (informative section only).

Strategic position

No schema changes. v1.2.1 senders and collectors remain conformant. This release is documentation hygiene — a worked example of how the reference implementation chose to surface the status tier in its delivery API.

ARP v1.2.1 — alias/bridge/namespace primitives + collector self-description

Patch release over v1.2.0. Five cross-standard alias / bridge / discovery primitives added so ARP plays cleanly with Sentry SDKs, LangSmith feedback, OTel GenAI evaluation spans, AGNTCY OASF taxonomies, and cross-collector discovery tooling. All additive — v1.2.0 senders work unchanged against v1.2.1 collectors.

Added

• §3.3 Sentry event.fingerprint alias — Collectors SHOULD accept the JSON pointer alias event.fingerprint (Sentry's envelope field name) and treat it identically to the canonical Warning.fingerprint. Server-side normalization MUST emit only the canonical name on outbound payloads. Lets Sentry SDK ingest land without translation.
• §3.4 LangSmith confidence ↔ feedback.score alias — When Recommendation.confidence is a 0..1 numeric, it is wire-compatible with LangSmith's feedback.score primitive. Collectors building an arp-langsmith-bridge MAY map between the two without lossy translation. Richer eval shapes (categorical / boolean / comparative) continue to use Score (§3.5).
• §3.4.1 gen_ai.evaluation.result → §4.1 Pattern bridge — Collectors MAY auto-promote OTel GenAI gen_ai.evaluation.result attributes into ARP §4.1 Patterns once observed ≥ N times across distinct sites (default N=3). Lets observability-first stacks (Langfuse, Arize, OpenInference adopters) surface cross-site patterns without wiring ARP push directly. Spec text is informative as of v1.2.1; reference implementation lands in a future ARP collector.
• §6.1 OASF 90000-99999 range reservation — ARP reserves AGNTCY OASF taxonomy IDs 90000-99999 as the agentminds.* extension namespace per the §1.2 normative reference. Vendors building skills against ARP MAY allocate their own number from this range without colliding with upstream canonical IDs (1xxx, 5xxx, etc.).
• §8.1 /.well-known/arp.json self-description (NORMATIVE) — Every ARP-conformant collector MUST publish a self-description at /.well-known/arp.json carrying arp_version, conformance_level, endpoints, auth_schemes, spec_url, extensions_advertised, and links to companion agent_card.json / oasf_descriptor.json / mcp_server.json. Cross-collector tools (adapters, analytics, dashboards) SHOULD probe this URL first to discover the collector's surface before issuing typed requests.

Schema / Spec

• No additions to agent_report.schema.json. §8.1 introduces a separate /.well-known/arp.json document (not part of the report envelope). The aliases (§3.3, §3.4) are collector-side normalization rules; the bridge (§3.4.1) is informative; the OASF reservation (§6.1) is a number range.
• Spec §1.2 Normative references updated to include v1.2.1 line items.
• Existing v1.2.0 fields unchanged. New v1.2.1 primitives are alias notes, informative bridges, namespace reservations, or out-of-band discovery contracts — none expand the report envelope.

ARP v1.2.0 — Phase 2 of v1.1 deepdive plan

Phase 2 of the v1.1 deepdive plan. Additive primitives covering multi-agent observability, prompt provenance, hibernation lifecycle, exception triage, hierarchical telemetry, and AGNTCY OASF skill taxonomy alignment. All backwards-compat — v1.0/v1.1.x senders work unchanged against v1.2 collectors.

Added

• §2.2 lifecycle_event envelope — cold_start | wake | scheduled | shutdown | running for hibernate-aware runtimes (Cloudflare DO, AWS Lambda). OPTIONAL — non-hibernating agents omit.
• §3.7 Exception evidence shape — Sentry-aligned, mechanism.handled distinguishes caught vs uncaught. Goes inside Warning.evidence.exception.
• §5.3 dotted_order on TelemetrySpan — LangSmith-compatible single-string hierarchical sort (<RFC3339>Z<uuid>.<RFC3339>Z<uuid>...). Lets clients sort spans without parent_id JOINs.
• §6.2 Handoff primitive + Report.handoffs[] — multi-agent delegation events. Lineage: OpenAI Agents SDK Handoff class. Required: from_agent + to_agent.
• §6.3 PromptManifest primitive + ProjectInfo.prompts[] — prompt provenance (LangSmith Prompt Hub + OpenInference prompt.* lineage).
• §6.1 oasf_skill_ids[] — cross-reference to AGNTCY OASF skill taxonomy IDs (e.g. [1106] for "Cross-Site Pattern Confidence" under Category 11). LF AI & Data alignment.
• §6.1 agentskills_io_canonical_name — optional cross-link to agentskills.io marketplace.
• §6.1 execution_tier — Cloudflare Agents 5-tier execution ladder + ARP in_process extension (workspace, dynamic_worker, npm, browser, sandbox, in_process).
• §6.4 tech_stack.mcp_server_exposed + mcp_clients_consumed[] — MCP role disambiguation. Closes the "is this site exposing or consuming MCP?" gap.

Schema

• New $defs: Handoff (required: from_agent, to_agent), PromptManifest (free-form provenance), Exception (mechanism.handled boolean for triage).
• lifecycle_event top-level enum property (5 values + OPTIONAL).
• TelemetrySpan.dotted_order string field.
• Report.handoffs[] array.
• ProjectInfo.prompts[] array.
• ProjectInfo.tech_stack typed properties (mcp_server_exposed, mcp_clients_consumed).
• SkillManifest: oasf_skill_ids (int array), agentskills_io_canonical_name, execution_tier (6-value enum).

Tests

19 new schema validator cases — total: 62 → 81 schema tests. Coverage: enum-validation paths for lifecycle_event, execution_tier; Handoff required-field enforcement; oasf_skill_ids type validation; Exception evidence shape; dotted_order on spans; v1.0/1.1.x backwards-compat round-trips on all new optional fields.

ARP v1.1.1 — Breadcrumbs + agentskills.io + OpenInference

Phase 1B of the v1.1 deepdive plan. Adds the remaining 3 must-ship items: Breadcrumbs, agentskills.io frontmatter alignment, OpenInference normative reference. All additive, all backwards-compat with v1.0 and v1.1.0.

Added

• §3.6 Breadcrumb trail array on Warning — Sentry-aligned timestamped events leading up to a warning. Required: timestamp + type (8-value enum: navigation/http/error/info/query/ui/user/default). Critical for cascade-failure debugging. Cap ~50/warning.
• §5.1 OpenInference v1 normative reference — ARP §5 telemetry now formally adopts OpenInference's attribute namespace by reference. Spec text only (Apache-2.0); Phoenix runtime explicitly excluded (ELv2 + US patent claims).
• §5.2 TelemetrySpan typed shape — OPTIONAL upgrade from v1.0 free-form span dicts. New optional fields: kind (10-value OpenInference enum), subtype (8-value OpenAI Agents enum), trace_id, span_id, parent_span_id, start_time, end_time, status, attributes, events, _meta. v1.0 free-form spans still validate.
• §6.1 SkillManifest expansion — agentskills.io 6 open-spec frontmatter fields adopted verbatim: name, description, version, license (SPDX), metadata (free-form), compatibility. Plus auto_invocable: bool — polarity-flipped from Anthropic Skills' disable-model-invocation. Default false (opt-in is safer; collectors translate inverted upstream form on ingest).

Schema

• New $defs: Breadcrumb (required: timestamp, type), OpenInferenceSpanKind (10-value enum), OpenAISpanSubtype (8-value enum), TelemetrySpan (typed shape).
• Warning.breadcrumbs[] references Breadcrumb.
• Telemetry.spans[] now references TelemetrySpan (was free-form).
• SkillManifest.metadata and SkillManifest.auto_invocable added.

Tests

18 new schema validator cases — total: 44 → 62 schema tests. Coverage: breadcrumb attach + reject paths, agentskills.io fields acceptance + auto_invocable boolean enforcement, TelemetrySpan typed validation incl. enum-rejection paths and v1.0 free-form backwards-compat.

What this unlocks

• Sentry SDK adapter — ARP collectors can now translate Sentry breadcrumb arrays directly without lossy normalization.
• OpenInference adopters (Arize, Langfuse, anyone using the attribute namespace) — direct interop, no field renames.
• Anthropic / agentskills.io ecosystem — skill metadata round-trips without lossy translation; the polarity flip on auto_invocable is a small clarity win.

ARP v1.1.0 — Score primitive + _meta envelope + fingerprint union

Additive backwards-compat release. v1.0 senders work unchanged against v1.1 collectors. v1.1 senders work against v1.0 collectors because all new fields are OPTIONAL and unknown-key-safe.

Phase 1A scope (4/7 of the must-ship tier from the standards deepdive synthesis).

Added

• §3.5 Score primitive — Typed evaluation outcomes (numeric / categorical / boolean) attached to warnings, patterns, or the report as a whole. Closed data_type enum to prevent fragmentation. Lineage: Langfuse Score model + LangSmith Feedback. Unlocks eval pipeline interop.
• §2.1 _meta reverse-DNS extension envelope — MCP-aligned vendor extension convention. Available on the envelope and on every $def (Warning, Recommendation, Pattern, Score, Memory, SkillManifest, ProjectInfo). Reserved second-level namespaces: agentminds.*, arp.*. Other implementers use first-come-first-served reverse-DNS.
• §3.3 fingerprint accepts array form — Sentry-aligned string[] form with {{ default }} placeholder support coexists with the canonical lowercase-hex SHA-256 single-string form. Per payload, senders pick one; v1.0 senders unaffected.
• §2 envelope additions — session_id, user_id, conversation_id for multi-turn agent flow correlation. Aliases of LangSmith Threads + OpenInference session.id / user.id + OTel gen_ai.conversation.id semantics.
• §7.1 version compatibility matrix — Explicit table covering v1.0↔v1.1 cross-version interop guarantees.

Schema

• Fingerprint is now a oneOf between the canonical string form and the Sentry-aligned array form.
• New Score $def with closed data_type enum.
• _meta field added to top-level + Report + Warning + Recommendation + Pattern + Memory + ProjectInfo + SkillManifest + Score.
• session_id, user_id, conversation_id top-level properties.

Tests

24 new test cases covering each addition, including v1.0 backwards-compat round-trips and rejection of malformed inputs. Total schema validator tests: 20 → 44.

ARP v1.0.0 — Initial public release

Initial release of ARP v1.0. Published as a profile, not a competing standard.

Added

• 13-section specification covering: envelope (§2), report shape (§3), warning lifecycle (§3.3), recommendation object (§3.4), memory + learned-patterns (§4), OTel-compatible telemetry (§5), project-info with skills (§6), versioning rules (§7), transport bindings (§8), conformance levels L0–L5 (§9), worked example (§10), implementer notes (§11), public comment process (§12), and a profile-vs-standard FAQ (§13).
• JSON Schema (draft 2020-12) at schemas/agent_report.schema.json with full coverage of every required and optional field.
• Five lineages cited — Sentry data schemas, OpenTelemetry GenAI, Model Context Protocol, Anthropic Claude Skills, AGNTCY OASF.
• One novel extension — §4.1 Pattern object, the cross-site learned-pattern lifecycle.
• Conformance levels L0–L5 — collectors and senders self-declare level.

Strategic position

This release explicitly disclaims any intent to compete with the upstream standards. ARP is AgentMinds' documented adoption of those standards, plus one extension. When any upstream standard absorbs the pattern-lifecycle primitive, ARP MAJOR+1 must defer to the upstream definition within 30 days.