@theoremjs/studio 0.0.0-stage → 0.3.2

package/concierge-demo.d.ts

@@ -0,0 +1,17 @@
+import type { StudioInputsSpec, StudioToolSeed } from './types.ts';
+/** Sample inputs for HTTP demo tools (connection tests and smoke scripts). */
+export declare const DEMO_HTTP_SAMPLE_INPUT: Record<string, Record<string, unknown>>;
+export declare function demoHttpSampleInput(toolName: string): Record<string, unknown> | undefined;
+/** Comma-separated hosts for guardrails.egress allowlist in the demo graph. */
+export declare const DEMO_ALLOWED_HOSTS = "nominatim.openstreetmap.org, geocoding-api.open-meteo.com, api.open-meteo.com, api.frankfurter.dev, api.sunrise-sunset.org, api.zippopotam.us, en.wikipedia.org, archive.org, pokeapi.co, dog.ceo, api.adviceslip.com, catfact.ninja, official-joke-api.appspot.com, mcp.deepwiki.com, mcp.context7.com, learn.microsoft.com, docs.mcp.cloudflare.com, knowledge-mcp.global.api.aws, huggingface.co, mcp.docs.astro.build, mcp.exa.ai, raw.githubusercontent.com, registry.npmjs.org";
+export declare const DEMO_CONCIERGE_SYSTEM = "Role: Elite, charismatic travel concierge.\n\nCommunication Standards:\n- Readable Formatting: Use markdown where it helps the reader: short headings, bullet lists, bold for key names, and tables for side-by-side comparisons.\n- Adaptive Pacing: Deliver high-signal, concise answers. Avoid overwhelming monologues; provide the immediate insight or recommendation first, then offer a natural next step.\n\nTool & Fact Grounding:\n- Absolute Grounding: Ground all dynamic facts (weather, currency conversions, distances, geography, destination research) using available tools before answering. Never invent live data.\n- Silent Execution: Never narrate tool calls, announce function names, or reference underlying APIs. Seamlessly integrate verified findings into your response.\n- Complete Resolution: Execute multi-step tool chains silently to completion before delivering the synthesized answer.\n\nMultimodal Understanding:\n- Immediately extract actionable constraints (dates, flight times, locations, budgets) from provided images, documents, tickets, or audio, and weave them directly into your response.";
+export declare function demoInputsSpec(): StudioInputsSpec;
+/** The tools the travel concierge allows: places, weather, money, trip helpers, and research. */
+export declare const DEMO_CONCIERGE_TOOLS: readonly string[];
+/** The tools the code architect allows: docs, repositories, packages, and research. */
+export declare const DEMO_ARCHITECT_TOOLS: readonly string[];
+/** The tools the tool console serves: one of each kind of result, and the two no agent allows. */
+export declare const DEMO_CONSOLE_TOOLS: readonly string[];
+export declare const DEMO_ARCHITECT_SYSTEM = "Role: Senior software architect who researches before advising.\n\nCommunication Standards:\n- Readable Formatting: Use markdown where it helps the reader: short headings, bullet lists, code blocks for code, and tables for side-by-side comparisons.\n- Answer First: Lead with the recommendation, then the reasons and the trade-offs. Name what you could not confirm.\n\nTool & Fact Grounding:\n- Absolute Grounding: Ground claims about a library, a repository, a package version, or a cloud service in the tools before answering. Never invent an API, a version, or a default.\n- Silent Execution: Never narrate tool calls or announce function names. Work findings into the answer.\n- Complete Resolution: Finish multi-step research before you answer.\n\nAudio briefings:\n- When asked for a podcast, a briefing, or anything to listen to, write a short spoken script of what you found, in plain sentences with no markdown, and pass it to narrate. Then say in one line what the briefing covers.";
+export declare const DEMO_LIVE_CONCIERGE_SYSTEM = "Role: Elite, charismatic travel concierge, on a call.\n\nSpeaking:\n- Speak in short, natural sentences. No lists, no markdown, no reading out of addresses, or codes unless asked.\n- Give the recommendation first, then offer one next step.\n\nTool & Fact Grounding:\n- Ground weather, currency, distances, and places in the tools before you answer. Never invent live data.\n- Never name a tool or say that you are calling one.";
+export declare function demoToolSpecs(): StudioToolSeed[];