Skip to content

Guided tour

FabrCore 2.0 · Release and package availability

These guides track the current 2.0 source. Stable 2.0.0 publication is pending; package commands show the release target. Until it is published, follow the source quick start or use a matching available prerelease set. Release migration · Runtime modes

MODULE 06 · LESSON 6.3

Delegate to addressable agents

Delegate independent work to addressable specialist agents.

Lesson 35 of 86 · FabrCore 2.0

Overview

A roster lets the model discover useful specialists with meaningful descriptions. Delegation remains ordinary FabrCore messaging with principal ownership, ACL and monitoring. A private internal specialist has no public handle; a roster delegate does.

A roster describes addressable capabilities

The parent needs to know which specialist handle is useful and what it can do. Create the specialist instances first, give them clear descriptions, and list the intended handles in _HarnessBackgroundAgents. A roster entry does not create the agent or grant cross-principal access. Private internal agents from module 3 have a different ownership and addressing model.

Waiting is not cancellation

A delegation can continue while a wait call reaches its own timeout. Track task states rather than assuming the absence of a reply means failure or completion. The parent must collect the result, report a timeout honestly, and avoid launching duplicate business work just because a UI stopped waiting. Inspect failed or lost outcomes before deciding to retry.

Provision and select delegates

  1. Create policy and request-history instances and describe their capabilities. Configure _HarnessBackgroundAgents with correct handles.
  2. Set background task and wait timeouts; collect results with the background tools rather than assuming a started task succeeded.
  3. Continue a completed delegate when more work is required, clear completed records when appropriate, and surface failed/lost outcomes to the user.
Background Agents · reference snippet 
"args": {
  "_HarnessBackgroundAgents": "eric:crm,eric:policy-desk",
  "_HarnessBackgroundTimeoutSeconds": "180"
}

Observe a successful and failed delegate

  1. Provision a policy specialist and confirm its fully qualified address is reachable under the parent's authorization. Ask the parent to request a bounded policy review.
  2. Inspect the delegated request, specialist response and parent summary. The parent should use the actual returned result and retain any qualification about missing facts.
  3. Make the specialist unavailable in a test. Expect the task/parent response to identify that failure or timeout. A “started” record alone must not be shown as a completed review.

Delegation adds another asynchronous business operation. Its receipt, lifetime and result need the same care as any other remote call.

If the result is different

Descriptions should say when to consult versus assign execution. A timeout from the wait tool may leave background work running; it is not automatic cancellation.

Go deeper

Explore the related documentation.