/**
 * File-claim verdict.
 *
 * Phase 5 cutover: PreToolUse routes Edit/Write/NotebookEdit through here.
 *
 * Two checks:
 *   1. Conflict: is the path already claimed by a fresh peer? Block with
 *      the peer's name in the reason.
 *   2. Ordering: if we already hold a claim on path A and want path
 *      B, B must sort > A lexicographically. Otherwise emit
 *      claim.authority_conflict (ordering_violation) and block.
 *
 * Reads the authority-safe V3 coordination projection. Disposable heartbeat
 * caches are materialization targets, never the source of claim authority.
 */
export type { VerdictResult } from "./verdict.js";
import type { VerdictResult } from "./verdict.js";
export interface ClaimRequest {
    rule: "claim";
    instance_id: string;
    session_id?: string;
    path: string;
    mode?: "read" | "write";
}
/**
 * Evaluate a file-claim. Returns deny when another fresh peer claims the
 * path, OR when this owner already holds a lower-sorted claim and the new
 * one would create a circular wait.
 */
export declare function evaluateClaim(coordRoot: string, req: ClaimRequest): VerdictResult;
//# sourceMappingURL=claim-conflict.d.ts.map