Validation Summary — ARPA v0.9.0
Validation command:
make release-check
Results
| Surface | Result |
|---|---|
| Valid and invalid schema examples | 46/46 passed |
| Profile conformance vectors | 12/12 passed |
| Extended governance vectors | 14/14 passed |
| Operational resilience vectors | 8/8 passed |
| Reference-service tests | 5/5 passed |
| v0.5-derived interoperability checks updated for v0.9.0 | 7/7 passed |
| ARPA–TRQP projection vectors and candidate checks | 15/15 passed |
| Candidate mapping completeness | Passed |
| Schemas, controlled registries, OpenAPI and AsyncAPI parsing | Passed |
| Flagship repository artifacts and local Markdown links | Passed |
| Implementation report generation | Passed |
Retained evidence
artifacts/candidate-specification/candidate-validation-report.jsonartifacts/candidate-specification/evidence-bundle.jsonartifacts/candidate-specification/requirements.jsonartifacts/interoperability/interoperability-report.jsonartifacts/interoperability/evidence-bundle.jsonartifacts/operational-resilience/evidence-bundle.jsonartifacts/release/compatibility-matrix.jsonconformance/reports/reference-implementation-report.json
Assurance boundary
The bundled implementation paths are maintained in one repository and are not evidence of independent external adoption. Network testing uses loopback endpoints, durable-event behavior uses SQLite, and the ARPA–TRQP profile is informative. The validation does not constitute certification, legal recognition, formal TRQP conformance, production security approval, or universal interoperability.
Specification authority correction
The release now has one authoritative prose specification:
spec/agent-registry-protocol-v0.9.0.md. The unchanged v0.5.0 draft and
detached Candidate requirements overlay have been removed. All repository
references and validation gates resolve to the consolidated specification.
GitHub Pages publication hardening
The repository now declares 70 rendered Markdown sources in docs/publication-map.yml. The publication pipeline generates a deterministic source-to-output manifest and blocks deployment when a declared page is absent, an internal .md URL remains unresolved, a local target or asset is missing, a heading fragment is invalid, or two sources collide on one output path.
Offline validation completed for the publication inventory, explicit front matter, local Markdown source links, workflow YAML, repository validation, candidate validation, and the complete release-check suite. The authoritative Jekyll rendering check runs in GitHub Actions through make pages-check, where the pinned Ruby dependencies are installed by ruby/setup-ruby.
v0.9.1 Implementation Accelerator validation
make release-check: passed.- Python service and publication-validator tests: 10 passed.
- End-to-end sample registry loading: 6 records accepted.
- Pilot readiness validator: 14/14 checks passed; decision
ready. - Publication manifest: 89 rendered pages declared.
- Local Jekyll rendering was not executed in the build environment because Bundler was unavailable; GitHub Actions remains the authoritative Pages rendering gate.
Passing these checks demonstrates repository-controlled reference behaviour only. It does not replace operator governance, security review, production hardening or independent conformance assessment.
v0.9.3 A2A registry convergence
make release-check additionally validates A2A publication invariants, structured discovery semantics, immutable snapshot requirements, compatibility classification and non-implication of authority. Dedicated results are emitted under artifacts/interoperability/a2a-registry-*.json.
v0.9.5 TypeScript and information-architecture validation
- TypeScript unit tests: 13/13 passed.
- Shared TypeScript conformance vectors: 12/12 passed.
- TypeScript historical-resolution vectors: 15/15 passed.
- TypeScript A2A adapter checks: 5/5 passed.
- Python↔TypeScript deterministic + historical equivalence: 27/27 passed.
- Python↔TypeScript loopback HTTP interoperability: 7/7 passed.
- Repository release gate:
make release-check-all. - Documentation navigation is organized around six task-oriented journey hubs while retaining existing document URLs.
The local execution environment did not expose a working Bundler/Jekyll executable, so the GitHub Pages build remains enforced by the repository Pages workflow. Repository-level Markdown link validation and publication-manifest generation are included in CI.
Operational resilience assurance hardening
The unreleased hardening increment adds cross-cutting operational resilience requirements in Candidate Specification §36.9 and a machine-readable Operational Resilience Declaration. The repository suite validates 8/8 modeled vectors covering retry budgets, partial outage, recovery hysteresis, poison-event isolation, durable acknowledgement order, dependency amplification, and safety-critical progress under query saturation. The normative-requirements registry now contains 316 synchronized requirements.
These fixtures demonstrate repository-owned modeled assurance only. Deployment-specific failure injection, capacity testing, observability evidence and independent assurance remain operator responsibilities.