/**
 * How seats learn the rules (DES-decision-capture §4.7, DC-S7) — the text halves, pure.
 *
 *  - The chat scope statement lists the chat project's in-force rules as `[rule:<id>] statement`
 *    lines, severity-ordered and capped at {@link RULES_STATEMENT_CAP}.
 *  - A rule remembered mid-chat reaches the seats as a crew-authored `wicked-context` preface on
 *    the next send, disclosed to the operator as a `system` transcript record.
 *
 * Both tell the seat to cite a rule it follows as `[rule:<id>]`, and both say what crew does with
 * that: shows it as cited — unchecked. Nothing here (and nothing anywhere in crew) turns a citation into
 * a compliance verdict; that belongs to DES-rule-check (B4).
 */
import type { ConformanceRule } from '../core/types.js';
export declare const RULES_STATEMENT_CAP = 20;
/** Severity first (critical → info), then id — a stable order a seat and an operator both read. */
export declare function orderBySeverity<T extends Pick<ConformanceRule, 'id' | 'severity'>>(rules: ReadonlyArray<T>): T[];
/** The `## Rules in force` section of the scope statement (no trailing blank line). */
export declare function rulesStatementLines(rules: ReadonlyArray<ConformanceRule>): string[];
/** The preface a send carries when rules landed since the seats last heard from crew. */
export declare function rulesPreface(rules: ReadonlyArray<ConformanceRule>): string;
//# sourceMappingURL=rules-text.d.ts.map