import { PromptModule, ModuleConfig } from './prompt-module.interface.js';
/**
 * Role Boundary module — enforces per-role boundaries and the Try-Before-Refuse protocol.
 *
 * Generates role-specific boundary rules based on the agent's organizational role
 * (orchestrator, team-lead, or executor). Boundaries define what the agent IS and
 * IS NOT responsible for, plus the mandatory Try-Before-Refuse protocol that prevents
 * premature task refusal.
 *
 * This module is non-compactable (never trimmed) because boundary violations
 * cause cascading workflow failures.
 *
 * Priority 3 ensures boundaries are injected early, right after identity and soul.
 */
export declare class RoleBoundaryModule implements PromptModule {
    name: string;
    priority: number;
    maxTokens: number;
    compactable: boolean;
    /**
     * Always included — every agent needs role boundaries.
     *
     * @param _config - Module configuration (unused)
     * @returns Always true
     */
    shouldInclude(_config: ModuleConfig): boolean;
    /**
     * Build the role boundary section based on the agent's organizational role.
     *
     * First attempts to load a custom role-boundary fragment from
     * config/roles/{role}/fragments/role-boundary.md. If not found,
     * falls back to inline content determined by orgRole.
     *
     * @param config - Module configuration with orgRole and role fields
     * @returns Formatted markdown role boundary section
     */
    build(config: ModuleConfig): Promise<string>;
    /**
     * Build organization context section (job, ownership, service contract).
     * Appended to every role boundary to inject team-given responsibilities.
     */
    private buildOrganizationContext;
    /**
     * Build the shared Guidance Priority Chain that applies to all roles.
     *
     * Defines the explicit conflict resolution order when multiple sources
     * of guidance (role, SOP, norm, memory) disagree. Higher-priority
     * constraints always win.
     *
     * @returns Guidance priority chain markdown
     */
    private buildGuidancePriorityChain;
    /**
     * Build the shared Core Execution Principles that apply to all roles.
     *
     * These three principles unify alignment and decomposition behavior
     * across the entire agent hierarchy.
     *
     * @returns Core execution principles markdown
     */
    private buildCoreExecutionPrinciples;
    /**
     * Build boundary content for the orchestrator role.
     *
     * Orchestrators are message routers and context compressors.
     * They must not make strategy decisions or write code.
     *
     * @returns Orchestrator boundary markdown
     */
    private buildOrchestratorBoundary;
    /**
     * Build boundary content for the team-lead role.
     *
     * Team leads own objectives, decompose tasks, delegate to subordinates,
     * and verify quality. They do not communicate directly with users.
     *
     * @returns Team lead boundary markdown
     */
    private buildTeamLeadBoundary;
    /**
     * Build boundary content for the executor role.
     *
     * Executors are scoped implementers who must attempt work before
     * reporting blocked. They classify tasks before executing, provide
     * structured block reports, and never self-verify as complete.
     *
     * @returns Executor boundary markdown
     */
    private buildExecutorBoundary;
}
//# sourceMappingURL=role-boundary.module.d.ts.map