@promptbook/node 0.72.0 → 0.73.0

package/esm/typings/src/commands/TEMPLATE/TemplateTypes.d.ts

@@ -12,4 +12,4 @@ export type TemplateType = TupleToUnion<typeof TemplateTypes>;
  * @see https://github.com/webgptorg/promptbook#template-type
  * @public exported from `@promptbook/core`
  */
-export declare const TemplateTypes: readonly ["PROMPT_TEMPLATE", "SIMPLE_TEMPLATE", "SCRIPT_TEMPLATE", "DIALOG_TEMPLATE", "SAMPLE", "KNOWLEDGE", "INSTRUMENT", "ACTION"];
+export declare const TemplateTypes: readonly ["PROMPT_TEMPLATE", "SIMPLE_TEMPLATE", "SCRIPT_TEMPLATE", "DIALOG_TEMPLATE", "EXAMPLE", "KNOWLEDGE", "INSTRUMENT", "ACTION"];

package/esm/typings/src/config.d.ts

@@ -121,7 +121,7 @@ export declare const REPLACING_NONCE = "u$k42k%!V2zo34w7Fu#@QUHYPW";
  *
  * @public exported from `@promptbook/core`
  */
-export declare const RESERVED_PARAMETER_NAMES: readonly ["content", "context", "knowledge", "samples", "modelName", "currentDate"];
+export declare const RESERVED_PARAMETER_NAMES: readonly ["content", "context", "knowledge", "examples", "modelName", "currentDate"];
 /**
  * @@@
  *

package/esm/typings/src/conversion/prettify/renderPipelineMermaidOptions.d.ts

@@ -22,9 +22,9 @@ export type renderPipelineMermaidOptions = {
  */
 export declare function renderPromptbookMermaid(pipelineJson: PipelineJson, options?: renderPipelineMermaidOptions): string;
 /**
- * TODO: !!!!! FOREACH in mermaid graph
- * TODO: !!!!! Knowledge in mermaid graph
- * TODO: !!!!! Personas in mermaid graph
+ * TODO: [🧠] !! FOREACH in mermaid graph
+ * TODO: [🧠] !! Knowledge in mermaid graph
+ * TODO: [🧠] !! Personas in mermaid graph
  * TODO: Maybe use some Mermaid package instead of string templating
  * TODO: [🕌] When more than 2 functionalities, split into separate functions
  */

package/esm/typings/src/conversion/utils/stringifyPipelineJson.d.ts

@@ -9,7 +9,7 @@ import type { string_json } from '../../types/typeAliases';
  */
 export declare function stringifyPipelineJson<TType>(pipeline: TType): string_json<TType>;
 /**
- * TODO: [🐝] Not Working propperly @see https://promptbook.studio/samples/mixed-knowledge.ptbk.md
+ * TODO: [🐝] Not Working propperly @see https://promptbook.studio/examples/mixed-knowledge.ptbk.md
  * TODO: [🧠][0] Maybe rename to `stringifyPipelineJson`, `stringifyIndexedJson`,...
  * TODO: [🧠] Maybe more elegant solution than replacing via regex
  * TODO: [🍙] Make some standard order of json properties

package/esm/typings/src/conversion/validation/_importPipeline.d.ts

@@ -7,7 +7,7 @@ import type { string_json } from '../../types/typeAliases';
  * Note: Using here custom import to work in jest tests
  * Note: Using sync version is 💩 in the production code, but it's ok here in tests
  *
- * @param path - The path to the file relative to samples/pipelines directory
+ * @param path - The path to the file relative to examples/pipelines directory
  * @private internal function of tests
  */
 export declare function importPipelineWithoutPreparation(path: `${string}.ptbk.md`): PipelineString;

package/esm/typings/src/conversion/validation/validatePipeline.d.ts

@@ -20,7 +20,7 @@ export declare function validatePipeline(pipeline: PipelineJson): PipelineJson;
  */
 export declare function validatePipelineCore(pipeline: PipelineJson): void;
 /**
- * TODO: !!!!! [🧞‍♀️] Do not allow joker + foreach
+ * TODO: !! [🧞‍♀️] Do not allow joker + foreach
  * TODO: [🧠] Work with promptbookVersion
  * TODO: Use here some json-schema, Zod or something similar and change it to:
  *     > /**
@@ -32,7 +32,7 @@ export declare function validatePipelineCore(pipeline: PipelineJson): void;
  *     >  ex port function validatePipeline(promptbook: really_unknown): asserts promptbook is PipelineJson {
  */
 /**
- * TODO: [🧳][main] !!!! Validate that all samples match expectations
+ * TODO: [🧳][main] !!!! Validate that all examples match expectations
  * TODO: [🧳][🐝][main] !!!! Validate that knowledge is valid (non-void)
  * TODO: [🧳][main] !!!! Validate that persona can be used only with CHAT variant
  * TODO: [🧳][main] !!!! Validate that parameter with reserved name not used RESERVED_PARAMETER_NAMES

package/esm/typings/src/execution/createPipelineExecutor/{getSamplesForTemplate.d.ts → getExamplesForTemplate.d.ts}

@@ -7,4 +7,4 @@ import type { string_parameter_value } from '../../types/typeAliases';
  *
  * @private internal utility of `createPipelineExecutor`
  */
-export declare function getSamplesForTemplate(template: ReadonlyDeep<TemplateJson>): Promise<string_parameter_value & string_markdown>;
+export declare function getExamplesForTemplate(template: ReadonlyDeep<TemplateJson>): Promise<string_parameter_value & string_markdown>;

package/esm/typings/src/formats/_common/FormatDefinition.d.ts

@@ -15,7 +15,7 @@ export type FormatDefinition<TValue extends TPartialValue, TPartialValue extends
     /**
      * The name of the format used in .ptbk.md files
      *
-     * @sample "JSON"
+     * @example "JSON"
      */
     readonly formatName: string_name & string_SCREAMING_CASE;
     /**
@@ -25,7 +25,7 @@ export type FormatDefinition<TValue extends TPartialValue, TPartialValue extends
     /**
      * The mime type of the format (if any)
      *
-     * @sample "application/json"
+     * @example "application/json"
      */
     readonly mimeType?: string_mime_type;
     /**

package/esm/typings/src/formats/_common/FormatSubvalueDefinition.d.ts

@@ -11,7 +11,7 @@ export type FormatSubvalueDefinition<TValue extends string, TSettings extends em
     /**
      * The name of the format used in .ptbk.md files
      *
-     * @sample "CELL"
+     * @example "CELL"
      */
     readonly subvalueName: string_name & string_SCREAMING_CASE;
     /**

package/esm/typings/src/personas/preparePersona.d.ts

@@ -10,7 +10,7 @@ import type { string_persona_description } from '../types/typeAliases';
  */
 export declare function preparePersona(personaDescription: string_persona_description, tools: Pick<ExecutionTools, 'llm'>, options: PrepareAndScrapeOptions): Promise<PersonaPreparedJson['modelRequirements']>;
 /**
- * TODO: [🔃][main] !!!!! If the persona was prepared with different version or different set of models, prepare it once again
+ * TODO: [🔃][main] !! If the persona was prepared with different version or different set of models, prepare it once again
  * TODO: [🏢] !! Check validity of `modelName` in pipeline
  * TODO: [🏢] !! Check validity of `systemMessage` in pipeline
  * TODO: [🏢] !! Check validity of `temperature` in pipeline

package/esm/typings/src/prepare/isPipelinePrepared.d.ts

@@ -6,11 +6,11 @@ import type { PipelineJson } from '../types/PipelineJson/PipelineJson';
  */
 export declare function isPipelinePrepared(pipeline: PipelineJson): boolean;
 /**
- * TODO: [🔃][main] !!!!! If the pipeline was prepared with different version or different set of models, prepare it once again
+ * TODO: [🔃][main] !! If the pipeline was prepared with different version or different set of models, prepare it once again
  * TODO: [🐠] Maybe base this on `makeValidator`
  * TODO: [🧊] Pipeline can be partially prepared, this should return true ONLY if fully prepared
  * TODO: [🧿] Maybe do same process with same granularity and subfinctions as `preparePipeline`
  *     - [🏍] ? Is context in each template
- *     - [♨] Are samples prepared
+ *     - [♨] Are examples prepared
  *     - [♨] Are templates prepared
  */

package/esm/typings/src/prepare/prepareTemplates.d.ts

@@ -24,7 +24,7 @@ export {};
 /**
  * TODO: [🧠] Add context to each template (if missing)
  * TODO: [🧠] What is better name `prepareTemplate` or `prepareTemplateAndParameters`
- * TODO: [♨][main] !!! Prepare index the samples and maybe templates
+ * TODO: [♨][main] !!! Prepare index the examples and maybe templates
  * TODO: Write tests for `preparePipeline`
  * TODO: [🏏] Leverage the batch API and build queues @see https://platform.openai.com/docs/guides/batch
  * TODO: [🧊] In future one preparation can take data from previous preparation and save tokens and time

package/esm/typings/src/scrapers/document/DocumentScraper.test.d.ts

@@ -1,4 +1,4 @@
 export {};
 /**
- * TODO: [📓] Maybe test all file in samples (not just 10-simple.docx)
+ * TODO: [📓] Maybe test all file in examples (not just 10-simple.docx)
  */

package/esm/typings/src/scrapers/document-legacy/LegacyDocumentScraper.test.d.ts

@@ -1,4 +1,4 @@
 export {};
 /**
- * TODO: [📓] Maybe test all file in samples (not just 10-simple.doc)
+ * TODO: [📓] Maybe test all file in examples (not just 10-simple.doc)
  */

package/esm/typings/src/scrapers/markdown/MarkdownScraper.test.d.ts

@@ -1,4 +1,4 @@
 export {};
 /**
- * TODO: [📓] Maybe test all file in samples (not just 10-simple.md)
+ * TODO: [📓] Maybe test all file in examples (not just 10-simple.md)
  */

package/esm/typings/src/types/PipelineJson/ParameterJson.d.ts

@@ -27,10 +27,10 @@ export type ParameterJson = {
      */
     readonly description?: string_markdown_text;
     /**
-     * Sample values of the parameter
+     * Example values of the parameter
      * Note: This values won't be actually used as some default values, but they are just for better understanding of the parameter
      */
-    readonly sampleValues?: Array<string_parameter_value>;
+    readonly exampleValues?: Array<string_parameter_value>;
 };
 /**
  * TODO: [🧠] Should be here registered subparameters from foreach or not?

package/esm/typings/src/types/PipelineJson/PreparationJson.d.ts

@@ -18,5 +18,5 @@ export type PreparationJson = {
 /**
  * TODO: [🍙] Make some standard order of json properties
  * TODO: Maybe put here used `modelName`
- * TODO: [🍥] When using `date` it changes all samples .ptbk.json files each time so until some more elegant solution omit the time from prepared pipeline
+ * TODO: [🍥] When using `date` it changes all examples .ptbk.json files each time so until some more elegant solution omit the time from prepared pipeline
  */

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@promptbook/node",
-    "version": "0.72.0",
+    "version": "0.73.0",
     "description": "Supercharge your use of large language models",
     "private": false,
     "sideEffects": false,
@@ -31,7 +31,8 @@
         "o1",
         "o1-mini",
         "o1-preview",
-        "anthropic"
+        "anthropic",
+        "LLMOps"
     ],
     "license": "CC-BY-4.0",
     "bugs": {
@@ -52,7 +53,7 @@
     "module": "./esm/index.es.js",
     "typings": "./esm/typings/src/_packages/node.index.d.ts",
     "peerDependencies": {
-        "@promptbook/core": "0.72.0"
+        "@promptbook/core": "0.73.0"
     },
     "dependencies": {
         "colors": "1.4.0",

package/umd/index.umd.js

@@ -35,7 +35,7 @@
     /**
      * The version of the Promptbook library
      */
-    var PROMPTBOOK_VERSION = '0.72.0-34';
+    var PROMPTBOOK_VERSION = '0.72.0';
     // TODO: [main] !!!! List here all the versions and annotate + put into script
 
     /*! *****************************************************************************
@@ -423,10 +423,10 @@
         'content',
         'context',
         'knowledge',
-        'samples',
+        'examples',
         'modelName',
         'currentDate',
-        // <- TODO: !!!!! list here all command names
+        // <- TODO: list here all command names
         // <- TODO: Add more like 'date', 'modelName',...
         // <- TODO: Add [emoji] + instructions ACRY when adding new reserved parameter
     ]);
@@ -1360,7 +1360,7 @@
      * TODO: [👷‍♂️] @@@ Manual about construction of llmTools
      */
 
-    var PipelineCollection = [{title:"Prepare Knowledge from Markdown",pipelineUrl:"https://promptbook.studio/promptbook/prepare-knowledge-from-markdown.ptbk.md",parameters:[{name:"knowledgeContent",description:"Markdown document content",isInput:true,isOutput:false},{name:"knowledgePieces",description:"The knowledge JSON object",isInput:false,isOutput:true}],templates:[{templateType:"PROMPT_TEMPLATE",name:"knowledge",title:"Knowledge",content:"You are experienced data researcher, extract the important knowledge from the document.\n\n# Rules\n\n-   Make pieces of information concise, clear, and easy to understand\n-   One piece of information should be approximately 1 paragraph\n-   Divide the paragraphs by markdown horizontal lines ---\n-   Omit irrelevant information\n-   Group redundant information\n-   Write just extracted information, nothing else\n\n# The document\n\nTake information from this document:\n\n> {knowledgeContent}",resultingParameterName:"knowledgePieces",dependentParameterNames:["knowledgeContent"]}],knowledgeSources:[],knowledgePieces:[],personas:[],preparations:[],sourceFile:"./promptbook-collection/prepare-knowledge-from-markdown.ptbk.md"},{title:"Prepare Keywords",pipelineUrl:"https://promptbook.studio/promptbook/prepare-knowledge-keywords.ptbk.md",parameters:[{name:"knowledgePieceContent",description:"The content",isInput:true,isOutput:false},{name:"keywords",description:"Keywords separated by comma",isInput:false,isOutput:true}],templates:[{templateType:"PROMPT_TEMPLATE",name:"knowledge",title:"Knowledge",content:"You are experienced data researcher, detect the important keywords in the document.\n\n# Rules\n\n-   Write just keywords separated by comma\n\n# The document\n\nTake information from this document:\n\n> {knowledgePieceContent}",resultingParameterName:"keywords",dependentParameterNames:["knowledgePieceContent"]}],knowledgeSources:[],knowledgePieces:[],personas:[],preparations:[],sourceFile:"./promptbook-collection/prepare-knowledge-keywords.ptbk.md"},{title:"Prepare Title",pipelineUrl:"https://promptbook.studio/promptbook/prepare-knowledge-title.ptbk.md",parameters:[{name:"knowledgePieceContent",description:"The content",isInput:true,isOutput:false},{name:"title",description:"The title of the document",isInput:false,isOutput:true}],templates:[{templateType:"PROMPT_TEMPLATE",name:"knowledge",title:"Knowledge",content:"You are experienced content creator, write best title for the document.\n\n# Rules\n\n-   Write just title, nothing else\n-   Title should be concise and clear\n-   Write maximum 5 words for the title\n\n# The document\n\n> {knowledgePieceContent}",resultingParameterName:"title",expectations:{words:{min:1,max:8}},dependentParameterNames:["knowledgePieceContent"]}],knowledgeSources:[],knowledgePieces:[],personas:[],preparations:[],sourceFile:"./promptbook-collection/prepare-knowledge-title.ptbk.md"},{title:"Prepare Keywords",pipelineUrl:"https://promptbook.studio/promptbook/prepare-persona.ptbk.md",parameters:[{name:"availableModelNames",description:"List of available model names separated by comma (,)",isInput:true,isOutput:false},{name:"personaDescription",description:"Description of the persona",isInput:true,isOutput:false},{name:"modelRequirements",description:"Specific requirements for the model",isInput:false,isOutput:true}],templates:[{templateType:"PROMPT_TEMPLATE",name:"make-model-requirements",title:"Make modelRequirements",content:"You are experienced AI engineer, you need to create virtual assistant.\nWrite\n\n## Sample\n\n```json\n{\n\"modelName\": \"gpt-4o\",\n\"systemMessage\": \"You are experienced AI engineer and helpfull assistant.\",\n\"temperature\": 0.7\n}\n```\n\n## Instructions\n\n-   Your output format is JSON object\n-   Write just the JSON object, no other text should be present\n-   It contains the following keys:\n    -   `modelName`: The name of the model to use\n    -   `systemMessage`: The system message to provide context to the model\n    -   `temperature`: The sampling temperature to use\n\n### Key `modelName`\n\nPick from the following models:\n\n-   {availableModelNames}\n\n### Key `systemMessage`\n\nThe system message is used to communicate instructions or provide context to the model at the beginning of a conversation. It is displayed in a different format compared to user messages, helping the model understand its role in the conversation. The system message typically guides the model's behavior, sets the tone, or specifies desired output from the model. By utilizing the system message effectively, users can steer the model towards generating more accurate and relevant responses.\n\nFor example:\n\n> You are an experienced AI engineer and helpful assistant.\n\n> You are a friendly and knowledgeable chatbot.\n\n### Key `temperature`\n\nThe sampling temperature, between 0 and 1. Higher values like 0.8 will make the output more random, while lower values like 0.2 will make it more focused and deterministic. If set to 0, the model will use log probability to automatically increase the temperature until certain thresholds are hit.\n\nYou can pick a value between 0 and 2. For example:\n\n-   `0.1`: Low temperature, extremely conservative and deterministic\n-   `0.5`: Medium temperature, balanced between conservative and creative\n-   `1.0`: High temperature, creative and bit random\n-   `1.5`: Very high temperature, extremely creative and often chaotic and unpredictable\n-   `2.0`: Maximum temperature, completely random and unpredictable, for some extreme creative use cases\n\n# The assistant\n\nTake this description of the persona:\n\n> {personaDescription}",resultingParameterName:"modelRequirements",format:"JSON",dependentParameterNames:["availableModelNames","personaDescription"]}],knowledgeSources:[],knowledgePieces:[],personas:[],preparations:[],sourceFile:"./promptbook-collection/prepare-persona.ptbk.md"}];
+    var PipelineCollection = [{title:"Prepare Knowledge from Markdown",pipelineUrl:"https://promptbook.studio/promptbook/prepare-knowledge-from-markdown.ptbk.md",parameters:[{name:"knowledgeContent",description:"Markdown document content",isInput:true,isOutput:false},{name:"knowledgePieces",description:"The knowledge JSON object",isInput:false,isOutput:true}],templates:[{templateType:"PROMPT_TEMPLATE",name:"knowledge",title:"Knowledge",content:"You are experienced data researcher, extract the important knowledge from the document.\n\n# Rules\n\n-   Make pieces of information concise, clear, and easy to understand\n-   One piece of information should be approximately 1 paragraph\n-   Divide the paragraphs by markdown horizontal lines ---\n-   Omit irrelevant information\n-   Group redundant information\n-   Write just extracted information, nothing else\n\n# The document\n\nTake information from this document:\n\n> {knowledgeContent}",resultingParameterName:"knowledgePieces",dependentParameterNames:["knowledgeContent"]}],knowledgeSources:[],knowledgePieces:[],personas:[],preparations:[],sourceFile:"./promptbook-collection/prepare-knowledge-from-markdown.ptbk.md"},{title:"Prepare Keywords",pipelineUrl:"https://promptbook.studio/promptbook/prepare-knowledge-keywords.ptbk.md",parameters:[{name:"knowledgePieceContent",description:"The content",isInput:true,isOutput:false},{name:"keywords",description:"Keywords separated by comma",isInput:false,isOutput:true}],templates:[{templateType:"PROMPT_TEMPLATE",name:"knowledge",title:"Knowledge",content:"You are experienced data researcher, detect the important keywords in the document.\n\n# Rules\n\n-   Write just keywords separated by comma\n\n# The document\n\nTake information from this document:\n\n> {knowledgePieceContent}",resultingParameterName:"keywords",dependentParameterNames:["knowledgePieceContent"]}],knowledgeSources:[],knowledgePieces:[],personas:[],preparations:[],sourceFile:"./promptbook-collection/prepare-knowledge-keywords.ptbk.md"},{title:"Prepare Title",pipelineUrl:"https://promptbook.studio/promptbook/prepare-knowledge-title.ptbk.md",parameters:[{name:"knowledgePieceContent",description:"The content",isInput:true,isOutput:false},{name:"title",description:"The title of the document",isInput:false,isOutput:true}],templates:[{templateType:"PROMPT_TEMPLATE",name:"knowledge",title:"Knowledge",content:"You are experienced content creator, write best title for the document.\n\n# Rules\n\n-   Write just title, nothing else\n-   Title should be concise and clear\n-   Write maximum 5 words for the title\n\n# The document\n\n> {knowledgePieceContent}",resultingParameterName:"title",expectations:{words:{min:1,max:8}},dependentParameterNames:["knowledgePieceContent"]}],knowledgeSources:[],knowledgePieces:[],personas:[],preparations:[],sourceFile:"./promptbook-collection/prepare-knowledge-title.ptbk.md"},{title:"Prepare Keywords",pipelineUrl:"https://promptbook.studio/promptbook/prepare-persona.ptbk.md",parameters:[{name:"availableModelNames",description:"List of available model names separated by comma (,)",isInput:true,isOutput:false},{name:"personaDescription",description:"Description of the persona",isInput:true,isOutput:false},{name:"modelRequirements",description:"Specific requirements for the model",isInput:false,isOutput:true}],templates:[{templateType:"PROMPT_TEMPLATE",name:"make-model-requirements",title:"Make modelRequirements",content:"You are experienced AI engineer, you need to create virtual assistant.\nWrite\n\n## Example\n\n```json\n{\n\"modelName\": \"gpt-4o\",\n\"systemMessage\": \"You are experienced AI engineer and helpfull assistant.\",\n\"temperature\": 0.7\n}\n```\n\n## Instructions\n\n-   Your output format is JSON object\n-   Write just the JSON object, no other text should be present\n-   It contains the following keys:\n    -   `modelName`: The name of the model to use\n    -   `systemMessage`: The system message to provide context to the model\n    -   `temperature`: The sampling temperature to use\n\n### Key `modelName`\n\nPick from the following models:\n\n-   {availableModelNames}\n\n### Key `systemMessage`\n\nThe system message is used to communicate instructions or provide context to the model at the beginning of a conversation. It is displayed in a different format compared to user messages, helping the model understand its role in the conversation. The system message typically guides the model's behavior, sets the tone, or specifies desired output from the model. By utilizing the system message effectively, users can steer the model towards generating more accurate and relevant responses.\n\nFor example:\n\n> You are an experienced AI engineer and helpful assistant.\n\n> You are a friendly and knowledgeable chatbot.\n\n### Key `temperature`\n\nThe sampling temperature, between 0 and 1. Higher values like 0.8 will make the output more random, while lower values like 0.2 will make it more focused and deterministic. If set to 0, the model will use log probability to automatically increase the temperature until certain thresholds are hit.\n\nYou can pick a value between 0 and 2. For example:\n\n-   `0.1`: Low temperature, extremely conservative and deterministic\n-   `0.5`: Medium temperature, balanced between conservative and creative\n-   `1.0`: High temperature, creative and bit random\n-   `1.5`: Very high temperature, extremely creative and often chaotic and unpredictable\n-   `2.0`: Maximum temperature, completely random and unpredictable, for some extreme creative use cases\n\n# The assistant\n\nTake this description of the persona:\n\n> {personaDescription}",resultingParameterName:"modelRequirements",format:"JSON",dependentParameterNames:["availableModelNames","personaDescription"]}],knowledgeSources:[],knowledgePieces:[],personas:[],preparations:[],sourceFile:"./promptbook-collection/prepare-persona.ptbk.md"}];
 
     /**
      * This error indicates that the promptbook in a markdown format cannot be parsed into a valid promptbook object
@@ -1787,7 +1787,7 @@
         }
     }
     /**
-     * TODO: !!!!! [🧞‍♀️] Do not allow joker + foreach
+     * TODO: !! [🧞‍♀️] Do not allow joker + foreach
      * TODO: [🧠] Work with promptbookVersion
      * TODO: Use here some json-schema, Zod or something similar and change it to:
      *     > /**
@@ -1799,7 +1799,7 @@
      *     >  ex port function validatePipeline(promptbook: really_unknown): asserts promptbook is PipelineJson {
      */
     /**
-     * TODO: [🧳][main] !!!! Validate that all samples match expectations
+     * TODO: [🧳][main] !!!! Validate that all examples match expectations
      * TODO: [🧳][🐝][main] !!!! Validate that knowledge is valid (non-void)
      * TODO: [🧳][main] !!!! Validate that persona can be used only with CHAT variant
      * TODO: [🧳][main] !!!! Validate that parameter with reserved name not used RESERVED_PARAMETER_NAMES
@@ -2169,12 +2169,12 @@
         return true;
     }
     /**
-     * TODO: [🔃][main] !!!!! If the pipeline was prepared with different version or different set of models, prepare it once again
+     * TODO: [🔃][main] !! If the pipeline was prepared with different version or different set of models, prepare it once again
      * TODO: [🐠] Maybe base this on `makeValidator`
      * TODO: [🧊] Pipeline can be partially prepared, this should return true ONLY if fully prepared
      * TODO: [🧿] Maybe do same process with same granularity and subfinctions as `preparePipeline`
      *     - [🏍] ? Is context in each template
-     *     - [♨] Are samples prepared
+     *     - [♨] Are examples prepared
      *     - [♨] Are templates prepared
      */
 
@@ -3918,7 +3918,7 @@
             var preparedPipeline, template;
             return __generator(this, function (_a) {
                 preparedPipeline = options.preparedPipeline, template = options.template;
-                // TODO: [♨] Implement Better - use real index and keyword search from `template` and {samples}
+                // TODO: [♨] Implement Better - use real index and keyword search from `template` and {examples}
                 TODO_USE(template);
                 return [2 /*return*/, preparedPipeline.knowledgePieces.map(function (_a) {
                         var content = _a.content;
@@ -3933,7 +3933,7 @@
      *
      * @private internal utility of `createPipelineExecutor`
      */
-    function getSamplesForTemplate(template) {
+    function getExamplesForTemplate(template) {
         return __awaiter(this, void 0, void 0, function () {
             return __generator(this, function (_a) {
                 // TODO: [♨] Implement Better - use real index and keyword search
@@ -3950,7 +3950,7 @@
      */
     function getReservedParametersForTemplate(options) {
         return __awaiter(this, void 0, void 0, function () {
-            var preparedPipeline, template, pipelineIdentification, context, knowledge, samples, currentDate, modelName, reservedParameters, _loop_1, RESERVED_PARAMETER_NAMES_1, RESERVED_PARAMETER_NAMES_1_1, parameterName;
+            var preparedPipeline, template, pipelineIdentification, context, knowledge, examples, currentDate, modelName, reservedParameters, _loop_1, RESERVED_PARAMETER_NAMES_1, RESERVED_PARAMETER_NAMES_1_1, parameterName;
             var e_1, _a;
             return __generator(this, function (_b) {
                 switch (_b.label) {
@@ -3962,16 +3962,16 @@
                         return [4 /*yield*/, getKnowledgeForTemplate({ preparedPipeline: preparedPipeline, template: template })];
                     case 2:
                         knowledge = _b.sent();
-                        return [4 /*yield*/, getSamplesForTemplate(template)];
+                        return [4 /*yield*/, getExamplesForTemplate(template)];
                     case 3:
-                        samples = _b.sent();
+                        examples = _b.sent();
                         currentDate = new Date().toISOString();
                         modelName = RESERVED_PARAMETER_MISSING_VALUE;
                         reservedParameters = {
                             content: RESERVED_PARAMETER_RESTRICTED,
                             context: context,
                             knowledge: knowledge,
-                            samples: samples,
+                            examples: examples,
                             currentDate: currentDate,
                             modelName: modelName,
                         };
@@ -4589,7 +4589,7 @@
         });
     }
     /**
-     * TODO: [🔃][main] !!!!! If the persona was prepared with different version or different set of models, prepare it once again
+     * TODO: [🔃][main] !! If the persona was prepared with different version or different set of models, prepare it once again
      * TODO: [🏢] !! Check validity of `modelName` in pipeline
      * TODO: [🏢] !! Check validity of `systemMessage` in pipeline
      * TODO: [🏢] !! Check validity of `temperature` in pipeline
@@ -5340,7 +5340,7 @@
                     case 0:
                         _a = options.maxParallelCount, maxParallelCount = _a === void 0 ? DEFAULT_MAX_PARALLEL_COUNT : _a;
                         templates = pipeline.templates, parameters = pipeline.parameters, knowledgePiecesCount = pipeline.knowledgePiecesCount;
-                        // TODO: [main] !!!!! Apply samples to each template (if missing and is for the template defined)
+                        // TODO: [main] !! Apply examples to each template (if missing and is for the template defined)
                         TODO_USE(parameters);
                         templatesPrepared = new Array(templates.length);
                         return [4 /*yield*/, forEachAsync(templates, { maxParallelCount: maxParallelCount /* <- TODO: [🪂] When there are subtasks, this maximul limit can be broken */ }, function (template, index) { return __awaiter(_this, void 0, void 0, function () {
@@ -5370,7 +5370,7 @@
     /**
      * TODO: [🧠] Add context to each template (if missing)
      * TODO: [🧠] What is better name `prepareTemplate` or `prepareTemplateAndParameters`
-     * TODO: [♨][main] !!! Prepare index the samples and maybe templates
+     * TODO: [♨][main] !!! Prepare index the examples and maybe templates
      * TODO: Write tests for `preparePipeline`
      * TODO: [🏏] Leverage the batch API and build queues @see https://platform.openai.com/docs/guides/batch
      * TODO: [🧊] In future one preparation can take data from previous preparation and save tokens and time
@@ -5579,7 +5579,7 @@
         'SIMPLE_TEMPLATE',
         'SCRIPT_TEMPLATE',
         'DIALOG_TEMPLATE',
-        'SAMPLE',
+        'EXAMPLE',
         'KNOWLEDGE',
         'INSTRUMENT',
         'ACTION',
@@ -5638,7 +5638,7 @@
             'SCRIPT',
             'DIALOG',
             // <- [🅱]
-            'SAMPLE',
+            'EXAMPLE',
             'KNOWLEDGE',
             'INSTRUMENT',
             'ACTION',
@@ -5671,7 +5671,7 @@
          */
         parse: function (input) {
             var normalized = input.normalized;
-            normalized = normalized.split('EXAMPLE').join('SAMPLE');
+            normalized = normalized.split('SAMPLE').join('EXAMPLE');
             var templateTypes = TemplateTypes.filter(function (templateType) {
                 return normalized.includes(templateType.split('_TEMPLATE').join(''));
             });
@@ -5704,14 +5704,14 @@
             if ($templateJson.content === undefined) {
                 throw new UnexpectedError("Content is missing in the templateJson - probbably commands are applied in wrong order");
             }
-            if (command.templateType === 'SAMPLE') {
+            if (command.templateType === 'EXAMPLE') {
                 expectResultingParameterName();
                 var parameter = $pipelineJson.parameters.find(function (param) { return param.name === $templateJson.resultingParameterName; });
                 if (parameter === undefined) {
-                    throw new ParseError("Can not find parameter {".concat($templateJson.resultingParameterName, "} to assign sample value on it"));
+                    throw new ParseError("Can not find parameter {".concat($templateJson.resultingParameterName, "} to assign example value on it"));
                 }
-                parameter.sampleValues = parameter.sampleValues || [];
-                parameter.sampleValues.push($templateJson.content);
+                parameter.exampleValues = parameter.exampleValues || [];
+                parameter.exampleValues.push($templateJson.content);
                 $templateJson.isTemplate = false;
                 return;
             }
@@ -9774,7 +9774,7 @@
         return pipelineJsonStringified;
     }
     /**
-     * TODO: [🐝] Not Working propperly @see https://promptbook.studio/samples/mixed-knowledge.ptbk.md
+     * TODO: [🐝] Not Working propperly @see https://promptbook.studio/examples/mixed-knowledge.ptbk.md
      * TODO: [🧠][0] Maybe rename to `stringifyPipelineJson`, `stringifyIndexedJson`,...
      * TODO: [🧠] Maybe more elegant solution than replacing via regex
      * TODO: [🍙] Make some standard order of json properties