// Copyright 2024-2026 Tymofii Pidlisnyi. Apache-2.0 license. See LICENSE.
// ══════════════════════════════════════════════════════════════════
// Credential Check Policy — verification timing for governance metadata
// ══════════════════════════════════════════════════════════════════
// Proposed by @piiiico on a2aproject/A2A governance metadata thread.
//
// A credential (delegation, attestation, capability token) needs to
// declare WHEN it should be re-verified. Different credential types have
// different trust decay profiles and should be checkable at different
// points in the lifecycle.
//
// Modes:
//   on-accept — verify once at credential acceptance time. Cheap. Trusts
//               the snapshot. Use for long-lived session credentials where
//               live revocation cost is prohibitive and staleness is OK.
//   on-process — verify on every action evaluation. Expensive. Catches
//                live revocation. Default for most delegations.
//   both — verify at acceptance AND at process time. For high-stakes
//          actions (large spend, irreversible operations, cross-org
//          transactions) where you want both checks.
// ══════════════════════════════════════════════════════════════════
export {};
//# sourceMappingURL=types.js.map