Independent Researcher

deonte@goodshyt.fun https://orcid.org/0009-0005-8586-3650

Security Internet Engineering Task Force AID-1 conformance test vectors identity provenance replay This document defines provider-independent conformance requirements for AID-1. It specifies the execution model for a deterministic machine-readable test-vector corpus, including canonicalization, cryptographic, identity-binding, delegation, authorization, temporal, revocation, replay, attestation, provenance, and integration cases. The conformance corpus contains 69 vectors. Six replay cases are architectural boundary tests, including R5, which requires AID-1 verification to succeed while a downstream D6 scientific-admissibility decision rejects the same evidence.

Introduction AID-1 is intentionally independent of software-only, TPM, TEE, HSM, enclave, cloud, or other implementation providers. Conformance therefore depends on observable verification behavior rather than implementation mechanism. This document defines the semantic contract for the AID-1-TEST machine-readable corpus and its reference vector runner.

Conformance Requirements An implementation claiming conformance to AID-1 MUST execute the complete required vector corpus and MUST produce the expected outcome for every required vector. The provider under test MUST NOT receive privileged knowledge of the expected result beyond the ordinary input data supplied to an AID-1 verifier. The same vector corpus MUST be usable without semantic modification against SoftwareProvider, MockTPMProvider, MockTEEProvider, and future provider implementations.

Machine-Readable Corpus The AID-1-TEST v1 corpus contains 69 deterministic vectors. Each vector SHOULD contain, directly or by stable reference, a base fixture, mutation or transformation, expected verification outcome, expected failure codes where applicable, and any downstream boundary expectations. The machine-readable corpus is the executable test artifact. This document specifies the semantics required for interpreting that corpus.

Vector Execution Model A reference runner SHOULD evaluate each vector using the following conceptual process: A mutation MUST be deterministic. A runner MUST NOT modify fields that are outside the mutation specified by the vector.

Expected Outcomes A vector MAY expect ALLOW, DENY, or INDETERMINATE. A vector MAY also expect one or more standardized failure codes. INDETERMINATE MUST NOT be treated as equivalent to ALLOW for conformance purposes.

Required Coverage The corpus MUST include vectors covering at least:

• JCS canonicalization and rejection of unsupported values;
• Ed25519 positive and negative signature verification;
• tampered-envelope rejection;
• key-substitution rejection;
• identity binding independent from a self-supplied key;
• capability, resource, state, time, and delegation enforcement;
• revoked and unavailable revocation states;
• duplicate nonce and action replay;
• forged or untrusted external attestation;
• key rotation, overlap, supersession, and historical validity;
• audit-chain deletion, reordering, and mutation detection; and
• confused-deputy, audience-confusion, cross-repository replay, delegation-escalation, and stale-credential cases.

Replay and Architectural Boundary Cases Six replay cases, R1 through R6, are reserved as architecture-level conformance cases. These cases are intended to detect accidental collapse of trust domains across implementations.

R5: AID-1 Valid, D6 Reject R5 is a mandatory conformance invariant. An implementation MUST pass R5 by preserving the distinction between AID-1 identity/provenance verification and downstream scientific admissibility. A provider or integration that automatically converts successful AID-1 verification into downstream D6 acceptance is non-conformant.

Provider Independence A provider implementation MAY use software keys, TPM-backed keys, TEE-backed keys, HSMs, secure enclaves, or future mechanisms. The provider MUST expose behavior compatible with the AID-1 verifier and MUST preserve the same externally observable decision semantics. Provider-specific implementation details MUST NOT alter the expected outcome of any provider-independent vector.

Reference Vector Runner The reference runner SHOULD load the corpus manifest, validate each vector against its schema, construct the candidate object, execute the AID-1 verifier, compare actual and expected outcomes, and emit a deterministic report. The reference runner SHOULD report at least the vector identifier, actual decision, expected decision, observed failure codes, expected failure codes, and PASS or FAIL status.

Release Gates An implementation MUST NOT claim completion of the AID-1 v1 security conformance profile until the required gates pass. These gates include:

1. JCS conformance and rejection tests;
2. Ed25519 positive, negative, tampered-envelope, and key-substitution vectors;
3. identity-binding separation from self-supplied key material;
4. independent authorization checks for capability, resource, state, time, and delegation;
5. revocation and unavailable-registry handling;
6. replay resistance;
7. external attestation verification;
8. rotation and historical-verification behavior;
9. audit-integrity checks; and
10. adversarial trust-boundary vectors.

Security Considerations A conformance suite is security-sensitive because a weak oracle can certify incorrect behavior. The corpus, manifest, schemas, and runner SHOULD therefore be content-addressed or otherwise integrity protected. Test providers MUST NOT be permitted to alter vector expectations during execution. CI systems SHOULD pin the corpus revision used for a conformance claim.

Privacy Considerations Conformance fixtures SHOULD use synthetic identities, synthetic credentials, and non-production attestation material unless a test explicitly requires otherwise. Real personal credentials, production secrets, and live private keys MUST NOT be distributed in the public corpus.

IANA Considerations This document requests no IANA actions.

Publication and Versioning The 69-vector corpus SHOULD be versioned independently but SHOULD declare the AID-1 specification revision against which it is evaluated. Published conformance reports SHOULD identify both the corpus revision and the implementation revision.

Normative References