@tacitai/mcp-server 0.6.17 → 0.6.18
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/prompts.d.ts +16 -16
- package/dist/prompts.js +20 -19
- package/package.json +1 -1
package/dist/prompts.d.ts
CHANGED
|
@@ -20,42 +20,42 @@ export declare const GM_WORKFLOW: {
|
|
|
20
20
|
readonly steps: readonly [{
|
|
21
21
|
readonly id: "ingest";
|
|
22
22
|
readonly name: "Ingest";
|
|
23
|
-
readonly action: "Call tacit_gm_ingest with a title and the content (inline text via \"content\", or a local file via \"file_path\" — never both). Do NOT set domain_id.";
|
|
23
|
+
readonly action: "Call tacit_gm_ingest with a title and the content (inline text via \"content\", or a local file via \"file_path\" — never both). Do NOT set domain_id. IMPORTANT: The response will include a placement_proposal with suggested_surface — IGNORE this field, it is a backend stub that always says \"lake.\" You will determine placement yourself in the next steps.";
|
|
24
24
|
readonly tools: readonly ["tacit_gm_ingest"];
|
|
25
|
-
readonly signal: "You receive a catalog_id, artifact_id, content_type, and is_duplicate flag.";
|
|
25
|
+
readonly signal: "You receive a catalog_id, artifact_id, content_type, and is_duplicate flag. Save the catalog_id — you will need it for placement.";
|
|
26
26
|
readonly on_duplicate: "If is_duplicate is true, tell the user this content already exists and ask how to proceed: update, skip, or ingest as a new version.";
|
|
27
27
|
}, {
|
|
28
28
|
readonly id: "classify_present";
|
|
29
|
-
readonly name: "Present classification";
|
|
30
|
-
readonly action: "Tell the user what the GM classified their content as
|
|
29
|
+
readonly name: "Present classification and offer options";
|
|
30
|
+
readonly action: "Tell the user what the GM classified their content as. Then ALWAYS offer placement options — do not default to lake. Say something like: \"Your [title] is cataloged. Where should it live? I can file it in your workspace structure, add it to your knowledge base, both, or keep it in the data lake for now. Or say 'you decide' and I'll recommend a spot.\" STOP here and wait for the user to respond. Do not proceed until they choose.";
|
|
31
31
|
readonly tools: readonly [];
|
|
32
|
-
readonly signal: "User chooses: workspace structure
|
|
32
|
+
readonly signal: "User chooses: workspace structure, knowledge base, both, lake-only, or \"you decide.\"";
|
|
33
33
|
}, {
|
|
34
34
|
readonly id: "review_structure";
|
|
35
|
-
readonly name: "Review workspace structure";
|
|
36
|
-
readonly action: "
|
|
35
|
+
readonly name: "Review workspace structure (MANDATORY for pyramid placement)";
|
|
36
|
+
readonly action: "You MUST call ALL THREE tools in sequence — do not skip any: (1) Call tacit_pyramid_list_portfolios to see all portfolios. Pick the best fit. (2) Call tacit_pyramid_list_programs with that portfolio_id. Pick the best-fit program. (3) Call tacit_pyramid_list_dossiers with that program_id. Pick the best-fit dossier. If no dossier fits, note that you will propose creating a new one. You MUST drill down to the dossier level — placing at the program level without a dossier creates an orphan.";
|
|
37
37
|
readonly tools: readonly ["tacit_pyramid_list_portfolios", "tacit_pyramid_list_programs", "tacit_pyramid_list_dossiers"];
|
|
38
|
-
readonly signal: "You have identified a specific portfolio → program → dossier
|
|
38
|
+
readonly signal: "You have identified a specific portfolio → program → dossier, or determined a new dossier name is needed.";
|
|
39
39
|
readonly skip_when: "User chose KB-only or lake-only.";
|
|
40
40
|
}, {
|
|
41
41
|
readonly id: "propose";
|
|
42
|
-
readonly name: "Propose
|
|
43
|
-
readonly action: "Present
|
|
42
|
+
readonly name: "Propose and WAIT for approval";
|
|
43
|
+
readonly action: "Present a specific proposal and STOP. Do not call tacit_gm_approve yet. Say: \"I'd file this under [portfolio] → [program] → [dossier] — [one sentence reason]. Should I go ahead?\" If proposing a new dossier: \"There's no dossier that fits under [program], so I'd create one called [name]. Good?\" For KB: \"I'd add this to your [collection] knowledge base. It will start as a draft. Approve?\" CRITICAL: You MUST wait for the user to say yes, approve, or confirm BEFORE proceeding to the next step. Do NOT interpret the user's earlier request to \"place it\" as approval — they need to approve the SPECIFIC location you are proposing.";
|
|
44
44
|
readonly tools: readonly [];
|
|
45
|
-
readonly signal: "User approves, redirects to a different location, or declines.";
|
|
45
|
+
readonly signal: "User explicitly approves (\"yes\", \"approve\", \"do it\", \"go ahead\"), redirects to a different location, or declines.";
|
|
46
46
|
}, {
|
|
47
47
|
readonly id: "place";
|
|
48
|
-
readonly name: "
|
|
49
|
-
readonly action: "
|
|
48
|
+
readonly name: "Execute approved placement";
|
|
49
|
+
readonly action: "ONLY after the user explicitly approved the proposal in step 4: For pyramid — if a new dossier is needed, call tacit_pyramid_create_dossier first to get the dossier_id. Then call tacit_gm_approve with the catalog_id from step 1, surface=\"pyramid\", collection_or_program set to the program UUID, and dossier_id set to the dossier UUID. NEVER call tacit_gm_approve without a dossier_id for pyramid placement. For KB: call tacit_gm_approve with surface=\"kb\" and the collection UUID. For both: pyramid first, then KB (two separate calls). For lake-only: no call needed.";
|
|
50
50
|
readonly tools: readonly ["tacit_gm_approve", "tacit_pyramid_create_dossier"];
|
|
51
51
|
readonly signal: "tacit_gm_approve returns success.";
|
|
52
52
|
readonly skip_when: "User chose lake-only.";
|
|
53
53
|
}, {
|
|
54
54
|
readonly id: "confirm";
|
|
55
|
-
readonly name: "Confirm";
|
|
56
|
-
readonly action: "Tell the user where their content landed
|
|
55
|
+
readonly name: "Confirm in plain language";
|
|
56
|
+
readonly action: "Tell the user where their content landed: \"Done — your [title] is filed under [portfolio] → [program] → [dossier].\" For KB: \"Added to your [collection] knowledge base as a draft — it won't appear in search results until published.\" For lake-only: \"Saved to your data lake — you can file it somewhere anytime by asking me.\" NEVER show catalog IDs, artifact IDs, UUIDs, or SHA hashes in your response.";
|
|
57
57
|
readonly tools: readonly [];
|
|
58
|
-
readonly signal: "User sees a clear confirmation
|
|
58
|
+
readonly signal: "User sees a clear, plain-language confirmation.";
|
|
59
59
|
}];
|
|
60
60
|
};
|
|
61
61
|
export declare const EXPERIENCES: readonly [{
|
package/dist/prompts.js
CHANGED
|
@@ -57,7 +57,7 @@ function buildAssistantSystemPrompt(state) {
|
|
|
57
57
|
lines.push('- For all content ingestion (adding documents, text, URLs, or files to the workspace), follow the GM Workflow below. Do not call tacit_artifact_create, tacit_import_artifact, tacit_ingest_file, tacit_ingest_url, tacit_ingest_url_general, or tacit_kb_create_article directly for new content — those bypass the data lake classification pipeline.');
|
|
58
58
|
lines.push('');
|
|
59
59
|
lines.push('### GM Workflow — Content Ingestion & Placement');
|
|
60
|
-
lines.push('When the user asks to add, save, ingest, or file content, follow these steps in order. Lake ingestion alone is NEVER "done" — always complete through to the confirm step.');
|
|
60
|
+
lines.push('When the user asks to add, save, ingest, or file content, follow these steps in order. Lake ingestion alone is NEVER "done" — always complete through to the confirm step. RULES: (1) NEVER show UUIDs, catalog IDs, artifact IDs, or SHA hashes to the user — use human-readable names only. (2) NEVER place content without explicit user approval of the specific location. (3) ALWAYS drill down to dossier level for pyramid placement — program-level placement creates orphans.');
|
|
61
61
|
for (const step of GM_WORKFLOW.steps) {
|
|
62
62
|
let line = `${step.id.toUpperCase()}: ${step.action}`;
|
|
63
63
|
if ('skip_when' in step && step.skip_when) {
|
|
@@ -117,8 +117,9 @@ export const CAPABILITY_DOMAINS = [
|
|
|
117
117
|
{ domain: 'Code & GitHub', triggers: ['Show my repo connections…', 'Sync from GitHub…'], description: 'Repository connections and code sync' },
|
|
118
118
|
];
|
|
119
119
|
// ─── GM Workflow Chain ──────────────────────────────────────────────────────
|
|
120
|
-
// Mirrors the /gm skill SOPs (SOP-01
|
|
121
|
-
//
|
|
120
|
+
// Mirrors the /gm skill happy-path SOPs (SOP-01 ingest, SOP-03 KB, SOP-04 pyramid,
|
|
121
|
+
// SOP-05 lake-only, SOP-06 cross-ref). SOP-02 (classify existing) and SOP-04a
|
|
122
|
+
// (build-program dossier set) are not yet covered.
|
|
122
123
|
export const GM_WORKFLOW = {
|
|
123
124
|
name: 'Content Ingestion & Placement',
|
|
124
125
|
trigger: 'User asks to add, save, ingest, or file content into the workspace',
|
|
@@ -126,47 +127,47 @@ export const GM_WORKFLOW = {
|
|
|
126
127
|
{
|
|
127
128
|
id: 'ingest',
|
|
128
129
|
name: 'Ingest',
|
|
129
|
-
action: 'Call tacit_gm_ingest with a title and the content (inline text via "content", or a local file via "file_path" — never both). Do NOT set domain_id.',
|
|
130
|
+
action: 'Call tacit_gm_ingest with a title and the content (inline text via "content", or a local file via "file_path" — never both). Do NOT set domain_id. IMPORTANT: The response will include a placement_proposal with suggested_surface — IGNORE this field, it is a backend stub that always says "lake." You will determine placement yourself in the next steps.',
|
|
130
131
|
tools: ['tacit_gm_ingest'],
|
|
131
|
-
signal: 'You receive a catalog_id, artifact_id, content_type, and is_duplicate flag.',
|
|
132
|
+
signal: 'You receive a catalog_id, artifact_id, content_type, and is_duplicate flag. Save the catalog_id — you will need it for placement.',
|
|
132
133
|
on_duplicate: 'If is_duplicate is true, tell the user this content already exists and ask how to proceed: update, skip, or ingest as a new version.',
|
|
133
134
|
},
|
|
134
135
|
{
|
|
135
136
|
id: 'classify_present',
|
|
136
|
-
name: 'Present classification',
|
|
137
|
-
action: 'Tell the user what the GM classified their content as
|
|
137
|
+
name: 'Present classification and offer options',
|
|
138
|
+
action: 'Tell the user what the GM classified their content as. Then ALWAYS offer placement options — do not default to lake. Say something like: "Your [title] is cataloged. Where should it live? I can file it in your workspace structure, add it to your knowledge base, both, or keep it in the data lake for now. Or say \'you decide\' and I\'ll recommend a spot." STOP here and wait for the user to respond. Do not proceed until they choose.',
|
|
138
139
|
tools: [],
|
|
139
|
-
signal: 'User chooses: workspace structure
|
|
140
|
+
signal: 'User chooses: workspace structure, knowledge base, both, lake-only, or "you decide."',
|
|
140
141
|
},
|
|
141
142
|
{
|
|
142
143
|
id: 'review_structure',
|
|
143
|
-
name: 'Review workspace structure',
|
|
144
|
-
action: '
|
|
144
|
+
name: 'Review workspace structure (MANDATORY for pyramid placement)',
|
|
145
|
+
action: 'You MUST call ALL THREE tools in sequence — do not skip any: (1) Call tacit_pyramid_list_portfolios to see all portfolios. Pick the best fit. (2) Call tacit_pyramid_list_programs with that portfolio_id. Pick the best-fit program. (3) Call tacit_pyramid_list_dossiers with that program_id. Pick the best-fit dossier. If no dossier fits, note that you will propose creating a new one. You MUST drill down to the dossier level — placing at the program level without a dossier creates an orphan.',
|
|
145
146
|
tools: ['tacit_pyramid_list_portfolios', 'tacit_pyramid_list_programs', 'tacit_pyramid_list_dossiers'],
|
|
146
|
-
signal: 'You have identified a specific portfolio → program → dossier
|
|
147
|
+
signal: 'You have identified a specific portfolio → program → dossier, or determined a new dossier name is needed.',
|
|
147
148
|
skip_when: 'User chose KB-only or lake-only.',
|
|
148
149
|
},
|
|
149
150
|
{
|
|
150
151
|
id: 'propose',
|
|
151
|
-
name: 'Propose
|
|
152
|
-
action: 'Present
|
|
152
|
+
name: 'Propose and WAIT for approval',
|
|
153
|
+
action: 'Present a specific proposal and STOP. Do not call tacit_gm_approve yet. Say: "I\'d file this under [portfolio] → [program] → [dossier] — [one sentence reason]. Should I go ahead?" If proposing a new dossier: "There\'s no dossier that fits under [program], so I\'d create one called [name]. Good?" For KB: "I\'d add this to your [collection] knowledge base. It will start as a draft. Approve?" CRITICAL: You MUST wait for the user to say yes, approve, or confirm BEFORE proceeding to the next step. Do NOT interpret the user\'s earlier request to "place it" as approval — they need to approve the SPECIFIC location you are proposing.',
|
|
153
154
|
tools: [],
|
|
154
|
-
signal: 'User approves, redirects to a different location, or declines.',
|
|
155
|
+
signal: 'User explicitly approves ("yes", "approve", "do it", "go ahead"), redirects to a different location, or declines.',
|
|
155
156
|
},
|
|
156
157
|
{
|
|
157
158
|
id: 'place',
|
|
158
|
-
name: '
|
|
159
|
-
action: '
|
|
159
|
+
name: 'Execute approved placement',
|
|
160
|
+
action: 'ONLY after the user explicitly approved the proposal in step 4: For pyramid — if a new dossier is needed, call tacit_pyramid_create_dossier first to get the dossier_id. Then call tacit_gm_approve with the catalog_id from step 1, surface="pyramid", collection_or_program set to the program UUID, and dossier_id set to the dossier UUID. NEVER call tacit_gm_approve without a dossier_id for pyramid placement. For KB: call tacit_gm_approve with surface="kb" and the collection UUID. For both: pyramid first, then KB (two separate calls). For lake-only: no call needed.',
|
|
160
161
|
tools: ['tacit_gm_approve', 'tacit_pyramid_create_dossier'],
|
|
161
162
|
signal: 'tacit_gm_approve returns success.',
|
|
162
163
|
skip_when: 'User chose lake-only.',
|
|
163
164
|
},
|
|
164
165
|
{
|
|
165
166
|
id: 'confirm',
|
|
166
|
-
name: 'Confirm',
|
|
167
|
-
action: 'Tell the user where their content landed
|
|
167
|
+
name: 'Confirm in plain language',
|
|
168
|
+
action: 'Tell the user where their content landed: "Done — your [title] is filed under [portfolio] → [program] → [dossier]." For KB: "Added to your [collection] knowledge base as a draft — it won\'t appear in search results until published." For lake-only: "Saved to your data lake — you can file it somewhere anytime by asking me." NEVER show catalog IDs, artifact IDs, UUIDs, or SHA hashes in your response.',
|
|
168
169
|
tools: [],
|
|
169
|
-
signal: 'User sees a clear confirmation
|
|
170
|
+
signal: 'User sees a clear, plain-language confirmation.',
|
|
170
171
|
},
|
|
171
172
|
],
|
|
172
173
|
};
|