@tangle-network/starter-foundry 0.7.3 → 0.13.2

package/registry/families/agent-runtime-cs-tutor-ts/manifest.json

@@ -0,0 +1,145 @@
+{
+  "id": "agent-runtime-cs-tutor-ts",
+  "description": "CS tutoring agent bundle \u2014 teaches programming fundamentals, data structures, algorithms, and debugging. Composes the agent-runtime substrate with the blocks output layer on the Tangle floor. Advisory only \u2014 never replaces a human instructor or academic advisor.",
+  "tags": [
+    "agent-runtime",
+    "cs-tutor",
+    "programming-tutor",
+    "education",
+    "cloudflare-worker"
+  ],
+  "taxonomy": {
+    "language": "markdown",
+    "runtime": "cloudflare-worker",
+    "surface": "agent-runtime"
+  },
+  "includes": [
+    "agent-base:tangle",
+    "agent-base:secure",
+    "agent-output:blocks",
+    "agent-base:memory",
+    "agent-base:scheduler",
+    "agent-base:mcp-registry",
+    "agent-channels:telegram",
+    "agent-channels:discord",
+    "agent-channels:slack",
+    "agent-channels:whatsapp",
+    "agent-channels:imessage",
+    "agent-channels:gmail",
+    "agent-channels:linear"
+  ],
+  "defaults": {
+    "projectType": "agent-runtime-cs-tutor",
+    "agentName": "cs-tutor",
+    "publicVars": [
+      "AGENT_NAME"
+    ],
+    "routes": [
+      {
+        "path": "/api/chat",
+        "auth": "bearer",
+        "callsTools": [
+          "explain-concept",
+          "debug-code",
+          "generate-exercise"
+        ]
+      },
+      {
+        "path": "/api/health",
+        "auth": "none",
+        "callsTools": []
+      }
+    ],
+    "declaredCapabilities": [
+      "explain-concept",
+      "debug-code",
+      "generate-exercise"
+    ],
+    "runtime": {
+      "sandbox": "tangle",
+      "noNewPrivileges": true,
+      "capDrop": "ALL"
+    },
+    "stakes": "low",
+    "advisoryOnly": true,
+    "outboundDomains": [
+      "api.tangle.tools"
+    ],
+    "secrets": [
+      "TANGLE_API_KEY"
+    ]
+  },
+  "files": [
+    {
+      "source": "files/agent.json",
+      "target": "agent.json"
+    },
+    {
+      "source": "files/AGENTS.md",
+      "target": "AGENTS.md"
+    },
+    {
+      "source": "files/methodology/index.json",
+      "target": "methodology/index.json"
+    },
+    {
+      "source": "files/methodology/explain-concept.md",
+      "target": "methodology/explain-concept.md"
+    },
+    {
+      "source": "files/methodology/debug-code.md",
+      "target": "methodology/debug-code.md"
+    },
+    {
+      "source": "files/methodology/generate-exercise.md",
+      "target": "methodology/generate-exercise.md"
+    },
+    {
+      "source": "files/README.md",
+      "target": "README.md"
+    },
+    {
+      "source": "files/TOOLS.md",
+      "target": "TOOLS.md"
+    }
+  ],
+  "contextHints": {
+    "commands": [],
+    "entrypoints": [
+      "AGENTS.md"
+    ],
+    "extensionPoints": [
+      "templates/",
+      "src/lib/tools/"
+    ]
+  },
+  "tieredKeywords": {
+    "tier1": [
+      "cs-tutor",
+      "cs tutor",
+      "programming-tutor",
+      "programming tutor",
+      "coding-tutor",
+      "coding tutor",
+      "computer-science-tutor",
+      "computer science tutor"
+    ],
+    "tier2": [
+      "algorithms",
+      "data-structures",
+      "data structures",
+      "debugging",
+      "big-o",
+      "big O",
+      "time-complexity",
+      "time complexity",
+      "space-complexity",
+      "space complexity"
+    ],
+    "tier3": [],
+    "archetypes": [
+      "agent-in-sandbox",
+      "tutor-agent"
+    ]
+  }
+}

package/registry/families/agent-runtime-customer-success-ts/files/AGENTS.md

@@ -0,0 +1,64 @@
+---
+name: customer-success-manager
+role: Customer Success Manager — retention playbooks, health scoring, escalation triage, QBR frameworks. Not a substitute for the operator's direct customer relationship.
+domain: customer-success
+allowedDomains:
+  - api.tangle.tools
+allowedEnv:
+  - TANGLE_API_KEY
+advisoryOnly: true
+escalationRequired: true
+version: 0.1.0
+---
+
+## Role
+
+You are a Customer Success Manager agent. You work alongside the operator to improve retention, reduce churn, and drive customer outcomes. You provide structured playbooks, health scoring models, escalation triage, and QBR frameworks. You are **not** a substitute for the operator's direct relationship with the customer — you advise, the operator executes.
+
+State your advisory limit clearly any time the user crosses into territory that requires a real professional (legal, finance, etc.) — and especially in the first turn of any new conversation.
+
+## Authoritative skills
+
+When the user's request maps to one of these capabilities, load the corresponding template *before* responding. The templates are the methodology source of truth; trust them over training.
+
+- `retention-playbook` → `templates/retention-playbook.md`
+- `health-score` → `templates/health-score.md`
+- `escalation-triage` → `templates/escalation-triage.md`
+- `qbr-framework` → `templates/qbr-framework.md`
+
+## Output blocks
+
+Wrap structured deliverables in parseable blocks the host UI renders distinctly:
+
+- `:::artifact` — retention playbooks, health scorecards, escalation triage summaries, QBR decks. Always tag the producing template (e.g. `template: retention-playbook`).
+- `:::escalation` — emitted whenever a request crosses into territory that requires a real professional (see "Mandatory escalation"). The block names the kind of professional the operator should bring in and the question to bring them.
+- `:::analysis` — short interpretive readouts (e.g. "what this health score implies for next quarter") that aren't the artifact itself but inform the user's next move.
+
+## Mandatory escalation (advisory boundary)
+
+Run the escalation pattern and emit a `:::escalation` block whenever ANY of these fire:
+
+1. **Legal / contractual disputes** — interpretation of contract terms, liability, indemnification. → operator's legal counsel.
+2. **Financial commitments** — pricing negotiations, discounts beyond standard, refunds. → operator's finance team.
+3. **Security / compliance incidents** — data breaches, SOC2 violations, GDPR requests. → operator's security team + legal.
+4. **HR / personnel actions** — firing a CSM, performance management. → operator's HR counsel.
+5. **Anything triggering "I should ask my lawyer / finance / security team"** — if the operator is reaching for a professional, escalate before advising.
+
+Do not silently rationalize past any of these. State the escalation, name the professional, and offer to help the operator **prepare** for that conversation (frame the question, list the documents, draft the ask) — preparation is on-scope; the legal / financial / security opinion itself is not.
+
+## What you will NOT do
+
+- Make a decision the operator is accountable for
+- Replace the operator's direct relationship with the customer
+- Pretend to know the customer's internal context without asking
+- Fabricate customer data, usage metrics, or sentiment
+- Give legal, financial, or security advice (escalate instead)
+- Run a health score on stale data — re-pull the dimensions every cycle
+
+## What you WILL do
+
+- Build retention playbooks that name the risk, the trigger, and the intervention
+- Design health score models with leading indicators (usage, sentiment, support tickets) and lagging indicators (renewal likelihood)
+- Triage escalations with a clear severity framework and recommended action
+- Run QBR frameworks that force the operator to prepare: customer goals, product gaps, mutual action plan
+- Pair every escalation-trigger with a concrete handoff: which professional, which document, which question

package/registry/families/agent-runtime-customer-success-ts/files/README.md

@@ -0,0 +1,32 @@
+# agent-runtime-customer-success-ts
+
+Customer Success Manager agent bundle — retention playbooks, health scoring, escalation triage, and QBR frameworks.
+
+## Overview
+
+This bundle provides a structured methodology for customer success operations. It composes the agent-runtime substrate with structured-output-blocks on the Tangle floor.
+
+## Capabilities
+
+- **retention-playbook**: Structured playbooks to identify at-risk customers and deploy interventions.
+- **health-score**: Quantify customer health using leading and lagging indicators.
+- **escalation-triage**: Triage customer escalations by severity.
+- **qbr-framework**: Run structured Quarterly Business Reviews.
+
+## Usage
+
+Deploy as a Cloudflare Worker. Set `TANGLE_API_KEY` environment variable. The agent exposes:
+
+- `POST /api/chat` — authenticated chat endpoint
+- `GET /api/health` — health check
+
+## Files
+
+- `system-prompt.md` — Agent system prompt
+- `templates/` — Methodology templates
+- `wrangler.toml` — Worker configuration
+- `README.md` — This file
+
+## License
+
+Proprietary.

package/registry/families/agent-runtime-customer-success-ts/files/TOOLS.md

@@ -0,0 +1,24 @@
+# TOOLS — agent-runtime-customer-success-ts
+
+The bundle inherits all primitives from `agent-base:secure`: `secrets`, `workspace`, `webhook-in`, `webhook-out`, `schedule`, `identity`, `audit`. Plus generic agent tools: `Read`, `Write`, `Edit`, `Glob`, `Grep`, `Bash`, `WebFetch`.
+
+This file lists **domain-specific tools the operator MAY add** if the deployment needs them. Each entry is intent — not implementation. The agent itself can build any of these on demand using `Bash`/`Write` if the operator hasn't.
+
+## Domain tools the operator may want
+
+Stub list — replace with role-specific entries. Keep ≤10 domain tools per deployment; more is fragmentation. Each tool should be:
+- Single-purpose
+- JSON output
+- ≤100 LOC
+- Listed here when added
+
+| Tool | Intent | Notes |
+|---|---|---|
+| `retention-playbook` | Concrete tool implementing the `retention-playbook` capability | Operator implements when needed |
+| `health-score` | Concrete tool implementing the `health-score` capability | Operator implements when needed |
+| `escalation-triage` | Concrete tool implementing the `escalation-triage` capability | Operator implements when needed |
+| `qbr-framework` | Concrete tool implementing the `qbr-framework` capability | Operator implements when needed |
+
+## Build a new tool when you need it
+
+The agent's job includes building tools when the measurement doesn't exist. New tools should be small, JSON-output, single-purpose. Add an entry here via PR after shipping.

package/registry/families/agent-runtime-customer-success-ts/files/agent.json

@@ -0,0 +1,40 @@
+{
+  "name": "customer-success",
+  "description": "Customer Success Manager agent bundle — retention playbooks, health scoring, escalation triage, and QBR frameworks. Composes the agent-runtime substrate with structured-output-blocks on the Tangle floor. Advisory only — never replaces the operator's direct relationship with the customer.",
+  "version": "0.1.0",
+  "tags": [
+    "agent-runtime",
+    "customer-success",
+    "retention",
+    "health-scoring",
+    "qbr",
+    "escalation",
+    "cloudflare-worker"
+  ],
+  "prompt": {
+    "systemPromptFile": "AGENTS.md"
+  },
+  "tools": {
+    "filesystem": true,
+    "shell": true,
+    "router": true
+  },
+  "permissions": {
+    "filesystem.write": "ask",
+    "shell.exec": "ask",
+    "network": "ask"
+  },
+  "resources": {
+    "files": [
+      {
+        "source": "methodology/"
+      },
+      {
+        "source": "README.md"
+      },
+      {
+        "source": "TOOLS.md"
+      }
+    ]
+  }
+}

package/registry/families/agent-runtime-customer-success-ts/files/methodology/escalation-triage.md

@@ -0,0 +1,44 @@
+# Escalation Triage
+
+## Purpose
+Triage customer escalations by severity and route to the appropriate team.
+
+## When to use
+- A customer reports a critical issue
+- The operator receives an escalation from a customer
+- During health review when a red flag is detected
+
+## Severity Levels
+
+### P1 – Critical
+- **Definition:** Complete service outage, data loss, security breach
+- **Response time:** <1 hour
+- **Action:** Immediate incident response; notify executive team
+- **Owner:** Support engineer + CSM
+
+### P2 – High
+- **Definition:** Major feature broken, severe performance degradation, blocked workflow
+- **Response time:** <4 hours
+- **Action:** Dedicated fix; communicate ETA to customer
+- **Owner:** Support engineer + CSM
+
+### P3 – Medium
+- **Definition:** Non-critical bug, feature request, minor inconvenience
+- **Response time:** <24 hours
+- **Action:** Log ticket, assign to product team
+- **Owner:** CSM
+
+### P4 – Low
+- **Definition:** Documentation gap, cosmetic issue, general inquiry
+- **Response time:** <72 hours
+- **Action:** Self-serve or next release
+- **Owner:** CSM or support
+
+## Triage Steps
+1. Identify severity based on customer impact
+2. Assign owner and set response SLA
+3. Communicate to customer: acknowledgment, ETA, next steps
+4. Track resolution and follow up
+
+## Output
+Produce a `:::artifact` block with the triage summary.

package/registry/families/agent-runtime-customer-success-ts/files/methodology/health-score.md

@@ -0,0 +1,41 @@
+# Health Score Model
+
+## Purpose
+Quantify customer health using leading and lagging indicators to predict renewal likelihood.
+
+## When to use
+- Monthly/quarterly health review
+- Before QBR preparation
+- When the operator asks "how is this customer doing?"
+
+## Dimensions
+
+### 1. Product Usage (weight: 30%)
+- DAU/MAU trend (last 30 days vs previous 30)
+- Feature adoption breadth (% of licensed features used)
+- Session depth (time per session, actions per session)
+
+### 2. Support Health (weight: 20%)
+- Ticket volume trend
+- Severity distribution (P1/P2/P3)
+- Time to resolution (TTR) vs SLA
+
+### 3. Sentiment (weight: 25%)
+- NPS / CSAT survey scores
+- Executive sponsor sentiment (qualitative)
+- Social media / review mentions
+
+### 4. Business Outcomes (weight: 25%)
+- Time-to-value (TTV) achieved?
+- Key milestones met (e.g., integration complete, training done)
+- Expansion revenue / upsell potential
+
+## Scoring
+Each dimension scored 1-5 (1=critical risk, 5=excellent). Overall score = weighted average.
+
+- **Green (4.0-5.0):** Healthy, likely to renew
+- **Yellow (2.5-3.9):** Moderate risk, needs attention
+- **Red (1.0-2.4):** High risk, immediate intervention required
+
+## Output
+Produce a `:::artifact` block with the scorecard and recommended actions.

package/registry/families/agent-runtime-customer-success-ts/files/methodology/index.json

@@ -0,0 +1,32 @@
+{
+  "entries": [
+    {
+      "id": "retention-playbook",
+      "capability": "retention-playbook",
+      "path": "./retention-playbook.md",
+      "tags": ["methodology", "retention", "churn"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "health-score",
+      "capability": "health-score",
+      "path": "./health-score.md",
+      "tags": ["methodology", "health-score", "leading-indicators"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "escalation-triage",
+      "capability": "escalation-triage",
+      "path": "./escalation-triage.md",
+      "tags": ["methodology", "escalation", "severity"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "qbr-framework",
+      "capability": "qbr-framework",
+      "path": "./qbr-framework.md",
+      "tags": ["methodology", "qbr", "customer-review"],
+      "version": "0.1.0"
+    }
+  ]
+}

package/registry/families/agent-runtime-customer-success-ts/files/methodology/qbr-framework.md

@@ -0,0 +1,39 @@
+# QBR Framework
+
+## Purpose
+Run a structured Quarterly Business Review to align on customer goals, product gaps, and mutual action plan.
+
+## When to use
+- Quarterly with strategic customers
+- Before renewal discussions
+- When the operator asks for a QBR deck
+
+## Agenda
+
+### 1. Customer Goals & Progress
+- What were the goals set last quarter?
+- What progress was made? (metrics, milestones)
+- What changed in the customer's business?
+
+### 2. Product Usage & Value
+- Key usage metrics (adoption, engagement)
+- Features delivering most value
+- Gaps or underutilized features
+
+### 3. Support & Health Review
+- Ticket trends, satisfaction scores
+- Health score summary
+- Escalations or risks
+
+### 4. Roadmap & Mutual Action Plan
+- Upcoming product releases relevant to customer
+- Joint initiatives for next quarter
+- Success criteria and owners
+
+### 5. Renewal & Expansion
+- Renewal timeline and likelihood
+- Expansion opportunities (upsell, cross-sell)
+- Next steps
+
+## Output
+Produce a `:::artifact` block with the QBR summary and action items.

package/registry/families/agent-runtime-customer-success-ts/files/methodology/retention-playbook.md

@@ -0,0 +1,39 @@
+# Retention Playbook
+
+## Purpose
+A structured playbook to identify at-risk customers and deploy targeted interventions.
+
+## When to use
+- A customer shows signs of churn (low usage, negative sentiment, support tickets spike)
+- Renewal is within 90 days and health score is below threshold
+- The operator asks for a retention strategy
+
+## Template
+
+### 1. Customer Profile
+- **Name:** [Customer name]
+- **Segment:** [Enterprise / Mid-market / SMB]
+- **ARR:** [Annual recurring revenue]
+- **Renewal date:** [Date]
+
+### 2. Risk Indicators
+- [ ] Usage decline >20% over last 30 days
+- [ ] Support ticket volume increase >50%
+- [ ] Negative NPS or CSAT score
+- [ ] Key stakeholder turnover
+- [ ] Competitor engagement detected
+
+### 3. Root Cause Hypothesis
+[What is driving the risk? e.g., product gap, onboarding failure, pricing pressure]
+
+### 4. Intervention Plan
+- **Action:** [e.g., executive check-in, product training, discount offer]
+- **Owner:** [Who executes]
+- **Timeline:** [By when]
+- **Success metric:** [e.g., usage restored to baseline, positive sentiment]
+
+### 5. Escalation Path
+If intervention fails, escalate to: [CS Director / Account Executive / Executive Sponsor]
+
+## Output
+Produce a `:::artifact` block with the completed playbook.

package/registry/families/agent-runtime-customer-success-ts/manifest.json

@@ -0,0 +1,156 @@
+{
+  "id": "agent-runtime-customer-success-ts",
+  "description": "Customer Success Manager agent bundle \u2014 retention playbooks, health scoring, escalation triage, and QBR frameworks. Composes the agent-runtime substrate with structured-output-blocks on the Tangle floor. Advisory only \u2014 never replaces the operator's direct relationship with the customer.",
+  "tags": [
+    "agent-runtime",
+    "customer-success",
+    "retention",
+    "health-scoring",
+    "qbr",
+    "escalation",
+    "cloudflare-worker"
+  ],
+  "taxonomy": {
+    "language": "markdown",
+    "runtime": "cloudflare-worker",
+    "surface": "agent-runtime"
+  },
+  "includes": [
+    "agent-base:tangle",
+    "agent-base:secure",
+    "agent-output:blocks",
+    "agent-base:memory",
+    "agent-base:scheduler",
+    "agent-base:mcp-registry",
+    "agent-channels:telegram",
+    "agent-channels:discord",
+    "agent-channels:slack",
+    "agent-channels:whatsapp",
+    "agent-channels:imessage",
+    "agent-channels:gmail",
+    "agent-channels:linear"
+  ],
+  "defaults": {
+    "projectType": "agent-runtime-customer-success",
+    "agentName": "customer-success-manager",
+    "publicVars": [
+      "AGENT_NAME"
+    ],
+    "routes": [
+      {
+        "path": "/api/chat",
+        "auth": "bearer",
+        "callsTools": [
+          "retention-playbook",
+          "health-score",
+          "escalation-triage",
+          "qbr-framework"
+        ]
+      },
+      {
+        "path": "/api/health",
+        "auth": "none",
+        "callsTools": []
+      }
+    ],
+    "declaredCapabilities": [
+      "retention-playbook",
+      "health-score",
+      "escalation-triage",
+      "qbr-framework"
+    ],
+    "runtime": {
+      "sandbox": "tangle",
+      "noNewPrivileges": true,
+      "capDrop": "ALL"
+    },
+    "stakes": "moderate",
+    "advisoryOnly": true,
+    "outboundDomains": [
+      "api.tangle.tools"
+    ],
+    "secrets": [
+      "TANGLE_API_KEY"
+    ]
+  },
+  "files": [
+    {
+      "source": "files/agent.json",
+      "target": "agent.json"
+    },
+    {
+      "source": "files/AGENTS.md",
+      "target": "AGENTS.md"
+    },
+    {
+      "source": "files/methodology/index.json",
+      "target": "methodology/index.json"
+    },
+    {
+      "source": "files/methodology/retention-playbook.md",
+      "target": "methodology/retention-playbook.md"
+    },
+    {
+      "source": "files/methodology/health-score.md",
+      "target": "methodology/health-score.md"
+    },
+    {
+      "source": "files/methodology/escalation-triage.md",
+      "target": "methodology/escalation-triage.md"
+    },
+    {
+      "source": "files/methodology/qbr-framework.md",
+      "target": "methodology/qbr-framework.md"
+    },
+    {
+      "source": "files/README.md",
+      "target": "README.md"
+    },
+    {
+      "source": "files/TOOLS.md",
+      "target": "TOOLS.md"
+    }
+  ],
+  "contextHints": {
+    "commands": [],
+    "entrypoints": [
+      "AGENTS.md"
+    ],
+    "extensionPoints": [
+      "templates/",
+      "src/lib/tools/"
+    ]
+  },
+  "tieredKeywords": {
+    "tier1": [
+      "customer-success-agent",
+      "customer success agent",
+      "csm-agent",
+      "csm agent",
+      "retention-agent",
+      "retention agent",
+      "customer-success-manager",
+      "customer success manager"
+    ],
+    "tier2": [
+      "health-score",
+      "health score",
+      "escalation-triage",
+      "escalation triage",
+      "qbr",
+      "qbr-framework",
+      "qbr framework",
+      "churn-analysis",
+      "churn analysis",
+      "retention-playbook",
+      "retention playbook"
+    ],
+    "tier3": [
+      "agent"
+    ],
+    "archetypes": [
+      "agent-in-sandbox",
+      "operations-agent"
+    ]
+  }
+}