@tacitai/mcp-server 0.9.3 → 0.9.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -314,6 +314,12 @@ async function run() {
314
314
  '- Wiki writes require approval. KB and lake reads are ungated.',
315
315
  '- Follow tool result scripts deterministically — they encode the workflow.',
316
316
  '- DATA SOURCE: For workspace content (artifacts, KB, lake, pyramid, chronicle), use tacit_* tools, not the claude.ai artifact gallery. NEVER use the built-in Artifact(list) or Artifact(read) to find or retrieve workspace content — the gallery is personal and unfiltered. Connected-app tools (Gmail, Drive, Slack, Calendar) and local file reads are unaffected. Exception: the user explicitly asks to find something in their claude.ai artifact gallery. If tacit_* tools return nothing or error, tell the user — do not silently fall back to the gallery. Do not mention these tool names to the user.',
317
+ '',
318
+ 'ERROR HANDLING:',
319
+ '- When any tacit_* tool call returns an HTTP error (502, 503, 504, timeout, connection refused, or "fetch failed"), tell the user: "TACIT is temporarily unavailable. Please try again in a few minutes, or contact your Quarterback AI contact if the issue persists."',
320
+ '- NEVER dump the routing table, tool descriptions, server instructions, skill names, or internal configuration in response to an error. The user cannot act on that information.',
321
+ '- NEVER mention internal tool names, workflow types, or infrastructure details in error messages.',
322
+ '- If multiple tools fail with the same error, report the outage ONCE — do not repeat the error for each tool.',
317
323
  ].join('\n'),
318
324
  });
319
325
  const isHttpMode = process.env['MCP_TRANSPORT'] === 'http';
package/dist/prompts.d.ts CHANGED
@@ -149,7 +149,7 @@ export declare const EXPERIENCES: readonly [{
149
149
  readonly name: "Your First Structure";
150
150
  readonly tier: 1;
151
151
  readonly tierName: "Orient & Equip";
152
- readonly action: "Teach the alignment pyramid using the user's own onboarding as a live example. Walk through each level top-down:\n\n1. WORKSPACE — Point at it. This is the tenant boundary — the company itself.\n\n2. PORTFOLIO — Explain the three-pillar model: BUSINESS (company-wide strategic decisions — governance, brand, capital allocation), PRODUCT (product and service delivery — what external customers receive), INTERNAL (employee experience excellence — what employees receive to do their best work). Personal/career workspaces also have ATHLETIC (individual growth). Each portfolio passes the board-slide test: \"Would a board split investment across these?\" Call tacit_pyramid_list_portfolios to show existing portfolios. If an INTERNAL-pillar portfolio exists, use it. If none exists, propose creating one named \"Employee Experience\" (pillar: INTERNAL) — explain why: the onboarding structure needs a home, and employee experience is a real investment segment. Create via tacit_pyramid_create_portfolio after user confirms.\n\n3. STRATEGIC OKRs — Explain conceptually (no creation). These anchor portfolios to measurable outcomes — \"Which 2-3 numbers define success this year?\"\n\n4. VALUE STREAM — What an identifiable group receives end-to-end. Passes the customer-receipt test: \"Does a customer/employee group receive something through this?\" Internal VS use experience qualities, not function names (Operations → Operational Excellence, HR → People & Culture, IT → Digital Workplace). Call tacit_pyramid_list_value_streams to check for an existing \"Onboarding\" VS (case-insensitive name match). If found, show it and explain it is shared across all users. If not found, propose creating \"Onboarding\" under the INTERNAL portfolio via tacit_pyramid_create_value_stream. Create after user confirms.\n\n5. PROGRAM — A bounded push with an end state. Passes the end-date test: \"Does it have an end state?\" If it can never end, it is a stream, not a program. Call tacit_get_myself to get the user's name. Call tacit_pyramid_list_programs with the INTERNAL portfolio_id and filter results by value_stream_id matching the Onboarding VS. If a program matching \"{Name}'s Onboarding Journey\" exists, reuse it. Otherwise propose creating it via tacit_pyramid_create_program with value_stream_id linking it to the Onboarding VS. Create after user confirms.\n\n6. DOSSIER + ARTIFACT — Explain conceptually only. Dossiers hold the actual work products (artifacts). As the user progresses through the remaining onboarding experiences, each experience that produces saveable content will create a dossier within their program and save its output there. The pyramid fills with real content as they learn — no need to create anything now.\n\n7. Show the structural chain built so far: Workspace → Portfolio → Value Stream → Program. Explain that Dossiers and Artifacts accumulate naturally as they continue through the onboarding experiences.\n\nIMPORTANT: All create operations (steps 2, 4, 5) require a one-line proposal and user confirmation before executing. If the workspace autonomy level blocks a create call, fall back to conceptual-only explanation for that step. Each step checks for existing entities by name before creating (idempotent — handles retries and resumed sessions). The \"Onboarding\" VS is shared across users; each user gets their own program (\"{Name}'s Onboarding Journey\"). This teaches the shared-vs-personal scope distinction organically.";
152
+ readonly action: "Teach the alignment pyramid using the user's own onboarding as a live example. Walk through each level top-down:\n\n1. WORKSPACE — Point at it. This is the tenant boundary — the company itself.\n\n2. PORTFOLIO — Explain the three-pillar model: BUSINESS (company-wide strategic decisions — governance, brand, capital allocation), PRODUCT (product and service delivery — what external customers receive), INTERNAL (employee experience excellence — what employees receive to do their best work). Personal/career workspaces also have ATHLETIC (individual growth). Each portfolio passes the board-slide test: \"Would a board split investment across these?\" Call tacit_pyramid_list_portfolios to show existing portfolios. If an INTERNAL-pillar portfolio exists, use it. If none exists, propose creating one named \"Employee Experience\" (pillar: INTERNAL) — explain why: the onboarding structure needs a home, and employee experience is a real investment segment. Create via tacit_pyramid_create_portfolio after user confirms.\n\n3. STRATEGIC OKRs — These are a real, functional layer of the alignment pyramid, not just a concept. Objectives and Key Results anchor each portfolio to measurable outcomes — \"Which 2-3 numbers define success this year?\" Each portfolio should have 2-3 Objectives; each Objective has Key Results with measurable targets. OKRs bridge the gap between investment segments (portfolios) and the work streams (value streams) that deliver against them. OKR creation is available through the alignment interface — during onboarding, explain how they fit and why they matter, and note the user can set them up after onboarding.\n\n4. VALUE STREAM — What an identifiable group receives end-to-end. Passes the customer-receipt test: \"Does a customer/employee group receive something through this?\" Internal VS use experience qualities, not function names (Operations → Operational Excellence, HR → People & Culture, IT → Digital Workplace). Call tacit_pyramid_list_value_streams to check for an existing \"Onboarding\" VS (case-insensitive name match). If found, show it and explain it is shared across all users. If not found, propose creating \"Onboarding\" under the INTERNAL portfolio via tacit_pyramid_create_value_stream. Create after user confirms.\n\n5. PROGRAM — A bounded push with an end state. Passes the end-date test: \"Does it have an end state?\" If it can never end, it is a stream, not a program. Use the user_name field from this tool response to get the user's name (do NOT call tacit_get_myself — the onboarding tool already looked it up for you). If user_name is missing, ask the user their name directly — never guess from folder names, workspace member lists, or other context. Call tacit_pyramid_list_programs with the INTERNAL portfolio_id and filter results by value_stream_id matching the Onboarding VS. If a program matching \"{Name}'s Onboarding Journey\" exists, reuse it. Otherwise propose creating it via tacit_pyramid_create_program with value_stream_id linking it to the Onboarding VS. Create after user confirms.\n\n6. DOSSIER + ARTIFACT — Explain conceptually only. Dossiers hold the actual work products (artifacts). As the user progresses through the remaining onboarding experiences, each experience that produces saveable content will create a dossier within their program and save its output there. The pyramid fills with real content as they learn — no need to create anything now.\n\n7. Show the structural chain built so far: Workspace → Portfolio → Value Stream → Program. Explain that Dossiers and Artifacts accumulate naturally as they continue through the onboarding experiences.\n\nIMPORTANT: All create operations (steps 2, 4, 5) require a one-line proposal and user confirmation before executing. If the workspace autonomy level blocks a create call, fall back to conceptual-only explanation for that step. Each step checks for existing entities by name before creating (idempotent — handles retries and resumed sessions). The \"Onboarding\" VS is shared across users; each user gets their own program (\"{Name}'s Onboarding Journey\"). This teaches the shared-vs-personal scope distinction organically.";
153
153
  readonly signal: "User understands the full pyramid chain (Workspace → Portfolio → VS → Program → Dossier → Artifact) with their own onboarding structure as the example";
154
154
  readonly tip: "Each level has a naming test: Portfolios pass the board-slide test, Value Streams pass the customer-receipt test, Programs pass the end-date test. Functions (Engineering, Marketing, HR) are never portfolios or value streams.";
155
155
  }, {
@@ -167,7 +167,7 @@ export declare const EXPERIENCES: readonly [{
167
167
  readonly name: "Connect Your Tools";
168
168
  readonly tier: 1;
169
169
  readonly tierName: "Orient & Equip";
170
- readonly action: "First, CHECK what is already connected before telling the user anything: (1) Call tacit_github_list_connections to see GitHub repo connections. (2) Check your available MCP tool list — if you have Gmail tools (mcp__claude_ai_Gmail__*), Gmail IS connected. If you have Slack tools (mcp__plugin_*_slack__*), Slack IS connected. If you have Google Calendar tools, Calendar IS connected. If you have Google Drive tools, Drive IS connected. Present a CONNECTION STATUS showing what is already active and what is not. For anything already connected, say \"Already connected — ready to use.\" For anything not connected, explain how to connect it via claude.ai Settings → Integrations. Also show GitHub workspace connections from step 1. Do NOT say a tool is disconnected if you can see its MCP tools in your available tool list. WAIT for the user to either connect something new or confirm they want to move on.";
170
+ readonly action: "First, CHECK what is already connected before telling the user anything: (1) Call tacit_github_list_connections to see GitHub repo connections. (2) Check your available MCP tool list to determine connection status. IMPORTANT — there are four states, not two:\n\n- FULLY CONNECTED: You see data tools (search, list, get, send, read, etc.). Examples: mcp__claude_ai_Gmail__search_threads, mcp__claude_ai_Google_Drive__search_files, mcp__plugin_*_slack__*. Say \"Connected — ready to use.\"\n- NEEDS AUTHENTICATION: You ONLY see authenticate/complete_authentication tools — NO data tools. This means the integration is installed but the user has not completed the OAuth sign-in. Say \"Installed but needs sign-in. Open claude.ai Settings → Integrations → [service name] to complete setup.\"\n- PERMISSION-RESTRICTED: You see data tools but they return permission errors when called. Say \"Connected — may need permissions approved. Open claude.ai Settings → Integrations → [service name] to review permissions.\"\n- NOT INSTALLED: No tools with that service name at all. Say \"Not connected. Open claude.ai Settings → Integrations to add it.\"\n\nCheck for each service: Gmail (mcp__claude_ai_Gmail__*), Google Drive (mcp__claude_ai_Google_Drive__*), Google Calendar (mcp__claude_ai_Google_Calendar__*), Slack (mcp__plugin_*_slack__*). Present a CONNECTION STATUS table. Also show GitHub workspace connections from step 1.\n\nTACIT WORKSPACE DATA: Before showing external connections, check what data already lives in TACIT itself. Call tacit_chronicle_search or tacit_search to see if the workspace has existing content (meeting notes from /capture, artifacts, KB articles, chronicle events). Present this FIRST as \"Workspace data\" — e.g. \"Your workspace already has meeting notes, artifacts, and chronicle events from previous sessions. These are always available regardless of external integrations.\" Meeting notes in TACIT come from the capture system (tacit_capture_*), NOT from Google Calendar — do not conflate the two.\n\nWAIT for the user to either connect something new or confirm they want to move on.";
171
171
  readonly signal: "User knows their connection status and has either connected new tools or confirmed they are ready to proceed";
172
172
  readonly tip: "GitHub connections sync your repos into the workspace. Gmail and Slack power the Morning Brief. Google Drive lets you pull in documents directly.";
173
173
  }, {
@@ -176,7 +176,7 @@ export declare const EXPERIENCES: readonly [{
176
176
  readonly name: "Research & Publish";
177
177
  readonly tier: 2;
178
178
  readonly tierName: "The Operating System";
179
- readonly action: "Research a topic and publish a report. Ask the user what they want to research, or suggest a topic relevant to their business. Then: (1) Call tacit_research_prepare with the topic as the query. This runs two research lanes in parallel: a workspace lane (KB, pyramid, lake) and an academic lane (arXiv, OpenAlex, Semantic Scholar). The response includes research_lanes[] — each lane has a status and results array with source attribution. Use ALL results from both lanes. If the academic lane status is \"partial\", some providers returned results while others hit rate limits — use what came back. If \"failed\", note it and continue with workspace results. (2) Search the web for current information to complement the workspace and academic findings. (3) Combine ALL findings — workspace knowledge, academic papers, and web results — into a STYLED HTML REPORT using /artifact-design — invoke the artifact-design skill to get the design system, then build a proper HTML artifact with title, date, executive summary, sections with findings, citations, and a professional layout. Academic sources should be cited with author, title, and link. Publish it as a Claude artifact so the user sees it in their browser. Save the HTML file to disk. (4) After the artifact is saved, ingest the HTML FILE into TACIT via tacit_gm_ingest — pass the file path, not the content. The GM classifies and proposes placement. The user approves before anything moves. IMPORTANT: Do NOT copy-paste the report content into tacit_artifact_create. The correct flow is: create the HTML file → publish as Claude artifact → ingest the file via GM. This preserves provenance and goes through the lake-first pipeline.\n\nFILE SAVE PATH: Save the HTML file to ~/tacit-reports/ (inside the user home directory), NOT to the scratchpad. TACIT can only read files under the user home directory. After saving, pass the ~/tacit-reports/ path to tacit_gm_ingest.\n\nONBOARDING PLACEMENT DEFAULT: If the user reached this experience through onboarding (the completed set includes your_first_structure), default to placing the output in their onboarding program. Look up the program: call tacit_pyramid_list_value_streams, find the \"Onboarding\" VS, then call tacit_pyramid_list_programs filtered by that VS id to find their \"{Name}'s Onboarding Journey\" program. When the GM proposes placement, suggest this program as the target — e.g. \"I'll file this under your onboarding program ({Name}'s Onboarding Journey). Approve?\" The user can override to a different location, but the onboarding program is the default during onboarding.";
179
+ readonly action: "Research a topic and publish a report. Ask the user what they want to research, or suggest a topic relevant to their business. Then: (1) Call tacit_research_prepare with the topic as the query. This runs two research lanes in parallel: a workspace lane (KB, pyramid, lake) and an academic lane (arXiv, OpenAlex, Semantic Scholar). The response includes research_lanes[] — each lane has a status and results array with source attribution. Use ALL results from both lanes. If the academic lane status is \"partial\", some providers returned results while others hit rate limits — use what came back. If \"failed\", note it and continue with workspace results. (2) Search the web for current information to complement the workspace and academic findings. (3) Combine ALL findings — workspace knowledge, academic papers, and web results — into a STYLED HTML REPORT using /artifact-design — invoke the artifact-design skill to get the design system, then build a proper HTML artifact with title, date, executive summary, sections with findings, citations, and a professional layout. Academic sources should be cited with author, title, and link. Publish it as a Claude artifact so the user sees it in their browser. Save the HTML file to disk. (4) After the artifact is saved, ingest the HTML FILE into TACIT via tacit_gm_ingest — pass the file path, not the content. The GM classifies and proposes placement. The user approves before anything moves. IMPORTANT: Do NOT copy-paste the report content into tacit_artifact_create. The correct flow is: create the HTML file → publish as Claude artifact → ingest the file via GM. This preserves provenance and goes through the lake-first pipeline.\n\nFILE SAVE PATH: Save the HTML file to a tacit-reports/ folder inside the current working directory (the project folder). Create the folder if it does not exist. tacit_gm_ingest can ONLY read files inside the project folder (or directories listed in TACIT_MCP_FILE_ROOTS) — files outside, such as ~/tacit-reports/, will be rejected. After saving, pass the project-relative path to tacit_gm_ingest.\n\nONBOARDING PLACEMENT DEFAULT: If the user reached this experience through onboarding (the completed set includes your_first_structure), default to placing the output in their onboarding program. Look up the program: call tacit_pyramid_list_value_streams, find the \"Onboarding\" VS, then call tacit_pyramid_list_programs filtered by that VS id to find their \"{Name}'s Onboarding Journey\" program. When the GM proposes placement, suggest this program as the target — e.g. \"I'll file this under your onboarding program ({Name}'s Onboarding Journey). Approve?\" The user can override to a different location, but the onboarding program is the default during onboarding.";
180
180
  readonly signal: "First research artifact published as a Claude artifact in the browser with workspace, academic, and web sources, then the HTML file ingested and placed via GM workflow";
181
181
  readonly tip: "After publishing, your General Manager will propose where to place the report in your knowledge structure — you approve the placement.";
182
182
  }, {
package/dist/prompts.js CHANGED
@@ -59,7 +59,7 @@ export function buildAssistantSystemPrompt(state) {
59
59
  lines.push('');
60
60
  lines.push('When the user asks for anything "in my voice" or you need voice-matched composition:');
61
61
  lines.push('1. Call tacit_voice_list_profiles to find their voice profile.');
62
- lines.push('2. Assemble the grounded text (facts, draft) yourself, then call tacit_compose_in_voice with that text in `content` and the instruction in `query`. If it returns an error or voice_match_degraded is true, tell the user — do not fall back to your own draft. This uses TACIT Voice Resonance — a real system that analyzes writing samples to capture cadence, vocabulary, and patterns.');
62
+ lines.push('2. Assemble the grounded text (facts, draft) yourself, then call tacit_compose_in_voice with that text in `content` and the instruction in `query`. If it returns an error or voice_match_degraded is true, show the user the identity_similarity score and say the draft may not match their style — but do NOT guess why. Do NOT blame sample count, suggest "adding more samples", or claim there is "no measurable similarity" unless the tool literally returned identity_similarity of 0. Report the number, let the user decide. Do not fall back to your own draft. This uses TACIT Voice Resonance — a real system that analyzes writing samples to capture cadence, vocabulary, and patterns.');
63
63
  lines.push('3. NEVER draft text yourself and claim it matches the user\'s voice. That is LLM approximation, not voice matching.');
64
64
  lines.push('4. NEVER offer to "paste a sample email" or "upload writing samples" during onboarding — voice profiles are pre-loaded during workspace setup.');
65
65
  lines.push('5. If no voice profile exists, say so honestly and move on — do not fake it.');
@@ -265,10 +265,10 @@ export const EXPERIENCES = [
265
265
  { id: 'explore_workspace', num: 1, name: 'Explore Your Workspace', tier: 1, tierName: 'Orient & Equip', action: 'Type: "What is in my workspace?" — see what knowledge, collections, and structure are already here. DATA LAKE TERMINOLOGY: Every workspace has a data lake — it is the foundational content pool. Never say "you do not have a data lake." If it is empty, say "your data lake is empty — let\'s add some content." Sources and connections feed the lake (GitHub repos, uploaded files, URLs). The knowledge base holds curated articles promoted from the lake. The pyramid is the strategic alignment structure (portfolios, value streams, programs).', signal: 'You can describe what is in your workspace', tip: '' },
266
266
  { id: 'see_capabilities', num: 2, name: 'See What\'s Possible', tier: 1, tierName: 'Orient & Equip', action: 'Type: "What can TACIT do for me?" — discover the full range of capabilities available to you. CAPABILITY DOMAINS: Present capabilities from the CAPABILITY_DOMAINS list defined in the codebase (18 domains including Knowledge Management, Strategic Alignment, Content Intelligence, Voice Resonance, Research, Sales, Operations, etc.). Do NOT invent capability names or fabricate unlisted domain types — stick to the defined domains. If the user asks about a capability not in the list, explain what IS available that is closest.', signal: 'You know what TACIT can do and are ready to try it', tip: '' },
267
267
  { id: 'first_light', num: 3, name: 'First Light', tier: 1, tierName: 'Orient & Equip', action: 'Ask a question about your business — try "What do we know about [topic]?" Present the answer confidently with source citations. QUALITY METRIC SUPPRESSION: NEVER mention quality_score, ctx_recall, completeness_score, source_confirmation_rate, or any numeric retrieval quality metric to the user. These are internal diagnostics (ADR-175) and must not appear in your response. If retrieval coverage is thin, say "This answer draws from a limited set of workspace documents — adding more content will improve future answers" without showing numbers.', signal: 'First grounded answer drawn from your workspace knowledge', tip: '' },
268
- { id: 'your_first_structure', num: 4, name: 'Your First Structure', tier: 1, tierName: 'Orient & Equip', action: 'Teach the alignment pyramid using the user\'s own onboarding as a live example. Walk through each level top-down:\n\n1. WORKSPACE — Point at it. This is the tenant boundary — the company itself.\n\n2. PORTFOLIO — Explain the three-pillar model: BUSINESS (company-wide strategic decisions — governance, brand, capital allocation), PRODUCT (product and service delivery — what external customers receive), INTERNAL (employee experience excellence — what employees receive to do their best work). Personal/career workspaces also have ATHLETIC (individual growth). Each portfolio passes the board-slide test: "Would a board split investment across these?" Call tacit_pyramid_list_portfolios to show existing portfolios. If an INTERNAL-pillar portfolio exists, use it. If none exists, propose creating one named "Employee Experience" (pillar: INTERNAL) — explain why: the onboarding structure needs a home, and employee experience is a real investment segment. Create via tacit_pyramid_create_portfolio after user confirms.\n\n3. STRATEGIC OKRs — Explain conceptually (no creation). These anchor portfolios to measurable outcomes — "Which 2-3 numbers define success this year?"\n\n4. VALUE STREAM — What an identifiable group receives end-to-end. Passes the customer-receipt test: "Does a customer/employee group receive something through this?" Internal VS use experience qualities, not function names (Operations → Operational Excellence, HR → People & Culture, IT → Digital Workplace). Call tacit_pyramid_list_value_streams to check for an existing "Onboarding" VS (case-insensitive name match). If found, show it and explain it is shared across all users. If not found, propose creating "Onboarding" under the INTERNAL portfolio via tacit_pyramid_create_value_stream. Create after user confirms.\n\n5. PROGRAM — A bounded push with an end state. Passes the end-date test: "Does it have an end state?" If it can never end, it is a stream, not a program. Call tacit_get_myself to get the user\'s name. Call tacit_pyramid_list_programs with the INTERNAL portfolio_id and filter results by value_stream_id matching the Onboarding VS. If a program matching "{Name}\'s Onboarding Journey" exists, reuse it. Otherwise propose creating it via tacit_pyramid_create_program with value_stream_id linking it to the Onboarding VS. Create after user confirms.\n\n6. DOSSIER + ARTIFACT — Explain conceptually only. Dossiers hold the actual work products (artifacts). As the user progresses through the remaining onboarding experiences, each experience that produces saveable content will create a dossier within their program and save its output there. The pyramid fills with real content as they learn — no need to create anything now.\n\n7. Show the structural chain built so far: Workspace → Portfolio → Value Stream → Program. Explain that Dossiers and Artifacts accumulate naturally as they continue through the onboarding experiences.\n\nIMPORTANT: All create operations (steps 2, 4, 5) require a one-line proposal and user confirmation before executing. If the workspace autonomy level blocks a create call, fall back to conceptual-only explanation for that step. Each step checks for existing entities by name before creating (idempotent — handles retries and resumed sessions). The "Onboarding" VS is shared across users; each user gets their own program ("{Name}\'s Onboarding Journey"). This teaches the shared-vs-personal scope distinction organically.', signal: 'User understands the full pyramid chain (Workspace → Portfolio → VS → Program → Dossier → Artifact) with their own onboarding structure as the example', tip: 'Each level has a naming test: Portfolios pass the board-slide test, Value Streams pass the customer-receipt test, Programs pass the end-date test. Functions (Engineering, Marketing, HR) are never portfolios or value streams.' },
268
+ { id: 'your_first_structure', num: 4, name: 'Your First Structure', tier: 1, tierName: 'Orient & Equip', action: 'Teach the alignment pyramid using the user\'s own onboarding as a live example. Walk through each level top-down:\n\n1. WORKSPACE — Point at it. This is the tenant boundary — the company itself.\n\n2. PORTFOLIO — Explain the three-pillar model: BUSINESS (company-wide strategic decisions — governance, brand, capital allocation), PRODUCT (product and service delivery — what external customers receive), INTERNAL (employee experience excellence — what employees receive to do their best work). Personal/career workspaces also have ATHLETIC (individual growth). Each portfolio passes the board-slide test: "Would a board split investment across these?" Call tacit_pyramid_list_portfolios to show existing portfolios. If an INTERNAL-pillar portfolio exists, use it. If none exists, propose creating one named "Employee Experience" (pillar: INTERNAL) — explain why: the onboarding structure needs a home, and employee experience is a real investment segment. Create via tacit_pyramid_create_portfolio after user confirms.\n\n3. STRATEGIC OKRs — These are a real, functional layer of the alignment pyramid, not just a concept. Objectives and Key Results anchor each portfolio to measurable outcomes — "Which 2-3 numbers define success this year?" Each portfolio should have 2-3 Objectives; each Objective has Key Results with measurable targets. OKRs bridge the gap between investment segments (portfolios) and the work streams (value streams) that deliver against them. OKR creation is available through the alignment interface — during onboarding, explain how they fit and why they matter, and note the user can set them up after onboarding.\n\n4. VALUE STREAM — What an identifiable group receives end-to-end. Passes the customer-receipt test: "Does a customer/employee group receive something through this?" Internal VS use experience qualities, not function names (Operations → Operational Excellence, HR → People & Culture, IT → Digital Workplace). Call tacit_pyramid_list_value_streams to check for an existing "Onboarding" VS (case-insensitive name match). If found, show it and explain it is shared across all users. If not found, propose creating "Onboarding" under the INTERNAL portfolio via tacit_pyramid_create_value_stream. Create after user confirms.\n\n5. PROGRAM — A bounded push with an end state. Passes the end-date test: "Does it have an end state?" If it can never end, it is a stream, not a program. Use the user_name field from this tool response to get the user\'s name (do NOT call tacit_get_myself — the onboarding tool already looked it up for you). If user_name is missing, ask the user their name directly — never guess from folder names, workspace member lists, or other context. Call tacit_pyramid_list_programs with the INTERNAL portfolio_id and filter results by value_stream_id matching the Onboarding VS. If a program matching "{Name}\'s Onboarding Journey" exists, reuse it. Otherwise propose creating it via tacit_pyramid_create_program with value_stream_id linking it to the Onboarding VS. Create after user confirms.\n\n6. DOSSIER + ARTIFACT — Explain conceptually only. Dossiers hold the actual work products (artifacts). As the user progresses through the remaining onboarding experiences, each experience that produces saveable content will create a dossier within their program and save its output there. The pyramid fills with real content as they learn — no need to create anything now.\n\n7. Show the structural chain built so far: Workspace → Portfolio → Value Stream → Program. Explain that Dossiers and Artifacts accumulate naturally as they continue through the onboarding experiences.\n\nIMPORTANT: All create operations (steps 2, 4, 5) require a one-line proposal and user confirmation before executing. If the workspace autonomy level blocks a create call, fall back to conceptual-only explanation for that step. Each step checks for existing entities by name before creating (idempotent — handles retries and resumed sessions). The "Onboarding" VS is shared across users; each user gets their own program ("{Name}\'s Onboarding Journey"). This teaches the shared-vs-personal scope distinction organically.', signal: 'User understands the full pyramid chain (Workspace → Portfolio → VS → Program → Dossier → Artifact) with their own onboarding structure as the example', tip: 'Each level has a naming test: Portfolios pass the board-slide test, Value Streams pass the customer-receipt test, Programs pass the end-date test. Functions (Engineering, Marketing, HR) are never portfolios or value streams.' },
269
269
  { id: 'build_your_map', num: 5, name: 'Build Your Map', tier: 1, tierName: 'Orient & Equip', action: 'This experience adapts to the workspace state. First, detect what exists:\n\n1. Call tacit_pyramid_list_portfolios to get all portfolios.\n2. For each portfolio, call tacit_pyramid_list_programs(portfolio_id) to aggregate programs.\n3. Call tacit_pyramid_list_value_streams to get all value streams.\n4. Exclude onboarding scaffolding when counting: ignore programs matching "*Onboarding Journey" and value streams named "Onboarding". Never exclude a portfolio — even if its only VS is "Onboarding", it represents a real investment segment.\n5. Count the remaining "real" programs and value streams.\n\nBRANCH A — EMPTY WORKSPACE (zero real programs AND zero real value streams after excluding onboarding scaffolding):\nRun the setup interview to build the user\'s actual pyramid. First, check existing portfolios by pillar — if Experience 4 or a prior session already created portfolios (e.g. an INTERNAL "Employee Experience"), adopt them per pillar. Do not duplicate. Ask whether each existing name fits or should be renamed. Then ask these questions one at a time:\n\n(1) "What do customers pay you for today?" → Distinct offerings become Value Streams inside a PRODUCT portfolio.\n(2) "What company-wide strategic decisions govern how you invest across everything?" → A BUSINESS portfolio covering governance, brand, capital allocation.\n(3) "What experience qualities do your employees receive that enable them to deliver?" → An INTERNAL portfolio covering employee experience excellence.\n(4) "What must stay true no matter what you are currently working on?" → The Knowledge Base: stream categories for offering truth, domain categories for cross-stream truth.\n(5) "Which 2-3 numbers define success this year?" → Strategic Objectives and Key Results at portfolio level, then VS Objectives that ladder up.\n(6) "What are you driving to done in the next 12 months?" → These become Programs.\n\nCreate real entities across all three pillars (BUSINESS, PRODUCT, INTERNAL). Validate every name against the four naming tests: board-slide (portfolio), customer-receipt (value stream), end-date (program), matrix/function-detection (should it be a domain category instead?). Functions like Engineering, Marketing, HR, Finance are NEVER portfolios or value streams — they describe how work gets done, not investment segments or offerings.\n\nBRANCH B — POPULATED WORKSPACE (any real programs OR real value streams exist after excluding onboarding scaffolding — i.e. NOT Branch A):\nShow what is already there — list all portfolios, value streams, programs, and dossiers. Explain each entity using the same definitions taught in Experience 4. Then run an audit/review against the setup interview questions, reframed as review questions:\n\n- "Does your portfolio structure cover all three pillars (BUSINESS, PRODUCT, INTERNAL)?"\n- "Do your value streams pass the customer-receipt test? Are any named after functions instead of what people receive?"\n- "Do your programs pass the end-date test? Are any immortal (never-ending)?"\n- "Are there functions masquerading as portfolios or value streams?" (the org-chart anti-pattern)\n- Identify gaps: missing pillars, orphan programs not linked to a value stream, function-named entities, flat pyramid (everything in one program).\n\nPresent findings as suggestions, not directives. Offer to help fix any issues found.', signal: 'User has either built their real pyramid structure (Branch A) or reviewed and validated their existing structure (Branch B)', tip: 'Three pillars: BUSINESS (where to invest), PRODUCT (what customers receive), INTERNAL (what employees receive). Every name has a test — if it fails, it belongs on a different tier.' },
270
- { id: 'connect_your_tools', num: 6, name: 'Connect Your Tools', tier: 1, tierName: 'Orient & Equip', action: 'First, CHECK what is already connected before telling the user anything: (1) Call tacit_github_list_connections to see GitHub repo connections. (2) Check your available MCP tool list — if you have Gmail tools (mcp__claude_ai_Gmail__*), Gmail IS connected. If you have Slack tools (mcp__plugin_*_slack__*), Slack IS connected. If you have Google Calendar tools, Calendar IS connected. If you have Google Drive tools, Drive IS connected. Present a CONNECTION STATUS showing what is already active and what is not. For anything already connected, say "Already connected — ready to use." For anything not connected, explain how to connect it via claude.ai Settings → Integrations. Also show GitHub workspace connections from step 1. Do NOT say a tool is disconnected if you can see its MCP tools in your available tool list. WAIT for the user to either connect something new or confirm they want to move on.', signal: 'User knows their connection status and has either connected new tools or confirmed they are ready to proceed', tip: 'GitHub connections sync your repos into the workspace. Gmail and Slack power the Morning Brief. Google Drive lets you pull in documents directly.' },
271
- { id: 'research_publish', num: 7, name: 'Research & Publish', tier: 2, tierName: 'The Operating System', action: 'Research a topic and publish a report. Ask the user what they want to research, or suggest a topic relevant to their business. Then: (1) Call tacit_research_prepare with the topic as the query. This runs two research lanes in parallel: a workspace lane (KB, pyramid, lake) and an academic lane (arXiv, OpenAlex, Semantic Scholar). The response includes research_lanes[] — each lane has a status and results array with source attribution. Use ALL results from both lanes. If the academic lane status is "partial", some providers returned results while others hit rate limits — use what came back. If "failed", note it and continue with workspace results. (2) Search the web for current information to complement the workspace and academic findings. (3) Combine ALL findings — workspace knowledge, academic papers, and web results — into a STYLED HTML REPORT using /artifact-design — invoke the artifact-design skill to get the design system, then build a proper HTML artifact with title, date, executive summary, sections with findings, citations, and a professional layout. Academic sources should be cited with author, title, and link. Publish it as a Claude artifact so the user sees it in their browser. Save the HTML file to disk. (4) After the artifact is saved, ingest the HTML FILE into TACIT via tacit_gm_ingest — pass the file path, not the content. The GM classifies and proposes placement. The user approves before anything moves. IMPORTANT: Do NOT copy-paste the report content into tacit_artifact_create. The correct flow is: create the HTML file → publish as Claude artifact → ingest the file via GM. This preserves provenance and goes through the lake-first pipeline.\n\nFILE SAVE PATH: Save the HTML file to ~/tacit-reports/ (inside the user home directory), NOT to the scratchpad. TACIT can only read files under the user home directory. After saving, pass the ~/tacit-reports/ path to tacit_gm_ingest.\n\nONBOARDING PLACEMENT DEFAULT: If the user reached this experience through onboarding (the completed set includes your_first_structure), default to placing the output in their onboarding program. Look up the program: call tacit_pyramid_list_value_streams, find the "Onboarding" VS, then call tacit_pyramid_list_programs filtered by that VS id to find their "{Name}\'s Onboarding Journey" program. When the GM proposes placement, suggest this program as the target — e.g. "I\'ll file this under your onboarding program ({Name}\'s Onboarding Journey). Approve?" The user can override to a different location, but the onboarding program is the default during onboarding.', signal: 'First research artifact published as a Claude artifact in the browser with workspace, academic, and web sources, then the HTML file ingested and placed via GM workflow', tip: 'After publishing, your General Manager will propose where to place the report in your knowledge structure — you approve the placement.' },
270
+ { id: 'connect_your_tools', num: 6, name: 'Connect Your Tools', tier: 1, tierName: 'Orient & Equip', action: 'First, CHECK what is already connected before telling the user anything: (1) Call tacit_github_list_connections to see GitHub repo connections. (2) Check your available MCP tool list to determine connection status. IMPORTANT — there are four states, not two:\n\n- FULLY CONNECTED: You see data tools (search, list, get, send, read, etc.). Examples: mcp__claude_ai_Gmail__search_threads, mcp__claude_ai_Google_Drive__search_files, mcp__plugin_*_slack__*. Say "Connected — ready to use."\n- NEEDS AUTHENTICATION: You ONLY see authenticate/complete_authentication tools — NO data tools. This means the integration is installed but the user has not completed the OAuth sign-in. Say "Installed but needs sign-in. Open claude.ai Settings → Integrations → [service name] to complete setup."\n- PERMISSION-RESTRICTED: You see data tools but they return permission errors when called. Say "Connected — may need permissions approved. Open claude.ai Settings → Integrations → [service name] to review permissions."\n- NOT INSTALLED: No tools with that service name at all. Say "Not connected. Open claude.ai Settings → Integrations to add it."\n\nCheck for each service: Gmail (mcp__claude_ai_Gmail__*), Google Drive (mcp__claude_ai_Google_Drive__*), Google Calendar (mcp__claude_ai_Google_Calendar__*), Slack (mcp__plugin_*_slack__*). Present a CONNECTION STATUS table. Also show GitHub workspace connections from step 1.\n\nTACIT WORKSPACE DATA: Before showing external connections, check what data already lives in TACIT itself. Call tacit_chronicle_search or tacit_search to see if the workspace has existing content (meeting notes from /capture, artifacts, KB articles, chronicle events). Present this FIRST as "Workspace data" — e.g. "Your workspace already has meeting notes, artifacts, and chronicle events from previous sessions. These are always available regardless of external integrations." Meeting notes in TACIT come from the capture system (tacit_capture_*), NOT from Google Calendar — do not conflate the two.\n\nWAIT for the user to either connect something new or confirm they want to move on.', signal: 'User knows their connection status and has either connected new tools or confirmed they are ready to proceed', tip: 'GitHub connections sync your repos into the workspace. Gmail and Slack power the Morning Brief. Google Drive lets you pull in documents directly.' },
271
+ { id: 'research_publish', num: 7, name: 'Research & Publish', tier: 2, tierName: 'The Operating System', action: 'Research a topic and publish a report. Ask the user what they want to research, or suggest a topic relevant to their business. Then: (1) Call tacit_research_prepare with the topic as the query. This runs two research lanes in parallel: a workspace lane (KB, pyramid, lake) and an academic lane (arXiv, OpenAlex, Semantic Scholar). The response includes research_lanes[] — each lane has a status and results array with source attribution. Use ALL results from both lanes. If the academic lane status is "partial", some providers returned results while others hit rate limits — use what came back. If "failed", note it and continue with workspace results. (2) Search the web for current information to complement the workspace and academic findings. (3) Combine ALL findings — workspace knowledge, academic papers, and web results — into a STYLED HTML REPORT using /artifact-design — invoke the artifact-design skill to get the design system, then build a proper HTML artifact with title, date, executive summary, sections with findings, citations, and a professional layout. Academic sources should be cited with author, title, and link. Publish it as a Claude artifact so the user sees it in their browser. Save the HTML file to disk. (4) After the artifact is saved, ingest the HTML FILE into TACIT via tacit_gm_ingest — pass the file path, not the content. The GM classifies and proposes placement. The user approves before anything moves. IMPORTANT: Do NOT copy-paste the report content into tacit_artifact_create. The correct flow is: create the HTML file → publish as Claude artifact → ingest the file via GM. This preserves provenance and goes through the lake-first pipeline.\n\nFILE SAVE PATH: Save the HTML file to a tacit-reports/ folder inside the current working directory (the project folder). Create the folder if it does not exist. tacit_gm_ingest can ONLY read files inside the project folder (or directories listed in TACIT_MCP_FILE_ROOTS) — files outside, such as ~/tacit-reports/, will be rejected. After saving, pass the project-relative path to tacit_gm_ingest.\n\nONBOARDING PLACEMENT DEFAULT: If the user reached this experience through onboarding (the completed set includes your_first_structure), default to placing the output in their onboarding program. Look up the program: call tacit_pyramid_list_value_streams, find the "Onboarding" VS, then call tacit_pyramid_list_programs filtered by that VS id to find their "{Name}\'s Onboarding Journey" program. When the GM proposes placement, suggest this program as the target — e.g. "I\'ll file this under your onboarding program ({Name}\'s Onboarding Journey). Approve?" The user can override to a different location, but the onboarding program is the default during onboarding.', signal: 'First research artifact published as a Claude artifact in the browser with workspace, academic, and web sources, then the HTML file ingested and placed via GM workflow', tip: 'After publishing, your General Manager will propose where to place the report in your knowledge structure — you approve the placement.' },
272
272
  { id: 'run_sales', num: 8, name: 'Run Sales', tier: 2, tierName: 'The Operating System', action: 'Part 1 — Discovery Brief: Say "Prepare a discovery brief for a potential client." TACIT uses workspace knowledge to build a discovery framework. The brief should be a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk, then ingest the HTML file via tacit_gm_ingest for placement. ONBOARDING PLACEMENT DEFAULT: If the user reached this experience through onboarding (the completed set includes your_first_structure), default to placing the output in their onboarding program — look up the "Onboarding" VS via tacit_pyramid_list_value_streams, then find their "{Name}\'s Onboarding Journey" program via tacit_pyramid_list_programs filtered by that VS. Propose this program as the target; the user can override. Part 2 — Voice Composition: After the brief, draft an intro email using the TACIT Voice Resonance system. MANDATORY TWO-STEP FLOW: (1) GROUND FIRST — assemble the key facts from the discovery brief (prospect name, pain points, value proposition, relevant capabilities) into a structured plain-text brief. This is the content the voice system will work with. (2) COMPOSE IN VOICE — call tacit_voice_list_profiles to find the user\'s voice profile (it MUST exist — voice samples were pre-loaded). Then call tacit_compose_in_voice, passing the grounded-facts brief as the `content` argument (the instruction goes in `query`). This ensures the voice system has concrete facts instead of re-retrieving from workspace docs. This uses TACIT\'s actual voice fingerprinting system, NOT LLM approximation. NEVER draft the email yourself and claim it matches the user\'s voice. NEVER offer to "paste a sample email" or "upload writing samples" — voice profiles are already loaded. If tacit_voice_list_profiles returns no profiles, say "I expected to find your voice profile but it is not set up yet — let me check with the team" and move on.\n\nGROUNDING ENFORCEMENT: NEVER fabricate people names, meeting dates, verbatim quotes, financial figures, or technical specifications. Every claim in the discovery brief and email must be grounded in workspace data returned by TACIT tools. If the workspace has thin data on the prospect, produce an honest thin brief — state what is known, flag what is missing, and suggest how to fill the gaps. A short, honest brief is always better than a fabricated detailed one.', signal: 'First sales deliverable as HTML report, then first voice-matched composition using TACIT Voice Resonance (not LLM approximation)', tip: 'Voice Resonance is a real system — it analyzes your writing samples to capture your cadence, vocabulary, and patterns. Every "in my voice" request routes through this system.' },
273
273
  { id: 'morning_brief', num: 9, name: 'Morning Brief', tier: 2, tierName: 'The Operating System', action: 'IMPORTANT — CONNECTOR DETECTION: Before running the brief, CHECK your available MCP tool list to determine what is connected. Gmail IS connected if you have mcp__claude_ai_Gmail__* tools available. Slack IS connected if you have mcp__plugin_*_slack__* tools. Calendar IS connected if you have mcp__claude_ai_Google_Calendar__* tools. Do NOT say "Gmail not connected" if you can see Gmail MCP tools — that is a false negative.\n\nSCOPE CHECK: After detecting connected tools, verify each connector belongs to the same organization as the workspace. If Slack channels or Gmail accounts reference a different company than the workspace name, exclude that connector data and explain why — say "Your connected [tool] appears to belong to a different organization than [workspace name]. That data has been excluded to maintain workspace isolation." Only include connector data from the workspace-matched organization.\n\nRun the COS daily brief: gather workspace state (programs, deadlines, proposals, KB freshness), and for each connected tool, pull real data — Gmail threads, Slack channels, Calendar events. Present the full operating picture. If a connector genuinely has no MCP tools available, say "not yet connected" and explain how to connect via claude.ai Integrations. After the brief, offer to draft a team message in the user\'s voice. TWO-STEP VOICE FLOW (mandatory): (1) GROUND FIRST — assemble a structured brief of the key facts, numbers, and updates you gathered from the morning brief (programs, deadlines, email highlights, meeting items). Write this as plain text with concrete data points. (2) COMPOSE IN VOICE — call tacit_compose_in_voice, passing the grounded-facts brief as the `content` argument (the instruction goes in `query`). This ensures the voice system has verified facts to work with instead of re-retrieving from workspace documents (which cannot see the live MCP query results you just gathered). NEVER skip step 1 and call tacit_compose_in_voice with just "draft a team update" — the voice system cannot access the live data you collected.', signal: 'First daily operating picture with accurate connector status and real data from connected tools', tip: 'Meet your executive team. COS (Chief of Staff — daily ops, email, meetings), COO (Chief Operating Officer — business ops, sales, audits), GM (General Manager — content ingestion, classification, pyramid placement). Address them by name to route through their workflow.' },
274
274
  { id: 'business_pulse', num: 10, name: 'Your Business Pulse', tier: 2, tierName: 'The Operating System', action: 'Show the user what TACIT can see about their business right now. Ask "Want to see your business pulse?" Then: (1) Gather workspace data — call tacit_pyramid_list_portfolios, tacit_pyramid_list_programs, tacit_pyramid_list_value_streams to assess structure completeness. Call tacit_kb_freshness to check knowledge currency. Call tacit_lake_browse_catalog to gauge content volume. Check connector status from the MCP tool list (Gmail, Slack, Calendar, Drive, GitHub). Call tacit_voice_list_profiles to check voice readiness. (2) Score each dimension (structure completeness, knowledge freshness, content depth, tool connectivity, voice readiness) and produce a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk. The report should include dimension scores, a summary health grade, and concrete recommendations for what to build next. Frame it as a health snapshot, not a formal audit. (3) After the artifact is saved, ingest the HTML file via tacit_gm_ingest for placement. ONBOARDING PLACEMENT DEFAULT: If the user reached this experience through onboarding (the completed set includes your_first_structure), default to placing the output in their onboarding program — look up the "Onboarding" VS via tacit_pyramid_list_value_streams, then find their "{Name}\'s Onboarding Journey" program via tacit_pyramid_list_programs filtered by that VS. Propose this program as the target; the user can override.', signal: 'First business pulse report published as a Claude artifact showing workspace health scores, then filed via GM workflow', tip: 'This is your quick health snapshot. When you want the deep version, say "Have COO audit our business" — COO runs the formal operational review with remediation tracking.' },
@@ -291,7 +291,7 @@ function buildScript(role, workflowType = role.workflow_type, workspaceId) {
291
291
  steps.push('1. Call tacit_voice_list_profiles and confirm a profile with voice_active true exists. If none exists, tell the user a voice profile needs 3+ samples and stop.');
292
292
  steps.push('2. Assemble the grounded source text yourself (the draft, letter or facts to rewrite). Do not invent facts.');
293
293
  steps.push('3. Call tacit_compose_in_voice with the grounded text in `content` and the instruction in `query`. Omit `content` only for KB-grounded drafts.');
294
- steps.push('4. If the result has voice_match_degraded true, or the tool returns an error, show the user and stop for review. Never draft text yourself and claim it matches their voice.');
294
+ steps.push('4. If the result has voice_match_degraded true, or the tool returns an error, show the user the raw identity_similarity score and stop for review. Do NOT guess why voice matching failed — do not blame sample count, do not suggest "adding more samples would help" unless you verified the profile has fewer than 10. Report only: "Voice matching returned degraded (similarity: X.XX). The draft may not match your writing style. Review it before using." Never draft text yourself and claim it matches their voice.');
295
295
  return steps;
296
296
  }
297
297
  if (workflowType === 'gm_content_removal') {
@@ -489,6 +489,23 @@ export declare function handleWriteback(args: unknown): Promise<{
489
489
  }>;
490
490
  isError?: boolean;
491
491
  }>;
492
+ export declare const CATALOG_STATS_TOOL_DEF: {
493
+ name: "tacit_lake_catalog_stats";
494
+ description: string;
495
+ inputSchema: {
496
+ type: "object";
497
+ properties: {};
498
+ required: string[];
499
+ };
500
+ };
501
+ export declare function buildCatalogStatsRequest(client: TacitClient): ToolRequest;
502
+ export declare function handleCatalogStats(): Promise<{
503
+ content: Array<{
504
+ type: 'text';
505
+ text: string;
506
+ }>;
507
+ isError?: boolean;
508
+ }>;
492
509
  export declare const browseCatalogInputSchema: z.ZodObject<{
493
510
  limit: z.ZodOptional<z.ZodNumber>;
494
511
  offset: z.ZodOptional<z.ZodNumber>;
@@ -516,6 +516,32 @@ export async function handleWriteback(args) {
516
516
  }
517
517
  return buildWritebackRequest(getClient(), parsed.data).execute();
518
518
  }
519
+ // ─── tacit_lake_catalog_stats ────────────────────────────────────────────────
520
+ export const CATALOG_STATS_TOOL_DEF = {
521
+ name: 'tacit_lake_catalog_stats',
522
+ description: 'Get data lake catalog counts: total items, breakdown by origin and status, source counts. Lightweight — no pagination needed. Route: GET /api/v1/org/lake/catalog/stats.',
523
+ inputSchema: {
524
+ type: 'object',
525
+ properties: {},
526
+ required: [],
527
+ },
528
+ };
529
+ export function buildCatalogStatsRequest(client) {
530
+ return {
531
+ async execute() {
532
+ try {
533
+ const result = await client.get('/api/v1/org/lake/catalog/stats', {});
534
+ return { content: [{ type: 'text', text: JSON.stringify(result) }] };
535
+ }
536
+ catch (err) {
537
+ return apiErrorResult(err, 'tacit_lake_catalog_stats');
538
+ }
539
+ },
540
+ };
541
+ }
542
+ export async function handleCatalogStats() {
543
+ return buildCatalogStatsRequest(getClient()).execute();
544
+ }
519
545
  // ─── tacit_lake_browse_catalog ───────────────────────────────────────────────
520
546
  export const browseCatalogInputSchema = z.object({
521
547
  limit: z.number().optional().describe('Max items to return'),
@@ -1064,6 +1090,10 @@ export function registerLakeTools(server, getClientFn) {
1064
1090
  const client = await getClientFn();
1065
1091
  return buildWritebackRequest(client, args).execute();
1066
1092
  });
1093
+ server.tool('tacit_lake_catalog_stats', CATALOG_STATS_TOOL_DEF.description, {}, async () => {
1094
+ const client = await getClientFn();
1095
+ return buildCatalogStatsRequest(client).execute();
1096
+ });
1067
1097
  server.tool('tacit_lake_browse_catalog', BROWSE_CATALOG_TOOL_DEF.description, browseCatalogInputSchema.shape, async (args) => {
1068
1098
  const client = await getClientFn();
1069
1099
  return buildBrowseCatalogRequest(client, args).execute();
@@ -1,7 +1,17 @@
1
1
  import { z } from 'zod';
2
2
  import { TacitApiError, TokenExpiredError } from '../client.js';
3
3
  import { success, error, featureDisabledResult } from './errors.js';
4
- import { EXPERIENCES, fetchWorkspaceState, normalizeCompleted } from '../prompts.js';
4
+ import { EXPERIENCES, CAPABILITY_DOMAINS, fetchWorkspaceState, normalizeCompleted } from '../prompts.js';
5
+ function formatCapabilityDomains() {
6
+ const lines = ['', '### Capability Domains', ''];
7
+ for (const d of CAPABILITY_DOMAINS) {
8
+ lines.push(`**${d.domain}** — ${d.description}`);
9
+ lines.push(` Try: ${d.triggers.join(' · ')}`);
10
+ lines.push('');
11
+ }
12
+ lines.push(`${CAPABILITY_DOMAINS.length} capability domains total.`);
13
+ return lines.join('\n');
14
+ }
5
15
  export function registerOnboardingTools(server, getClient) {
6
16
  server.tool('tacit_onboarding', 'Guide the user through the TACIT onboarding journey — the Eleven Experiences. ' +
7
17
  'ONLY call this when the user explicitly asks for onboarding: "onboard me", "take me through onboarding", ' +
@@ -23,6 +33,14 @@ export function registerOnboardingTools(server, getClient) {
23
33
  try {
24
34
  const client = await getClient();
25
35
  const state = await fetchWorkspaceState(client);
36
+ let userName;
37
+ try {
38
+ const me = await client.request('GET', '/api/v1/people/myself');
39
+ userName = me?.display_name || me?.name || undefined;
40
+ }
41
+ catch {
42
+ // person record may not exist — proceed without it
43
+ }
26
44
  const completedIds = normalizeCompleted(args.completed || '');
27
45
  const completedSet = new Set(completedIds);
28
46
  const tier1 = EXPERIENCES.filter(e => e.tier === 1);
@@ -50,15 +68,21 @@ export function registerOnboardingTools(server, getClient) {
50
68
  }
51
69
  }
52
70
  const lines = [];
53
- lines.push(`## Onboarding: ${state.name}`);
71
+ const greeting = userName
72
+ ? `## Welcome, ${userName} — Onboarding: ${state.name}`
73
+ : `## Onboarding: ${state.name}`;
74
+ lines.push(greeting);
54
75
  if (state.description) {
55
76
  lines.push(`*${state.description}*`);
56
77
  }
57
78
  lines.push('');
58
79
  lines.push(`Progress: ${completedIds.length} of ${EXPERIENCES.length} experiences complete.`);
59
80
  lines.push('');
60
- lines.push('⚠️ **Account notice:** Your claude.ai session may be associated with a different account than this workspace. Artifacts you create will publish to your personal claude.ai account. If this is not what you want, switch accounts before continuing to Experience 7.');
61
- lines.push('');
81
+ const pubExperiences = new Set(['research_publish', 'morning_brief', 'delegate_to_crew', 'build_your_voice', 'daily_operating_rhythm']);
82
+ if (next && pubExperiences.has(next.id)) {
83
+ lines.push('⚠️ **Account notice:** This experience publishes artifacts to your claude.ai account. If your claude.ai login is a different account than this workspace owner, those artifacts will go to your personal account. To switch: close this Claude Code session, sign into the correct claude.ai account in your browser, then start a new Claude Code session.');
84
+ lines.push('');
85
+ }
62
86
  if (!next) {
63
87
  lines.push('All eleven experiences complete — you are a TACIT power user.');
64
88
  lines.push('');
@@ -73,6 +97,9 @@ export function registerOnboardingTools(server, getClient) {
73
97
  lines.push(`*${next.tierName}*`);
74
98
  lines.push('');
75
99
  lines.push(next.action);
100
+ if (next.id === 'see_capabilities') {
101
+ lines.push(formatCapabilityDomains());
102
+ }
76
103
  lines.push('');
77
104
  if (next.tip) {
78
105
  lines.push(`💡 **Tip:** ${next.tip}`);
@@ -100,7 +127,11 @@ export function registerOnboardingTools(server, getClient) {
100
127
  status: 'in_progress',
101
128
  completed: completedIds.length,
102
129
  total: EXPERIENCES.length,
103
- next_experience: { id: next.id, num: next.num, name: next.name, tier: next.tier, action: next.action },
130
+ ...(userName ? { user_name: userName } : {}),
131
+ next_experience: {
132
+ id: next.id, num: next.num, name: next.name, tier: next.tier, action: next.action,
133
+ ...(next.id === 'see_capabilities' ? { capability_domains: CAPABILITY_DOMAINS } : {}),
134
+ },
104
135
  });
105
136
  }
106
137
  catch (e) {
@@ -77,6 +77,7 @@ const READ_TOOLS = [
77
77
  'tacit_kb_list_categories',
78
78
  'tacit_kb_list_collections',
79
79
  'tacit_lake_browse_catalog',
80
+ 'tacit_lake_catalog_stats',
80
81
  'tacit_lake_catalog_detail',
81
82
  'tacit_lake_folder_list',
82
83
  'tacit_lake_list_proposals',
package/package.json CHANGED
@@ -1,7 +1,6 @@
1
1
  {
2
2
  "name": "@tacitai/mcp-server",
3
- "version": "0.9.3",
4
- "private": false,
3
+ "version": "0.9.5",
5
4
  "description": "stdio MCP server wrapping Tacit /api/v1 REST/SSE API",
6
5
  "license": "UNLICENSED",
7
6
  "repository": {