ad-hoc-profile-load

Role switching outside the mission runtime loop is handled by loading an agent profile on demand, which applies the profile's identity, specialization boundaries, and scoped doctrine directives immediately for the current session.

Loading an agent profile resolves the target role either by matching an explicit profile ID or by inferring the best match from described task intent, then applies the initialization declaration and governance scope.

Yes, adopting a profile loads only the doctrine directives relevant to that profile and pulls charter context scoped to the inferred or requested action, ensuring the agent operates within correct boundaries.

Persisting the role selection to tool context is optional, allowing subsequent invocations within the interactive session to maintain the adopted identity, specialization boundaries, and governance scope.

The best way to adopt a reviewer persona is to request a role-scoped agent profile by describing your intent, which applies the initialization declaration and specialization boundaries for immediate behavior alignment.

Handoff boundaries and specialization limits are needed to ensure the agent behaves appropriately immediately after role switching, restricting operations to the profile-scoped doctrine directives and adopted identity.