@tacitai/mcp-server 0.9.0 → 0.9.1
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/tools/gm.js +1 -1
- package/package.json +1 -1
package/dist/tools/gm.js
CHANGED
|
@@ -33,7 +33,7 @@ export const GM_INGEST_NEXT_STEP = 'NEXT STEP: nothing has been placed yet. Tell
|
|
|
33
33
|
'If suggested_surface is "lake", say it is saved in the data lake and ask whether to file it in the workspace structure or the knowledge base; do not pick one yourself. ' +
|
|
34
34
|
'RESEARCH ROUTING (FEAT-273): if the response includes research_kind, this is research content with automated placement rules. ' +
|
|
35
35
|
'If audited is true, propose KB DRAFT in the suggested_collection_name. If audited is false, default to lake-only but let the user override to KB. ' +
|
|
36
|
-
'Research content is never proposed for pyramid
|
|
36
|
+
'Research content is never proposed for pyramid (pyramid_default is always false for detected research). ' +
|
|
37
37
|
'When the user picks a surface (e.g. "pyramid", "KB"), that is a SURFACE CHOICE, not a location approval. You must THEN drill down ' +
|
|
38
38
|
'(list portfolios → programs → dossiers for pyramid, or list collections for KB), propose the SPECIFIC location ' +
|
|
39
39
|
'(e.g. "I\'d file this under Product → GoodOps Site → GoodOps Site v1. Approve?"), and wait for the user to approve THAT location in a new message. ' +
|