@tangle-network/starter-foundry 0.7.3 → 0.13.2

package/registry/families/agent-runtime-college-counselor-ts/files/methodology/index.json

@@ -0,0 +1,25 @@
+{
+  "entries": [
+    {
+      "id": "application-strategy",
+      "capability": "application-strategy",
+      "path": "./application-strategy.md",
+      "tags": ["methodology", "college-list", "application-plan"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "essay-coaching",
+      "capability": "essay-coaching",
+      "path": "./essay-coaching.md",
+      "tags": ["methodology", "essay", "personal-statement"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "financial-aid-navigation",
+      "capability": "financial-aid-navigation",
+      "path": "./financial-aid-navigation.md",
+      "tags": ["methodology", "financial-aid", "fafsa", "css-profile"],
+      "version": "0.1.0"
+    }
+  ]
+}

package/registry/families/agent-runtime-college-counselor-ts/manifest.json

@@ -0,0 +1,144 @@
+{
+  "id": "agent-runtime-college-counselor-ts",
+  "description": "College admissions counselor agent bundle \u2014 application strategy, essay coaching, and financial-aid navigation for high-school students and their families. Composes the agent-runtime substrate with structured-output-blocks on the Tangle floor. Advisory only \u2014 never replaces a licensed college counselor, financial-aid officer, or admissions professional.",
+  "tags": [
+    "agent-runtime",
+    "college-counselor",
+    "admissions-coach",
+    "essay-coaching",
+    "financial-aid",
+    "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-college-counselor",
+    "agentName": "college-counselor",
+    "publicVars": [
+      "AGENT_NAME"
+    ],
+    "routes": [
+      {
+        "path": "/api/chat",
+        "auth": "bearer",
+        "callsTools": [
+          "application-strategy",
+          "essay-coaching",
+          "financial-aid-navigation"
+        ]
+      },
+      {
+        "path": "/api/health",
+        "auth": "none",
+        "callsTools": []
+      }
+    ],
+    "declaredCapabilities": [
+      "application-strategy",
+      "essay-coaching",
+      "financial-aid-navigation"
+    ],
+    "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/application-strategy.md",
+      "target": "methodology/application-strategy.md"
+    },
+    {
+      "source": "files/methodology/essay-coaching.md",
+      "target": "methodology/essay-coaching.md"
+    },
+    {
+      "source": "files/methodology/financial-aid-navigation.md",
+      "target": "methodology/financial-aid-navigation.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": [
+      "college-counselor-agent",
+      "college counselor agent",
+      "admissions-coach",
+      "admissions coach",
+      "college-counselor",
+      "college counselor"
+    ],
+    "tier2": [
+      "application-strategy",
+      "application strategy",
+      "essay-coaching",
+      "essay coaching",
+      "financial-aid-navigation",
+      "financial aid navigation",
+      "college-list",
+      "college list",
+      "common-app",
+      "common app"
+    ],
+    "tier3": [],
+    "archetypes": [
+      "agent-in-sandbox",
+      "tutor-agent"
+    ]
+  }
+}

package/registry/families/agent-runtime-cs-research-ts/files/AGENTS.md

@@ -0,0 +1,62 @@
+---
+name: cs-research-assistant
+role: CS Research Assistant — literature survey, paper summarization, citation-graph exploration, research-question formulation
+ domain: cs-research
+allowedDomains:
+  - api.tangle.tools
+  - export.arxiv.org
+  - api.semanticscholar.org
+  - api.openalex.org
+  - api.crossref.org
+allowedEnv:
+  - TANGLE_API_KEY
+advisoryOnly: true
+version: 0.1.0
+---
+
+## Role
+
+You are a CS Research Assistant — a tool for exploring the computer science literature, summarizing papers, tracing citation graphs, and formulating research questions. You are **not** a peer reviewer, not an IRB, not a substitute for the researcher's own judgment. Your job is to help the researcher **survey the landscape**, **understand key contributions**, **identify gaps**, and **structure their inquiry**.
+
+You ground every claim in citations from arxiv, Semantic Scholar, OpenAlex, or Crossref. You never fabricate a paper, a result, or a citation. You state clearly when you cannot find evidence for a claim.
+
+## 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.
+
+- `literature-survey` → `templates/literature-survey.md`
+- `paper-summarization` → `templates/paper-summarization.md`
+- `citation-graph-exploration` → `templates/citation-graph-exploration.md`
+- `research-question-formulation` → `templates/research-question-formulation.md`
+
+## Output blocks
+
+Wrap structured deliverables in parseable blocks the host UI renders distinctly:
+
+- `:::artifact` — survey write-ups, paper summaries, citation-graph analyses, research-question drafts. Always tag the producing template (e.g. `template: literature-survey`).
+- `:::survey` — citation-grounded literature context produced via the research-corpus tools. Inline cite by `[surname, year]`; collect full citations at the bottom of the block. Refuse to fabricate citations.
+- `:::escalation` — emitted when the user's request crosses into territory that requires a real professional (e.g., IRB approval, clinical trial design, proprietary data access). Name the professional and the question to bring them.
+
+## Research-corpus discipline
+
+When the user asks for literature context, related work, benchmark data, or "what does the literature say about X" — **use the research-corpus tools**. Do not hallucinate papers, results, or citation counts. Search arxiv / Semantic Scholar / OpenAlex / Crossref, cite by `[surname, year]`, and emit the result inside a `:::survey` block.
+
+If you cannot find a citation, say so plainly and downgrade the claim to a hypothesis the user can test — never fabricate.
+
+## What you will NOT do
+
+- Fabricate papers, citations, or results
+- Provide peer review (you are not a domain expert; you summarize, not evaluate)
+- Give advice on research ethics, IRB compliance, or data privacy (escalate instead)
+- Claim to have read a paper you have not retrieved
+- Override the researcher's own judgment on methodology or interpretation
+
+## What you WILL do
+
+- Search and retrieve papers from arxiv, Semantic Scholar, OpenAlex, Crossref
+- Summarize papers concisely: problem, method, key result, limitations
+- Trace citation graphs: who cites whom, seminal works, recent surveys
+- Help formulate research questions: gap identification, hypothesis framing, related work positioning
+- Cite every claim with `[surname, year]` and provide full references
+- State when evidence is thin or conflicting
+- Pair every escalation-trigger with a concrete handoff: which professional, which document, which question

package/registry/families/agent-runtime-cs-research-ts/files/README.md

@@ -0,0 +1,35 @@
+# CS Research Assistant Agent Bundle
+
+## Overview
+A Cloudflare Worker agent that assists with computer science research: literature surveys, paper summarization, citation-graph exploration, and research-question formulation. Uses the research-corpus layer (arxiv, Semantic Scholar, OpenAlex, Crossref) for citation-grounded responses.
+
+## Includes
+- agent-base:tangle
+- agent-tools:research-corpus
+- agent-output:blocks
+
+## Capabilities
+- literature-survey
+- paper-summarization
+- citation-graph-exploration
+- research-question-formulation
+
+## Routes
+- `POST /api/chat` — Bearer auth, calls research tools
+- `GET /api/health` — No auth
+
+## Environment Variables
+- `TANGLE_API_KEY` (required)
+- `AGENT_NAME` (public)
+
+## Usage
+Deploy to Cloudflare Workers with the provided wrangler.toml. The agent runs in a Tangle sandbox with no new privileges and all capabilities dropped by default.
+
+## Templates
+- `templates/literature-survey.md`
+- `templates/paper-summarization.md`
+- `templates/citation-graph-exploration.md`
+- `templates/research-question-formulation.md`
+
+## License
+MIT

package/registry/families/agent-runtime-cs-research-ts/files/TOOLS.md

@@ -0,0 +1,33 @@
+# TOOLS — agent-runtime-cs-research-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.
+
+## Research corpus (inherited from `agent-tools:research-corpus`)
+
+| Capability | Intent |
+|---|---|
+| `corpus.arxiv(query)` | arXiv paper search |
+| `corpus.semanticScholar(query)` | Semantic Scholar |
+| `corpus.openalex(query)` | OpenAlex |
+| `corpus.crossref(query)` | Crossref DOI metadata |
+
+## 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 |
+|---|---|---|
+| `literature-survey` | Concrete tool implementing the `literature-survey` capability | Operator implements when needed |
+| `paper-summarization` | Concrete tool implementing the `paper-summarization` capability | Operator implements when needed |
+| `citation-graph-exploration` | Concrete tool implementing the `citation-graph-exploration` capability | Operator implements when needed |
+| `research-question-formulation` | Concrete tool implementing the `research-question-formulation` 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-cs-research-ts/files/agent.json

@@ -0,0 +1,39 @@
+{
+  "name": "cs-research",
+  "description": "CS Research Assistant agent bundle — literature survey, paper summarization, citation-graph exploration, and research-question formulation. Composes the agent-runtime substrate with the research-corpus layer (arxiv / Semantic Scholar / OpenAlex / Crossref) so every claim is citation-grounded. Advisory only — never replaces peer review, IRB, or the researcher's own judgment.",
+  "version": "0.1.0",
+  "tags": [
+    "agent-runtime",
+    "cs-research",
+    "literature-survey",
+    "paper-summarization",
+    "citation-graph",
+    "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-cs-research-ts/files/methodology/citation-graph-exploration.md

@@ -0,0 +1,36 @@
+# Citation Graph Exploration Template
+
+## Purpose
+Trace the citation graph around a seed paper or topic: who cites whom, seminal works, recent surveys.
+
+## Steps
+1. **Seed**: Identify the starting paper(s).
+2. **Forward**: Find papers that cite the seed.
+3. **Backward**: Find papers cited by the seed.
+4. **Cluster**: Group by theme, method, or community.
+5. **Analyze**: Identify influential works, trends, and gaps.
+
+## Output format
+```
+:::artifact template: citation-graph-exploration
+## Citation Graph: [Seed Paper]
+
+### Seed
+- [surname, year] Title.
+
+### Influential Citations (forward)
+- [surname, year] Title. (citations count)
+- ...
+
+### Key References (backward)
+- [surname, year] Title.
+- ...
+
+### Clusters
+- **Cluster 1**: ...
+- **Cluster 2**: ...
+
+### Insights
+- ...
+:::
+```

package/registry/families/agent-runtime-cs-research-ts/files/methodology/index.json

@@ -0,0 +1,32 @@
+{
+  "entries": [
+    {
+      "id": "literature-survey",
+      "capability": "literature-survey",
+      "path": "./literature-survey.md",
+      "tags": ["methodology", "survey", "literature"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "paper-summarization",
+      "capability": "paper-summarization",
+      "path": "./paper-summarization.md",
+      "tags": ["methodology", "summarization", "paper"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "citation-graph-exploration",
+      "capability": "citation-graph-exploration",
+      "path": "./citation-graph-exploration.md",
+      "tags": ["methodology", "citation", "graph"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "research-question-formulation",
+      "capability": "research-question-formulation",
+      "path": "./research-question-formulation.md",
+      "tags": ["methodology", "research-question", "gap"],
+      "version": "0.1.0"
+    }
+  ]
+}

package/registry/families/agent-runtime-cs-research-ts/files/methodology/literature-survey.md

@@ -0,0 +1,40 @@
+# Literature Survey Template
+
+## Purpose
+Conduct a systematic survey of the literature on a given topic, identifying key papers, trends, and gaps.
+
+## Steps
+1. **Define scope**: Clarify the research question, time range, and venues.
+2. **Search**: Use research-corpus tools to retrieve papers from arxiv, Semantic Scholar, OpenAlex, Crossref.
+3. **Screen**: Filter by relevance, quality, and recency.
+4. **Extract**: For each paper, note problem, method, key result, limitations.
+5. **Synthesize**: Identify themes, debates, and open questions.
+6. **Report**: Produce a structured survey with citations.
+
+## Output format
+```
+:::artifact template: literature-survey
+## Survey: [Topic]
+
+### Scope
+- Research question: ...
+- Databases searched: ...
+- Time range: ...
+- Keywords: ...
+
+### Key Papers
+| Paper | Problem | Method | Key Result | Limitations |
+|-------|---------|--------|------------|-------------|
+| [surname, year] | ... | ... | ... | ... |
+
+### Themes
+1. ...
+2. ...
+
+### Gaps
+- ...
+
+### References
+- [surname, year] Title. Venue. URL
+:::
+```

package/registry/families/agent-runtime-cs-research-ts/files/methodology/paper-summarization.md

@@ -0,0 +1,120 @@
+# Paper Summarization Template
+
+## Purpose
+Summarize a single CS / ML paper concisely and faithfully: problem,
+method, key result, claims-vs-evidence, limitations, and relevance
+to the user's question. Citation-grounded — never paraphrase what
+the paper doesn't say.
+
+## When to use
+Trigger when the user asks "what does this paper claim" or
+"summarize <arXiv ID>." For broader literature surveys, use
+literature-survey.md. For citation graphs, use
+citation-graph-exploration.md.
+
+## Method
+
+1. **Retrieve via research-corpus.** Don't summarize from
+   training memory; pull the actual paper. arXiv preferred (full
+   PDF + LaTeX source); fall back to OpenAlex / publisher.
+2. **Pin the version.** Papers update; cite the version
+   (`arXiv:2401.12345v3`, journal version, conference camera-
+   ready). Differences across versions can be material.
+3. **Read structurally.**
+   - **Abstract**: the claim. Often over-stated; use as a
+     starting hypothesis, not a conclusion.
+   - **Introduction**: the framing, the prior work, the gap the
+     paper claims to fill.
+   - **Method**: the actual technical content. Read this
+     carefully — many papers' contribution is small relative to
+     the abstract's framing.
+   - **Experiments**: what was tested, against what baselines,
+     on which benchmarks.
+   - **Results**: the numbers. Note variance, baselines, and
+     whether the gain is statistically and practically
+     meaningful.
+   - **Limitations**: what the paper says it doesn't do, and
+     (importantly) what it should say but doesn't.
+   - **Related work**: what's missed or sandbagged.
+4. **Distinguish claim from evidence.**
+   - The paper *claims* X.
+   - The experiments *show* Y.
+   - X and Y are sometimes the same; often they're not.
+   - "Our method generalizes" with experiments only on one
+     benchmark — claim, not evidence.
+5. **Surface the surprises.**
+   - Negative results buried in appendix.
+   - Ablations that show the headline component contributes
+     less than the abstract suggests.
+   - Compute / data scale that limits the claim's
+     generalizability.
+   - Reproducibility issues (no code, missing seeds).
+6. **Write the summary** in a tight, structured form (see
+   output below). Length scales with importance: 200 words for
+   most papers; 500–1000 for foundational works.
+7. **Tag relevance.** How does this paper bear on the user's
+   question? Direct evidence / indirect evidence / methodologically
+   relevant / not relevant.
+
+## Reading order tips
+
+- For most papers, **abstract → conclusion → figures → method →
+  experiments**. Conclusion is often more honest than abstract.
+- Read figures before reading the prose around them; they
+  compress the empirical claim.
+- Track citations forward: a 2020 paper read in 2026 has 5 years
+  of follow-up that may have refined or refuted it.
+
+## Output
+
+```
+:::artifact
+template: paper-summarization
+paper:
+  title: "..."
+  authors: [...]
+  venue: "NeurIPS 2023"
+  year: 2023
+  arxiv: "2310.XXXXX"
+  version: "v3"
+  doi: "10.xxxx"
+problem: "..."
+method: "..."
+contribution: "..."
+key-results: [...]
+baselines: [...]
+benchmarks: [...]
+claim-vs-evidence: "claims X; evidence supports X' which is narrower"
+limitations:
+  paper-states: [...]
+  reader-notices: [...]
+reproducibility:
+  code: "released" | "promised" | "absent"
+  seeds: ...
+  hparams: "complete" | "partial" | "absent"
+related-work-gaps: [...]
+relevance-to-query: "direct" | "methodologically related" | "tangential"
+:::
+```
+
+## Common summarization failures
+
+1. **Abstract regurgitation.** The summary parrots the abstract
+   without engaging the method or results.
+2. **Missing ablations.** Headline gains often shrink under
+   ablations; report both.
+3. **Compute / data scale dropped.** "Method M outperforms" — at
+   what scale? Always report.
+4. **Reproducibility silent.** Code / seeds / hparams status is
+   first-class information.
+5. **No comparison to baselines.** "X% on benchmark" without
+   comparison is meaningless.
+6. **Hand-wave limitations.** "Future work will address" is the
+   author's wishlist, not a real limitation report.
+
+## Refusal
+
+The agent will not:
+- Summarize a paper from memory without retrieving it.
+- Fabricate results, metrics, or citations.
+- Soften limitations to be polite to the authors.