AI智能体项目最佳实践-第五章：路由编排与多智能体协作

BestPracticeforAIAgentsProject

Chapter5

Routing,Orchestration,andMulti-AgentTeamwork

JunxianZhu1YiranSun2GuanpingDai3

LinkMindProject

1JunxianZhu,LinkMindProjectTeam,

LandingBJ

2YiranSun,LinkMindProjectTeam,

XiamenUniversityMalaysia

3GuanpingDai,LinkMindProjectTeam,FounderandCEOof

LandingBJ

Contents

1

AbouttheContributors

2

Chapter5.Routing,Orchestration,andMulti-AgentTeamwork

3

LearningObjectives

4

5.1RoutingasaFirst-ClassDecisionLayer

4

5.2OrchestrationIstheWorkPath,NottheModelPath

5

5.3Multi-AgentDesignasResponsibilityArchitecture

6

5.4TheTopologyofMultipleLobsters,OneLinkMind

6

5.5Hands-OnLab:AMulti-AgentIncidentWorkflow

7

5.6Observability,Cost,andReliabilityinTeamedAgentSystems

10

5.7TheTeamOperatingModel

10

5.8CommonAnti-Patterns

11

5.9CollaborationPatternsbeyondtheSimpleTrio

11

5.10DistributedTopologies:Proxy,GEO,Cascade,andLocalAccel-

eration

12

5.11MeasuringMaturityinMulti-AgentPrograms

13

5.12AdoptionRoadmapandOrganizationalDesign

13

ChapterSummary

14

ReviewQuestions

15

FurtherStudy:SharedStandardsandCross-TeamBudgeting

15

FurtherStudy:MigrationfromIsolatedSuccessestoaCommonPlane

16

AbouttheContributors

2

JunxianZhu

LinkMindProjectTeam,

LandingBJ

•Focusontheresearchanddevelopmentoflargemodelproducts,coveringalgorithmsandapplications

•Richexperienceinfull-processdevelopmentanddeliveryofgovernmentandenterpriseprojects

YiranSun

LinkMindProjectTeam,

XiamenUniversityMalaysia

•FocusonAIagentengineeringpracticesandappliedAIworkflows

•Backgroundincomputerscience,machinelearning,andAI-relatedsystemresearch

GuanpingDai

LinkMindProjectTeam,FounderandCEOof

LandingBJ

•Over20yearsofexperienceinAIalgorithmresearchanddevelopment.Builtproprietarydeeplearningandlarge-modelframeworks

•Extensiveexperienceinbankingandtelecommunicationssystemarchitec-ture.ParticipatedinimageanalysisprojectsfortheNationalAutomotiveSafetyLaboratoryandtelemetrytrackingsystemsforShenzhouspace-craftrecoverycapsules

•FormerexperienceattheChineseAcademyofSciencesSoftwareInstitute

•FormerexperienceatBEA/Oracle(China)

3

5

CHAPTER

Routing,Orches-tration,andMulti-AgentTeamwork

Agentsystemsbecomestrategicallyimportantwhentheystopbeingisolatedassistantsandstartbecomingacoordinatedlayerofwork.Atthatpointthreequestionsemergeatonce.Whichmodelorbackendshouldhandleeachrequest?Inwhatsequenceshouldreasoning,retrieval,andtoolcallsoccur?Andwhenseveralagentsparticipate,whichagentownswhichresponsibility?Thefirstquestionisrouting,thesecondisorchestration,andthethirdismulti-agentdesign.Confusingthemleadstomuddledarchitectureandvagueaccountability.

ThefinalchapterbringsthesequestionstogetherbecauseLinkMindises-peciallyrevealingwhenseveralagentsshareonesubstrate.Theplatformmaterialsdescriberoutingstrategiessuchasfailover,polling,parallelinvoca-tion,best-routeselection,andpass-throughcompatibility.TheyalsodescribetopologiessuchasAgentServer,AgentMate,SecurityGateway,ProxyplusGEOplusCascade,andmulti-teamsharedmiddlelayers.Readasengineeringpatterns,theseideastellacoherentstory:manyagentsurfacescanremaindiverseaslongasonecontrolplanegovernsmodelaccess,capabilities,knowledgeboundaries,costpolicy,andaudit.

Thischapteralsoreturnstotheuser’srequestedscenariodirectly:multipleLobsteragents,oneLinkMind.HermesAgententersasanaturalcounterpartforstructuredrevieworworkfloworchestration.Theobjectiveisnottocele-brateaparticularinterface.Theobjectiveistoshowhowseveralinterfacesandagentrolescancooperatewithoutfragmentingtheplatformunderneaththem.

4

LearningObjectives

•Differentiaterouting,orchestration,andmulti-agentresponsibilitydesign.

•Understandwhymodelchoiceshouldbepolicy-drivenratherthanhard-codedperclient.

•UseLinkMindpatternstocentralizecost,failover,observability,andsafetyforseveralagentsatonce.

•Buildandinspectamulti-agentworkflowwithdistinctrolesandsharedcapabilities.

•Translatethetopologyof“multipleLobsters,oneLinkMind”intoasustain-ableteamoperatingmodel.

5.1RoutingasaFirst-ClassDecisionLayer

Routinganswersaspecificquestion:giventhistask,whichbackendpathshouldtherequesttake?Theanswermaydependoncost,latency,modality,reasoningdepth,regulatorylocation,orproviderhealth.Acommonearlymistakeistohardcodeonemodelchoiceperapplicationandthencallthesystem“multi-model”becauseseveralvendoraccountsexistinaspreadsheet.Trueroutingmeansthatmodelselectionbecomesexplicitpolicyratherthanscatteredhabit.

Atravelsummary,aretrievalcondensationstep,andafinalexecutivememodonotnecessarilydeservethesamemodel.Nordoavisionclassificationstep,adensereasoningstep,andalow-riskextractionstep.Routingmattersbecauseitturnsmodelheterogeneityfromamaintenanceburdenintoadesignresource.Oncethemiddlelayergovernsthechoice,upperlayerscanrequestworkintermsofneedratherthanvendor-specificendpointnames.

Failoverispartofroutingratherthanmerelyaninfrastructureafterthought.Iftheprimarymodelisunavailableorunhealthy,thesystemmustdecidewhethertosubstituteanothermodel,deferthetask,ordegradetheoutputclass.Thesearebusinessdecisionsexpressedthroughtechnicalroutes.LinkMind’semphasisonfailoverandroutepolicyisthereforenotcosmetic.Itreflectsthepracticaltruththatproductionagentsystemscannotbebuiltontheassumptionthateveryproviderisalwaysavailableandequallyappro-priate.

5

RoutingStrategy

WhatItOptimizes

TypicalTrade-off

Failover

Businesscontinuityduringproviderfailure

Qualitymaydegradeunlessmonitoredcarefully

Cost-awarerouting

Loweruniteconomicsforsimpletasks

Taskclassificationmustbereliable

Parallelinvocation

Higherconfidenceor

broaderevidencecollection

Highercostandmergecomplexity

Best-routeselection

Adaptiveoptimizationacrosslatency,cost,orquality

Requiresgoodtelemetryandpolicytuning

Pass-through

compatibility

Easyadoptionbyexistingclients

Canhidegovernanceifoverusedasacrutch

5.2OrchestrationIstheWorkPath,NottheModelPath

Routingchooseswherearequestgoes.Orchestrationchooseshowworkunfolds.Aworkflowmayrequireretrieval,thenclassification,thenticketing,thenreview,thenfinalcommunication.ThesestepscanberepresentedexplicitlyinaworkflowruntimesuchasHermesAgent,ortheycanbepartiallyimplicitinsideasingleagentloop.Thedistinctionmattersbecausethemoreproceduralandinspectabletheprocessmustbe,themoreorchestrationdeservesanexplicitrepresentation.

However,noteverymulti-stepflowisamulti-agentsystem.Asingleagentcanperformseveralstepsifitretainsoneroleandoneresponsibilityboundary.Multi-agentdesignbeginswhenrolesdivergemeaningfully.Oneagentmaybeallowedtoresearchbutnottoact.Anothermaybeallowedtoactbutnottoapprove.Athirdmaybedesignedspecificallytoreviewoutput,policycitations,andtrace.Whentheserolessplit,orchestrationmusthandlehandoffsaswellassteps.

ThisiswhereHermesAgentoftenfindsitsmostnaturalrole.Itcanexpressproceduralgraphsclearly.Yetthegraphshouldnotbecomethesoleownerofsharedskills,policysemantics,orproviderlogic.Thosebelonglowerinthestack.Otherwiseeachworkflowbecomesaminiatureplatform,andconsistencydisappears.

6

5.3Multi-AgentDesignasResponsibilityArchitecture

Multi-agentdesigniseasiesttomisunderstandbecauseitiseasytomakeitlooksophisticated.Severalnamedagentscanexchangemessagesandstilladdnorealvalueiftheydonotembodydistinctresponsibilities.Ahelpfultestistoaskwhethereachagentcouldbegivenaseparateperformancereview.Iftheanswerisno,thenthedesignmaymerelybefragmentedpromptingratherthanmeaningfulroledecomposition.

Meaningfulrolesoftendifferalongfourdimensions.Theydifferinobjective:researcher,planner,operator,reviewer.Theydifferintoolrights:onecanretrieveknowledge,anothercanwritetosystems,anothercanapprovebutnotact.Theydifferinanswerstyleoroutputobligation:oneproducesevi-dencenotes,anotherproducesmachineactions,anotherproducesexecutivesummaries.Andtheydifferinevaluation:eachrolesucceedsbyadifferentcriterion.Oncethesedifferencesexist,collaborationbeginstomakesense.

Thedeepervalueofmulti-agentdecompositionisnotthatseveralmodelsarespeaking.Itisthatresponsibilitybecomeslocalwhilegovernanceremainsshared.LinkMindisusefulpreciselybecauseitallowsrolediversityabovewhilepreservingcommonroutes,commonknowledge,commoncapabilities,commonsafety,andcommonobservabilitybelow.

5.4TheTopologyofMultipleLobsters,OneLinkMind

Thephrase“multipleLobsters,oneLinkMind”describesmorethananet-workingpattern.Itdescribesanoperatingmodelinwhichseveralinteractiveagentsoroperatorworkbenchesshareonecontrolplane.EachLobsterin-stancemayembodyadifferentprompt,taskfocus,ordepartmentrole.Yetallofthemconsumethesamemiddle-layerproviderendpoint,thesameskillregistry,thesamesafetyfence,andthesameroutingpolicy.Thisdramaticallyreducesduplicationandmakesgovernancevisible.

ThesamepatternextendsnaturallywhenHermesAgentjoinstheenviron-ment.HermescanactasastructuredworkfloworreviewerplanewhileLobsterremainsthehuman-facingexplorationplane.LinkMindsitsbeneathboth.Inthisarrangement,Lobsterdoesnotneedtoknowthedetailsofvec-torization,fallback,orcapabilityblacklists.Hermesdoesnotneedtoowneveryproviderconfigurationorsafetyfilterlocally.Bothbecomemoreusefulpreciselybecausetheyarenolongeraskedtobecompleteplatforms.

7

Thistopologyisalsoorganizationallysane.Domainteamscanowntheprompts,interactionpatterns,andworkflowgraphsthatreflecttheirbusinesspractice.Aplatformteamcanownroutingtemplates,capabilityregistration,corporaboundaries,andauditconventions.Withoutthissplit,eithertheplatformbecomesoverlycontrollingorthedomainsbecomeinfrastructuremaintainersbyaccident.

Figure5.1.MultipleagentsurfacessharingoneLinkMindcontrolplaneforrouting,knowledge,capabilities,andaudit.

5.5Hands-OnLab:AMulti-AgentIncidentWorkflow

Thelabinthischapterassemblesasmallmulti-agentteamaroundanincidentresponsescenario.Anemployeereportsasuspectedphishingemailonacompanylaptop.Thesystemmustdeterminetherelevantpolicy,identifytheassetowner,openthenecessaryserviceticket,anddraftaconciseexecutivenote.Weusethreeroles.TheResearcherretrievespolicyandincidentguid-ance.TheOperatorverifiesassetfactsandcreatestheticket.TheReviewercheckspolicyalignment,tracequality,andtheappropriatenessofthefinalcommunication.

Thisscenarioisusefulbecauseeachrolehasadifferentsuccesscriterion.

TheResearchermustbegrounded.TheOperatormustbepreciseandsafeintooluse.TheReviewermustbeskeptical,policy-aware,andconcise.Atthe

8

sametime,allthreerolesshouldshareoneLinkMindlayerformodelroutes,capabilities,safetycontrols,andtraces.Thebuildthereforedemonstratesbothcollaborationandcommongovernance.

▷Step1.PlaceeveryagentsurfacebehindthesameLinkMindendpoint.

RepointeachLobsterinstanceandanyHermesworkflownodesfromrawproviderURLstothecommonLinkMindendpoint.Thisisthearchitecturalpivotonwhichtherestofthelabdepends.Withoutit,thethreerolesremainseparateclientswithnocommoncontrolsurface.Withit,theybecomedifferentiatedconsumersofonegovernedsubstrate.

Thepracticaltestissimple.Eachroleshouldstillbeabletoconverseorexe-cuteasbefore,butproviderchoice,capabilityexposure,andtracegenerationshouldnowbevisiblecentrally.Ifthisstepisincomplete,laterevaluationofroutingorpolicywillbemisleadingbecausethesystemwillstillbefragmentedunderneath.

▷Step2.Registersharedknowledgeandcapabilitiesonce.

•Researcher:accesstophishingresponsepolicy,devicehandlingproce-dure,andsecurityFAQcorpora.

•Operator:accesstolookup_asset_ownerandcreate_service_ticket.

•Reviewer:accesstotraces,policycitations,andapprovalcheckpoints,butnottounrestrictedadministrativetools.

Thepointofsharedregistrationisnotsimplyconvenience.Itensuresthatwhenpolicychanges,toolsemanticschange,oracapabilityisdisabled,allagentsinheritthechangecoherently.Thisisthesystemsversionofhavingonesourceoftruthforbehaviorratherthanmanypartialcopies.

▷Step3.Routebytasktyperatherthanbyclienthabit.

#illustrativeroutingintent

routes:

-when:task=="knowledge_retrieval_summary"use:economical-chat

-when:task=="final_executive_note"

use:reasoning-chat

-when:task=="provider_error"fallback:backup-chat

9

Therouteplanisintentionallymodest.Retrievalsummarizationmaynotneedthemostexpensivereasoningmodel.Finalsynthesisforanexecutivenotemayjustifyastrongerbackend.Providererrorsshouldtriggeradefinedfallback.Thisstructureteachesanimportantdiscipline:modelstrengthshouldbeallocatedbytaskneed,notbysuperstitionorconvenience.

Teamsthatroutethiswayalsogainclearercostvisibility.Tokenusagecanbeattributednotjusttoanapplication,buttoaroleandatasktype.Thismakeslateroptimizationfarmorerationalthanblanketeffortsto“usefewertokens.”

▷Step4.Runtheincidentworkflowendtoend.

•Researcherreceivesthephishingreportandreturnstherelevantpolicyfactswithcitations.

•Operatorconfirmstheaffectedassetandopenstheserviceticketusingthesharedcapabilitylayer.

•Reviewercheckswhethertheticketsummary,policybasis,andfinalexec-utivenotealignandremainwithinroleboundaries.

Observewhetherthehandoffsaresemanticallyclean.TheResearchershouldnotquietlyperformoperationalactions.TheOperatorshouldnotimprovisepolicybeyondtheretrievedevidence.TheReviewershouldnotbecomeasec-ondoperator.Cleardivisionoflaboriswhatmakesthesysteminterpretablewhenseveralagentsparticipate.

▷Step5.Inspectcollaborationasanoperationalsystem.

•Cantokenusebeattributedbyagentroleratherthanonlybyapplication?

•Cantheteamseewhichmodelservedwhichstepandwhichfallback,ifany,occurred?

•Canonesharedcapabilityberevisedordisabledwithouteditingallagents?

•Ifoneproviderfails,doesthemulti-agentworkflowdegradegracefullyratherthandeadlock?

•Cananauditorreconstructwhodecided,whoacted,andwhichevidencesupportedtheaction?

Thisinspectionstepiswhatturnsapleasingdemointoanoperationalpattern.

10

Collaborationisnotonlyaboutwhetherthefinalnotesoundsgood.Itisaboutwhethertheorganizationcanobserve,price,govern,andevolvethesystemafterdeployment.

5.6Observability,Cost,andReliabilityinTeamedAgentSys-

tems

Multi-agentsystemscreateatemptationtofocusonlyonemergentbehaviorwhileignoringcostandreliability.Inreality,sharedcontrolbecomesmoreimportantastheagentcountrises.Aplatformshouldbeabletoattributetokenusagebydepartment,project,andagentrole;revealroutechoices;showfallbackfrequency;andidentifywhichcapabilitycallsdominatecostorlatency.LinkMind’sownpositioningaroundunifiedobservabilityandtokenaccountingshouldthereforebereadasacoreengineeringrequirementratherthanasacosmeticdashboardfeature.

Reliabilityalsobecomesagraphproblem.Asingleunavailableprovidermayaffectonlyonestep,oritmaystalltheentirecollaborativepathifnofallbackhasbeendefined.Teamsshouldthereforeevaluatenotonlynodereliabilitybutworkflowresilience.CantheResearcherstillproduceareducedanswerifonecorpusisunavailable?CantheOperatordeferactionwhilepreservingtheevidencetrail?CantheReviewerdistinguishbetweenpolicyuncertaintyandinfrastructuredegradation?Thesequestionsdeterminewhethermulti-agentdesignisgenuinelyrobustormerelytheatrical.

5.7TheTeamOperatingModel

Thetechnicaltopologyofmulti-agentsystemsisinseparablefromthehumantopologyoftheteamsthatmaintainthem.Ausefuloperatingmodeloftendi-videsownershipasfollows.TheplatformteamownsLinkMindconfiguration,routepatterns,sharedskills,capabilitypolicies,auditschema,andcommoncorporaconventions.Domainteamsownprompts,roledefinitions,workflowcomposition,evaluationcases,anduser-facinginteractionpatterns.Securityorcomplianceteamsmayco-ownpolicyreview,incidentbenchmarks,andhigh-riskcapabilityapproval.

Thissplitmattersbecauseitkeepsexpertisewhereitbelongs.Domainteamsunderstandbusinesstasksandshouldshapeagentrolesaccordingly.Platformteamsunderstandreliability,reuse,andgovernance,andshould

11

shapethecontrolplaneaccordingly.Ifdomainsownallinfrastructurelocally,inconsistencyproliferates.Iftheplatformownseverypromptandworkflowdetail,businessfitnessdecays.

“MultipleLobsters,oneLinkMind”isthereforenotonlyadeploymentphrase.Itisagovernanceprinciple.Manyworkersmayexist.Onesharedcontrolplaneshouldstilldefinetherulesofengagement.ThesameprincipleholdsifHer-mesAgentisadded:manyrole-specializedsurfacesabove,onegovernablesubstratebelow.

5.8CommonAnti-Patterns

•Callingasystemmulti-agentwhenitmerelycontainsseveralpromptswithnorealresponsibilityseparation.

•Embeddingroutelogicindependentlyineveryclientinsteadofcentralizingit.

•Lettingworkflowenginesaccumulatelocalcopiesofsharedcapabilitysemantics.

•Ignoringcostattributionuntilafterseveralagentsarealreadyinproduc-tion.

•Designingcollaborationwithoutaudit,makingitimpossibletoreconstructwhodidwhat.

5.9CollaborationPatternsbeyondtheSimpleTrio

TheResearcher-Operator-Reviewertriousedinthelabisonlyonecollabo-rationpattern.Severalothersrecurinpractice.Aplanner-executor-reviewerpatternseparatestaskdecompositionfromactionandfromqualitycontrol.Asupervisor-workerpatternusesonecoordinatingagenttoassignworktospecializedworkers.Amarketordebatepatternletsseveralagentsproposealternativesbeforeajudgeormergerstepchoosesamongthem.Anevent-drivenpatternallowsagentstoreacttosystemeventsratherthantoasingleconversationalthread.

Eachpatterndistributesresponsibilitydifferently.Theplanner-executor-reviewerpatternisstrongwherecorrectnessmattersmorethanspeedbe-causeitinsertsstructuredcritique.Thesupervisor-workerpatternisusefulwhentasksfanoutacrossdomainsordatasources.Debate-stylepatterns

12

mayimproverobustnesswhenseveraluncertaininterpretationscompete.Event-drivenpatternsarecommoninoperationssettingswhereagentsmustreacttosignalssuchasalerts,tickets,ordocumentarrivals.

Theimportantarchitecturalpointisthatthesepatternsshouldstillconsumesharedroutes,capabilities,andsafetypolicy.Otherwiseeachpatternbe-comesitsownmini-platform.LinkMindisvaluableherebecauseitcankeepthelowersubstratestablewhiletheuppercollaborationpatternchanges.Teamsmaydiscoverthatthebestcollaborationdesignforfinancediffersfromthebestdesignforincidentresponse,yetbothcanremaingovernableifthesharedcontrolplaneisintact.

Textbookmaturityappearswhenteamsstoparguingaboutwhichcollabora-tionpatternisuniversallybestandstartmatchingpatternstorisk,latency,domainshape,andhumanreviewneeds.

5.10DistributedTopologies:Proxy,GEO,Cascade,andLocalAcceleration

Asagentusegrowsacrossregionsordepartments,routingandgovernanceoftenrequireamoredistributedtopology.TheLinkMindmaterialsrefertoproxynodes,geographicallyawaredeployment,cascadelayering,andlocalaccelerationpatternssuchasMedusa.Theseconceptsareimportantbecausetheyshowthatacontrolplanecanitselfbelayeredorregionalizedwithoutceasingtobeacontrolplane.

Aproxypatternisusefulwhenseveralteamsneedonemanagedupstreamexittoexternalmodels.Itcentralizescredentials,routerules,safetyfilters,andcostaccounting.AGEO-awarepatternbecomesimportantwhenlatency,networkpolicy,orregulatorylocationmatters.AcascadepatternseparatesresponsibilitiesacrossseveralLinkMindlayers,suchasonesafety-focusedlayerandonerouting-focusedlayer.Alocalaccelerationlayerbecomesvaluableinon-premiseoredgesettingswhererepeatedpromptsandlimitedGPUresourcesmakecachingeconomicallymeaningful.

Thesetopologiesshouldnotbeadoptedsimplybecausetheysoundad-vanced.Eachoneaddsoperationalsurfacearea.Thequestioniswhetherthebusinessneedjustifiesthecomplexity.Alargemulti-regiondeploymentmayneedthem.Asmallinternalpilotalmostcertainlydoesnot.Goodarchitecturegrowsbynecessity,notbyambitionalone.

13

Whatremainsconstantacrosstheseshapesistheprincipleofcentralpolicywithdistributedexecution.Evenwhenseveralnodesexist,theorganizationstillneedsacoherentwaytodefinerouterules,safetyboundaries,capabilityexposure,andobservabilityconventions.Otherwisedistributionbecomesfragmentation.

5.11MeasuringMaturityinMulti-AgentPrograms

Maturemulti-agentprogramsarenotdefinedbythesheernumberofagents.Theyaredefinedbyhowwelltheorganizationcanexplain,observe,andevolvethoseagents.Aweakprogrammayhavemanynamedagentsbutnoreliableownership,costvisibility,safetyconsistency,orevaluationdiscipline.Astrongprogrammayhavefeweragentsbutclearroleboundaries,sharedcapabilities,stableroutes,andabenchmarksuitethatrevealsregressionquickly.

Onehelpfulmaturitylenshasfourlevels.Atlevelone,teamsbuildisolateddemosarounddirectmodelcalls.Atleveltwo,oneormoreagentsbecomeusefulbutstillcarrylocalcopiesofproviderandtoollogic.Atlevelthree,asharedcontrolplaneemerges,centralizingroutes,safety,andcommoncapabilities.Atlevelfour,theorganizationoperatesseveralroles,workflows,orregionsatopthatsharedplanewithmeasurablecost,reliability,andgover-nance.Thepurposeofsuchamodelisnotbureaucracy.Itisself-awareness.

Metricsshouldreflectthismaturity.Earlymetricsmayemphasizetaskcom-pletionanduserdelight.Latermetricsmustincluderouteperformance,fallbackfrequency,corpusfreshness,toolfailurerate,safetydenialaccu-racy,costperworkflow,andreviewburdenperagentrole.Oncethesystembecomesaplatform,platformmetricsbecomeunavoidable.

Maturitymodelsareusefulwhentheyencouragesequencing.Theybecomeharmfulwhentheyareusedtoshameteamsintocomplexitybeforethefoundationsareready.Thegoalisnottobecomemulti-agentquickly.Thegoalistobecomemulti-agentcoherently.

5.12AdoptionRoadmapandOrganizationalDesign

Arealisticadoptionroadmapoftenstartswithoneortwonarrowagentsthatprovevalueinaboundedworkflow.Thenextstageintroducessharedknowledgeorsharedcapabilitiessothatduplicationbeginstofall.Thethird

14

stagemovesroutepolicy,safetypolicy,andobservabilityintoacentrallayersuchasLinkMind.Onlythendoesbroadmulti-agentcollaborationusuallybecomehealthy,becausetheorganizationhasasubstratestrongenoughtosupportrolediversitywithoutchaos.

Organizationaldesignshouldfollowthesamerhythm.Earlyon,asinglesmallteammayowneverythingbecausethescopeismodest.Asadoptiongrows,specializationbecomesuseful.Aplatformgroupownsroutes,capabilities,andsafetyinfrastructure.Domainteamsownroleprompts,workflows,andevaluationcases.Securityandcomplianceteamsco-ownhigh-riskcapabilityreleaseandincidentreview.Theimportantthingisnotrigidhierarchy.Itisexplicitownership.

Theuser’sphrase“multipleLobsters,oneLinkMind”capturesthisroadmapelegantly.Manyinteractiveagentsmaybloomabove.Onecommonsubstrateshouldstillgovernhowthoseagentsreachmodels,corpora,tools,andpolicy.ThesameideaextendsnaturallywhenHermesAgentorotherorchestratorsjointhestack.Multiplicityaboveneednotimplyfragmentationbelow.

Theclassicmistakeistodelayplatformthinkinguntilmanyagentsalreadyexist.Bythattimelocalhabitshavehardenedandconvergencebecomesexpensive.Atextbookonagentengineeringshouldthereforeemphasizethatplatformizationisnottheenemyofexperimentation.Doneattherightmoment,itiswhatallowsexperimentationtoscalewithoutdissolvingintotechnicaldebt.

ChapterSummary

•Routing,orchestration,andmulti-agentresponsibilityaredistinctlayersofdesignandshouldbeevaluatedseparately.

•Asharedcontrolplaneturnsmodeldiversity,capabilityreuse,andsafetypolicyintoplatformassetsratherthanclientburdens.

•MultipleLobsteragentscancoexisteffectivelywhenLinkMindcentralizesroutes,skills,corpora,andaudit.

•HermesAgentcomplementsratherthanreplacessuchasetupwhenitisusedforstructuredworkfloworreview.

•Theorganizationalsplitbetweenplatformownershipanddomainowner-shipisasimportantasthetechnicalsplit.

15

ReviewQuestions

•Whyshouldroutingpolicyliveseparatelyfromworkflowdefinition?

•Whatdistinguishesarealmulti-agentdesignfromafragmentedsingle-agentone?

•HowdoesthepatternofmultipleLobstersoveroneLinkMindimprovegovernance?

•Whyiscostattributionbyroleortasktypeimportantinmulti-agentsys-tems?

•Howwouldyoudivideownershipbetweenplatformanddomainteamsina