/**
 * The `aidlc compliance` command group — install, inspect and report on
 * compliance packs.
 *
 * Registered early in the instance, before any subcommand has an implementation,
 * for two reasons the design review established. Six later tasks assert
 * observable properties of invocations of these commands, so the commands have to
 * exist before those tasks can be written. And the moment a top-level command is
 * registered, five pre-existing pins fail — the website's exact sorted command
 * set, the website's generated CLI reference, the entrypoint command count, the
 * menu's unaccounted-commands tripwire, and the two hand-maintained README
 * tables. Those updates belong in one commit with the registration rather than
 * spread across the tasks that follow it.
 *
 * The full option surface is declared here even though the actions are not
 * implemented, because the generated CLI reference is produced by a `--help` walk
 * of the built CLI. Declaring the surface once means regenerating that reference
 * once.
 *
 * Every action currently exits 2 with a message naming the task that will
 * implement it. Exit 2 is this feature's usage-or-load-error class, so an
 * unimplemented subcommand cannot be mistaken for a passing check — a compliance
 * command that exited 0 while doing nothing is precisely the silent false-green
 * this feature exists to avoid.
 *
 * Requirements: compliance-packs/AC-51 (menu accounting). The behaviour of each
 * subcommand is carried by its own task and its own criteria.
 */
import { Command } from 'commander';
/**
 * Register the `aidlc compliance` group and its subcommands.
 *
 * @param program - The commander program.
 */
export declare function registerCompliance(program: Command): void;
//# sourceMappingURL=compliance.d.ts.map