/**
 * Storage Categories & Bucket Organization
 *
 * Provider-agnostic storage organization by PURPOSE and CONTENT TYPE.
 * Adapters internally translate these purposes to their naming conventions.
 *
 * Universal approach:
 * - Define buckets by PURPOSE (compliance, media-images, backups, etc.)
 * - Paths are universal across all providers
 * - Adapters handle their own naming rules internally
 *
 * @module @plyaz/config/storage/categories
 */
import type { StorageCategory } from '@plyaz/types';
import { BUCKET_PURPOSE } from '@plyaz/types';
/**
 * Constants for storage retention policies (in days)
 */
export declare const STORAGE_RETENTION_DAYS: {
    readonly DAYS_PER_YEAR: 365;
    readonly COMPLIANCE_YEARS: 7;
    readonly TEMPORARY_DAYS: 7;
    readonly BACKUP_DAYS: 90;
};
/**
 * Constants for TTL calculations
 */
export declare const STORAGE_TTL_CONSTANTS: {
    readonly SECONDS_PER_DAY: 86400;
};
/**
 * Storage category definitions
 * Provider-agnostic organization by purpose
 */
export declare const STORAGE_CATEGORIES: Record<BUCKET_PURPOSE, StorageCategory>;
/**
 * Example adapter bucket name translation:
 *
 * Identifier: "compliance:enterprise:acme-corp:prod"
 *
 * CloudflareR2Adapter translates to:
 * → plyaz-prod-weur-enterprise-acme-corp-records-vault
 *
 * SupabaseStorageAdapter translates to:
 * → compliance-acme-corp (projects handle env)
 *
 * S3Adapter translates to:
 * → plyaz-compliance-enterprise-acme-corp-prod-us-east-1
 *
 * All use the SAME paths internally!
 */
//# sourceMappingURL=categories.d.ts.map