Update agents_design.md

module/move/assistant/design/agents_design.md

@@ -50,97 +50,44 @@ There are two builtin scenarios:
 
 Each node has an `id` property (its name) and a `type` property.
 
-`type` specifies node type in a special format - `category.type`. Number of levels separated by dots may vary.
+`type` specifies node type in a special format - `category::type`. Number of levels separated by dots may vary.
 
 ### Input nodes
 
 These nodes read an input from external environment and pass it to the graph.
 
 Current **types**:
 
-- `trigger.stdin`: stdin input node.
-- `trigger.file`: file input node.
-
-#### Stdin input node
-
-**Description**: retrieves input from user from the command line. A prompt can be supplied additionally.
-
-**Parameters**:
-
-- `prompt`: Text to show before the input, e.g.: `Query: `, `Your question: `, etc.
-
-#### File input node
-
-**Description**: reads file from the `path` parameters and passes to the next node.
-
-**Parameters**:
-
-- `path`: path to the file to read.
+- `trigger::stdin`: stdin input node.
+  Parameters: `prompt`.
+- `trigger::file`: file input node. 
+  Parameters `path`.
 
 ### Processing nodes
 
 Those nodes perform intermediate processing of information. It can be either a mechanical one using an external program, or a real LLM agent.
 
 - `script`: script node.
-- `agent.completion`: agent completion node.
-
-#### Script node
-
-**Description**: takes input from the node, runs the specified program, passes the input to the program's stdin, reads the programs output and passes it to the next node (this refs UNIX philosophy).
-
-**Paramters**:
-
-- `cmd`: command to execute with path to the executable and arguments.
-
-#### Agent completion node
-
-**Description**: the core node type, represents an LLM agent that transforms text in one from to another.
-
-**Parameters**:
-
-- `provider`: LLM provider e.g.: `openai`, `anthropic`, etc.
-- `model`: LLM model name, e.g.: `gpt-4o-mini`, `claude`, etc.
-- `system_message`: system message template.
-- `user_message`: user message template.
-- `agent_reuse`: reuse conversation history from other agent.
-
-`system_message` and `user_message` are templates. Variables available to those templates are **node names**.
+  Parameters: `cmd`.
+- `agent::completion`: agent completion node.
+  Parameters: `provider`, `model`, `system_message`, `user_message`, `agent_reuse`.
+  `system_message` and `user_message` are templates. Variables available to those templates are **node names**.
 
 ### Output nodes
 
 These nodes take an input from other node and present it to the external world.
 
 Current **types**:
 
-- `event.stdout`: stdout output node.
-- `event.file`: file output node.
-
-#### Stdout output node
-
-**Description**: prints the input to the console.
-
-**Parameters**:
-
-- `prefix`: print text before the output, e.g.: `Answer: `, etc.
-
-#### File output node
-
-**Description**: saves input to a file.
-
-**Parameters**:
-
-- `path`: path to save the input.
+- `event::stdout`: stdout output node.
+  Parameters: `output`.
+- `event::file`: file output node.
+  Parameters: `path`.
 
 ### Utility nodes
 
 These nodes are special nodes for various purposes.
 
 Current **types**:
 
-- `scenario.termination`: scenario termination node.
-
-#### Scenario termination node
-
-**Description**: when the process of execution is passed to this node, the whole program of the multi-agent system terminates.
-
-This node is **implicitly present in every graph**, and to call it you just need to fill `next:` with the `scenario.terminate`.
+- `scenario::termination`: scenario termination node.