// Copyright 2024-2026 Tymofii Pidlisnyi. Apache-2.0 license. See LICENSE.
// ══════════════════════════════════════════════════════════════════
// W2-B3. Revocation enforcement - type surface (additive, optional)
// ══════════════════════════════════════════════════════════════════
// These types sit on top of the M4 verifier-hardening recorder
// (src/v2/verifier-hardening/index.ts). M4 records WHAT a revocation
// source reported (a RevocationFreshnessRecord). This module decides
// what a relying party DOES with that record, under a stated policy.
//
// Layer boundary: the SDK ships the policy shape, the ephemeral-token
// FORMAT, the refresh check, and the SET emission HOOK. Distribution
// (Bloom filters, push channels, transparency logs) is the gateway's
// job and is out of scope here. See the proof box in ./index.ts.
//
// Claims language: these primitives are "specified / tested / validated",
// never "proved / guaranteed". A freshness-policy decision applies the
// configured rule to the recorded staleness; it does not assert the
// revocation source was globally current beyond that recorded staleness.
export {};
//# sourceMappingURL=types.js.map