import { type KitBlueprint } from './core.js';
/** Options for {@link moderationBlueprint}. */
export interface ModerationBlueprintOptions {
    /** Prefix for the type/function names. Defaults to none. */
    typePrefix?: string;
}
/** Names derived by {@link moderationBlueprint} for a given prefix. */
export interface ModerationNames {
    reportType: string;
    muteType: string;
    fileReportFn: string;
    resolveReportFn: string;
}
/** Compute the type/function names a moderation blueprint (and its runtime helper) uses. */
export declare function moderationNames(typePrefix?: string): ModerationNames;
/**
 * Blueprint for **moderation** (matrix P6) — MODEL + CLIENT, no compute:
 *
 * - `ModReport` containers are the escalation queue: any player files one
 *   against a subject (`file_report` is member-instantiable through the
 *   runtime helper — the caller's own report row); app admins read the
 *   open queue and `resolve_report` with a disposition.
 * - `ModMute` containers are per-player mute lists (client-enforced: the
 *   runtime helper filters chat client-side — mutes are personal, not
 *   punitive).
 * - ENFORCEMENT stays on existing platform surfaces: admins revoke access
 *   tiers / grid permissions; nothing new to trust here.
 *
 * Runtime counterpart: `client.kit(appId).moderation`.
 */
export declare function moderationBlueprint(options?: ModerationBlueprintOptions): KitBlueprint;
//# sourceMappingURL=moderation.d.ts.map