Proposed specificationSource-located exemplarH1

Manager coordination

Keep a coordinating agent in control of specialists.

JOIN POINTmanager_owned_specialist_workRECORD STATUSCandidate · v0.1.0

UML class view

The proposed contract drawn as participant roles, received calls, and numbered dependencies.

Object interactions

The same roles and calls as a class collaboration and a numbered message sequence.

Object interaction diagram for Manager coordination, showing role collaboration and a numbered message sequence — FIG. W06 / OBJECT INTERACTIONS
Open full SVG Download PDF

Pointcut

Where the mechanism applies. All four dimensions belong to the proposed match, not just its vocabulary.

Context: A manager remains responsible while specialists perform parts of a task.
Trigger: The manager delegates, selects, or calls a specialist.
Structure: Manager-owned plan, specialist interfaces, and integrated response.
Effect: The manager synthesizes specialist outputs and preserves responsibility.

Protected contract

The obligation that clients, operators, and auditors should be able to rely on.

Requires: Manager and specialist roles are distinguishable.
Ensures: Specialist outputs are attributed and integrated under manager authority.
Invariant: Delegation does not transfer final goal ownership implicitly.
Violation: Specialist conflict, failure, or omission is resolved or surfaced by the manager.

Negative control

A coordinator that merely launches tasks without integration is W04.

Variation & lifecycle

The hot spot is admitted only where the protected semantics survive.

Permitted variation

Hierarchical Crew, supervisor, coordinator, and manager-agent patterns.

Test obligation

Test specialist disagreement, failure, and manager synthesis.

Evolution question

Did managers gain explicit budgets and specialist authorization?

Prompt + code design

An illustrative prompt and a small design sketch for the proposed contract. Names and APIs are invented; this is not a repository excerpt.

PROMPT SKETCH

Let the manager own task assignment and integration. Specialists may propose outputs, but the manager must attribute each contribution and decide what enters the final result.

CODE DESIGN / PYTHON

def manage(task, specialists, manager):
    assignments = manager.assign(task, specialists)
    contributions = []
    for specialist, subtask in assignments:
        output = specialist.run(subtask)
        contributions.append(Attribution(specialist.id, subtask.id, output))
    return manager.integrate(task, contributions)

Illustrative design sketch. Attribution is the manager's contract; unlabeled specialist text is not integration. This example is a teaching aid, not implementation evidence or a conformance claim.

Detection & matching

The frozen rule that retrieves this record, the canonical source exemplar, and the control that should stay unmatched.

Join point: manager_owned_specialist_work
Source locator: OpenAI
Lexical cue: (?i)\b(?:manager[_-]?agent|supervisor|coordinator[_-]?agent|manager[_-]?coordination)\bFrozen expression, v0.1.0. A match is a retrieval cue, not a confirmed implementation.
Aliases: None
Canonical exemplar: crewAIInc/crewAIlib/crewai/src/crewai/crew.py:1533Support: lib/crewai/tests/test_crew.py:1
Negative control: A coordinator that merely launches tasks without integration is W04.

Scope-anchored review. pohe-agent analyze <repo> --pattern W06 anchors the cue to its enclosing declaration and checks a separate operational signature for all four pointcut dimensions. Missing roles and negative-control risks remain visible; a structural match is not E2/E3. Calibration report ↗

Repository files

Up to five public files retrieved by the frozen cue and pinned to the audited commit. A match is a place to inspect, not a confirmed implementation.

01crewAIInc/crewAIlib/crewai/src/crewai/crew.py:1533CANONICAL SOURCE 02agno-agi/agnolibs/agno/agno/sandbox/agentcore/server.py:86RETRIEVAL CUE 03anomalyco/opencodepackages/core/src/instance.ts:33RETRIEVAL CUE 04bytedance/deer-flowbackend/app/channels/runtime_config_store.py:15RETRIEVAL CUE 05cline/clineapps/cli/src/commands/connect.ts:122RETRIEVAL CUE

Evidence & provenance

Each layer answers a different question. Do not substitute retrieval for review.

Source-located exemplar

A concrete source anchor is available for this proposed record. It is one exemplar, not evidence that all repositories—or every contract field—conform.

Review boundary: this candidate and its specification come from an AI-assisted study. Independent human validation remains open.

ANY-EVIDENCE FAMILY COVERAGE27/36

75.0% of repository families in the frozen panel have at least one current cue, historical cue, or canonical source layer. This is not confirmed prevalence.

Current lexical-cue repositories: 28 / 41

Canonical source anchorcrewAIInc/crewAI 7abc196a176alib/crewai/src/crewai/crew.py:1533

Supporting surfacelib/crewai/tests/test_crew.py:1

Hierarchical process creates a manager agent.

Exploratory retrieval cue Regex / v0.1.0

(?i)\b(?:manager[_-]?agent|supervisor|coordinator[_-]?agent|manager[_-]?coordination)\b

This expression is a discovery instrument only. A match is a retrieval cue—not a confirmed implementation, pointcut match, or contract proof.