create-leafmesh 2.6.10__tar.gz → 2.7.0__tar.gz

create_leafmesh-2.7.0/PKG-INFO

@@ -0,0 +1,94 @@
+Metadata-Version: 2.4
+Name: create-leafmesh
+Version: 2.7.0
+Summary: Project scaffolding + cloud-deploy tool for LeafMesh
+License-Expression: MIT
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: questionary<3,>=2.0
+Requires-Dist: PyYAML>=6.0
+Requires-Dist: boto3<2,>=1.34
+
+# create-leafmesh
+
+Project scaffolding tool for [LeafMesh](https://pypi.org/project/leafmesh/) — the YAML-native multi-agent orchestration platform.
+
+## Install
+
+```bash
+pip install create-leafmesh
+```
+
+## Create a Project
+
+```bash
+create-leafmesh create my-project
+cd my-project
+python -m venv .venv && source .venv/bin/activate
+pip install -r requirements.txt
+python main.py
+```
+
+## CLI Options
+
+```bash
+# Create in a specific directory
+create-leafmesh create my-project -o /path/to/dir
+
+# Skip git initialization
+create-leafmesh create my-project --no-git
+
+# Interactive mode (prompts for project name)
+create-leafmesh create
+```
+
+## Generated Project Structure
+
+```
+my-project/
+  configs/
+    config.yaml              # Agent definitions, mesh wiring, HITL config
+  agency/
+    greeter_agent.py         # LLM agent with @pre_compose
+    processor_agent.py       # Programmatic agent with @conditional_chain
+    researcher_agent.py      # LLM agent with @chain_with_results + smart memory
+    fallback_researcher_agent.py  # Fast fallback (race pattern)
+    advisor_agent.py         # LLM fan-in with @chain + @compose
+    scheduler_agent.py       # Cron-scheduled agent
+    tools.py                 # Custom tools (@global_tool, @tool)
+    external_agents.py       # Integration reference (CrewAI, LangGraph, etc.)
+  main.py                    # Entry point
+  hitl_stub_receiver.py      # Webhook stub for testing HITL locally
+  requirements.txt
+  .env                       # API keys
+  Dockerfile
+  docker-compose.yml         # Redis + app
+```
+
+## What's Included
+
+- **8 agents** showcasing all 4 agent types (human, llm, programmatic, external)
+- **Human-in-the-Loop (HITL)** with dual webhook mode and `from_agent` routing
+- **Fan-in/fan-out** with OR expressions (`processor AND (researcher OR fallback)`)
+- **Smart memory** with hybrid recency/relevance scoring
+- **Scheduled agents** with cron expressions
+- **Custom tools** with access control and categories
+- **All 5 decorators**: `@pre_compose`, `@chain`, `@chain_with_results`, `@conditional_chain`, `@compose`
+- **HITL test stub** (`hitl_stub_receiver.py`) for local webhook testing
+- **Docker-ready** with Redis included
+- **Full README** with HITL walkthrough (2 scenarios, step-by-step)
+
+## Requirements
+
+- Python 3.10+
+- Redis server running (default: localhost:6379)
+- At least one LLM API key (e.g. `OPENAI_API_KEY` in `.env`)
+
+## Links
+
+- [LeafMesh SDK](https://pypi.org/project/leafmesh/)
+- [LeafCraft Studios](https://leafcraft.ai)
+
+## License
+
+MIT

create_leafmesh-2.7.0/create_leafmesh/__init__.py

@@ -0,0 +1,3 @@
+"""create-leafmesh — Project scaffolding + cloud-deploy tool for LeafMesh."""
+
+__version__ = "2.7.0"

create_leafmesh-2.7.0/create_leafmesh/templates/_registry.yaml

@@ -0,0 +1,552 @@
+# create-leafmesh — Template Registry
+#
+# Single source of truth for available templates. Used by:
+#   - The CLI picker (interactive)
+#   - `create-leafmesh --list`
+#   - `create-leafmesh --describe <slug>`
+#   - The CLI's --template flag validation
+#
+# Each template is one business function from the LeafCraft operating-ROI
+# model (see docs/roi-pricing-calculator.html). A template is a TEAM of
+# capable agents — not a fixed pipeline. Wires are conditional, the
+# workflow can start from any of multiple entry points, and any agent
+# can be a terminus. The Manager composes the team for each request.
+#
+# DO NOT remove or rename `slug` fields once published — customers may
+# pin to slugs. Add new templates by appending to the `templates:` list.
+#
+# `status` values:
+#   ready    — template fully implemented and tested; available in picker
+#   planned  — listed in --list with "(coming soon)" tag; not selectable
+#   deprecated — present for legacy support; not shown in picker
+
+version: 2
+
+templates:
+
+  # ──────────────────────────────────────────────────────────────
+  # START HERE
+  # ──────────────────────────────────────────────────────────────
+
+  - slug: starter
+    status: ready
+    category: "Start here"
+    short_name: "Starter"
+    full_name: "Starter — build a mesh from scratch"
+    one_line: "Blank canvas: 1 LLM intake → human review gate → WORM audit, with copy-paste patterns to grow."
+    industries: ["any"]
+    roi_cells: []
+    agent_count: 3
+    cron_count: 0
+    trust_lead: "human-review gate on sensitive requests; hash-chained audit terminus; default-deny on reviewer timeout"
+    complexity: "low"
+    decision_tree_path: "start_from_scratch"
+    keywords: "blank, scratch, empty, minimal, tutorial, hello world, boilerplate, skeleton, custom, build your own, getting started, starter kit, none of these fit, from zero, poc, prototype, experiment, sandbox, learn, demo mesh, base template, foundation, new project, greenfield, custom agency, build my own mesh"
+    description: >
+      The template to pick when none of the business templates fit —
+      a minimal, working 3-agent mesh whose configs/config.yaml is
+      written as a guided tutorial. Read it top to bottom: an LLM
+      intake agent classifies a request and routes (via readable
+      can_call wires) either to a human reviewer or straight to the
+      hash-chained audit log. Ships three commented, copy-paste
+      patterns to grow into — a second LLM agent, a connector agent
+      for your system of record (MCP/Zapier/n8n), and a scheduled
+      cron. YAML-first: the only Python is the shared WORM audit sink.
+      Includes validate_config.py for pre-flight checks.
+
+  # ──────────────────────────────────────────────────────────────
+  # SALES & GTM
+  # ──────────────────────────────────────────────────────────────
+
+  - slug: outbound-sdr
+    status: ready
+    category: "Sales & GTM"
+    short_name: "Outbound SDR"
+    full_name: "Outbound SDR — GTM-led demand generation"
+    one_line: "Onboard → research GTM → offerings → campaign → source (Apollo) → hyper-personalised sequences → send → reply → meeting."
+    industries: ["saas", "services"]
+    roi_cells: ["sdr × saas", "sdr × services"]
+    agent_count: 14
+    cron_count: 2
+    trust_lead: "GTM sign-off on strategy shifts; campaign approval before send (spend + brand); human reviews every reply; hash-chained audit"
+    complexity: "high"
+    decision_tree_path: "outbound_demand_generation"
+    keywords: "outbound, sdr, bdr, cold email, cold outreach, cold calling, demand generation, demand gen, lead generation, lead gen, prospecting, sequences, cadence, apollo, instantly, emailbison, lemlist, smartlead, salesloft, outreach io, sales development, gtm, go to market, pipeline generation, book meetings, appointment setting, sequencer, drip campaign, email outreach, outreach automation, sales emails, email campaigns, multichannel outreach, linkedin outreach, account based marketing, abm, lead enrichment, deliverability, mailbox warmup, reply handling, sdr team"
+    description: >
+      An autonomous outbound sales-development operation. A GTM head
+      agent researches the onboarded company (SERP/Surfer tools) and
+      owns a living go-to-market doc; an offering builder turns flagged
+      ideas into offerings with A/B × persona × industry variants; a
+      campaign strategist (human/owner-initiated) sources leads from
+      Apollo, drives a looping enrichment agent that writes
+      hyper-personalised multi-step sequences, and ships them through a
+      sequencer (EmailBison/Instantly); replies are pulled, classified,
+      and worked by a human reviewer to a booked meeting. Demonstrates
+      the full decorator set (pre_compose / chain / conditional_chain /
+      compose / sdk.intelligence), a stateful looping enrichment tool,
+      email channels, and connectors to Apollo / sequencer / mailbox /
+      calendar / CRM (inert until wired; a local dev store runs the LLM
+      chain day-0). See the template's PRD.md for the full design.
+
+  - slug: ai-dev-squad
+    status: ready
+    category: "Engineering"
+    short_name: "AI Dev Squad"
+    full_name: "AI Dev Squad — Jira-driven autonomous development"
+    one_line: "Raw request → product owner grooms a ticket (acceptance criteria) → plan → tech-lead sign-off → Claude Agent SDK builds + opens PR → independent QA re-runs the tests + files bugs → review → merge."
+    industries: ["saas", "services", "any with engineering"]
+    roi_cells: ["eng x saas"]
+    agent_count: 10
+    cron_count: 2
+    trust_lead: "tech-lead sign-off before any code is written AND before merge; an independent QA agent re-runs the tests (no self-marked homework) and files bugs to Jira; bounded rework; hash-chained audit"
+    complexity: "high"
+    decision_tree_path: "autonomous_development"
+    keywords: "engineering, software development, coding, developer, programmer, software engineer, jira, github, gitlab, pull request, pr, claude agent, claude code, autonomous coding, coding agent, ai engineer, sdlc, tech lead, qa testing, test automation, build features, feature development, ship code, dev team, sprint, tickets, backlog, acceptance criteria, bug fixing, write code, code review, refactor, ci cd, merge, product owner, devops"
+    description: >
+      A Jira-driven autonomous software-development squad. A product-owner
+      agent grooms a raw request into a well-formed ticket (testable
+      acceptance criteria + priority + QA discipline) and files it after a
+      stakeholder signs off scope. A planner agent then
+      pulls the tickets assigned to it (pre_compose), picks the best one,
+      writes a plan, and pings the tech lead with the ticket URL. On
+      sign-off, the developer agent — the real Claude Agent SDK, run
+      in-process via LeafMesh's native claude_agent external framework
+      (pure YAML, no connector code) — implements the feature: edits the
+      repo, runs tests, commits, pushes, opens a PR, and updates docs. An
+      independent QA agent — a second Claude Agent SDK, read+run only,
+      typed by discipline (backend/api/frontend) — RE-RUNS the test cases
+      on the build (so a self-reported green can't reach review), works its
+      own assigned test tickets, and files every defect back into Jira as a
+      bug the planner later picks up. A reviewer reads the PR diff; the
+      tech lead merges. Bounded qa/reviewer-developer rework, default-deny
+      human gates, hash-chained audit. Host prerequisites for the live
+      coder + QA: claude-agent-sdk +
+      the Claude Code CLI, gh + git, a repo checkout, Jira + GitHub
+      connectors. Replaces the former generic engineering-sdlc template.
+
+  - slug: finance-ops
+    status: ready
+    category: "Finance & back-office"
+    short_name: "Finance Ops"
+    full_name: "Finance Operations — AP / AR / close cycle"
+    one_line: "Invoice → extract → match → reconcile → fraud-check → GL → exception."
+    industries: ["goods", "saas", "services"]
+    roi_cells: ["fin × goods", "fin × saas", "fin × services"]
+    agent_count: 16
+    cron_count: 2
+    trust_lead: "regulator visibility (high) — every action audited, exception-routed to Controller"
+    complexity: "high"
+    decision_tree_path: "finance_automation"
+    keywords: "finance, accounting, accounts payable, ap, accounts receivable, ar, invoice, invoices, invoicing, vendor invoices, ocr invoice, reconciliation, reconcile, cash application, dunning, close cycle, month end close, financial close, gl, general ledger, journal entries, accruals, bookkeeping, controller, cfo, fraud check, duplicate detection, three way match, po matching, erp, netsuite, quickbooks, sap, expense, billing, payment processing, audit trail, ap automation, ar automation, finance team, back office"
+    description: >
+      Accounts payable + accounts receivable + close-cycle automation.
+      Multi-entry: invoices land via email, vendor portal, ERP webhook,
+      mobile photo. Team: extraction · PO-match · 3-way recon ·
+      fraud/duplicate · GL-coding · exception drafter, with AP clerk,
+      Controller, CFO, internal auditor in the human roster.
+      Industry config overlays for goods (PO-heavy), SaaS (revenue
+      recognition), services (project accounting).
+
+  - slug: recruiting-ops
+    status: ready
+    category: "People operations"
+    short_name: "Recruiting Ops"
+    full_name: "Recruiting & HR Operations"
+    one_line: "Source → screen → correspond → interview → schedule → offer, with bias + salary-band HITL gates."
+    industries: ["any (services-strong)"]
+    roi_cells: ["recruit × services"]
+    agent_count: 14
+    cron_count: 1
+    trust_lead: "compliance by construction — bias signal + out-of-band offer are hard HRBP gates; weekly EEOC 4/5ths audit; hash-chained WORM"
+    complexity: "medium"
+    decision_tree_path: "talent_pipeline"
+    keywords: "recruiting, recruitment, hiring, talent, talent acquisition, talent pipeline, candidates, applicants, ats, applicant tracking, interview scheduling, interview loop, candidate screening, resume, cv, sourcing, sourcer, screening, offer letter, offer management, salary band, hr, human resources, hrbp, headcount, hiring manager, recruiter, eeoc, bias check, diversity hiring, people ops, hr ops, job openings, job posting, requisition, onboarding, greenhouse, lever, workday, linkedin recruiter"
+    description: >
+      End-to-end recruiting team. Multi-entry: req filed in ATS,
+      referral submitted, LinkedIn-InMail reply, scheduled pipeline
+      sweep, async screen, weekly bias audit. YAML-first: candidates
+      live in YOUR ATS and interviews in YOUR calendar (sourcing,
+      funnel ledger and panel booking are n8n connectors). One
+      correspondence writer drafts all candidate messages (outreach,
+      band-enforced offers, bridge-preserving rejections); one
+      interview coordinator designs the loop and a booker schedules it;
+      a screening interviewer runs the async first round. Bias signals
+      and out-of-band offers are hard gates to the HRBP; the only
+      Python module is the compliance-grade EEOC 4/5ths-rule audit.
+      Recruiter, hiring manager, recruiting manager and HRBP form the
+      default-deny human chain; hash-chained WORM on every terminus.
+
+  # ──────────────────────────────────────────────────────────────
+  # CUSTOMER-FACING
+  # ──────────────────────────────────────────────────────────────
+
+  - slug: customer-support
+    status: ready
+    category: "Customer & growth"
+    short_name: "Customer Support"
+    full_name: "Customer Support — ticket triage & resolution"
+    one_line: "Ticket → triage → sentiment → KB → draft → QA → escalation."
+    industries: ["saas", "services", "any with support"]
+    roi_cells: ["supp × saas"]
+    agent_count: 15
+    cron_count: 0
+    trust_lead: "customer visibility — sentiment-aware, escalation default-deny on low confidence"
+    complexity: "medium"
+    decision_tree_path: "support_triage"
+    keywords: "customer support, support, help desk, helpdesk, tickets, ticketing, support tickets, triage, customer service, customer queries, customer care, cx, knowledge base, kb, kb articles, macros, deflection, escalation, csat, sla, zendesk, intercom, freshdesk, gorgias, kustomer, slack support, email support, chat support, live chat, whatsapp support, phone support, omnichannel support, agent assist, tier 1, tier 2, complaints, service desk, contact center, support team"
+    description: >
+      Reactive support team. Multi-entry: Slack/email/chat/phone/web
+      channels each fire ticket.opened. Team: triage · sentiment ·
+      knowledge · response · QA · escalation, with Tier-1, Tier-2,
+      Tier-3 SME, queue manager, QA reviewer, account-named-CSM in
+      the human roster. Channel-native HITL — operators reply where
+      they already work.
+
+  - slug: customer-success
+    status: ready
+    category: "Customer & growth"
+    short_name: "Customer Success"
+    full_name: "Customer Success — retention & renewal"
+    one_line: "Health score → risk → playbook → QBR → renewal — proactive."
+    industries: ["saas"]
+    roi_cells: ["cs × saas"]
+    agent_count: 16
+    cron_count: 1
+    trust_lead: "customer visibility — high — save-play actions HITL-gated"
+    complexity: "high"
+    decision_tree_path: "retention_motion"
+    keywords: "customer success, retention, churn, churn prevention, churn risk, renewal, renewals, renewal forecast, health score, account health, qbr, qbr deck, ebr, csm, csm team, account management, save play, playbooks, success plans, upsell, expansion, expansion revenue, nps, customer health, proactive outreach, onboarding customers, telemetry, adoption, success manager, post sales, gainsight, totango, net revenue retention, nrr"
+    description: >
+      Proactive (NOT reactive) retention team. Multi-entry:
+      product-telemetry signal, billing event, support escalation
+      crossing CS threshold, scheduled health-score sweep. Team:
+      health-score · risk detector · playbook trigger · QBR drafter ·
+      renewal forecaster · save-play, with CSM, senior CSM,
+      renewals manager, AE, CS Ops, VP CS in the human roster.
+
+  # ──────────────────────────────────────────────────────────────
+  # ENGINEERING & INFRA
+  # ──────────────────────────────────────────────────────────────
+
+
+  - slug: infra-cost-ops
+    status: ready
+    category: "Engineering & platform"
+    short_name: "Infra Cost Ops"
+    full_name: "Infrastructure & Cloud Cost Optimization"
+    one_line: "Telemetry → right-size → reserved-plan → drift → tune."
+    industries: ["saas", "any cloud-heavy"]
+    roi_cells: ["infra × saas"]
+    agent_count: 9
+    cron_count: 1
+    trust_lead: "internal — risky tunes HITL-gated by SRE"
+    complexity: "medium"
+    decision_tree_path: "cloud_cost"
+    keywords: "infrastructure, cloud cost, cost optimization, cost management, finops, cloud finops, aws, gcp, azure, ec2, s3 cost, right sizing, instance right sizing, autoscaling, reserved instances, spot instances, savings plan, commitment discounts, cloud spend, billing optimization, sre, devops, iac, terraform drift, cost anomaly, cost allocation, tagging, platform engineering, cloud bill, cloud waste, spend optimization, kubernetes cost, optimize spend"
+    description: >
+      Continuous cloud-cost optimization. Multi-entry: cost-anomaly
+      alert, scheduled right-size sweep, IaC commit triggers drift
+      check, reserved-capacity renewal window. Team: cost tuner ·
+      right-sizer · reserved-capacity planner · anomaly detector ·
+      IaC drift, with SRE, DevOps, platform eng, cost analyst, CTO
+      in the human roster.
+
+  # ──────────────────────────────────────────────────────────────
+  # REVENUE & GO-TO-MARKET
+  # ──────────────────────────────────────────────────────────────
+
+  - slug: sales-orchestration
+    status: ready
+    category: "Customer & growth"
+    short_name: "Sales Orchestration"
+    full_name: "Sales & Marketing — lead-to-handoff"
+    one_line: "Score → route → sequence → personalise → handoff."
+    industries: ["saas", "services"]
+    roi_cells: ["sales × saas"]
+    agent_count: 11
+    cron_count: 1
+    trust_lead: "customer — pipeline-health monitor on adaptive routing"
+    complexity: "medium"
+    decision_tree_path: "inbound_sales"
+    keywords: "inbound sales, lead scoring, lead routing, lead management, lead distribution, round robin routing, sales, marketing handoff, mql, sql, marketing qualified, sales qualified, lead handoff, lead nurture, nurture sequences, lead enrichment, lead qualification, sequences, crm, salesforce, hubspot, marketo, pardot, revops, ae, sdr handoff, demo request, web form leads, pipeline routing, pipeline management, deal routing, inbound leads, sales engagement, sales ops"
+    description: >
+      Inbound-sales team. Multi-entry: web-form submit, demo request,
+      event-list ingest, partner-lead handoff, scheduled
+      pipeline-health sweep. Team: scorer · router · sequence
+      orchestrator · personalisation · handoff · health monitor, with
+      SDR, AE, sales manager, marketing ops, RevOps, sales engineer,
+      VP Sales in the human roster.
+
+  - slug: bd-proposals
+    status: ready
+    category: "Customer & growth"
+    short_name: "BD Proposals"
+    full_name: "Business Development — proposals & RFPs"
+    one_line: "RFP → past-proposal → draft → pricing → compliance."
+    industries: ["services"]
+    roi_cells: ["bd × services"]
+    agent_count: 15
+    cron_count: 0
+    trust_lead: "customer — legal compliance reviewer + practice-lead HITL on pricing"
+    complexity: "medium"
+    decision_tree_path: "proposal_factory"
+    keywords: "business development, bd, proposals, proposal automation, rfp, rfp response, rfp automation, rfq response, bids, bidding, bid response, tenders, tender response, govcon, capture management, win themes, win proposals, proposal writing, proposal library, pricing, pricing strategy, compliance review, engagement, sow, statement of work, redline, contracts review, presales, presales engineering, solutioning, response writing, loopio, responsive, qvidian"
+    description: >
+      RFP-response team. Multi-entry: RFP email, RFP portal upload,
+      partner-referred opportunity. Team: RFP ingester · past-proposal
+      retriever · section drafter · pricing-config · compliance
+      reviewer · closing, with BD rep, practice lead, proposal
+      writer, engagement architect, partner, legal in the human roster.
+
+  - slug: quote-to-cash
+    status: ready
+    category: "Finance & back-office"
+    short_name: "Quote to Cash"
+    full_name: "Pricing & Quote-to-Cash"
+    one_line: "RFQ → cost calc → discount policy → approval → quote."
+    industries: ["goods", "services"]
+    roi_cells: ["price × goods"]
+    agent_count: 14
+    cron_count: 0
+    trust_lead: "customer + regulator (margin policy) — discount approval HITL-gated"
+    complexity: "medium"
+    decision_tree_path: "dynamic_pricing"
+    keywords: "quote to cash, cpq, cpq automation, pricing, price quoting, quote, quoting, quote generation, rfq, discount, discount governance, deal desk, deal desk approval, margin, margin protection, quotes, order forms, configure price quote, contracts, redline, sales quote, pricing approval, approval workflow, q2c, price calculation, pricing engine, discount approval, deal approval, salesforce cpq, dealhub, quoting team, sales operations"
+    description: >
+      RFQ-to-quote team. Multi-entry: RFQ email, sales-rep request,
+      CPQ event, competitor-price-change webhook. Team: RFQ ingester ·
+      cost calculator · pricing strategist (its wires ARE the
+      approval matrix) · quote drafter · competitor watch · cross-sell
+      strategist · contract redline registrar · deal-compliance
+      analyst, with sales rep, deal desk, finance approver, CFO in the
+      human roster and a hash-chained WORM audit terminus.
+
+  # ──────────────────────────────────────────────────────────────
+  # SERVICES DELIVERY
+  # ──────────────────────────────────────────────────────────────
+
+  - slug: services-delivery
+    status: ready
+    category: "Services & delivery"
+    short_name: "Services Delivery"
+    full_name: "Professional Services — delivery operations"
+    one_line: "Brief → context → research → analysis → draft → QA."
+    industries: ["services", "saas (PS arm)"]
+    roi_cells: ["util × services", "hours × services"]
+    agent_count: 19
+    cron_count: 1
+    trust_lead: "customer — engagement-lead HITL on final delivery"
+    complexity: "high"
+    decision_tree_path: "consulting_engagement"
+    keywords: "professional services, consulting, delivery, client delivery, billable, billable hours, engagement, engagement management, deliverables, deliverable production, client deliverables, client work, research, research reports, analysis, reports, consulting reports, slide decks, ps arm, professional services automation, psa, utilization, consultant, project delivery, qa review, sme review, agency work, agency delivery, advisory, delivery team"
+    description: >
+      Billable-delivery team — covers both "more output per head" and
+      "fewer hours per job" ROI angles in a single mesh. Multi-entry:
+      brief filed, client message, scheduled status report. Team:
+      research · context · analysis · draft · QA · knowledge ·
+      citation, with consultant, senior consultant, SME, engagement
+      lead, partner, QA reviewer in the human roster.
+
+  - slug: bench-management
+    status: ready
+    category: "People operations"
+    short_name: "Bench Management"
+    full_name: "Resource & Bench Allocation"
+    one_line: "Forecast → skills match → allocate → idle-detect."
+    industries: ["services"]
+    roi_cells: ["bench × services"]
+    agent_count: 12
+    cron_count: 0
+    trust_lead: "internal — staffing-partner HITL on allocation conflicts"
+    complexity: "medium"
+    decision_tree_path: "staff_utilization"
+    keywords: "bench, bench management, bench optimization, resource management, resource allocation, staffing, staffing decisions, allocation, utilization, utilization rate, billable utilization, capacity planning, capacity management, skills matching, skills inventory, resource planning, staff allocation, project staffing, talent deployment, idle resources, reskilling, resourcing, people allocation, resource manager, staffing partner, consultant allocation"
+    description: >
+      Continuous resource-allocation team. Multi-entry: new project
+      kickoff, person rolls off engagement, weekly bench review.
+      Team: capacity forecaster · skills matcher · project
+      allocator · idle detector · reskilling recommender, with
+      resource manager, staffing partner, engagement lead, practice
+      lead, talent ops in the human roster.
+
+  # ──────────────────────────────────────────────────────────────
+  # GOODS / MANUFACTURING
+  # ──────────────────────────────────────────────────────────────
+
+  - slug: production-planning
+    status: ready
+    category: "Production & supply"
+    short_name: "Production Planning"
+    full_name: "Production Planning & Scheduling"
+    one_line: "Demand sense → schedule → constraint flag → release."
+    industries: ["goods"]
+    roi_cells: ["prod × goods"]
+    agent_count: 14
+    cron_count: 1
+    trust_lead: "internal — planner HITL on conflict / major change"
+    complexity: "medium"
+    decision_tree_path: "factory_planning"
+    keywords: "production planning, production scheduling, manufacturing, manufacturing planning, scheduling, factory, demand sensing, demand forecasting, capacity planning, mrp, mps, master production schedule, materials planning, shop floor, shop floor scheduling, plant, plant scheduling, production schedule, master scheduler, supply planning, line scheduling, line balancing, build plan, make plan, make to order, planner"
+    description: >
+      Production-planning team. Multi-entry: demand signal arrives,
+      capacity change event, scheduled re-optimization wake-up. Team:
+      demand sensor · scheduler · constraint flagger · re-optimizer ·
+      conflict resolver, with demand planner, master scheduler, plant
+      manager, capacity planner, materials manager, ops director in
+      the human roster.
+
+  - slug: quality-yield
+    status: ready
+    category: "Production & supply"
+    short_name: "Quality & Yield"
+    full_name: "Quality Inspection & Yield Optimization"
+    one_line: "Inspect → defect → root-cause → corrective → release."
+    industries: ["goods"]
+    roi_cells: ["qual × goods"]
+    agent_count: 10
+    cron_count: 1
+    trust_lead: "internal — QA-manager HITL on batch-release decisions"
+    complexity: "medium"
+    decision_tree_path: "quality_systems"
+    keywords: "quality, qa, quality assurance, quality inspection, quality control, qc, yield, yield optimization, yield improvement, scrap reduction, defect detection, defect tracking, root cause, root cause analysis, corrective action, corrective and preventive action, capa, spc, spc charts, statistical process control, manufacturing quality, batch release, batch quality, inspection, inspection automation, six sigma, qa inspector, quality team"
+    description: >
+      Quality-inspection team. Multi-entry: vision-system event,
+      SPC-out-of-control signal, customer complaint webhook,
+      scheduled batch inspection. Team: defect detector · root-cause
+      analyzer · yield optimizer · SPC monitor · corrective-action
+      drafter, with QA inspector, QA manager, plant engineer, process
+      engineer, reliability lead in the human roster.
+
+  - slug: predictive-maintenance
+    status: ready
+    category: "Production & supply"
+    short_name: "Predictive Maintenance"
+    full_name: "Asset Condition & Predictive Maintenance"
+    one_line: "Condition sense → predict failure → work order → parts → repair."
+    industries: ["goods"]
+    roi_cells: ["maint × goods"]
+    agent_count: 11
+    cron_count: 1
+    trust_lead: "internal — reliability-engineer HITL on shutdown / unscheduled work"
+    complexity: "medium"
+    decision_tree_path: "asset_reliability"
+    keywords: "predictive maintenance, maintenance, condition based maintenance, preventive maintenance, asset management, asset reliability, condition monitoring, equipment monitoring, failure prediction, vibration analysis, work order, work order management, iiot, iot sensors, sensors, reliability, reliability engineer, cmms, downtime, downtime reduction, maintenance scheduling, equipment, repair, technician dispatch, machine health, maintenance team"
+    description: >
+      Condition-based maintenance team. Multi-entry: IIoT sensor
+      anomaly, work order filed, scheduled inspection, parts-arrived
+      event. Team: condition sensor · failure predictor · work-order
+      scheduler · parts requestor · technician dispatcher, with
+      maintenance tech, reliability engineer, ops manager, asset
+      planner in the human roster.
+
+  - slug: warehouse-supply-chain
+    status: ready
+    category: "Production & supply"
+    short_name: "Warehouse / Supply Chain"
+    full_name: "Warehouse Operations & Supply Chain (with humanoid integration)"
+    one_line: "Order → allocate → pick (humanoid) → inspect → pack → ship."
+    industries: ["goods"]
+    roi_cells: ["supply × goods"]
+    agent_count: 16
+    cron_count: 1
+    trust_lead: "internal + safety — ops-supervisor HITL on damage / exception; humanoid actions audit-trailed"
+    complexity: "high"
+    decision_tree_path: "physical_operations"
+    keywords: "warehouse, warehouse operations, supply chain, supply chain operations, logistics, logistics automation, fulfillment, order fulfillment, picking, packing, shipping, pick pack ship, inventory, inventory management, wms, wms integration, humanoid, humanoid robots, robotics, robotics fulfillment, distribution, distribution center, dc operations, 3pl, third party logistics, cycle count, cycle counting, ecommerce fulfillment, returns, warehouse team"
+    description: >
+      Warehouse-operations team — introduces the humanoid actor kind
+      for physical work. Multi-entry: order placed, returns received,
+      restock event, scheduled cycle count. Team: allocation ·
+      inventory · routing · exception (agents) PLUS picker · inspection
+      · loader (humanoids — projected $3-8/hr), with ops supervisor,
+      warehouse manager, inventory analyst, inbound coordinator,
+      safety officer, transport planner in the human roster.
+
+  - slug: procurement-ops
+    status: ready
+    category: "Production & supply"
+    short_name: "Procurement Ops"
+    full_name: "Procure-to-Pay & Supply Chain Operations"
+    one_line: "Order intake → inventory check → supplier sourcing → PO → goods receipt."
+    industries: ["goods", "services"]
+    roi_cells: ["procurement × goods"]
+    agent_count: 12
+    cron_count: 1
+    trust_lead: "operations-manager HITL on order approval; po-approver HITL before formal PO issuance; hash-chained audit on every state change"
+    complexity: "high"
+    decision_tree_path: "procure_to_pay"
+    keywords: "procurement, purchasing, purchasing automation, procure to pay, p2p, purchase order, po, po generation, supplier, supplier management, supplier onboarding, sourcing, strategic sourcing, vendor management, vendor sourcing, vendor onboarding, goods receipt, supply chain, buyer, requisition, purchase requisition, three way match, trade compliance, tariff, erp, sap procurement, coupa, ariba, spend management, spend control, procurement team"
+    description: >
+      Procure-to-pay team — order intake + compliance screening in a
+      single LLM pass, then inventory check, supplier sourcing,
+      logistics planning, PO generation (real PDF rendering),
+      goods-receipt note, and supply-health reporting. Seed data in
+      configs/inventory.yaml, configs/suppliers.yaml, configs/open_pos.yaml
+      gives a working demo on first run; replace with ERP / WMS /
+      supplier-management API calls in production. Two human roles:
+      operations_manager (order approval) and po_approval (PO issuance).
+      Includes Lyzr-inspired trade_compliance + tariff_classifier
+      agents for international procurement workflows.
+
+  # ──────────────────────────────────────────────────────────────
+  # MARKETING & GROWTH
+  # ──────────────────────────────────────────────────────────────
+
+  - slug: marketing-ops
+    status: ready
+    category: "Customer & growth"
+    short_name: "Marketing Ops"
+    full_name: "Marketing Operations — campaign & growth"
+    one_line: "Brief → audience+comp → strategy → copy+visual → compliance → publish → perf → attribute."
+    industries: ["saas", "services", "goods"]
+    roi_cells: ["mkt × saas", "mkt × services", "mkt × goods"]
+    agent_count: 15
+    cron_count: 0
+    trust_lead: "brand + legal visibility — compliance gates publish; legal HITL on regulated claims; CMO on budget > 50K and crises"
+    complexity: "high"
+    decision_tree_path: "campaign_growth"
+    keywords: "marketing, marketing operations, marketing automation, campaign, campaign management, growth, growth marketing, content, content marketing, content creation, copywriting, creative, brand, brand campaigns, advertising, ad campaigns, paid ads, attribution, marketing attribution, performance marketing, cmo, cmo office, social media, social media marketing, publishing, demand generation, seo, email marketing, hubspot marketing, marketo, content team"
+    description: >
+      Marketing team — campaign briefs land via many channels (form,
+      email, product-launch, competitor signal, crisis). Team:
+      brief intake · audience intelligence · competitor intel ·
+      campaign strategist · copywriter · visual briefer · compliance
+      reviewer · publisher · performance analyzer · attribution ·
+      crisis responder, with marketing manager, legal reviewer, and
+      CMO in the human roster. Includes weekly performance sweep
+      cron + rapid crisis-response side path.
+
+  # ──────────────────────────────────────────────────────────────
+  # REFERENCE PODS (2.4.131 · pod-standard exemplars)
+  # ──────────────────────────────────────────────────────────────
+
+  - slug: expense-reimbursement
+    status: ready
+    category: "Finance & back-office"
+    short_name: "Expense Reimbursement"
+    full_name: "Expense Reimbursement — claim pod (reference)"
+    one_line: "Receipts → extract (confidence) → policy → form → confirm → approve (Box) → finance → payout, humans on every gate."
+    industries: ["any with travel expense"]
+    roi_cells: ["expense × any"]
+    agent_count: 9
+    cron_count: 1
+    trust_lead: "default-deny on every human gate; Sol finisher fails closed (approve-token re-check + delete-on-block); hash-chained WORM ledger; a low-confidence field becomes a question, never a guess"
+    complexity: "high"
+    decision_tree_path: "expense_reimbursement"
+    keywords: "expense, expenses, reimbursement, expense report, expense claim, receipts, travel expense, claim, per diem, mileage, corporate card, concur, sap concur, expensify, outlook, box, approval workflow, finance, ap, spend, employee claim, expense pod, remi"
+    description: >
+      Reference pod (SDK 2.4.131, pod-standard). Four digital employees — Remi
+      (Claim Coordinator), Odo (Proofs & Extraction Analyst, super_agent +
+      playbook), Fern (Claim Builder), Sol (Approvals & Finance Liaison, the
+      finisher) — plus four human members (Employee, Approver, Finance-Ops Lead,
+      Finance Officer) under a LeafMesh-Manager supervisor. Runs a travel-expense
+      claim end to end: receipts → confidence-scored extraction → policy
+      pre-check → form build → employee confirm → Box approval (e-sign) → finance
+      submission → payout & live status. Every wire is conditional; every human
+      gate default-denies on silence; Odo turns a low-confidence field into a
+      question rather than a guess; Fern cross-checks and returns to Odo on a
+      mismatch; Sol re-checks approval (fail closed on an unknown verdict),
+      renders the approved pack, and deletes it on a blocked floor; a hash-chained
+      WORM ledger is the terminus. Demonstrates playbook, super_agent, timezone'd
+      wake_up, dev-store tools that announce themselves, and the finisher pattern.
+      Runs day-0 on seed proofs; wire the Outlook/Box mcp block for real systems.