/**
 * A centralized collection of numeric constants used to avoid magic numbers across the codebase.
 *
 * Purpose:
 * - Provide named aliases for common numeric values so intent is clearer and maintenance is easier.
 * - Keep commonly used numeric literals (counts, thresholds, time durations, limits) in one place.
 *
 * Typical uses:
 * - Time and duration calculations (e.g., seconds/minutes/hours, TTLs, timeouts).
 * - Pagination, limit and capacity defaults.
 * - Validation thresholds, scaling factors and numeric formatting.
 * - Bit/byte or base arithmetic where small numeric constants improve readability.
 *
 * Properties (brief intent and common usage):
 * - TWO (2) — small counts, boolean-like numeric operations, pair-related logic.
 * - FIVE (5) — small retry counts or UI/validation limits.
 * - NINE (9) — index/format boundaries or small-range checks.
 * - TEN (10) — decimal/base operations, digit limits, common loop bounds.
 * - SIXTEEN (16) — bit/hex operations, buffer sizes or base-16 related math.
 * - TWENTY_FOUR (24) — hours-in-day, daily calculations.
 * - THIRTY_SIX (36) — base-36 or domain-specific scaling factors.
 * - SIXTY (60) — seconds/minutes conversions.
 * - NINETY (90) — percentage/angle thresholds or large-range caps.
 * - HUNDERD (100) — percentage base or general scaling (note: name preserved for backward compatibility).
 * - THOUSAND (1000) — millisecond/rounding bases or thousand-scale thresholds.
 * - FIVE_THOUSAND (5000) — medium-duration timeouts or capacity hints (e.g., ms).
 * - THREE_HUNDERD (300) — short timeouts or conventional numeric boundaries (name preserved).
 * - THIRTY_SIX_HUNDERD (3600) — seconds-per-hour; common default TTL/cache durations (3600 seconds).
 * - THIRTY_THOUSAND (30000) — longer timeouts/polling intervals in milliseconds.
 *
 * Remarks:
 * - Using these constants improves readability and makes it easier to change a value in one place.
 * - Several keys contain spelling inconsistencies (e.g., "HUNDERD", "THREE_HUNDERD", "THIRTY_SIX_HUNDERD") — keep names stable to avoid breaking callers; consider normalizing names in a planned refactor.
 *
 * Example:
 * - const timeoutMs = digits.FIVE_THOUSAND;          // use 5000 ms timeout
 * - const hourlySeconds = digits.THIRTY_SIX_HUNDERD; // use 3600 seconds for TTL
 */
export declare const NUMERIX: {
    TWO: number;
    FIVE: number;
    NINE: number;
    TEN: number;
    TWENTY_FOUR: number;
    THIRTY_SIX: number;
    FIFTY: number;
    SIXTY: number;
    NINETY: number;
    HUNDRED: number;
    FIVE_HUNDERD: number;
    ONE_THOUSAND_AND_FIVE_HUNDERD: number;
    THOUSAND: number;
    TWO_THOUSAND: number;
    THREE_THOUSAND: number;
    FOUR_THOUSAND: number;
    FIVE_THOUSAND: number;
    THIRTY_SIX_HUNDERD: number;
    THREE_HUNDERD: number;
    SIXTEEN: number;
    TWENTY_THOUSAND: number;
    THIRTY_THOUSAND: number;
    FORTY_FIVE_THOUSAND: number;
    FIFTY_THOUSAND: number;
    SIXTY_THOUSAND: number;
};
//# sourceMappingURL=constants.d.ts.map