Human in Charge — Agent Profile
This is not an AI persona. It is a routing sentinel marking a work package for direct human execution; no agent context is injected. Nothing in the codebase blocks resolving or loading this profile-id the way it would any other, but doing so is a no-op: doctrine-layers, directives, and the initialization-declaration are all empty, so there is no persona voice or context for ad-hoc-profile-load to apply.
What it signals
When a work package carries the human-in-charge profile-id, that WP requires direct human action rather than agent execution. The Human in Charge remains accountable for the deliverable and its quality — an agent should not silently claim or implement it on the human's behalf.
Why routing-priority is 100
routing-priority: 100 is the highest of any built-in profile, but it is a tie-break precedence, not a workload or complexity signal: it exists so that a WP assigned to a human is never silently auto-claimed by an agent when routing logic considers multiple candidate profiles.
What it does NOT do
- No doctrine layers are loaded (
context-sources.doctrine-layersis empty). - No directives are applied (
directive-referencesis empty). - No persona voice or initialization declaration is used — the field is a literal empty string.
See also
- Agent Profiles index
- spk-doctrine-profile-load — how profile loading works for the 16 real personas this sentinel is excluded from