Clarifying Core Component Cooperation #149
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains daily documentation updates based on the following suggestion:
Ensure readers are clear on the differences and usage of
Actions,Generators, andAgentsas the framework's foundation. Currently, the distinctions could be more vividly portrayed with examples and use cases where multiple of these components work in tandem.description of file changes: Revise
docs/concepts/index.mdto expand on how actions, generators, and agents cooperate:\n\n### How Components Cooperate\n\n1. Generators: Focused on data transformation by generating outputs without complex decision-making capabilities.\n\n2. Actions: Perform operations outside of data transformation: data retrieval, file writing, etc. Typical in conjunction with generators for data pre and post-processing.\n\n3. Agents: Autonomous units that execute tasks or monitor systems using generators and actions, triggered by conditions like file changes or time intervals.\n\n#### Example Showcase\nA task that involves an action extracting data, a generator transforming it, and an agent handling the execution based on triggers would clarify the workflow.