Skip to content
AIGP

RFC-013: Inter-Gandalf Delegation Protocol (IMDP) — 2. Core Principles

AIGP Specification › RFC-013: Inter-Gandalf Delegation Protocol (IMDP) › 2. Core Principles

← 1. Purpose · Section index · 3. Domain Map →

2. Core Principles

  1. Domain Ownership

    • Each Gandalf owns a domain of expertise. It is the authority for that domain.
    • Delegation happens when a request crosses domain boundaries.

  2. Originator Stays in the Loop

    • The originating Gandalf is the user’s interface. It delegates, receives the result, and summarizes.
    • The user never interacts directly with the delegate Gandalf.

  3. Capability-First Routing

    • Before delegating, the originator queries the target’s capability manifest.
    • If the target cannot handle the request, delegation does not occur.

  4. Bounded Depth

    • Max delegation depth: 2 (originator delegate sub-delegate).
    • A sub-delegate MUST NOT delegate further.

  5. AIGP-Governed

    • Every delegation is an AI operation. It MUST pass an AIGP REQUEST check before dispatch.
    • Every delegation result MUST be recorded via AIGP RECORD.

  6. ACP-Contextualized

    • The delegate receives execution context via ACP, not raw user input.
    • The originator assembles the context payload before delegating.

← 1. Purpose · Section index · 3. Domain Map →