Skip to content

RFC-013: Inter-Gandalf Delegation Protocol (IMDP) — 5. Delegation Flow

AIGP SpecificationRFC-013: Inter-Gandalf Delegation Protocol (IMDP) › 5. Delegation Flow

← 4. Capability Manifests · Section index · 6. Protocol Messages →

5. Delegation Flow

User Originator governance-server Delegate
Gandalf (AIGP) Gandalf
1. Request
>
2. CAPABILITY_QUERY
>
3. Capability Manifest
<
4. AIGP REQUEST
(delegation)
>
5. ALLOW
<
6. DELEGATE (with ACP context)
>
7. Execute
(domain work)
8. DELEGATE_RESULT
<
9. AIGP RECORD
(delegation)
>
10. Summary
<

5.1 Flow Steps

Step Actor Action
1 User Sends request to originator Gandalf
2 Originator Sends CAPABILITY_QUERY to candidate delegate
3 Delegate Returns capability manifest
4 Originator Sends AIGP REQUEST to governance-server (is this delegation allowed?)
5 governance-server Returns ALLOW / DENY
6 Originator Sends DELEGATE message with ACP-assembled context
7 Delegate Executes the task within its domain
8 Delegate Returns DELEGATE_RESULT to originator
9 Originator Sends AIGP RECORD to governance-server (delegation completed)
10 Originator Summarizes the result and responds to user

5.2 Example: Cross-Domain Delegation

User asks identity-service Gandalf: “Convert our Prisma policies to AWS format”

  1. identity-service Gandalf recognizes this is an analytics domain task
  2. Queries analytics-service Gandalf’s capabilities finds policy_conversion
  3. Checks with governance-server ALLOW
  4. Assembles ACP context (source policies, conversion parameters)
  5. Sends DELEGATE to analytics-service Gandalf
  6. analytics-service Gandalf executes the conversion
  7. Returns DELEGATE_RESULT with conversion_state
  8. identity-service Gandalf summarizes: “Converted 47 policies 42 clean, 3 gaps, 2 manual review”

← 4. Capability Manifests · Section index · 6. Protocol Messages →