/**
 * NB-5 — the decomposition-policy system blurb + few-shot. Prepended to a Family-A worker's system prompt so
 * the model has an in-context example of HOW to split before it is offered the `spawn_child` A-tool. Flat-first
 * (§4.2/§8): the model fans out flat over a window-sized batch and only escalates to a nested `spawn_child`
 * when a single sub-task is genuinely too large to handle directly. Worked splits are deliberately small —
 * the lift is from showing the SHAPE of a good split, not from volume.
 * @type {string}
 */
export const DECOMPOSITION_POLICY: string;
/**
 * NB-4 / RC-12 — the depth-aware capability-scrub suffix. Deeper workers get a more conservative prompt:
 * "prefer direct action, only delegate if truly necessary." Combined with the inline `canSpawn` check (the
 * tool half of the scrub: `depth < maxDepth` withholds `spawn_child` at the cap) in recurse.js, this realizes
 * guard #5's prompt+tool-shaping half (the part bareguard's blind
 * `policy` cap cannot express). At depth 0 there is no suffix (the top-level worker decomposes freely);
 * from depth 1 on, each level nudges harder toward answering directly so recursion contracts toward its base
 * case rather than fanning out without bound.
 * @param {number} depth - The worker's depth (0 = top level).
 * @param {number} maxDepth - The topology ceiling; at `depth >= maxDepth` the `spawn_child` tool is withheld.
 * @returns {string} A suffix to append to the worker system prompt ('' at depth 0).
 */
export function capabilityScrub(depth: number, maxDepth: number): string;