import type { PostSynthCheck, PostSynthDiagnostic } from "./post-synth.js";
/**
 * Load project policy checks (one or more `PostSynthCheck` exports) from files,
 * **into this process**.
 *
 * chant #1131 — refuses while `./policy-sandbox.ts` is armed. Under `--sandbox`
 * the policy modules are imported and their checks run inside a child process
 * (`runProjectPolicies`); reaching this function anyway means a call site is
 * about to execute project-authored code in the CLI's own process, which is
 * precisely the thing the flag promises does not happen. Failing loudly is the
 * only honest option — falling through would make `--sandbox` mean less than it
 * says without anything visible to notice.
 */
export declare function loadPolicyChecks(paths: string[], configDir: string): Promise<PostSynthCheck[]>;
export interface PolicyEvaluation {
    /** All policy diagnostics (errors + warnings), after `lint.rules` severity overrides. */
    diagnostics: PostSynthDiagnostic[];
    /** The error-severity subset (post-override) — these are policy *violations* that gate. */
    violations: PostSynthDiagnostic[];
    /** The environment policies were evaluated against (if any). */
    env?: string;
    /**
     * chant #1138 — diagnostics `lint.rules` turned `"off"`, present here rather
     * than dropped so a caller (`policyGate`, below) can report a count instead
     * of the finding just vanishing.
     */
    suppressed: PostSynthDiagnostic[];
}
/**
 * Build a project and run its `lint.policies` over the resolved resources,
 * standalone — used by the `policyGate` Op step to gate an apply on the same
 * organizational policy `chant build` enforces. Loads the project's lexicons,
 * builds, then runs the policy pack with `env` (explicit, else `ownership.env`).
 */
export declare function evaluateProjectPolicies(opts: {
    path: string;
    env?: string;
}): Promise<PolicyEvaluation>;
//# sourceMappingURL=policy.d.ts.map