/**
 * The briefing: the text every connector hands its agent when a session starts, so an agent is told
 * the same things about working on the mesh whichever harness runs it, and the text is written
 * once. Each connector adds only how a peer message shows up in its model's context; everything
 * else (orient first, feedback, mesh-first, durable runs, where to talk, how to reply, attention)
 * is composed here from the shared sentences in `orientation.ts` and `config.ts`.
 *
 * `docs/agent-briefing.mdx` is generated from this module (`pnpm gen:briefingdoc`) so a reviewer
 * reads the text each harness receives, and `pnpm check:docsbundle` fails when the page drifts.
 */
import { type AgentConfig } from "./config.js";
/** The harnesses a briefing is rendered for, keyed as each connector tags its tools (`source`).
 *  `gateway` is a conversation that joined through `cotal_connect`; how it hears messages depends on
 *  the embedder, which says so in the connect result, so the briefing leaves that sentence out. */
export declare const BRIEFING_HARNESSES: readonly ["claude-code", "codex", "jcode", "opencode", "hermes", "pi", "gateway"];
export type BriefingHarness = (typeof BRIEFING_HARNESSES)[number];
/** How to answer, the same in every harness: a reply exists only when a tool sends it. */
export declare const REPLY_GUIDANCE: string;
/** Attention and per-channel modes, the same in every harness. */
export declare const ATTENTION_GUIDANCE: string;
/** Reply etiquette, the same in every harness. When to mention a peer lives with the channel
 *  guidance, where the wake rule is explained. */
export declare const REPLY_ETIQUETTE: string;
/** The briefing for one agent in one harness, as paragraphs. A connector prepends its persona and
 *  places the text where its harness takes a system prompt; it never edits the paragraphs. */
export declare function briefing(config: Pick<AgentConfig, "name" | "role" | "space" | "feedbackKey">, harness: BriefingHarness): string;
//# sourceMappingURL=briefing.d.ts.map