@tacitai/mcp-server 0.6.50 → 0.6.53

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.
@@ -103,3 +103,25 @@ roles:
103
103
  - structure_proposals
104
104
  workflow_types:
105
105
  - lake_operations
106
+
107
+ - slug: access_administrator
108
+ display_name: Access Administrator
109
+ description: Manages workspace membership, role assignments, and capability denials via IAM tools.
110
+ icon: shield
111
+ default_capabilities:
112
+ - iam_membership
113
+ - iam_role_management
114
+ - iam_denial_management
115
+ workflow_types:
116
+ - iam_membership_ops
117
+
118
+ - slug: security_officer
119
+ display_name: Security Officer
120
+ description: Manages credential inventory, rotation tracking, and T3 approval workflows.
121
+ icon: lock
122
+ default_capabilities:
123
+ - secret_inventory
124
+ - rotation_tracking
125
+ - t3_approval
126
+ workflow_types:
127
+ - security_audit
package/dist/index.js CHANGED
@@ -57,6 +57,7 @@ import { registerPeopleTools } from './tools/people.js';
57
57
  import { registerLakeStructureTools } from './tools/lake-structure.js';
58
58
  import { registerResearchTools } from './tools/research.js';
59
59
  import { registerGmTools } from './tools/gm.js';
60
+ import { registerCaptureTools } from './tools/capture.js';
60
61
  import { registerSkillTools } from './tools/skills.js';
61
62
  import { registerWikiTools } from './tools/wiki.js';
62
63
  import { registerVoiceTools } from './tools/voice.js';
@@ -65,6 +66,8 @@ import { registerWorkflowTools } from './tools/workflow.js';
65
66
  import { registerWorkflowTypeTools } from './tools/workflow-types.js';
66
67
  import { registerWorkflowPrereqsTool } from './tools/workflow-prereqs.js';
67
68
  import { registerCmoTools } from './tools/cmo.js';
69
+ import { registerSecretaryTools } from './tools/secretary.js';
70
+ import { registerIamTools, registerSecurityTools } from './tools/iam.js';
68
71
  import { registerPrompts } from './prompts.js';
69
72
  import { getRequestPrincipal, ensureAutonomy, resolveProfileOptions } from './client.js';
70
73
  // Setup wizard (MV-1057h / W5)
@@ -123,6 +126,8 @@ const GUIDANCE_MAP = {
123
126
  WIKI_AUTHORING: 'Wiki authoring active. Follow: classify → validate → author. Write/override require approval.',
124
127
  KB_MANAGEMENT: 'KB management active. Browse the KB structure first, then curate content.',
125
128
  LAKE_OPERATIONS: 'Data lake operations active. Explore catalog first, then ingest/classify, then propose structure.',
129
+ CTO_ENGINEERING: 'CTO Engineering active. Routes engineering requests to sub-execs (Agentic Engineering Exec). Describe the engineering need.',
130
+ SECRETARY_CHRONICLE: 'Secretary active. Use tacit_secretary_log to record events, tacit_secretary_recall to search history.',
126
131
  };
127
132
  function expandGuidance(raw, _typeName, phase) {
128
133
  const expanded = GUIDANCE_MAP[raw];
@@ -295,6 +300,8 @@ async function run() {
295
300
  '- "research", "competitors", "SOTA", "survey" → researcher (or use tacit_research_prepare directly)',
296
301
  '- "wiki article", "publish to wiki" → wiki_editor',
297
302
  '- "knowledge base", "KB article", "organize knowledge" → kb_curator',
303
+ '- "new exec role", "role creation", "engineering architecture" → cto_engineer',
304
+ '- "log decision", "meeting notes", "action items", "decision history" → secretary',
298
305
  '- "data sources", "data lake", "classify", "taxonomy" → lake_operator',
299
306
  '',
300
307
  'HOW TO START:',
@@ -378,6 +385,7 @@ async function run() {
378
385
  registerPeopleTools(server, getClient);
379
386
  registerLakeStructureTools(server, getClient);
380
387
  registerGmTools(server, getClient, gate);
388
+ registerCaptureTools(server, getClient);
381
389
  registerResearchTools(server, getClient, getRequestPrincipal);
382
390
  registerSkillTools(server, getClient);
383
391
  registerWikiTools(server, getClient);
@@ -387,7 +395,12 @@ async function run() {
387
395
  registerWorkflowTypeTools(server, getClient, gate.getRegistry());
388
396
  registerWorkflowPrereqsTool(server, gate.getRegistry());
389
397
  registerCmoTools(server);
398
+ if (process.env['FEATURE_SECRETARY'] !== 'false') {
399
+ registerSecretaryTools(server, getClient);
400
+ }
390
401
  registerExecRouteTool(server);
402
+ registerIamTools(server, getClient);
403
+ registerSecurityTools(server, getClient);
391
404
  registerPrompts(server, getClient);
392
405
  if (process.env['MCP_TRANSPORT'] === 'http') {
393
406
  await startHttpTransport(server);
package/dist/prompts.d.ts CHANGED
@@ -3,6 +3,7 @@ import type { TacitClient } from './client.js';
3
3
  export declare const ASSISTANT_SYSTEM_PROMPT_STATIC: string;
4
4
  export interface WorkspaceState {
5
5
  name: string;
6
+ description?: string;
6
7
  collectionNames: string[];
7
8
  collectionCount: number;
8
9
  portfolioNames: string[];
@@ -121,7 +122,7 @@ export declare const EXPERIENCES: readonly [{
121
122
  readonly name: "Explore Your Workspace";
122
123
  readonly tier: 1;
123
124
  readonly tierName: "Orient & Equip";
124
- readonly action: "Type: \"What is in my workspace?\" — see what knowledge, collections, and structure are already here.";
125
+ readonly 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).";
125
126
  readonly signal: "You can describe what is in your workspace";
126
127
  readonly tip: "";
127
128
  }, {
@@ -130,7 +131,7 @@ export declare const EXPERIENCES: readonly [{
130
131
  readonly name: "See What's Possible";
131
132
  readonly tier: 1;
132
133
  readonly tierName: "Orient & Equip";
133
- readonly action: "Type: \"What can TACIT do for me?\" — discover the full range of capabilities available to you.";
134
+ readonly 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.";
134
135
  readonly signal: "You know what TACIT can do and are ready to try it";
135
136
  readonly tip: "";
136
137
  }, {
@@ -139,7 +140,7 @@ export declare const EXPERIENCES: readonly [{
139
140
  readonly name: "First Light";
140
141
  readonly tier: 1;
141
142
  readonly tierName: "Orient & Equip";
142
- readonly action: "Ask a question about your business — try \"What do we know about [topic]?\"";
143
+ readonly 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.";
143
144
  readonly signal: "First grounded answer drawn from your workspace knowledge";
144
145
  readonly tip: "";
145
146
  }, {
@@ -175,7 +176,7 @@ export declare const EXPERIENCES: readonly [{
175
176
  readonly name: "Research & Publish";
176
177
  readonly tier: 2;
177
178
  readonly tierName: "The Operating System";
178
- 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\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 ~/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
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";
180
181
  readonly tip: "After publishing, your General Manager will propose where to place the report in your knowledge structure — you approve the placement.";
181
182
  }, {
@@ -184,7 +185,7 @@ export declare const EXPERIENCES: readonly [{
184
185
  readonly name: "Run Sales";
185
186
  readonly tier: 2;
186
187
  readonly tierName: "The Operating System";
187
- readonly 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 to voice-ify. 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.";
188
+ readonly 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 to voice-ify. 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.";
188
189
  readonly signal: "First sales deliverable as HTML report, then first voice-matched composition using TACIT Voice Resonance (not LLM approximation)";
189
190
  readonly 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.";
190
191
  }, {
@@ -193,7 +194,7 @@ export declare const EXPERIENCES: readonly [{
193
194
  readonly name: "Morning Brief";
194
195
  readonly tier: 2;
195
196
  readonly tierName: "The Operating System";
196
- readonly 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. Run 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 to voice-ify. 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.";
197
+ readonly 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 to voice-ify. 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.";
197
198
  readonly signal: "First daily operating picture with accurate connector status and real data from connected tools";
198
199
  readonly 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.";
199
200
  }, {
@@ -211,7 +212,7 @@ export declare const EXPERIENCES: readonly [{
211
212
  readonly name: "Your Operating Rhythm";
212
213
  readonly tier: 3;
213
214
  readonly tierName: "Agentic Mastery";
214
- readonly action: "Summarize what the user has accomplished across the onboarding and suggest their operating rhythm. CONNECTOR STATUS: Check your available MCP tool list — if you have Gmail/Slack/Calendar/Drive MCP tools, those ARE connected. Do NOT say they are disconnected. VOICE: Call tacit_voice_list_profiles — if profiles exist, voice is ready. Do NOT ask the user to upload samples if profiles already exist. Focus on: (1) Daily rhythm — morning brief via COS, email triage, meeting prep. (2) Weekly rhythm — COO business review, GM content organization. (3) Delegation — crew dispatch for complex deliverables. (4) What to explore next based on what they have connected and used.";
215
+ readonly action: "Summarize what the user has accomplished across the onboarding and suggest their operating rhythm. CONNECTOR STATUS: Check your available MCP tool list — if you have Gmail/Slack/Calendar/Drive MCP tools, those ARE connected. Do NOT say they are disconnected. CONNECTOR SCOPE: If any connector belongs to a different organization than the workspace (e.g., Slack is from \"GoodOps\" but the workspace is \"Redwood Inference\"), note this in the operating rhythm summary and advise that connector data from a different organization will be excluded from briefs to maintain workspace isolation. VOICE: Call tacit_voice_list_profiles — if profiles exist, voice is ready. Do NOT ask the user to upload samples if profiles already exist. Focus on: (1) Daily rhythm — morning brief via COS, email triage, meeting prep. (2) Weekly rhythm — COO business review, GM content organization. (3) Delegation — crew dispatch for complex deliverables. (4) What to explore next based on what they have connected and used.";
215
216
  readonly signal: "User has a clear picture of their operating rhythm and next steps";
216
217
  readonly tip: "By now you know the team: COS for daily ops, COO for business operations, GM for content. Address them directly anytime.";
217
218
  }];
package/dist/prompts.js CHANGED
@@ -16,6 +16,7 @@ export function buildAssistantSystemPrompt(state) {
16
16
  lines.push(`- Warm but direct. You know ${name} well and you are here to help.`);
17
17
  lines.push('- Refer to the workspace by name. When citing answers, name the collection or source they came from.');
18
18
  lines.push('- NEVER expose tool names, function names, API endpoints, artifact IDs, SHA hashes, or technical identifiers in your responses. Translate everything into plain language the user would understand. Instead of "tacit_gm_approve" say "approve the placement." Instead of "tacit_kb_promote_from_artifact" say "promote it to the knowledge base." Instead of "crew_compose" say "draft." Instead of "kb_create_collection" say "create a new collection." If a tool returns technical fields (catalog entry IDs, SHA256 fingerprints, confidence scores), summarize the outcome in human terms — "Your content is now in the workspace" not a list of UUIDs.');
19
+ lines.push('- NEVER expose quality_score, ctx_recall, completeness_score, source_confirmation_rate, or any numeric retrieval quality metric to the user. These are internal diagnostics (ADR-175). Present answers confidently with source citations. If retrieval coverage is thin, say "This answer draws from a limited set of workspace documents" without numbers.');
19
20
  lines.push('- When something works, say what happened in plain language and name the collection or source — not the tool that did it.');
20
21
  lines.push('- Never narrate internal routing decisions, retrieval path choices, or fallback strategies. If one approach does not return results, silently try another. The user should see the answer, not the search process.');
21
22
  lines.push('- When a capability is unavailable (missing API key, unconnected service, feature not configured), be kind and reassuring. Say what you CAN do, not what is broken. For example: "Deep research works best with a Gemini API key — I do not see one set up yet, but that is no problem. I have great research tools built in, so let me use those today." Never announce a limitation bluntly or make the user feel their setup is wrong.');
@@ -30,10 +31,30 @@ export function buildAssistantSystemPrompt(state) {
30
31
  lines.push('- GitHub connections: call tacit_github_list_connections to check workspace repo connections');
31
32
  lines.push('If a tool is in your available tool list, it IS connected. Do NOT tell the user to "connect" something that is already connected. When presenting connector status, check your tool list first.');
32
33
  lines.push('');
34
+ lines.push('## Account-workspace alignment (MANDATORY)');
35
+ lines.push('');
36
+ lines.push('The claude.ai account you are running under may not match the TACIT workspace you are connected to. Claude.ai artifacts, connectors (Slack, Gmail, Calendar, Drive), and file storage are tied to the claude.ai ACCOUNT. TACIT workspace data is tied to the WORKSPACE. If these are different organizations, warn the user before any experience that publishes artifacts or uses connectors.');
37
+ lines.push('');
38
+ lines.push('## Connector-workspace scope (MANDATORY)');
39
+ lines.push('');
40
+ lines.push('Claude.ai connectors (Slack, Gmail, Calendar, Drive) are bound to your claude.ai ACCOUNT, not to the TACIT workspace. Before including connector data in any response:');
41
+ lines.push('1. Check the workspace name from your TACIT session.');
42
+ lines.push('2. When you read Slack messages, check if the Slack workspace or channel names match the TACIT workspace organization.');
43
+ lines.push('3. If the connector data clearly belongs to a DIFFERENT organization than the workspace (e.g., Slack channels reference "GoodOps" but the TACIT workspace is "Redwood Inference"), EXCLUDE that data entirely.');
44
+ lines.push('4. Say: "Your connected [Slack/Gmail/Calendar] appears to belong to a different organization than [workspace name]. That data has been excluded to maintain workspace isolation."');
45
+ lines.push('5. This check applies to ALL experiences that use connectors: Morning Brief (9), Business Pulse (10), Operating Rhythm (11), and any ad-hoc connector queries.');
46
+ lines.push('');
33
47
  lines.push('## Data source (MANDATORY)');
34
48
  lines.push('');
35
49
  lines.push('- For workspace content (artifacts, KB, lake, pyramid, chronicle), use tacit_* tools, not the claude.ai artifact gallery. The gallery is personal and unfiltered. Connected-app tools and local file reads are unaffected. Exception: the user explicitly asks to search their claude.ai artifacts. 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.');
36
50
  lines.push('');
51
+ lines.push('## Data lake terminology (MANDATORY)');
52
+ lines.push('');
53
+ lines.push('Every workspace has a data lake — it is the foundational storage layer where all ingested content lands before being classified, placed in the pyramid, or promoted to the knowledge base. When describing what is in the workspace:');
54
+ lines.push('- The data lake ALWAYS exists (even if empty). Never say "you do not have a data lake." Say "your data lake is empty — let\'s add some content."');
55
+ lines.push('- "Sources" or "connections" are what feed the lake (GitHub repos, uploaded files, URLs). These may or may not be set up yet.');
56
+ lines.push('- Use "data lake" when referring to the raw content pool. Use "knowledge base" for curated, promoted articles. Use "pyramid" for the strategic alignment structure.');
57
+ lines.push('');
37
58
  lines.push('## Voice composition (MANDATORY)');
38
59
  lines.push('');
39
60
  lines.push('When the user asks for anything "in my voice" or you need voice-matched composition:');
@@ -127,8 +148,17 @@ export async function fetchWorkspaceState(client) {
127
148
  const sources = Array.isArray(sourcesRes)
128
149
  ? sourcesRes
129
150
  : sourcesRes?.sources ?? [];
151
+ let wsDescription;
152
+ try {
153
+ const wsRes = await client.get('/api/v1/workspaces/current');
154
+ wsDescription = wsRes?.description || undefined;
155
+ }
156
+ catch {
157
+ // description is optional — proceed without it
158
+ }
130
159
  return {
131
160
  name: wsName,
161
+ description: wsDescription,
132
162
  collectionNames: collections.map(c => c.name || c.display_name || '').filter(Boolean).slice(0, 5),
133
163
  collectionCount: collections.length,
134
164
  portfolioNames: portfolios.map(p => p.name || p.display_name || '').filter(Boolean).slice(0, 5),
@@ -232,17 +262,17 @@ export const PYR_EXEC_SUB_WORKFLOWS = [
232
262
  { id: 'list_dossiers', tool: 'tacit_pyramid_list_dossiers', trigger: 'Show dossiers under a program' },
233
263
  ];
234
264
  export const EXPERIENCES = [
235
- { 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.', signal: 'You can describe what is in your workspace', tip: '' },
236
- { 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.', signal: 'You know what TACIT can do and are ready to try it', tip: '' },
237
- { 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]?"', signal: 'First grounded answer drawn from your workspace knowledge', tip: '' },
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
+ { 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
+ { 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: '' },
238
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.' },
239
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.' },
240
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.' },
241
- { 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\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.' },
242
- { 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 to voice-ify. 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.', 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.' },
243
- { 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. Run 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 to voice-ify. 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.' },
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.' },
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 to voice-ify. 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
+ { 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 to voice-ify. 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.' },
244
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.' },
245
- { id: 'operating_rhythm', num: 11, name: 'Your Operating Rhythm', tier: 3, tierName: 'Agentic Mastery', action: 'Summarize what the user has accomplished across the onboarding and suggest their operating rhythm. CONNECTOR STATUS: Check your available MCP tool list — if you have Gmail/Slack/Calendar/Drive MCP tools, those ARE connected. Do NOT say they are disconnected. VOICE: Call tacit_voice_list_profiles — if profiles exist, voice is ready. Do NOT ask the user to upload samples if profiles already exist. Focus on: (1) Daily rhythm — morning brief via COS, email triage, meeting prep. (2) Weekly rhythm — COO business review, GM content organization. (3) Delegation — crew dispatch for complex deliverables. (4) What to explore next based on what they have connected and used.', signal: 'User has a clear picture of their operating rhythm and next steps', tip: 'By now you know the team: COS for daily ops, COO for business operations, GM for content. Address them directly anytime.' },
275
+ { id: 'operating_rhythm', num: 11, name: 'Your Operating Rhythm', tier: 3, tierName: 'Agentic Mastery', action: 'Summarize what the user has accomplished across the onboarding and suggest their operating rhythm. CONNECTOR STATUS: Check your available MCP tool list — if you have Gmail/Slack/Calendar/Drive MCP tools, those ARE connected. Do NOT say they are disconnected. CONNECTOR SCOPE: If any connector belongs to a different organization than the workspace (e.g., Slack is from "GoodOps" but the workspace is "Redwood Inference"), note this in the operating rhythm summary and advise that connector data from a different organization will be excluded from briefs to maintain workspace isolation. VOICE: Call tacit_voice_list_profiles — if profiles exist, voice is ready. Do NOT ask the user to upload samples if profiles already exist. Focus on: (1) Daily rhythm — morning brief via COS, email triage, meeting prep. (2) Weekly rhythm — COO business review, GM content organization. (3) Delegation — crew dispatch for complex deliverables. (4) What to explore next based on what they have connected and used.', signal: 'User has a clear picture of their operating rhythm and next steps', tip: 'By now you know the team: COS for daily ops, COO for business operations, GM for content. Address them directly anytime.' },
246
276
  ];
247
277
  // Legacy ID aliases for renamed experiences — maps old id → new id
248
278
  export const LEGACY_ID_ALIASES = Object.assign(Object.create(null), {
@@ -87,7 +87,12 @@ const FALLBACK_TEMPLATES = [
87
87
  { slug: 'coo_operator', display_name: 'COO Operator', description: 'Handles operational workflows.', icon: 'settings', default_capabilities: ['operations_management'], workflow_types: ['coo_operations'] },
88
88
  { slug: 'cmo_marketer', display_name: 'CMO Marketer', description: 'Manages marketing pipeline.', icon: 'megaphone', default_capabilities: ['marketing_pipeline'], workflow_types: ['cmo_marketing_pipeline'] },
89
89
  { slug: 'sales_executor', display_name: 'Sales Executor', description: 'Manages sales pipeline.', icon: 'trending_up', default_capabilities: ['pipeline_management'], workflow_types: ['sales_full_pipeline'] },
90
+ { slug: 'researcher', display_name: 'Research Analyst', description: 'Prepares research briefs, competitor analysis, SOTA surveys, and industry benchmarks.', icon: 'search', default_capabilities: ['search', 'recall', 'synthesize'], workflow_types: ['research_deep_dive'] },
90
91
  { slug: 'wiki_editor', display_name: 'Wiki Editor', description: 'Authors and maintains wiki content with structured classification and validation workflows.', icon: 'book', default_capabilities: ['wiki_authoring', 'content_classification', 'content_validation'], workflow_types: ['wiki_authoring'] },
91
92
  { slug: 'kb_curator', display_name: 'KB Curator', description: 'Curates knowledge base articles, collections, and source integrations.', icon: 'library', default_capabilities: ['kb_management', 'article_curation', 'source_administration'], workflow_types: ['kb_management'] },
93
+ { slug: 'cto_engineer', display_name: 'CTO Engineering', description: 'Engineering organization — routes to sub-execs for role creation and skill architecture.', icon: 'cpu', default_capabilities: ['engineering_routing', 'role_creation'], workflow_types: ['cto_engineering'] },
94
+ { slug: 'secretary', display_name: 'Secretary', description: 'Natural language Chronicle event management — logs decisions, meetings, action items, recalls history.', icon: 'calendar', default_capabilities: ['event_logging', 'event_recall', 'decision_tracking'], workflow_types: ['secretary_chronicle'] },
92
95
  { slug: 'lake_operator', display_name: 'Lake Operator', description: 'Manages data lake ingestion, classification, taxonomy, and structure proposals.', icon: 'database', default_capabilities: ['lake_ingestion', 'classification', 'taxonomy_management', 'structure_proposals'], workflow_types: ['lake_operations'] },
96
+ { slug: 'access_administrator', display_name: 'Access Administrator', description: 'Manages workspace membership, role assignments, and capability denials via IAM tools.', icon: 'shield', default_capabilities: ['iam_membership', 'iam_role_management', 'iam_denial_management'], workflow_types: ['iam_membership_ops', 'iam_access_review'] },
97
+ { slug: 'security_officer', display_name: 'Security Officer', description: 'Manages credential inventory, rotation tracking, and T3 approval workflows.', icon: 'lock', default_capabilities: ['secret_inventory', 'rotation_tracking', 't3_approval'], workflow_types: ['security_audit', 'secret_rotation'] },
93
98
  ];
@@ -66,19 +66,19 @@ export declare const agentDelegateInputSchema: z.ZodEffects<z.ZodObject<{
66
66
  kind: "task" | "goal" | "schedule";
67
67
  wait: boolean;
68
68
  wait_timeout: number;
69
+ dossier_ids?: string[] | undefined;
69
70
  program_ids?: string[] | undefined;
70
71
  role_slug?: string | undefined;
71
72
  agent_id?: string | undefined;
72
73
  target_ids?: string[] | undefined;
73
- dossier_ids?: string[] | undefined;
74
74
  }, {
75
75
  task: string;
76
+ dossier_ids?: string[] | undefined;
76
77
  program_ids?: string[] | undefined;
77
78
  role_slug?: string | undefined;
78
79
  agent_id?: string | undefined;
79
80
  kind?: "task" | "goal" | "schedule" | undefined;
80
81
  target_ids?: string[] | undefined;
81
- dossier_ids?: string[] | undefined;
82
82
  wait?: boolean | undefined;
83
83
  wait_timeout?: number | undefined;
84
84
  }>, {
@@ -86,19 +86,19 @@ export declare const agentDelegateInputSchema: z.ZodEffects<z.ZodObject<{
86
86
  kind: "task" | "goal" | "schedule";
87
87
  wait: boolean;
88
88
  wait_timeout: number;
89
+ dossier_ids?: string[] | undefined;
89
90
  program_ids?: string[] | undefined;
90
91
  role_slug?: string | undefined;
91
92
  agent_id?: string | undefined;
92
93
  target_ids?: string[] | undefined;
93
- dossier_ids?: string[] | undefined;
94
94
  }, {
95
95
  task: string;
96
+ dossier_ids?: string[] | undefined;
96
97
  program_ids?: string[] | undefined;
97
98
  role_slug?: string | undefined;
98
99
  agent_id?: string | undefined;
99
100
  kind?: "task" | "goal" | "schedule" | undefined;
100
101
  target_ids?: string[] | undefined;
101
- dossier_ids?: string[] | undefined;
102
102
  wait?: boolean | undefined;
103
103
  wait_timeout?: number | undefined;
104
104
  }>;
@@ -0,0 +1,14 @@
1
+ /**
2
+ * Capture tools — MV-1537 S3.5: Link Library capture operations exposed as MCP tools.
3
+ *
4
+ * 7 tools:
5
+ * READ: tacit_capture_find, tacit_capture_synthesize
6
+ * WRITE: tacit_capture_save, tacit_capture_remove, tacit_capture_restore,
7
+ * tacit_capture_note, tacit_capture_place
8
+ *
9
+ * All gated on FEATURE_GM_CAPTURE via the backend (returns 404 FEATURE_DISABLED
10
+ * when off). The featureDisabledResult helper surfaces that cleanly.
11
+ */
12
+ import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
13
+ import { TacitClient } from '../client.js';
14
+ export declare function registerCaptureTools(server: McpServer, getClientFn: () => Promise<TacitClient>): void;