phowell
/
pocketflow
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix cases

This commit is contained in:
zachary62 2025-01-06 02:57:10 +00:00
parent 6bbdc6d532
commit 7b85c37b57
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -37,7 +37,7 @@ Mini LLM Flow is designed to be **the framework used by LLMs**. In the future, L
1. **👍 Good at Low-level Details:** LLMs can handle details like *wrappers, tools, and prompts*, which don't belong in a framework. Current frameworks are over-engineered, making them hard for humans (and LLMs) to maintain. 1. **👍 Good at Low-level Details:** LLMs can handle details like *wrappers, tools, and prompts*, which don't belong in a framework. Current frameworks are over-engineered, making them hard for humans (and LLMs) to maintain.
2. **👎 Bad at High-level Paradigms:** While paradigms like *MapReduce, task decomposition, and agents* are powerful, LLMs still struggle to design them elegantly. These high-level concepts should be emphasized in frameworks. 2. **👎 Bad at High-level Paradigms:** While paradigms like *MapReduce, Task Decomposition, and Agents* are powerful, LLMs still struggle to design them elegantly. These high-level concepts should be emphasized in frameworks.
The ideal framework for LLMs should (1) **strip away low-level implementation details**, and (2) **keep high-level programming paradigms**. Hence, we provide this minimal (100-line) framework that allows LLMs to focus on what matters. The ideal framework for LLMs should (1) **strip away low-level implementation details**, and (2) **keep high-level programming paradigms**. Hence, we provide this minimal (100-line) framework that allows LLMs to focus on what matters.

2
docs/node.md
View File

@ -16,7 +16,7 @@ A **Node** is the smallest building block of Mini LLM Flow. Each Node has 3 step
2. `exec(prep_res)` 2. `exec(prep_res)`
- The **main execution** step, with optional retries and error handling (below). - The **main execution** step, with optional retries and error handling (below).
- Examples: *primarily for LLMs, but can also for remote APIs*。 - Examples: *primarily for LLMs, but can also for remote APIs*.
- ⚠️ If retries enabled, ensure idempotent implementation. - ⚠️ If retries enabled, ensure idempotent implementation.
- Returns `exec_res`, which is passed to `post()`. - Returns `exec_res`, which is passed to `post()`.