/**
 * What a finding about an instruction file tells the reader to DO — the one
 * owner of that wording, so lint, audit and compile cannot drift apart.
 *
 * Where always-loaded text can go instead of being deleted.
 *
 * Every finding that says "too much is loaded on every request" — the weight
 * ceiling, the ratchet's growth, the refusal to record a heavier baseline, a
 * section or the whole Rules section over its `compile-budget` — ends with
 * this list. Without it the one move the message offers is "cut content", and
 * the reader deletes rules that still matter instead of moving each one to the
 * carrier that loads it only when it applies. The order is the order to try: the cheapest carrier that
 * still fires at the right moment first, deletion last.
 */
export declare const MOVE_OUT_OF_ALWAYS_LOADED: string;
/**
 * The two ways to put a hand-written instruction file under a spec, each said
 * for what it does. They are not interchangeable: `init --target` is the
 * deterministic floor (`adoptMarkdown` — every heading becomes a verbatim prose
 * section, only backticked paths that resolve become checked `file()` refs, no
 * rule is inferred), while the `adopt-spec` skill is an agent reading the file
 * and mapping rules, commands and paths to typed calls. The skill is
 * user-invoked (`disable-model-invocation`), so it has to be asked for.
 * Neither edits the markdown: switching it to spec-managed is a `compile` the
 * user runs after reviewing.
 */
export declare function adoptInstructionFileRemedy(path: string): string;
/**
 * For a file the repository does not own — vendored, a corpus, a fixture: drop
 * its folder from what vigiles reads. `exclude` is top-level in
 * `.vigilesrc.json`, and its globs are relative to the repository root.
 */
export declare function excludeFolderRemedy(path: string): string;
/**
 * For instruction files kept hand-written on purpose (a notes or
 * knowledge-base folder): turn the rule off for those folders with an
 * `overrides` entry — the rule keeps guarding every other folder. Off for the
 * whole repository is the last resort, named last.
 */
export declare function keepHandWrittenRemedy(path: string): string;
/**
 * Everything a `require-instructions-spec` finding says to do, in the order to
 * try it: adopt, else exclude what is not yours, else turn the rule off for the
 * folders that stay hand-written. It is the first finding a new adopter sees,
 * so it names commands and config, not concepts.
 */
export declare function handWrittenInstructionRemedy(path: string): string;
//# sourceMappingURL=instruction-remedies.d.ts.map