/**
 * SystemOfUse contract types for the `resolveLLMForSystem` chokepoint (E9).
 *
 * A "system of use" is the semantic label for the subsystem that is requesting
 * an LLM client — e.g. `'sentient'`, `'memory'`, `'task-executor'`. It is
 * a higher-level, stable identity that CLEO maps to a {@link RoleName} for
 * config resolution. This indirection insulates call-sites from the config
 * vocabulary (roles) and from model/provider churn.
 *
 * `resolveLLMForSystem` is the single DRY chokepoint that the 4-resolver /
 * 3-picker sprawl will collapse onto (E9 · T11745).
 *
 * @module llm/system-resolver
 * @task T11749
 * @epic T11745
 */
/**
 * Static mapping from {@link SystemOfUse} to the {@link RoleName} used for
 * config resolution. This is the canonical default; callers may override
 * individual systems via `config.llm.systemRoles[system]`.
 *
 * @task T11749
 */
export const SYSTEM_ROLE_MAP = {
    sentient: 'consolidation',
    memory: 'extraction',
    'task-executor': 'judgement',
    deriver: 'derivation',
    hygiene: 'hygiene',
    plugin: 'plugin',
    compression: 'compression',
    /** `null` means "use the global LLM default, no per-role config". */
    default: null,
};
//# sourceMappingURL=system-resolver.js.map