All notable changes to the Agent-Adoption Specification per release.
v1.0.0 — 2026-04-26
Initial public release of the Agent-Adoption Specification.
- 25 measurable agent-readiness checks across 4 categories:
discoverability,accessControl,contentReadability,agentEndpoints - 12 scored checks (weight > 0) and 13 informational checks (weight = 0); sum of scored weights = 80
- Three-value status enum:
pass,fail,neutral(noerror, noskipped) - Three readiness levels (integer values 1, 2, 3) with single-check gates:
content-signals(L1→L2) andmarkdown-negotiation(L2→L3) - Three named cluster verdicts (
htmlPath,spaRenderingCap,noViablePathCap) emitted as a top-levelclustersarray, with normative cluster math (composition order: coefficients → base score → caps) - v1.0 wire surface is closed at the root (no top-level vendor namespace); vendor extensions live under per-check
detailsandmeta.counters, both open viaadditionalProperties: true - One bundled profile:
b2b-saas(profiles/b2b-saas.json) - Normative output schema at
schemas/output-v1.schema.json(JSON Schema draft 2020-12) - Score formula:
round(100 * passWeight / (passWeight + failWeight));neutralchecks andweight: 0checks excluded; divide-by-zero short-circuits toscore: 0 - Conformance contract for v1.0 implementations (see
SPEC.md§11)
- Live specification page: https://respectarium.com/spec/agent-adoption/v1
- Companion empirical research (Q1 baseline): https://respectarium.com/research/correlation-2026-04
- Reference data and analysis: https://github.com/respectarium/agent-adoption-research/releases/tag/study-2026-04
Licensed under CC-BY 4.0 (free use, modification, redistribution with attribution to Respectarium).