Skip to main content

AI Worker Catalog

The Agent Factory Thesis ka companion. Business verticals mein role-based AI Workers (Digital FTEs) ka living reference.

Is Document Ko Kaise Parhein​

The Agent Factory Thesis architecture define karti hai: seven invariants, two layers, one factory. Yeh catalog us architecture ke neeche chalne wali operational detail hai. Jahan thesis invariant layer par rehti hai -- aise durable rules jo nahin badalte -- yeh document specifics deta hai: har vertical mein kaun se Workers hain, woh kya karte hain, kya read aur write karte hain, kaun supervise karta hai, humans kahan verify karte hain, aur aaj kaun se engines unhein chalate hain.

Yeh document versioned hai. Thesis constitutional hai. Catalog operational hai. Workforce reality badlegi to catalog badlega; thesis nahin badlegi.

THESISConstitutional · Invariant · versions ke across qaaim7 InvariantsPrincipal → TriggerTwo-Layer ModelEdge + Workforce10-80-10 RuleIntent · Execute · VerifyPer-Worker EngineJob ko runtime se match kareinAuthorityEnvelopeoperational form mein badalta haiYEH CATALOG · v0.1Operational · Versioned · workforce reality ke sath evolve hota hai6 VerticalsGTM · Finance ·Support · Eng ·HR · LegalWorker FleetsRole-based,unbundled, focusedSupervisorsCRO · Controller ·EM · GC · CHROSystems of RecordCRM · GL · Tickets ·Repo · ATS · CLMEnginesDapr · ClaudeManaged · OpenAI

Har Vertical Ke Liye Teen Baatein Yaad Rakhein​

Pehli baat, Worker role nahin hota. "GTM Worker" koi aik AI employee nahin jo poora GTM akela karta ho. Har vertical ko role-based Workers ki fleet mein unbundled kiya jata hai, aur har Worker itna focused hota hai ke use specify, supervise, aur verify kiya ja sake. Unbundling hi asal point hai. Jo Worker bohat zyada kaam karne ki koshish karta hai, use na achhi tarah specify kiya ja sakta hai, na saaf evaluate, aur na poore function ko dobara banaye baghair replace kiya ja sakta hai.

Doosri baat, human relocate hota hai -- ghaib nahin hota. Har vertical ka aik human supervisor hota hai: GTM lead, controller, head of support, engineering manager, head of people, general counsel. Un ka kaam execution se nikal kar (middle 80%) intent aur verification par aa jata hai (first 10% aur final 10%). Catalog har vertical ke liye is supervisor ko explicitly name karta hai, kyun ke supervisor ka authority hi Worker fleet ko legitimate banata hai.

Teesri baat, system of record substrate hai. Har Worker aik durable store se read aur write karta hai jo agent session ke baad bhi baqi rehta hai -- GTM ke liye CRM, Finance ke liye general ledger, Support ke liye ticketing system, Engineering ke liye code repository. SoR ke baghair agents state hallucinate karte hain, transactions double-write karte hain, aur sessions ke darmiyan kaam kho dete hain. Catalog har vertical ke start par SoR name karta hai, kyun ke agent design mein yeh sab se kam discuss hone wali dependency hai.

1 · Worker role nahin hotaAik vertical bohat se specialists mein unbundle hota hai"GTM"monolithic roleunbundlesLead EnrichOutreachCRM HygienePipelineProposalDemoAttribution…Har aik itna focused hota hai kespecify, supervise, verify ho sake2 · Human relocate hota haiKaam ke darmiyan se edges ki tarafHuman attention kahan jati hai10%Intent80%Workers Execute10%VerifySpec set kareinBudgetEnvelopeReviewApproveSign-offSupervisor ka authority hiWorker fleet ko legitimate banata hai.Woh ghaib nahin hote. Woh relocate hote hain.3 · SoR substrate haiWorkers authoritative state ke against chalte hainWorkerreadWorkerwriteWorkerread+writeSYSTEM OF RECORDCRM · GL · Tickets · Repo · ATS · CLMSoR ke baghair agents state hallucinate karte hain,transactions double-write karte hain, aur kaam kho dete hainsessions ke darmiyan.Sach agent session ke baad bhi baqi rehta hai.

Catalog Template​

Har vertical entry wohi eight-field template follow karti hai:

  1. Definition -- yeh function plain language mein kya karta hai.
  2. System of Record -- woh authoritative store jis ke against Worker fleet chalti hai.
  3. Worker Fleet -- is vertical mein role-based Workers ki unbundled list.
  4. Authority Envelope -- supervisor kya delegate karta hai, attached budgets aur limits ke saath.
  5. Human Supervisor -- spec, budget, aur outcome ka owner kaun hai.
  6. Verification Checkpoints -- action commit hone se pehle humans kahan review karte hain.
  7. Reference Engines -- har Worker class ke liye current engine choices. Replaceable.
  8. Failure Modes -- envelope missing ho to kya ghalat hota hai.

Neeche named reference engines 2026 realizations hain, invariants nahin. Worker fleet, SoR, aur verification structure durable hain. Engines badlenge.

8-Field TemplateIs catalog ki har vertical entry wohi eight questions, wohi order mein answer karti hai.1DefinitionYeh function kya karta haiplain language mein. Scopespecifics se pehle set karta hai.misal: "combined sales,marketing, aur revenue motion..."2System of RecordWoh authoritative store jis keagainst Worker fleet chalti hai.Session ke baad bhi rehta hai.misal: CRM, General Ledger,Ticketing, Code Repository3Worker FleetUnbundled listrole-based AI Workers kijo is vertical ko staff karte hain.misal: Lead Enrichment, OutreachSequencer, CRM Hygiene...4Authority EnvelopeSupervisor kyadelegate karta hai, budgetsaur limits ke saath.misal: "$X/month cap, quote kar sakta haipre-approved bands ke andar..."5Human SupervisorSpec, budget, auroutcome ka owner kaun hai.Named, generic nahin.e.g. CRO · Controller · GC ·CHRO · Head of Support6VerificationJahan humans review aurapprove karte hain actionSoR mein commit hone se pehle.misal: Proposal review, JEapproval, PR merge gate7Reference EnginesHar Worker class ke liye2026 engine choices. Replaceablespec tode baghair.e.g. Dapr Agents, ClaudeManaged, OpenAI Agents SDK8Failure ModesKya ghalat hota hai jabenvelope, SoR, yaverification gate missing ho.misal: "Outreach Worker ban jata haispam cannon..."Order mein parhein to yeh eight fields vertical ko build, supervise, aur verify karne ke liye kaafi specify kar dete hain.

Vertical Ki Anatomy​

Six entries se pehle, yahan woh schema hai jo sab share karti hain. Har vertical ki architectural shape aik jaisi hoti hai: top par human supervisor, middle mein unbundled Workers ki fleet, bottom par system of record, fleet ke gird authority envelope, side par verification checkpoints, aur neeche per-Worker engine choice.

Vertical Ki AnatomyHar vertical entry isi shape ko follow karti hai. Boxes ka content badalta hai; architecture nahin.HUMAN SUPERVISORSpec ka owner · budget set karta hai · outcome approve karta haifirst 10%final 10%authority envelope ke andar delegate karta haiAUTHORITY ENVELOPE — budgets · scope · ceilingsWorker Arole-basedWorker Brole-basedWorker Crole-basedWorker Drole-basedWorker Erole-basedWorker Frole-basedWorker Grole-basedHar Worker itna focused hota hai ke independently specify, supervise, aur verify ho sake.VERIFICATION CHECKPOINTSPre-action reviewThreshold approvalPeriodic certificationPolicy update reviewJahan supervisor kafinal 10% hota hairead · writeSYSTEM OF RECORDAuthoritative state · har agent session ke baad bhi rehti haiREFERENCE ENGINESper Worker choose hote hain, per company nahinNeeche aane wale six verticals isi shape ko concrete content ke saath instantiate karte hain.Verticals ke across pattern recognition hi catalog ka central teaching device hai.

1. Go-To-Market (GTM)​

Definition. Sales, marketing, aur revenue motion ka combined function jo prospects ko paying customers mein badalta hai. Is mein outbound, inbound, sequencing, qualification, opportunity management, proposal, aur close shamil hain.

System of Record. CRM -- Salesforce, HubSpot, Pipedrive. Saari lead state, contact state, account state, opportunity state, aur activity history yahin rehti hai. Workers CRM se read aur CRM mein write karte hain; agent context windows mein koi material cheez yaad nahin rakhi jati.

Worker Fleet.

  • Lead Enrichment Worker -- inbound leads mein firmographic, technographic, aur intent data add karta hai. MCP ke zariye Clay, Apollo, Clearbit, aur ZoomInfo mein compose karta hai.
  • Outreach Sequencer Worker -- email, LinkedIn, aur SMS par multi-touch sequences draft aur dispatch karta hai. Tone, cadence, aur channel mix har ICP ke mutabiq hota hai.
  • CRM Hygiene Worker -- contacts deduplicate karta hai, account hierarchies normalize karta hai, ownership fix karta hai, missing fields fill karta hai, aur stale records archive karta hai.
  • Pipeline Analyst Worker -- opportunity stage history read karta hai, stalled deals flag karta hai, conversion anomalies surface karta hai, aur quota ke against weekly forecast deltas generate karta hai.
  • Proposal Generator Worker -- opportunity record, product catalog, aur pricing rules se tailored proposals produce karta hai.
  • Demo Customizer Worker -- prospect ICP aur stated needs ki bunyaad par demo library se tailored product demos assemble karta hai.
  • Attribution Worker -- channels ke across touchpoint data reconcile karta hai aur attribution outcomes CRM mein wapas write karta hai.

Authority Envelope. Outreach Sequencer har ICP ko har din N emails tak send kar sakta hai, sequencing tools par budget $X/month tak capped hota hai. Proposal Generator pre-approved discount bands ke andar quote kar sakta hai; band se bahar kuch bhi human approval maangta hai. Pipeline Analyst stage fields par read-only hota hai; flag kar sakta hai lekin human sign-off ke baghair deal move nahin kar sakta. Lead Enrichment ke liye per-record cost ceiling hoti hai.

Human Supervisor. Head of GTM / CRO / VP Sales. ICP definitions, sequencing strategy, discount policy, aur forecast methodology ke spec ka owner hota hai. Weekly forecast outputs aur deal-size threshold se upar proposal drafts verify karta hai.

Verification Checkpoints. (1) Har campaign se pehle outbound sequences approved. (2) Deal-size threshold se upar proposals send se pehle humans review karte hain. (3) Weekly forecast review mein Pipeline Worker ka output input hota hai, final output nahin. (4) Channel mix decisions ke liye quarterly attribution review.

Reference Engines. Outreach Sequencer aur CRM Hygiene Dapr Agents par chalte hain (SoR mein write karte waqt durability aur idempotency critical hoti hain). Proposal Generator Claude Managed Agents par chalta hai (long-context document work, tailored prose). Pipeline Analyst OpenAI Agents SDK ya Claude Managed Agents par chalta hai. Lead Enrichment Dapr Agents par chalta hai.

Failure Modes. Envelope ke baghair Outreach Worker spam cannon ban jata hai aur company ka domain blacklist ho jata hai. SoR contract ke baghair Pipeline Worker deal stages hallucinate karta hai aur forecast fiction ban jata hai. Verification ke baghair Proposal Worker policy se bahar quote karta hai aur revenue accidental discount ho jata hai.

Go-To-MarketSales · Marketing · Revenue motion · 7-Worker fleet · CRM as substrateSUPERVISOR · Head of GTM / CRO / VP SalesICP definitions · sequencing strategy · discount policy · forecast methodology ka ownerAUTHORITY ENVELOPE — sequence caps · discount bands · per-record ceilingsLead Enrichmentinbound enrichDapr AgentsOutreach Sequencermulti-touchDapr AgentsCRM Hygienededup · normalizeDapr AgentsPipeline Analystforecast deltasClaude ManagedProposal Generatortailored proposalsClaude ManagedDemo CustomizerICP-tailored demosClaude ManagedAttributiontouchpoint reconciliationDapr AgentsSeven Workers woh kaam replace karte hain jo SaaS era mein "GTM Engineers" haath se karte the.VERIFICATION CHECKPOINTSSequence approvalhar campaign ke liye, launch se pehleProposal reviewdeal-size threshold se uparForecast reviewweekly · output input hota haiAttribution reviewquarterly · channel mixSYSTEM OF RECORD · CRMSalesforce · HubSpot · Pipedrive — leads, contacts, accounts, opportunities, activity historyAgar envelope missing ho →Outreach Worker spam cannon ban jata hai · Pipeline forecast hallucinate karta hai ·Proposal Worker accidental revenue discount karta hai

2. Finance​

Definition. Woh function jo close, accounts receivable, accounts payable, financial planning and analysis, tax, aur statutory reporting ka zimmedar hota hai.

System of Record. General ledger -- NetSuite, QuickBooks, Xero, SAP, Oracle. Saari journal entries, account balances, aur period closes yahin rehte hain. SoR legally bhi important hai: auditors, tax authorities, aur regulators isi se read karte hain.

Worker Fleet.

  • Close Worker -- period-close checklist chalata hai: accruals, reclasses, intercompany eliminations, source documents se journal entry drafting.
  • AR Worker -- invoices issue karta hai, cash apply karta hai, receivables age karta hai, aur dunning sequences draft karta hai.
  • AP Worker -- vendor invoices receive karta hai, unhein POs aur receipts se match karta hai, aur terms ke andar payment runs schedule karta hai.
  • FP&A Worker -- budget ke against variance analysis produce karta hai, management reports draft karta hai, aur assumption inputs se scenario models generate karta hai.
  • Reconciliation Worker -- bank accounts, credit cards, aur sub-ledger balances ko GL se tie back karta hai.
  • Tax Worker -- indirect tax filings draft karta hai, income tax provision support karta hai, aur un transactions ko flag karta hai jinhein tax review chahiye.
  • Audit Trail Worker -- auditor-ready packages produce karta hai: workpapers, tie-outs, aur source systems se pulled supporting documentation.

Authority Envelope. AP Worker per-vendor aur per-batch ceiling tak payment runs schedule kar sakta hai; us se upar kuch bhi controller approval maangta hai. Close Worker materiality threshold tak journal entries post kar sakta hai; us se upar posting se pehle human review chahiye. Tax Worker draft karta hai lekin file nahin karta. FP&A Worker actuals par read-only hota hai; scenario models mein write kar sakta hai.

Human Supervisor. Controller / VP Finance / CFO. Accounting policies, materiality thresholds, close calendar, aur statutory filing approvals ke spec ka owner hota hai. Period close certify karta hai.

Verification Checkpoints. (1) Materiality threshold se upar har journal entry posting se pehle review hoti hai. (2) Books lock hone se pehle period close controller certify karta hai. (3) Statutory filings submission se pehle human tax practitioner review karta hai. (4) Release se pehle auditor packages controller review karta hai.

Reference Engines. Close Worker, AR Worker, AP Worker, aur Reconciliation Worker Dapr Agents par chalte hain -- finance durability, idempotency, aur replayability demand karta hai. FP&A Worker aur Tax Worker Claude Managed Agents par chalte hain (analytical aur document-heavy work). Audit Trail Worker Dapr Agents par chalta hai.

Failure Modes. Envelope ke baghair AP Worker vendors ko double-pay karta hai. SoR contract ke baghair Close Worker books ko reality se drift kar deta hai. Materiality threshold ke baghair har JE human par block hoti hai aur close kabhi finish nahin hota. Statutory filings ki verification ke baghair company aisi filing submit karti hai jise defend nahin kar sakti.

FinanceClose · AR · AP · FP&A · Tax · 7-Worker fleet · General Ledger as substrate · legally significantSUPERVISOR · Controller / VP Finance / CFOAccounting policies · materiality thresholds · close calendar · statutory approvals ka ownerAUTHORITY ENVELOPE — payment ceilings · materiality threshold · filings ke liye drafts onlyClose Workeraccruals · reclasses · JEsDapr AgentsAR Workerinvoice · cash · dunningDapr AgentsAP Worker3-way match · pay runsDapr AgentsFP&A Workervariance · scenariosClaude ManagedReconciliationbank · sub-ledger tiesDapr AgentsTax Workerindirect tax draftsClaude ManagedAudit Trailworkpapers · tie-outsDapr AgentsFinance durability aur replayability demand karta hai — aksar Workers Dapr par chalte hain.VERIFICATION CHECKPOINTSJE materiality se uparposting se pehle reviewedPeriod closecontroller-certifiedStatutory filingshuman tax practitionerAuditor packagesrelease se pehle controllerSYSTEM OF RECORD · General LedgerNetSuite · QuickBooks · Xero · SAP · Oracle — read by auditors, tax authorities, regulatorsAgar envelope missing ho →AP Worker vendors ko double-pay karta hai · Close Worker books ko reality se drift karta hai ·verification ke baghair filing aisi cheez produce karti hai jise company defend nahin kar sakti

3. Customer Support​

Definition. Woh function jo channels ke across customer issues resolve karta hai, escalation manage karta hai, aur learnings ko product aur documentation mein wapas feed karta hai.

System of Record. Ticketing system -- Zendesk, Intercom, Freshdesk, HelpScout -- knowledge base ke saath paired. Ticket state, conversation history, customer history, aur resolution outcomes yahin rehte hain.

Worker Fleet.

  • Triage Worker -- inbound tickets read karta hai, topic aur severity ke mutabiq classify karta hai, right queue mein route karta hai, aur initial priority set karta hai.
  • Resolution Worker -- known issues ka jawab KB use karke directly deta hai; novel issues par human review ke liye replies draft karta hai.
  • Escalation Worker -- pehchanta hai jab ticket first-line scope se bahar ho, aur structured handoff ke saath right specialist ya engineering team ko route karta hai.
  • KB Curation Worker -- high-volume topics identify karta hai jinke liye KB article nahin, new articles draft karta hai, stale articles update karta hai, obsolete content retire karta hai.
  • CSAT Analysis Worker -- survey responses aur ticket transcripts read karta hai, satisfaction drivers identify karta hai, aur leadership ke liye patterns surface karta hai.
  • Macro Generation Worker -- recurring resolved-ticket patterns ki bunyaad par new canned responses propose karta hai.
  • Voice-of-Customer Worker -- ticket themes ko product team ke liye product feedback packages mein synthesize karta hai.

Authority Envelope. Resolution Worker confidence threshold tak pre-approved patterns se match hone wale tickets ko auto-respond kar sakta hai; threshold se neeche kuch bhi human ko route hota hai. Macro Generation Worker draft karta hai lekin human approval ke baghair macros deploy nahin karta. KB Curation Worker staging state mein articles draft karta hai; humans publish karte hain.

Human Supervisor. Head of Support / Director of Customer Experience. Escalation policies, KB editorial standards, severity definitions, aur CSAT targets ke spec ka owner hota hai.

Verification Checkpoints. (1) Confidence threshold se neeche auto-responses send se pehle review hote hain. (2) New KB articles publication se pehle review hote hain. (3) New macros deployment se pehle approve hote hain. (4) Routing rules update karne ke liye weekly escalation pattern review.

Reference Engines. Triage Worker aur Resolution Worker Claude Managed Agents par chalte hain (conversational, context-heavy). KB Curation Worker Claude Managed Agents par chalta hai. CSAT Analysis Worker aur Voice-of-Customer Worker OpenAI Agents SDK ya Claude Managed Agents par chalte hain (analytical synthesis). Macro Generation Worker Dapr Agents par chalta hai.

Failure Modes. Envelope ke baghair Resolution Worker confidence ke saath ghalat jawab deta hai aur customers churn karte hain. Verification ke baghair KB Curation Worker knowledge base ko hallucinated guidance se pollute karta hai. Escalation thresholds ke baghair hard tickets first-line queues mein pade rehte hain jab tak complaints na ban jayein.

Customer SupportTriage · Resolution · Escalation · KB · 7-Worker fleet · Ticketing system + KB as substrateSUPERVISOR · Head of Support / Director Customer ExperienceEscalation policies · KB editorial standards · severity definitions · CSAT targets ka ownerAUTHORITY ENVELOPE — confidence thresholds · staging-only KB · macros approval maangte hainTriageclassify · routeClaude ManagedResolutionKB-grounded answersClaude ManagedEscalationstructured handoffClaude ManagedKB Curationdraft · update · retireClaude ManagedCSAT Analysisdrivers · patternsClaude ManagedMacro Generationrecurring patternsDapr AgentsVoice-of-Customerthemes → productOpenAI SDKConversational aur context-heavy work zyada tar Claude Managed Agents par chalta hai.VERIFICATION CHECKPOINTSAuto-responsesconfidence threshold se neecheKB articlespublish se pehle reviewedNew macrosdeploy se pehle approvedRouting rulesweekly escalation reviewSYSTEM OF RECORD · Ticketing System + Knowledge BaseZendesk · Intercom · Freshdesk · HelpScout — tickets, conversations, customer history, resolutionsAgar envelope missing ho →Resolution Worker confidence ke saath ghalat jawab deta hai · KB Curation guidance pollute karta hai ·hard tickets first-line queues mein pade rehte hain jab tak complaints na ban jayein

4. Engineering​

Definition. Woh function jo company ke software systems design, ship, operate, aur maintain karta hai.

System of Record. Code repository (GitHub, GitLab) source ke liye canonical SoR hai. CI/CD platform build aur deploy state ke liye SoR hai. Observability stack (Datadog, Grafana, Honeycomb) runtime state ke liye SoR hai. Har Worker apne domain ke canonical store mein write karta hai.

Worker Fleet.

  • Code Review Worker -- pull requests ko correctness, style, security issues, aur test coverage ke liye review karta hai. Inline comments karta hai.
  • Refactor Worker -- codebase ke across pre-specified refactors execute karta hai: rename, extract, restructure, dependency upgrade.
  • Deploy Worker -- builds ko environments ke through promote karta hai, smoke tests run karta hai, policy ke andar rollouts aur rollbacks execute karta hai.
  • Test Generation Worker -- new aur untested code paths ke liye unit, integration, aur end-to-end tests produce karta hai.
  • Incident Response Worker -- telemetry ko jor kar incident timelines draft karta hai, likely root causes identify karta hai, aur post-mortems draft karta hai.
  • Dependency Update Worker -- security patches aur minor version bumps ke liye PRs open karta hai, test suite run karta hai, review request karta hai.
  • Doc Generation Worker -- code, ADRs, aur design specs se technical documentation produce aur update karta hai.
  • On-Call Triage Worker -- alerts ka first responder hota hai, severity classify karta hai, context gather karta hai, aur action ke liye humans ko escalate karta hai.

Authority Envelope. Deploy Worker approval ke baghair staging tak promote kar sakta hai; production deploys human gate maangte hain. Refactor Worker pre-approved refactor spec par operate karta hai, kabhi freelance nahin karta. Dependency Update Worker green test suite pass karne wale patches ko pre-approved dependencies ke set ke andar merge kar sakta hai; major versions human review maangte hain. Incident Response Worker default taur par systems par read-only access rakhta hai.

Human Supervisor. Engineering Manager / Tech Lead / Head of Platform. Code style, deploy policy, test coverage targets, refactor priorities, aur incident response runbooks ke spec ka owner hota hai.

Verification Checkpoints. (1) Main mein merge se pehle PRs humans review karte hain. (2) Production deploys human approval se gated hote hain. (3) Incident commander hamesha human hota hai; Incident Response Worker assist karta hai, lead nahin karta. (4) Major dependency upgrades merge se pehle review hote hain.

Reference Engines. Code Review Worker, Refactor Worker, aur Test Generation Worker Claude Managed Agents par chalte hain (Claude Code is ka purpose-built tool hai aur right default hai). Deploy Worker, Dependency Update Worker, aur On-Call Triage Worker Dapr Agents par chalte hain (ops mein durability aur retry semantics matter karte hain). Incident Response Worker Claude Managed Agents par chalta hai. Coding-agent events ke triggers Claude Code Routines ke through chalte hain; baqi sab Inngest ke through chalta hai.

Failure Modes. Envelope ke baghair Deploy Worker unreviewed code production mein ship karta hai. SoR contract ke baghair Incident Response Worker stale telemetry se reason karta hai. Production deploys par human gate ke baghair regressions Saturday subah 3 baje ship ho jati hain.

EngineeringCode · Ship · Operate · Maintain · 8-Worker fleet · Repo + CI/CD + Observability as substrateSUPERVISOR · Engineering Manager / Tech Lead / Head of PlatformCode style · deploy policy · coverage targets · refactor priorities · incident runbooks ka ownerAUTHORITY ENVELOPE — default staging only · prod gated · refactor specs only · read-only opsCode ReviewPR commentsClaude ManagedRefactorspec-driven changesClaude ManagedDeployenv promote · rollbackDapr AgentsTest Generationunit · integration · e2eClaude ManagedIncident Responsetimeline · root causeClaude ManagedDependency Updatepatches · minor bumpsDapr AgentsDoc Generationcode → docsClaude ManagedOn-Call Triagefirst responderDapr AgentsCoding work → Claude Managed Agents (Claude Code). Ops work → Dapr (durability, retries).Coding-agent events Claude Code Routines se fire hote hain · baqi sab Inngest se.VERIFICATION CHECKPOINTSPR reviewhuman merge gateProduction deployhuman approval gateIncident commandhuman-led, Worker assist karta haiMajor upgradesmerge se pehle reviewedSYSTEM OF RECORD · Code Repo + CI/CD + Observability StackGitHub · GitLab · CI/CD platform · Datadog · Grafana · Honeycomb — different stores per domainAgar envelope missing ho →Deploy Worker unreviewed code ship karta hai · Incident Worker stale telemetry se reason karta hai ·regressions Saturday 3 a.m. par ship ho jati hain

5. Human Resources (People)​

Definition. Woh function jo workforce ko source, hire, onboard, develop, aur retain karta hai -- human bhi aur increasingly AI bhi.

System of Record. Candidates ke liye applicant tracking system (Greenhouse, Lever, Ashby). Employees ke liye HRIS (Rippling, Workday, BambooHR). Review state ke liye performance management system (Lattice, 15Five). Har Worker apne scope ke mutabiq right store read aur write karta hai.

Worker Fleet.

  • Sourcing Worker -- candidate databases search karta hai, personalized outreach draft karta hai, screening calls schedule karta hai.
  • Screening Worker -- applications ko role spec ke against review karta hai, fit score karta hai, hiring managers ke liye shortlists draft karta hai.
  • Scheduling Worker -- panels, candidates, aur conference rooms ke across interview loops coordinate karta hai.
  • Onboarding Worker -- accounts provision karta hai, first-week meetings schedule karta hai, training assets deliver karta hai, checklist completion track karta hai.
  • Performance Tracking Worker -- systems se performance signal gather karta hai, review packages draft karta hai, flight risks surface karta hai.
  • Compensation Benchmarking Worker -- compensation data pull karta hai, role aur level ke mutabiq ranges draft karta hai, anomalies flag karta hai.
  • Engagement Worker -- pulse surveys run karta hai, responses analyze karta hai, themes managers ko surface karta hai.
  • Policy Q&A Worker -- HR knowledge base se benefits, leave, aur policy ke bare mein employee questions ka jawab deta hai.

Authority Envelope. Sourcing Worker pre-approved templates aur daily volume cap ke andar outreach send kar sakta hai. Screening Worker shortlist karta hai lekin human review ke baghair reject nahin karta. Scheduling Worker pre-approved time windows ke andar book kar sakta hai. Onboarding Worker sirf pre-approved tools provision karta hai. Compensation Benchmarking Worker ranges draft karta hai; humans approve karte hain.

Human Supervisor. Head of People / VP Talent / CHRO. Role definitions, hiring rubrics, compensation philosophy, performance criteria, aur policy ke spec ka owner hota hai.

Verification Checkpoints. (1) Kisi interview se pehle hiring managers shortlists review karte hain. (2) Offer details extension se pehle human sign-off maangti hain. (3) Delivery se pehle managers performance reviews review karte hain. (4) Sourcing outreach templates quarterly review hote hain. (5) Compensation ranges publication se pehle approve hote hain.

Reference Engines. Sourcing Worker, Screening Worker, aur Policy Q&A Worker Claude Managed Agents par chalte hain. Scheduling Worker, Onboarding Worker, aur Engagement Worker Dapr Agents par chalte hain (durability matter karti hai; onboarding step skip ho to log notice karte hain). Performance Tracking Worker aur Compensation Benchmarking Worker Claude Managed Agents par chalte hain.

Failure Modes. Envelope ke baghair Sourcing Worker aisi outreach send karta hai jo EEO standards ya company brand violate karti hai. Verification ke baghair Screening Worker biased proxies par candidates filter karta hai. SoR contract ke baghair Onboarding Worker ghalat logon ke liye ghalat systems mein accounts provision karta hai.

Human Resources (People)Source · Hire · Onboard · Develop · Retain · 8-Worker fleet · ATS + HRIS + PM as substrateSUPERVISOR · Head of People / VP Talent / CHRORole definitions · hiring rubrics · compensation philosophy · performance criteria · policy ka ownerAUTHORITY ENVELOPE — pre-approved templates · volume caps · shortlist not reject · drafts onlySourcingcandidates · outreachClaude ManagedScreeningrole-spec scoringClaude ManagedSchedulinginterview loopsDapr AgentsOnboardingprovision · checklistsDapr AgentsPerformancereview packagesClaude ManagedComp Benchmarkingranges · anomaliesClaude ManagedEngagementpulse · themesDapr AgentsPolicy Q&Abenefits · leaveClaude ManagedOnboarding step skip ho to log notice karte hain — Dapr durable workflows handle karta hai.Conversational aur document-heavy work Claude Managed Agents par chalta hai.VERIFICATION CHECKPOINTSShortlistshiring manager reviewOffershuman sign-off requiredPerformance reviewsmanager-reviewedComp rangespublish se pehle approvedSYSTEM OF RECORD · ATS + HRIS + Performance SystemGreenhouse · Lever · Ashby (candidates) · Rippling · Workday · BambooHR (employees) · Lattice · 15Five (reviews)Agar envelope missing ho →Sourcing Worker EEO/brand violate karta hai · Screening biased proxies par filter karta hai ·Onboarding ghalat logon ke liye ghalat systems mein accounts provision karta hai

Definition. Woh function jo contracts draft, review, redline, aur manage karta hai; risk par advice deta hai; aur regulatory compliance ensure karta hai.

System of Record. Contract state ke liye contract lifecycle management system (Ironclad, DocuSign CLM, LinkSquares). Litigation aur advice ke liye matter management system. Regulatory obligations ke liye compliance register. Har Worker apne scope ke mutabiq right store mein write karta hai.

Worker Fleet.

  • Contract Review Worker -- inbound contracts read karta hai aur company playbook ke against structured risk summary produce karta hai.
  • Redline Worker -- playbook aur standard fallback positions ki bunyaad par redlines propose karta hai.
  • Intake Worker -- legal request queue handle karta hai: classify, prioritize, route, aur requesters se required information gather karta hai.
  • NDA Worker -- contracting ke high-volume, low-risk end ko handle karta hai: policy ke andar NDA review, redline, aur dispatch end-to-end.
  • Vendor Risk Assessment Worker -- vendor security questionnaires, contracts, aur posture review karta hai; risk recommendations produce karta hai.
  • Compliance Monitoring Worker -- regulatory changes track karta hai, unhein internal obligations se map karta hai, required updates surface karta hai.
  • Discovery Worker -- litigation discovery support karta hai: document review, privilege flagging, production drafting.

Authority Envelope. NDA Worker playbook ke andar NDAs fully execute kar sakta hai; playbook se bahar kuch bhi escalate hota hai. Redline Worker positions propose karta hai lekin human counsel review ke baghair counterparty ko send nahin karta. Vendor Risk Assessment Worker score karta hai lekin approve nahin karta. Compliance Monitoring Worker flag karta hai lekin company ko regulatory position par commit nahin karta.

Human Supervisor. General Counsel / Head of Legal / Deputy GC. Contract playbook, risk thresholds, regulatory positions, aur litigation strategy ke spec ka owner hota hai.

Verification Checkpoints. (1) NDA-tier se upar har redline counter-signing se pehle human counsel review karta hai. (2) Regulatory positions commitment se pehle human counsel approval maangti hain. (3) Discovery production release se pehle review hoti hai. (4) Playbook updates quarterly GC review karta hai.

Reference Engines. Contract Review Worker, Redline Worker, Vendor Risk Assessment Worker, aur Compliance Monitoring Worker Claude Managed Agents par chalte hain (long-context document work; precise legal language). NDA Worker Dapr Agents par chalta hai (is fleet ka wohi Worker jo end-to-end execute karta hai aur durability maangta hai). Discovery Worker Claude Managed Agents par chalta hai.

Failure Modes. Envelope ke baghair Redline Worker company ko aisi position par commit kar deta hai jise GC kabhi approve na kare. Verification ke baghair Compliance Monitoring Worker regulatory obligations misclassify karta hai. SoR contract ke baghair contracts do systems mein do terms ke saath sign ho jate hain, aur legal team ko renewal par pata chalta hai.

LegalContracts · Risk · Compliance · 7-Worker fleet · CLM + matter mgmt + compliance register as substrateSUPERVISOR · General Counsel / Head of Legal / Deputy GCContract playbook · risk thresholds · regulatory positions · litigation strategy ka ownerAUTHORITY ENVELOPE — NDAs end-to-end · baqi sab propose only · GC positions approve karta haiContract Reviewstructured risk summaryClaude ManagedRedlineplaybook fallbacksClaude ManagedIntakeclassify · route · prepClaude ManagedNDAend-to-end executionDapr AgentsVendor Riskquestionnaires · postureClaude ManagedCompliance Monitorreg-change trackingClaude ManagedDiscoveryprivilege flaggingClaude ManagedNDA hi woh Worker hai jo end-to-end execute karta hai — baqi sab human counsel ke liye propose karte hain.VERIFICATION CHECKPOINTSRedlines > NDA tierhuman counsel reviewRegulatory positionscounsel approval requiredDiscoveryrelease se pehle reviewedPlaybook updatesGC-reviewed quarterlySYSTEM OF RECORD · CLM + Matter Mgmt + Compliance RegisterIronclad · DocuSign CLM · LinkSquares — contracts, matters, regulatory obligationsAgar envelope missing ho →Redline Worker company ko aisi positions par commit karta hai jinhein GC approve nahin karega · ComplianceWorker obligations misclassify karta hai · contracts do systems mein do terms ke saath sign hote hain

Cross-Vertical Workers​

Kuch Workers kisi aik vertical se belong nahin karte. Woh har function serve karte hain aur behtar hai ke aik dafa build ho kar shared rahen.

  • Document Generation Worker -- structured inputs se formatted documents (PDFs, slides, spreadsheets) produce karta hai. GTM (proposals), Finance (audit packages), Legal (contracts), HR (offer letters) use karte hain.
  • Notification Worker -- email, Slack, SMS, aur push ke across authoritative notifications send karta hai. Har vertical use karta hai.
  • Translation Worker -- domain-aware vocabulary ke saath languages ke darmiyan content translate karta hai. GTM, Support, HR, Legal use karte hain.
  • Meeting Worker -- meetings join karta hai, transcribe karta hai, summaries draft karta hai, action items extract karta hai. Har vertical use karta hai.
  • Data Extraction Worker -- unstructured inputs (PDFs, emails, images) se structured data pull karta hai. Finance, Legal, HR, Support use karte hain.

Yeh cross-vertical Workers infrastructure hain. Inhein aik dafa build hona chahiye, Paperclip ke zariye governed hona chahiye, aur jis vertical ko zaroorat ho us ke Workers inhein call kar saken. Yeh vertical Workers se kam important nahin -- yeh connective tissue hain.

Cross-Vertical WorkersFive shared Workers har vertical serve karte hain. Aik dafa build karein, Paperclip se govern karein, kahin se bhi call karein.GTMProposals · TranslationNotifications · MeetingsFinanceAudit packages · Dataextraction · NotificationsSupportTranslation · MeetingsNotifications · ExtractionEngineeringDoc gen · NotificationsMeetings · ExtractionHROffer letters · TranslationNotifications · MeetingsLegalContracts · TranslationExtraction · NotificationsCROSS-VERTICAL WORKERSDocument GenNotificationTranslationMeetingData ExtractionAik dafa built · Paperclip se governed · kisi bhi vertical ke Worker se invocable.Yeh vertical Workers se kam important nahin — yeh connective tissue hain.Jab same capability teen ya zyada verticals mein aaye, use factor out karein. Catalog chhota rehta hai; platform compound karta hai.

Frontier Verticals​

Upar diye gaye six verticals woh jaghein hain jahan architecture is catalog ke v0.1 mein specifics commit karne ke liye kaafi mature hai. Kai doosre verticals clearly scope mein hain, lekin future versions mein apni separate treatment deserve karte hain.

  • RevOps -- GTM, Customer Success, aur Finance ke darmiyan shared cross-functional operational backbone. RevOps Workers data pipelines, attribution models, aur reporting layer manage karte hain jis par teen customer-facing functions rely karte hain.
  • Procurement -- agents-as-economic-actors ka sab se clean near-term demonstration. Procurement Workers humans ke set kiye hue authority envelopes ke andar ACP, AP2, x402, aur MPP rails use karte hue vendors se negotiate, contract, aur pay karenge.
  • Customer Success -- Support ke qareeb hai lekin different KPIs (retention, expansion, health) aur different SoR (customer health platform) ke saath.
  • Marketing -- scale par GTM se separate kiya ja sakta hai: brand, content, demand generation, aur lifecycle marketing har aik distinct Worker fleets support karte hain.
  • Product -- research, prioritization, spec drafting, release notes, aur roadmap maintenance sab role-based Worker territory hain.
  • Data & Analytics -- pipeline maintenance, anomaly detection, dashboard generation, ad-hoc analysis. Har doosre vertical ke neeche baithta hai.
  • Compliance & Risk -- Legal ke qareeb hai lekin distinct: enterprise risk register, control testing, audit response, regulatory reporting.

Inhein is catalog ke future versions mein add kiya jayega jab in ki Worker fleets aur verification patterns stabilize ho jayenge.

Catalog RoadmapSolid = v0.1 mein shipped · Dashed = frontier · Faded = future trajectoryv0.1 — Mature verticals (specifics committed)GTMSales · Marketing7-Worker fleetFinanceClose · AR · AP7-Worker fleetSupportTriage · Resolve7-Worker fleetEngineeringCode · Ship · Operate8-Worker fleetHRSource · Hire · Onboard8-Worker fleetLegalContracts · Compliance7-Worker fleetv0.1 boundary — current scopeFrontier — clearly scope mein, future versions ke liye queuedRevOpsCross-functional operationalbackbone (GTM/CS/Fin)ProcurementAgents-as-economic-actorsACP · AP2 · x402 · MPPCustomer SuccessRetention · expansion · healthCustomer health platform SoRMarketingBrand · Content · DemandLifecycle · distinct fleetsProductResearch · prioritize · specRelease notes · roadmapData & AnalyticsPipelines · anomaliesHar vertical ke neeche baithta haiCompliance & RiskRisk register · control testingAudit response · reg reporting...aur bhi jab patterns stabilize honHar naya vertical wohi 8-field template follow karta haitrajectory horizonSoftware se aage — jab frontier aayeEmbodied AI WorkersWarehouse · logistics · manufacturing · vehiclesFully autonomous economic agentsIdentity · payment · reputation · contractual capacityCross-company workforce mobilityPortable Workers · multi-employer envelopes · labor market

Physical Workers Par Ek Note​

Thesis end par embodied AI Workers ko aik trajectory ke taur par name karti hai. Jab woh frontier aayega, yeh catalog naye verticals hasil karega: warehouse operations, last-mile logistics, manufacturing floor operations, autonomous vehicles. Architecture nahin badlegi -- wohi authority envelopes, wohi manager API, wohi systems of record. Compute layer aik body add karegi. Waqt aane par catalog isay reflect karega.

Factory Company build karti hai; Company Workers employ karti hai; Workers system of record ke against chalte hain. Thesis rule name karti hai. Yeh catalog Workers name karta hai.