[FEATURE] Map user input into action / path and input

[20001LastOrder]

Description

With the flow policy (#398), there will be two kinds of nodes require human input

1. For certain action nodes, a human input is necessary (e.g. read a file)
2. For certain decision nodes, the path will selected based on human input

For each of them, we want to enable the user to input in action nature language text and then map the text into action input or path/action selection.

Basic Design

[20001LastOrder]

@Bubbletea98

cc. @amirfz Could you take a look at the description and see if it makes sense?

[amirfz]

@20001LastOrder @Bubbletea98 mm I am not 100% sure we're on the same page, so to help the conversation I put together this sample conversation. please take a look and let's have a discussion; https://docs.google.com/document/d/1wLFFoJu_Fz5GPlwInOYM5yCWFvjnhIdVOii66Kq4oSY/edit

[20001LastOrder]

@amirfz I think in general this is what I'm thinking about it too. I left some minor comments.

[amirfz]

ok great. I'll take a look. I asked the blog group to create a few similar ones so that we can compare and contrast

…

On Fri, Jul 5, 2024, 16:33 Boqi (Percy) Chen ***@***.***> wrote: @amirfz <https://github.com/amirfz> I think in general this is what I'm thinking about it too. I left some minor comments. — Reply to this email directly, view it on GitHub <#399 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD4OK5P4FUOXYOAUOASHK5TZK37KJAVCNFSM6AAAAABKIGCDGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGM4DIMJSHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>