/**
 * Three opt-in OpenBadges verification suite bundles.
 *
 * Consumers compose verifier configurations by passing one (or more)
 * of these to a verify call's `additionalSuites`:
 *
 * - {@link openBadgesSemanticSuite} — fast, in-process Zod-based
 *   cross-field semantic checks. **No network access required.**
 *   Safe to enable in latency-sensitive contexts.
 * - {@link openBadgesSchemaSuite} — AJV-backed JSON Schema validation
 *   against the published OBv3 schemas. Requires fetching the schema
 *   document at first use; subsequent runs reuse the AJV instance's
 *   in-memory cache.
 * - {@link openBadgesSuite} — the union of the two above. Convenience
 *   for consumers who want full OB coverage and accept the schema
 *   suite's network cost.
 *
 * None of these are part of the verifier's default suite set; the
 * 2026-04-18 plan ([Q2](../../docs/plans/2026-04-18-openbadges-module/00-questions.md#q2-default-path-behavior))
 * makes OpenBadges verification fully opt-in. To enable:
 *
 * @example
 * ```ts
 * import { createVerifier } from '@interop/verifier-core';
 * import { openBadgesSuite } from '@interop/verifier-core/openbadges';
 *
 * const verifier = createVerifier();
 * await verifier.verifyCredential({
 *   credential,
 *   additionalSuites: [openBadgesSuite],
 * });
 * ```
 */
import { VerificationSuite } from '../types/check.js';
export declare const openBadgesSemanticSuite: VerificationSuite;
export declare const openBadgesSchemaSuite: VerificationSuite;
export declare const openBadgesSuite: VerificationSuite;
//# sourceMappingURL=openbadges-suite.d.ts.map