Conformance
Separate wire-format vectors from source coverage and live integration proof.
Conformance is specific to a protocol and implementation revision. The source includes canonical ACT vectors, authentication transport vectors, and separate authority/integration cases. Their existence is not proof that every runner passed for a deployed release.
What to test
| Area | Required evidence |
|---|---|
| ACT format | Size and envelope limits, algorithm/version handling, signature verification, time, issuer, audience, scopes, delegation attenuation |
| Authentication | Exact challenge canonicalization, nonce correlation/replay/expiry, proof encoding, session expiry and transport scheme |
| Authority | Configured PrivilegedAuthorityVerifier, trusted lineage anchors, revocation/liveness, tenant policy |
| SDK integration | Real provider wiring, supported features, negative/error behavior, language-specific key restoration |
| Deployment | Actual ingress, replica-aware session state, secrets, runtime bindings and production policy |
Source locations
- Canonical token crate and specification:
act/agent-capability-token,act/SPECIFICATION.md. - Shared authentication/vector corpus:
openagent-sdk/conformance. - Per-language verifier tests and vector runners:
openagent-sdk/sdks/<language>. - Authority draft vectors:
openagent-sdk/conformance/vectors/openagent/lineage-authority.draft.json.
Draft vectors are design material, not a final interoperability certification. Fixed test counts are intentionally omitted: they drift independently of the protocol contract.
Release evidence
Record the revision, enabled features, runtime versions, vector corpus digest, command, pass/fail totals, and skipped cases. Keep source inspection, local sample execution, complete SDK tests, hosted smoke checks, and production certification separate. This documentation migration does not itself rerun every backend or cryptographic test suite.