Provide a repeatable public-only verification that a third-party integrator can implement a minimal Axme integration without private repository context.
axp-spec/docs/public-api-schema-index.mdaxp-spec/docs/schema-versioning-rules.mdaxp-spec/docs/protocol-error-status-model.mdaxp-spec/docs/idempotency-correlation-rules.mdaxme-docs/docs/public-api-auth.mdaxme-docs/docs/supported-limits-and-error-model.mdaxme-docs/docs/migration-and-deprecation-policy.mdaxme-docs/docs/openapi/gateway.v1.jsonaxme-docs/docs/integration-quickstart.mdaxme-docs/docs/axme-is-not-rpc.mdaxme-docs/docs/mcp-axme-continuation-pattern.mdaxme-docs/docs/migration-message-centric-to-intent-lifecycle.md
- Identify required auth headers and token/key semantics from
public-api-auth.md. - Generate client request models from OpenAPI and/or JSON schemas.
- Implement minimal API flow:
POST /v1/intentsGET /v1/intents/{intent_id}/events/streamGET /v1/intents/{intent_id}/events?since=<seq>GET /v1/intents/{intent_id}GET /v1/inbox
- Add retry/idempotency behavior for retryable write paths.
- Implement error handling for
401,403,409,413,422,429, and transient5xx. - Enforce version pinning and migration posture from the deprecation policy.
- Integrator can complete minimal flow implementation using only public repositories.
- Request/response payloads validate against published public API schemas.
- Error handling and rate-limit handling behavior are explicitly implemented.
- No private repository files are required to understand contracts or baseline integration behavior.
For each dry-run execution, capture:
- date and commit SHAs of
axp-specandaxme-docs, - implemented endpoints and payload contracts,
- validation result summary,
- observed issues/gaps and linked follow-up items (if any).